After home assistant has automatically updated my home assistant voice's firmware, Possibly broken. | Home Assistant | Page 1

wise zephyr Jun 9, 2025, 10:24 AM

#

After home assistant decided to update the firmware on my home assistant voice, it lost connection to home assistant. I have tried factory resetting the home assistant voice but it will not properly connect to home assistant anymore, and goes between the twinkling blue light ring and a solid white ring. I have gotten rather used to having this around and use it alot so not having it is quite disheartening, any help would be appreciated!

grand forge Jun 9, 2025, 10:28 AM

#

wise zephyr After home assistant decided to update the firmware on my home assistant voice, ...

try plugging the VPE to pc and and doing a manual reinstall of the firmware and wifi config by following these instructions which make use of this tool

wise zephyr Jun 9, 2025, 10:42 AM

#

grand forge try plugging the VPE to pc and and doing a manual reinstall of the firmware and ...

I attempted the instructions through this and the device is unable to connect to the serial port, as if it is not even picking up the device is connecting to my PC, I am on fedora 41 and have tried both firefox and brave browser, and still not getting the device to connect.

grand forge Jun 11, 2025, 4:47 PM

#

wise zephyr I attempted the instructions through this and the device is unable to connect to...

firefox is not compatable with serial port connection stuff. i dont know about brave.
I have only done it with chrome on windows tbh

wispy hedge Jun 11, 2025, 6:35 PM

#

grand forge firefox is not compatable with serial port connection stuff. i dont know about b...

Brave works fine. Using it for serial connections for almost a year.

brave dagger Jun 11, 2025, 7:29 PM

#

The same thing has happened to me today. Have tried reinstalling an earlier version of the firmware but no luck. Logs show the VPE connecting to the WiFi and then disconnecting a few seconds later and then just endlessly looping the same steps

brave dagger Jun 11, 2025, 9:39 PM

#

brave dagger The same thing has happened to me today. Have tried reinstalling an earlier vers...

Okay I have managed to resolve my issue. I had a look through my router logs and noticed it was my router that was constantly disconnecting the Voice Assistant. I resolved this by disabling Roaming Assistant on my router (ASUS RT-AX82U).

brazen jolt Jul 8, 2025, 2:10 AM

#

Hello,

I can't get my HAVPE working. It initially connected to my HA when I first got it but then HA did an f/w update. Now I can't factory reset, I don't get the white ring, it shows in ESPHome as "online" in HA but nothing works. What does seem to work is when I retrieve the logs from the device through the USB cable. I get back info but that's it.

Anyone have this same issue?

grand forge Jul 8, 2025, 2:26 AM

#

brazen jolt Hello, I can't get my HAVPE working. It initially connected to my HA when I fir...

what do you mean by shows as online in esphome? do you mean that you adopted (took control) of it into the builder tool?

#

if so, then what firmware modifications did you make?

brazen jolt Jul 8, 2025, 2:31 AM

#

The firmware was 2025.6.3, according to HA.

#

I just went to the "esphome.github.io/home-assistant-voice-pe" page & was able to install 25.5.2

#

I was able to get ESPHome to connect & add it again now, but I'm still having issues.

grand forge Jul 8, 2025, 2:33 AM

#

brazen jolt I was able to get ESPHome to connect & add it again now, but I'm still having is...

are you talking about the integration or the builder addon?

brazen jolt Jul 8, 2025, 2:35 AM

#

The 'integration' was able to add it under the 25.5.2..... ESPHome Builder shows it listed as well & is at this point:

INFO ESPHome 2025.6.3
INFO Reading configuration /config/esphome/hav-0a5b17.yaml...
INFO Generating C++ source...
INFO Updating https://github.com/espressif/esp-protocols.git@mdns-v1.8.2
INFO Compiling app...
Processing hav-0a5b17 (board: esp32-s3-devkitc-1; framework: espidf; platform: https://github.com/pioarduino/platform-espressif32/releases/download/53.03.13/platform-espressif32.zip)

Library Manager: Installing esphome/noise-c @ 0.1.6
INFO Installing esphome/noise-c @ 0.1.6
Unpacking [####################################] 100%
Library Manager: noise-c@0.1.6 has been installed!
INFO noise-c@0.1.6 has been installed!
Library Manager: Resolving dependencies...
INFO Resolving dependencies...
Library Manager: Installing esphome/libsodium @ 1.10018.4
INFO Installing esphome/libsodium @ 1.10018.4
Unpacking [####################################] 100%
Library Manager: libsodium@1.10018.4 has been installed!
INFO libsodium@1.10018.4 has been installed!
HARDWARE: ESP32S3 240MHz, 320KB RAM, 8MB Flash

framework-espidf @ 3.50302.0 (5.3.2)
tool-cmake @ 3.30.2
tool-esptoolpy @ 4.8.6
tool-mklittlefs @ 3.2.0
tool-ninja @ 1.7.1
tool-riscv32-esp-elf-gdb @ 14.2.0+20240403
tool-xtensa-esp-elf-gdb @ 14.2.0+20240403
toolchain-esp32ulp @ 2.35.0-20220830
toolchain-riscv32-esp @ 13.2.0+20240530
toolchain-xtensa-esp-elf @ 13.2.0+20240530
Reading CMake configuration...

grand forge Jul 8, 2025, 2:35 AM

#

are you trying to customise your firmware to change the code?

brazen jolt Jul 8, 2025, 2:38 AM

#

I've been trying to get it to work for a few days now, that I'm trying anything at this point.

Originally, it was loaded as a device. I used my phone to configure the WiFi info but couldn't get it to connect to the backend HA server (since they're on 2 different subnets). I've been able to fix that but lost the functionality of the HAVPE, with the exception of the serial connection.

grand forge Jul 8, 2025, 2:38 AM

#

please answer my question

brazen jolt Jul 8, 2025, 2:38 AM

#

Sorry, I was typing

#

What I've been trying to do since is get it totally back to square-one & start fresh.

grand forge Jul 8, 2025, 2:41 AM

#

if you are just wantomg to use the device then you should not be in the esphome builder tool at all. do not take control of the device in there. flash it back stock using the tool and stay out of the builder tool.

#

unless your writing/modifing firmware there is no need for you to even have the builder tool

brazen jolt Jul 8, 2025, 2:42 AM

#

How else do you edit the YAML file for it?

grand forge Jul 8, 2025, 2:42 AM

#

why do you want to do that?

brazen jolt Jul 8, 2025, 2:44 AM

#

One thing I read was that in order to get it to connect to the HA server over HTTPS, the YAML needed the 'ca.pem' info in the YAML. I also was going to set the IP info statically within the device.

#

mDNS also won't work across multiple routed subnets so I have that I'm trying to work around as well. Plus I don't use ".local" addresses (which a lot of the links try to utilize). I mean, I could setup my DNS server to use that, I guess.

grand forge Jul 8, 2025, 2:47 AM

#

brazen jolt One thing I read was that in order to get it to connect to the HA server over HT...

in general its recomended to use http locally. but if you have a cert set up correctly then in most cases it shouldn't to be added to the firmware.
also if you want to set a static ip then you are better off doing this on the dhcp server by setting a static assignment.

brazen jolt Jul 8, 2025, 2:48 AM

#

I've since created a DHCP reservation for it so that part is good. I have my own local CA I use for HTTPS & my HA server does use that. I don't like using HTTP, if I don't have to.

grand forge Jul 8, 2025, 2:48 AM

#

connections need to be able to be extablished back and forth from the device and the server. so you need to ensure your network supports this. using seperate subnets is not "officially supported"

brazen jolt Jul 8, 2025, 2:50 AM

#

I get that.

#

I have the blue pulsing lights again now. I just can't get it to respond to voice commands so I guess that's another thing I need to look into.

I've removed the ESPHome Builder add-on.

grand forge Jul 8, 2025, 2:52 AM

#

is it added in the integration? and have you got a voice pipeeline set up?

brazen jolt Jul 8, 2025, 2:53 AM

#

It's listed in the "ESPHome" integration & I did install Wyoming, Ollama

#

Wyoming has openWakeWord, Piper, Whisper, & somehow now I have Speech-to-Phrase.

grand forge Jul 8, 2025, 2:56 AM

#

ok so oww you dont need with the vpe. and STP you dont need either but if you have piper/whisper running lets see if you have a pipeline set up to use them and then make sure its assigned to the vpe

#

in settings-voice assistants you can see your set up assistants

brazen jolt Jul 8, 2025, 2:57 AM

#

I see "Assist" with one listed, yes.

grand forge Jul 8, 2025, 2:57 AM

#

press on it to open its settings (or you can make a new one also if you prefer)

brazen jolt Jul 8, 2025, 2:58 AM

#

Inside it I see "Conversation agent" set to "Home Assitant".

grand forge Jul 8, 2025, 2:58 AM

#

thats just the basic default agent not an llm

brazen jolt Jul 8, 2025, 2:58 AM

#

Under "Streaming wake work engine" it has 'openwakeword' & "ok nabu" listed.

grand forge Jul 8, 2025, 2:58 AM

#

but thats fine for now tbh, if we can get voice responses working then we can add llm adter

#

you dont need a streaming wake word

#

but its fine if its there

#

you have whisper and piper set up in the STT and TTS?

brazen jolt Jul 8, 2025, 3:00 AM

#

I just changed from STP in the STT to faster-whisper. TTS already has piper.

grand forge Jul 8, 2025, 3:00 AM

#

cool save that out

#

then go to the device page in the integration

brazen jolt Jul 8, 2025, 3:00 AM

#

I clicked "update".

grand forge Jul 8, 2025, 3:01 AM

#

yup

brazen jolt Jul 8, 2025, 3:01 AM

#

I'm in the device.

#

under "ESPHome"

grand forge Jul 8, 2025, 3:01 AM

#

in the vpe device page you can select the "assistant" which should be the pipeline we just set up

#

and the wake word selection

brazen jolt Jul 8, 2025, 3:02 AM

#

I see "Assist" with 1 disabled entity.

grand forge Jul 8, 2025, 3:03 AM

#

can you screenshot what you have?

brazen jolt Jul 8, 2025, 3:03 AM

#

Standby

#

This is the main page

grand forge Jul 8, 2025, 3:05 AM

#

ok, lots of stuff is disabled that i wouldnt expect to be disabled

#

on the esphome integration delete the device and readd it

brazen jolt Jul 8, 2025, 3:05 AM

#

Delete the device from ESPHome?

#

Delete from here?

grand forge Jul 8, 2025, 3:07 AM

#

yeah hit the 3 dots (upper) and delete device

brazen jolt Jul 8, 2025, 3:08 AM

#

Gone

grand forge Jul 8, 2025, 3:08 AM

#

then press add device and put its ip address in

brazen jolt Jul 8, 2025, 3:08 AM

#

Done

grand forge Jul 8, 2025, 3:08 AM

#

does the device page look any different now?

brazen jolt Jul 8, 2025, 3:08 AM

#

No

#

Same as before

grand forge Jul 8, 2025, 3:11 AM

#

i dont think i have ever seen "disabled by config entry" have you edited your configuration.yaml by any chance?

#

could also try restarting home assistant

brazen jolt Jul 8, 2025, 3:12 AM

#

I've added some stuff to my configuration.yaml file but nothing regarding this.... let me look again.

#

I have some lines in there for the HTTPS, like the SSL info for the files, plus 'use_x_forwarded_for: true' & 'trusted_proxies'

#

I do have Nginx installed

grand forge Jul 8, 2025, 3:15 AM

#

its probably not any of that, try restarting HA (maybe a hard reboot of entire system at this point tbh)

brazen jolt Jul 8, 2025, 3:15 AM

#

Standby

grand forge Jul 8, 2025, 3:15 AM

#

maybe in all of the back and forth something has gone wrong or something

brazen jolt Jul 8, 2025, 3:16 AM

#

Restarting the service now. Worse case, I can restart the VM.

#

I have red pulsing lights at the moment. It's been like that since I deleted & re-added.

#

HA's coming back up

#

Some services are still starting but it's back

grand forge Jul 8, 2025, 3:19 AM

#

any difference in the device page?

brazen jolt Jul 8, 2025, 3:20 AM

#

No.

But I am curious... the entities are showing the old device name & not the new one since the re-adding.

#

I wonder if that has anything to do with it.

grand forge Jul 8, 2025, 3:23 AM

#

it should probabl have the same internal name as its based on mac address usually

#

can try power cycling the vpe itself

brazen jolt Jul 8, 2025, 3:24 AM

#

Unplug & plug it back in?

grand forge Jul 8, 2025, 3:25 AM

#

yeah

brazen jolt Jul 8, 2025, 3:26 AM

#

Done

#

White ring..

#

Blue pulse

grand forge Jul 8, 2025, 3:27 AM

#

if you plug it into pc you can use the esphome web tool to connect and view the logs over usb

#

that might yield some info about what is happening

brazen jolt Jul 8, 2025, 3:30 AM

#

Checking.......

#

So far this is all I have:

[23:32:18]I (316) esp_image: segment 1: paddr=0019d6ec vaddr=3fca3d[I][logger:171]: Log initialized
[23:32:18][C][safe_mode:080]: There have been 1 suspected unsuccessful boot attempts
[23:32:18][D][esp32.preferences:142]: Writing 1 items: 0 cached, 1 written, 0 failed
[23:32:18][I][app:048]: Running through setup()
[23:32:18][C][i2c.idf:021]: Running setup
[23:32:18][I][i2c.idf:262]: Performing bus recovery
[23:32:18][D][esp-idf:000]: I (1223) gpio: GPIO[6]| InputEn: 1| OutputEn: 1| OpenDrain: 1| Pullup: 1| Pulldown: 0| Intr:0
[23:32:32][D[I][safe_mode:042]: Boot seems successful; resetting boot loop counter
[23:32:32][D][esp32.preferences:142]: Writing 1 items: 0 cached, 1 written, 0 failed

#

Well, now I have this showing up in my HA:

1 update

home_assistant_voice_0a5b17 Firmware
ESPHome 2025.6.3

grand forge Jul 8, 2025, 3:36 AM

#

ok its not on the stock firmware

#

it seems to be reverting

brazen jolt Jul 8, 2025, 3:36 AM

#

This is what the device shows in HA:

Home Assistant Voice PE
by Nabu Casa
Firmware: 25.6.0 (ESPHome 2025.6.2)

grand forge Jul 8, 2025, 3:37 AM

#

brazen jolt This is what the device shows in HA: Home Assistant Voice PE by Nabu Casa Firm...

this is right but above it mentions 2025.6.3

brazen jolt Jul 8, 2025, 3:37 AM

#

The settings show I have 1 update for it to go to 2025.6.3

grand forge Jul 8, 2025, 3:38 AM

#

this is going to sound strange but on the stock firmware flashing tool you should flash the firmware then once its flashed. you should flash it again straight away

Home Assistant Voice PE

Install firmware on Home Assistant Voice PE.

brazen jolt Jul 8, 2025, 3:39 AM

#

So flash it to what the site has & then upgrade it from HA to 2025.6.3?

grand forge Jul 8, 2025, 3:39 AM

#

i think its erroring and reverting to a random custom setup you had at some point during the issues. this will ensure its flashed and flashed a 2nd time to ensure stock firmware is in both slots

#

you should not see anything about updating it to 2025.6.3

#

the current stock firmware is based on 2025.6.2 the only way to update to 2025.6.3 would be to take control and recompile the firmware against esphome 2025.6.3

brazen jolt Jul 8, 2025, 3:40 AM

#

OK, so the site shows 25.6.0 so flash that twice?

grand forge Jul 8, 2025, 3:40 AM

#

yeah

brazen jolt Jul 8, 2025, 3:41 AM

#

Erasing

#

Installing

#

Done

grand forge Jul 8, 2025, 3:42 AM

#

i havent seen this error with the vpe but i have seen seen reports of other devices doing it

brazen jolt Jul 8, 2025, 3:42 AM

#

Erase User Data, connect to wifi, or just exit & do it again?

grand forge Jul 8, 2025, 3:43 AM

#

just exit and go again

#

then erease data and reconnect

#

during this you can delete it from the integration again

brazen jolt Jul 8, 2025, 3:44 AM

#

done

grand forge Jul 8, 2025, 3:44 AM

#

so once its hopefully set up "fresh" you can readd it

brazen jolt Jul 8, 2025, 3:44 AM

#

Configure the WiFi now?

grand forge Jul 8, 2025, 3:44 AM

#

yeah

#

then once its connected readd it in the integration and hopefully it will add with stuff available

brazen jolt Jul 8, 2025, 3:45 AM

#

re-adding

#

No change

grand forge Jul 8, 2025, 3:47 AM

#

reopen the device log and see if theres anything there of interest

brazen jolt Jul 8, 2025, 3:52 AM

#

No difference in the log file output.

I need to call it a night. It's almost midnight & I need to be up in 5hrs for work. I'll try again tomorrow after work.

#

Thanks for the help. At least it's looking normal right now. 😄

grand forge Jul 8, 2025, 3:53 AM

#

better than bricked 😛

brazen jolt Jul 8, 2025, 3:53 AM

#

For sure 😛

#

Thanks again. Have a good night.

grand forge Jul 8, 2025, 3:53 AM

#

gn

brazen jolt Jul 8, 2025, 2:46 PM

#

Morning,

Well, just an update but I now have some control after doing this:

Directly Edit Configuration Files (Advanced):
Warning: Editing these files directly can be risky. It's recommended to back up your configuration and Home Assistant instance before proceeding.

Locate the .storage directory in your Home Assistant configuration directory.
Find the following files:
core.config_entries
core.device_registry
core.entity_registry

Open these files in a text editor and search for the device or entity you are trying to enable.

Look for the "disabled_by" attribute and change it to null or "" (depending on the context) to re-enable the device or entity.

Save the changes and restart Home Assistant.

brazen jolt Jul 8, 2025, 3:26 PM

#

I've now gotten it to respond, but no playback after asking it anything. It just flashes blue on both sides of the dial.

That's progress, I think 😄

grand forge Jul 8, 2025, 5:50 PM

#

brazen jolt I've now gotten it to respond, but no playback after asking it anything. It just...

what does the device log look like now, when you try and use it?

brazen jolt Jul 8, 2025, 6:14 PM

#

There's quite a bit of info so not sure what you're looking for but there's WiFi info, Logger, i2c, etc.

grand forge Jul 8, 2025, 6:15 PM

#

what happens when you call the wake word and you say its not working?

brazen jolt Jul 8, 2025, 6:23 PM

#

I can say the wake word now & it looks like it's listening, along with the sound, but when it goes to respond, it just flashes those 2 LEDs & no sound.

#

So the wake word & the listening "bell" happens, but then after asking it for anything, it just flashes for a bit & no response.

#

Then it just go back to no lights.

grand forge Jul 8, 2025, 9:10 PM

#

on the voice assistants settings menu on the assistant hit the 3 dots and go to debug. this shows you the trace of a pipeline call

#

something like this

brazen jolt Jul 8, 2025, 9:24 PM

#

Checking........

#

This is what the last one looked like after making some changes.... but it still doesn't say anything:

grand forge Jul 8, 2025, 9:32 PM

#

if you press play audio at the bottom does it play the tts output on your browser?

brazen jolt Jul 8, 2025, 9:33 PM

#

Error
Error playing audio

grand forge Jul 8, 2025, 9:34 PM

#

ok so it might be having an issue with the url it generates for the audio file to be played

#

in settings system network then the home assistant url section see if there are any issues. with your fancy setup you can have to manually set a url

#

is uses that url as the base for when its constructing the url to send to the device to say "play this file"

brazen jolt Jul 8, 2025, 9:37 PM

#

#

Both domains are the same

grand forge Jul 8, 2025, 9:44 PM

#

is network set up so that the vpe from its subnet is allowed to establish a connection to it?
the logs during a call may indicate what its actually doing as it steps through the pipeline

brazen jolt Jul 8, 2025, 9:45 PM

#

The subnets can ping back/forth & my PC is on the same network as the HAVPE & I'm logged into HA from my PC.

grand forge Jul 8, 2025, 9:46 PM

#

ok

#

use web tool to watch device log live and then make a call to it and then show the log of what it does

brazen jolt Jul 8, 2025, 9:49 PM

#

I'd have to see if maybe there's a port being blocked by the FW but there shouldn't be between the 2 subnets.

OK... I'll try that in a a bit. I've got to take care of something.......

brazen jolt Jul 8, 2025, 11:10 PM

#

OK. I see a problem. It appears to be something with the cert.

📎 message.txt

grand forge Jul 9, 2025, 12:01 AM

#

ok right, now we are at a known state at least. getting certs to work is a bit of a pain as its not really supported.

what were you trying to do when you were looking at customising the firmware before? were you following a guide somewhere or something?

brazen jolt Jul 9, 2025, 12:08 AM

#

I was trying to get it to use the 'ca.pem' file so that there wouldn't be a certificate issue. I wasn't really following a guide, just going through as many search sites that might have suggestions & cross-referencing them with the use of A.I. searches.

#

My thing is, I'm trying to make sure all communications are through HTTPS as I don't want any unencrypted traffic, even over my own network. That's why I don't use HTTP, FTP, TFTP & everything that requires terminal access is through a jump server.

Security at work translates to security at home 🙂

grand forge Jul 9, 2025, 12:20 AM

#

I am just reading through this issue here - https://github.com/esphome/home-assistant-voice-pe/issues/315

it seems like it would not be a simple modification to just "add the cert file"

GitHub

PE device has no TTS responses (server SSL) · Issue #315 · esphom...

Firmware: 25.1.0 (ESPHome 2024.12.2) My symptoms seem very similar to #238 but I noticed that was diagnosed as a lack of TLS1.3 support on the device and closed. I also don't get TTS responses ...

#

looks like there have been some various workarounds

brazen jolt Jul 9, 2025, 12:24 AM

#

I'm reading it now.

#

So apparently I'm not the only one trying it this way 🙂

grand forge Jul 9, 2025, 12:26 AM

#

so it looks like disabling tls 1.3 and having it revert to 1.2 is the sort of running theme

brazen jolt Jul 9, 2025, 12:27 AM

#

Well, TLSv1.2 is better than nothing.

grand forge Jul 9, 2025, 12:27 AM

#

yeah theres always people trying to get stuff working in non supported setups. you wont be alone

brazen jolt Jul 9, 2025, 12:28 AM

#

So how do I set this to use v1.2?

grand forge Jul 9, 2025, 12:28 AM

#

the example in the 2nd part of this comment - https://github.com/esphome/home-assistant-voice-pe/issues/315#issuecomment-2722101531
looks to be something to try. david is confident anyway

#

right so you will need the esphome builder tool

brazen jolt Jul 9, 2025, 12:30 AM

#

Great... and me not being a coder must learn how to do it LMAO

grand forge Jul 9, 2025, 12:30 AM

#

i can help you out or at least try anyway

brazen jolt Jul 9, 2025, 12:31 AM

#

Well, last time I tried it broke communication with the device where it wouldn't respond to voice commands. At least that's working, from what the logs show.

grand forge Jul 9, 2025, 12:31 AM

#

you at least now know how to return to this known working state

#

or semi working at least

brazen jolt Jul 9, 2025, 12:32 AM

#

OK, so I have ESPHome Builder installed... so now I'm trying to add the device.

grand forge Jul 9, 2025, 12:32 AM

#

from what i rememberr the issuee was when taking control the builder tool was unable to connect to flash the device

#

ok take control and follow the instructions and it will try and build and flash

#

lets see where and how it fails and fix 1 issue at a time

brazen jolt Jul 9, 2025, 12:33 AM

#

So, I should use the name of the device as the name for the new device in ESPHome Builder, right?

grand forge Jul 9, 2025, 12:35 AM

#

just take the defaults

brazen jolt Jul 9, 2025, 12:35 AM

#

When I click "New Device" in ESPHome Builder, it's asking for a name.

#

Then it asks whether I want to skip the installation setup or connect.

grand forge Jul 9, 2025, 12:36 AM

#

ok hit connect. and it will flash the new "basic custom" or at least try

brazen jolt Jul 9, 2025, 12:37 AM

#

Preparing Installation is spinning & there's a device listed, while this is still spinning.

grand forge Jul 9, 2025, 12:38 AM

#

can you screenshot?

#

easier for me to know exactly where you are at with pictures 😛

brazen jolt Jul 9, 2025, 12:38 AM

#

#

Still "preparing"

grand forge Jul 9, 2025, 12:39 AM

#

ok lets give it a minute

#

what hardware are you running on?

brazen jolt Jul 9, 2025, 12:39 AM

#

HA?

grand forge Jul 9, 2025, 12:39 AM

#

yeah

#

firmware compiling can take a while depending on hardware

brazen jolt Jul 9, 2025, 12:40 AM

#

Dell PowerEdge 1950iii in a VM within Proxmox.

Hardware will probably be changing soon though.

grand forge Jul 9, 2025, 12:41 AM

#

ok, it shouldnt be too bad

#

i am grabbing my spare vpe and gunna match the steps

brazen jolt Jul 9, 2025, 12:41 AM

#

BTW, still spinning

#

Interesting thing is, if I open the same window in another tab, the device is listed & shows as "offline" while it's still spinning on the other tab.

grand forge Jul 9, 2025, 12:43 AM

#

it should be popping up with something like this

#

#

which then builds firmware

brazen jolt Jul 9, 2025, 12:44 AM

#

It acts like the WebUI is just stuck. while the device on the other tab is accessible.

I don't think I have popups disabled but let me double-check that.

grand forge Jul 9, 2025, 12:44 AM

#

its not a popup, its just an element

#

its probably just stuck, refresh the page

#

you say its showing as offline in the esphome builder?

brazen jolt Jul 9, 2025, 12:45 AM

#

#

If I open ESPHome Builder in another tab, it just shows the device, like that one

grand forge Jul 9, 2025, 12:46 AM

#

ok close the tab thats broken

#

in the new tab, use the 3 dots and "clean build files"

brazen jolt Jul 9, 2025, 12:47 AM

#

Done

grand forge Jul 9, 2025, 12:47 AM

#

now try install on the 3 dot menu

brazen jolt Jul 9, 2025, 12:48 AM

#

Do I close that window first?

grand forge Jul 9, 2025, 12:48 AM

#

which window?

brazen jolt Jul 9, 2025, 12:48 AM

#

grand forge Jul 9, 2025, 12:48 AM

#

yeah

#

then in same menu you cleared build files try running install

#

if it asks how choose "wirelessly"

#

hopefully it will build the firmware. it will probably fail to install but the logs around the failure will help us

brazen jolt Jul 9, 2025, 12:49 AM

#

Processing.

grand forge Jul 9, 2025, 12:50 AM

#

the firmware building will take a few minutes

brazen jolt Jul 9, 2025, 12:50 AM

#

grand forge Jul 9, 2025, 12:51 AM

#

will proceed into this kind of thing

#

you might see some warnings. these shouldnt be an issue

brazen jolt Jul 9, 2025, 12:53 AM

#

I recall seeing that before. Not sure why this is slow for me, unless it's something to do with the WiFi being 2.4GHz. I didn't add it to the 5GHz radio. I wasn't sure it could connect.

grand forge Jul 9, 2025, 12:53 AM

#

the first build will take a while, but further builds wont have to recompile every file so should be quicker. unless we have to clean for some reason

#

is it "doing stuff"?

brazen jolt Jul 9, 2025, 12:55 AM

#

It's compiling 'core.cpp.o'

#

Now gpio.cpp.o

#

So yeah.

This was the YAML I tried using last time I tried this:

https://github.com/esphome/home-assistant-voice-pe/blob/dev/home-assistant-voice.yaml

LoL

GitHub

home-assistant-voice-pe/home-assistant-voice.yaml at dev · esphome...

Home Assistant Voice PE. Contribute to esphome/home-assistant-voice-pe development by creating an account on GitHub.

grand forge Jul 9, 2025, 12:56 AM

#

cool it will churn away

#

vpe has alot of components, it took nearly 10 minutes to build on my n150 system

#

right so that's the core config. we wont need to change anything in there so will just load it as an external module

brazen jolt Jul 9, 2025, 12:57 AM

#

I have an old Gigabyte AORUS Master x299x that I plan on migrating my Proxmox over to. It'll have 264GB of RAM. It'll have to wait until I can build my new system 🙂

#

It's building "components" now... safe_mode.cpp.o

grand forge Jul 9, 2025, 12:59 AM

#

i have a 256gb ram big boy server too for other stuff but ha/frigate is running on a n150 mini pc

brazen jolt Jul 9, 2025, 12:59 AM

#

I'll have to look at that.

#

It's building the wifi components now.

grand forge Jul 9, 2025, 1:01 AM

#

question: in your proxmox config is your vm set to use "host" cpu mode?

#

#

if not then you will see performence boost but switching to host. as it gets to use the host cpu's instruction set directly instead of through an emulation layer

brazen jolt Jul 9, 2025, 1:04 AM

#

Well, I thought it was but I guess not 😦

#

I need to make a change after this.

#

It's in the 'bootloader_support' now.

#

'console' now.

grand forge Jul 9, 2025, 1:06 AM

#

the fact you can see each one is concerning. it should be zooming through stuff

#

also you need to give the poor vm some cores.

#

2 is the recommended absolutle min

#

i would recomend 4

brazen jolt Jul 9, 2025, 1:08 AM

#

This is the server stats right now as this is building:

grand forge Jul 9, 2025, 1:08 AM

#

i think you are better off stopping the build. changing the vm settings to host cpu and to 4 cores

brazen jolt Jul 9, 2025, 1:08 AM

#

Let me try that

grand forge Jul 9, 2025, 1:08 AM

#

then booting back in and building

#

with your vm config it could take hours/days

brazen jolt Jul 9, 2025, 1:10 AM

#

brb... while that reboots.

grand forge Jul 9, 2025, 1:14 AM

#

given you interupted it you might want to clean the build files before starting again. it shouldnt matter but better to be safe

brazen jolt Jul 9, 2025, 1:15 AM

#

OK.

grand forge Jul 9, 2025, 1:17 AM

#

hopefully it will start "zooming" a bit more this time 🙂

brazen jolt Jul 9, 2025, 1:18 AM

#

I'm learning how to adjust VMs to maximize their abilities.

grand forge Jul 9, 2025, 1:20 AM

#

does your network have a specific domain that it uses?
you mentioned above that stuff doesn't resolve on your network with .local i think but is there something you do use?

brazen jolt Jul 9, 2025, 1:20 AM

#

OK, clean first then build again.

#

Yeah, I don't use .local on my network, although I could easily set it up in my DNS server.

grand forge Jul 9, 2025, 1:21 AM

#

adding .local to resolve on dns is a possible solution but maybe we can make it work correctly with your network

brazen jolt Jul 9, 2025, 1:22 AM

#

It's started again.

grand forge Jul 9, 2025, 1:22 AM

#

cool, hopefully will get rolling. i am just trying to get some info for the next step

brazen jolt Jul 9, 2025, 1:23 AM

#

'Updating'

grand forge Jul 9, 2025, 1:25 AM

#

is there a domain that you do use?

brazen jolt Jul 9, 2025, 1:26 AM

#

I have a personal domain that I utilize within my home, currently. I've been playing around with migrating my domain into my home network.

grand forge Jul 9, 2025, 1:27 AM

#

so should: devicename.your-domain.tld resolve?

brazen jolt Jul 9, 2025, 1:28 AM

#

If I do a dig or nslookup on my domain, it resolves to my public IP, currently.

grand forge Jul 9, 2025, 1:28 AM

#

stuff is set to connect to devicename.local by default which we know doesnt work. i am just trying to figure out what does resolve

brazen jolt Jul 9, 2025, 1:29 AM

#

This build looks different.... it's not reading CMake configs.

grand forge Jul 9, 2025, 1:29 AM

#

brazen jolt This build looks different.... it's not reading CMake configs.

can you screenshot?

brazen jolt Jul 9, 2025, 1:29 AM

#

I can rapidly create a ".local" domain in my DNS server.

#

#

Now it's compiling

grand forge Jul 9, 2025, 1:30 AM

#

yeah was just grabbing the components after the clean

grand forge Jul 9, 2025, 1:31 AM

#

brazen jolt I can rapidly create a ".local" domain in my DNS server.

i get that but its possible that 1 line can make it work with your network which might be easier

#

i am just trying to understand how your network works a little bit. otherwise i cannot guide you

#

i dont need to know the domain itself. just how things work

brazen jolt Jul 9, 2025, 1:33 AM

#

If I do a homeassistant.mydomain.net, it resolves to my internal subnet for my VMs.

grand forge Jul 9, 2025, 1:34 AM

#

gotcha. so VPE-devicename.mydomain.net also resolves?

brazen jolt Jul 9, 2025, 1:34 AM

#

That's because of the Nginx reverse proxy & my FW DNS settings for internal DNS queries.

#

I didn't create a DNS record for the device name in the nameserver, but it should resolve.

#

I'll have to try it.

#

Do I need to create a host record for the device?

grand forge Jul 9, 2025, 1:37 AM

#

i dont know

brazen jolt Jul 9, 2025, 1:37 AM

#

Oh 🙂

grand forge Jul 9, 2025, 1:37 AM

#

i dont know your entire network config

#

i am just trying to work out what domain you need to type in for a connection

#

can try and ping it

brazen jolt Jul 9, 2025, 1:39 AM

#

Well, currently I can't after doing this. I was able to before doing this.

#

But only by IP

grand forge Jul 9, 2025, 1:44 AM

#

maybe if we specify static ip it will just use that. i am not 100% sure how esphome tools resolve

#

in any case lets see how things go with once its compiled

brazen jolt Jul 9, 2025, 1:45 AM

#

grand forge Jul 9, 2025, 1:45 AM

#

how quickly is it moving?

brazen jolt Jul 9, 2025, 1:45 AM

#

A little faster but I can still read what's going on.

#

It's at 'src/main.cpp.o'

grand forge Jul 9, 2025, 1:47 AM

#

i have no idea on the order of stuff tbh

#

its just gotta churn through it

brazen jolt Jul 9, 2025, 1:48 AM

#

It is moving a little faster.

grand forge Jul 9, 2025, 1:48 AM

#

some files will compile quicker than others just due to size etc...

brazen jolt Jul 9, 2025, 1:54 AM

#

It's still going but at a decent clip.

grand forge Jul 9, 2025, 1:55 AM

#

so my plan for the steps are:
see if it succeeds to flash after building.
if its not able to flash then look at the error and make minimal changes to get it so it can flash.
then we can add the modifications for the tls changes

#

then build it with the changes and flash it and hopefully it will work

brazen jolt Jul 9, 2025, 1:56 AM

#

Well, so far no warnings so that's good.

grand forge Jul 9, 2025, 1:59 AM

#

some components have some warnings i think but should be anything to be concerned about if you see some stuff

brazen jolt Jul 9, 2025, 2:12 AM

#

This is a pretty big build

grand forge Jul 9, 2025, 2:13 AM

#

its got a lot of components and the first build has to build all of esphome core too

brazen jolt Jul 9, 2025, 2:14 AM

#

Ahhh, that explains it

grand forge Jul 9, 2025, 2:15 AM

#

with a newer system it would build a bit quicker too but theres still a lot to build

brazen jolt Jul 9, 2025, 2:23 AM

#

It just created the esp32s3 image.

#

RAM: [= ] 10.7% (used 35036 bytes from 327680 bytes)
Flash: [===== ] 49.3% (used 904324 bytes from 1835008 bytes)
Building .pioenvs/first-floor-iot-hav-0a5b17/firmware.bin
Creating esp32s3 image...
Successfully created esp32s3 image.
esp32_create_combined_bin([".pioenvs/first-floor-iot-hav-0a5b17/firmware.bin"], [".pioenvs/first-floor-iot-hav-0a5b17/firmware.elf"])
SHA digest in image updated
Wrote 0xecdf0 bytes to file /data/build/first-floor-iot-hav-0a5b17/.pioenvs/first-floor-iot-hav-0a5b17/firmware.factory.bin, ready to flash to offset 0x0
esp32_copy_ota_bin([".pioenvs/first-floor-iot-hav-0a5b17/firmware.bin"], [".pioenvs/first-floor-iot-hav-0a5b17/firmware.elf"])
======================== [SUCCESS] Took 3797.00 seconds ========================

#

INFO Successfully compiled program.
INFO Resolving IP address of first-floor-iot-hav-0a5b17.local in mDNS
INFO Resolving IP address of first-floor-iot-hav-0a5b17.local
ERROR Error resolving IP address of first-floor-iot-hav-0a5b17.local. Is it connected to WiFi?
ERROR (If this error persists, please set a static IP address: https://esphome.io/components/wifi.html#manual-ips)
ERROR Error resolving IP address: Error resolving address with mDNS: Did not respond. Maybe the device is offline., [Errno -5] No address associated with hostname

ESPHome

WiFi Component

Instructions for setting up the WiFi configuration for your ESP node in ESPHome.

grand forge Jul 9, 2025, 2:28 AM

#

ok bingo, so it built but didnt flash. we kinda expected this

#

close the build box and press edit next to the device

#

this will open the yaml

brazen jolt Jul 9, 2025, 2:29 AM

#

Yep

grand forge Jul 9, 2025, 2:29 AM

#

show me what you have

brazen jolt Jul 9, 2025, 2:30 AM

#

esphome:
  name: first-floor-iot-hav-0a5b17
  friendly_name: first-floor-iot-hav-0a5b17

esp32:
  board: esp32-s3-devkitc-1
  framework:
    type: esp-idf

# Enable logging
logger:

# Enable Home Assistant API
api:
  encryption:
    key: "<KEY>"

ota:
  - platform: esphome
    password: "<PASSWD>"

wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_password

  # Enable fallback hotspot (captive portal) in case wifi connection fails
  ap:
    ssid: "First-Floor-Iot-Hav-0A5B17"
    password: "<pw>"

captive_portal:

grand forge Jul 9, 2025, 2:30 AM

#

put tripple back ticks around code

#

so it looks like this

#

3x ` at front and back

#

ok so we are gunna add a static ip to it

brazen jolt Jul 9, 2025, 2:31 AM

#

I put that in now.

grand forge Jul 9, 2025, 2:32 AM

#

  ssid: !secret wifi_ssid
  password: !secret wifi_password
  manual_ip:
    static_ip: x.x.x.x
    gateway: x.x.x.x
    subnet: 255.255.255.0
    dns1: x.x.x.x```

brazen jolt Jul 9, 2025, 2:32 AM

#

I've done that part before 😄 LoL

grand forge Jul 9, 2025, 2:32 AM

#

so wifi section should look like this

#

but with correct info obviously 😛

brazen jolt Jul 9, 2025, 2:32 AM

#

Yep, saved it with that info.

grand forge Jul 9, 2025, 2:33 AM

#

ok now after pressing save, press install

#

it may have to recompile a few network files but should take too long

brazen jolt Jul 9, 2025, 2:33 AM

#

Plug into this computer

grand forge Jul 9, 2025, 2:33 AM

#

no

#

wirelessly

#

note: this will need to be the ip it currently has in order for it to connect to it

brazen jolt Jul 9, 2025, 2:35 AM

#

I already reserved that IP in the DHCP server so it should have assigned it.

grand forge Jul 9, 2025, 2:35 AM

#

perrfect

#

was just checking to avoid any mishaps 🙂

brazen jolt Jul 9, 2025, 2:36 AM

#

INFO Successfully compiled program.
INFO Connecting to 192.168.50.243 port 3232...
ERROR Connecting to 192.168.50.243 port 3232 failed: [Errno 113] No route to host
ERROR Connection failed.

#

I should probably power-cycle the device.

#

I think I pushed it using the USB last time I tried this.

grand forge Jul 9, 2025, 2:37 AM

#

yeah power cycle the vpe then try installing again

brazen jolt Jul 9, 2025, 2:38 AM

#

retrying

grand forge Jul 9, 2025, 2:40 AM

#

flashing by usb has its uses but in this case we want to ensure networking works anyway otherwise it will be a pain in the future

brazen jolt Jul 9, 2025, 2:40 AM

#

========================= [SUCCESS] Took 40.82 seconds =========================
INFO Successfully compiled program.
INFO Connecting to 192.168.50.243 port 3232...
INFO Connected to 192.168.50.243
INFO Uploading /data/build/first-floor-iot-hav-0a5b17/.pioenvs/first-floor-iot-hav-0a5b17/firmware.bin (905008 bytes)
Uploading: [============================================================] 100% Done...

INFO Upload took 2.87 seconds, waiting for result...
INFO OTA successful
INFO Successfully uploaded program.
INFO Starting log output from 192.168.50.243 using esphome API
INFO Successfully resolved first-floor-iot-hav-0a5b17 @ 192.168.50.243 in 0.000s
WARNING Can't connect to ESPHome API for first-floor-iot-hav-0a5b17 @ 192.168.50.243: Error connecting to [AddrInfo(family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, proto=6, sockaddr=IPv4Sockaddr(address='192.168.50.243', port=6053))]: [Errno 111] Connect call failed ('192.168.50.243', 6053) (SocketAPIError)
INFO Trying to connect to first-floor-iot-hav-0a5b17 @ 192.168.50.243 in the background
INFO Successfully resolved first-floor-iot-hav-0a5b17 @ 192.168.50.243 in 0.000s
INFO Successfully connected to first-floor-iot-hav-0a5b17 @ 192.168.50.243 in 0.119s
INFO Successful handshake with first-floor-iot-hav-0a5b17 @ 192.168.50.243 in 0.118s
[22:39:31][I][app:137]: ESPHome version 2025.6.3 compiled on Jul  8 2025, 22:34:33

grand forge Jul 9, 2025, 2:40 AM

#

bingo, so you can now build and flash

brazen jolt Jul 9, 2025, 2:41 AM

#

[22:39:31][C][mdns:122]:   Hostname: first-floor-iot-hav-0a5b17
[22:40:24][I][safe_mode:042]: Boot seems successful; resetting boot loop counter
[22:40:24][D][esp32.preferences:142]: Writing 1 items: 0 cached, 1 written, 0 failed
[22:40:29][D][api:133]: Accepted 192.168.5.17
[22:40:29][W][api.connection:107]: : Socket operation failed: BAD_INDICATOR errno=11

grand forge Jul 9, 2025, 2:41 AM

#

it connected after that though i think

brazen jolt Jul 9, 2025, 2:41 AM

#

It just repeated the last 2 lines.

#

And "Stop" hasn't changed to "Close" on the window. If it's supposed to.

grand forge Jul 9, 2025, 2:42 AM

#

yeah its supposed to because it finished

brazen jolt Jul 9, 2025, 2:42 AM

#

So the api connection socket failure repeats.

grand forge Jul 9, 2025, 2:43 AM

#

you may need to remove and and readd thee device in the ha integration now

#

it may ask for the key from the yaml

brazen jolt Jul 9, 2025, 2:44 AM

#

So, "Stop", delete the device, & re-add?

grand forge Jul 9, 2025, 2:44 AM

#

this is on the home assistant integration

#

not in the builder

#

this sort of thing

#

the integration may be causes issues by trying to connect to it without the encryption key which it now has after the build

brazen jolt Jul 9, 2025, 2:46 AM

#

Click "Stop"?

grand forge Jul 9, 2025, 2:46 AM

#

where are you seeing stop?

#

i am not sure what you mean

#

screenshot it

brazen jolt Jul 9, 2025, 2:47 AM

#

grand forge Jul 9, 2025, 2:47 AM

#

yes

#

that just stops the log viewer which the build window turns into

brazen jolt Jul 9, 2025, 2:48 AM

#

OK, I got a message "Authentication expired for Home Assistant Voice 0a5b17".

grand forge Jul 9, 2025, 2:49 AM

#

press it and it will ask you for the key which is from the device yaml

brazen jolt Jul 9, 2025, 2:49 AM

#

Re-auth successful

grand forge Jul 9, 2025, 2:49 AM

#

bingo

#

right now we can make the mod

#

so back to the yaml

brazen jolt Jul 9, 2025, 2:50 AM

#

In ESPHome Device Builder or ESPHome Builder?

grand forge Jul 9, 2025, 2:50 AM

#

same place you made the static ip code change

#

we want to add a new section

#

esp32:
  board: esp32-s3-devkitc-1
  variant: esp32s3
  flash_size: 16MB
  framework:
    type: esp-idf
    version: recommended
    sdkconfig_options:
      CONFIG_ESP32S3_DEFAULT_CPU_FREQ_240: "y"
      CONFIG_ESP32S3_DATA_CACHE_64KB: "y"
      CONFIG_ESP32S3_DATA_CACHE_LINE_64B: "y"
      CONFIG_ESP32S3_INSTRUCTION_CACHE_32KB: "y"

      CONFIG_BT_ALLOCATION_FROM_SPIRAM_FIRST: "y"
      CONFIG_BT_BLE_DYNAMIC_ENV_MEMORY: "y"

      CONFIG_MBEDTLS_EXTERNAL_MEM_ALLOC: "y"

      # Overrides from default start here
      #
      # Disable TLS 1.3 completely
      CONFIG_MBEDTLS_SSL_PROTO_TLS1_3: "n"

      # Enable TLS 1.2 (required for WPA Supplicant and ESP-TLS)
      CONFIG_MBEDTLS_SSL_PROTO_TLS1_2: "y"

      # Set both minimum and maximum TLS versions to 1.2 (forces only TLS 1.2)
      CONFIG_MBEDTLS_SSL_MIN_MINOR_VERSION: "3"
      CONFIG_MBEDTLS_SSL_MAX_MINOR_VERSION: "3"

      # Disable TLS 1.3-specific extensions that may still be present in ClientHello
      CONFIG_MBEDTLS_SSL_TLS1_3_KEY_SHARE: "n"              # Prevents sending key_share extension (TLS 1.3 key exchange)
      CONFIG_MBEDTLS_SSL_TLS1_3_PSK_EXCHANGE: "n"           # Disables PSK key exchange modes for TLS 1.3

      # Remove TLS 1.3 compatibility and mixed-mode features
      CONFIG_MBEDTLS_SSL_TLS1_3_COMPATIBILITY_MODE: "n"     # Ensures no fallback to TLS 1.3 behavior
      CONFIG_MBEDTLS_SSL_TLS1_3_MIXED_MODE: "n"             # Prevents using TLS 1.3 alongside older versions

      # Fully disable additional TLS 1.3 features
      CONFIG_MBEDTLS_SSL_TLS1_3_EARLY_DATA: "n"             # Disables 0-RTT early data (TLS 1.3 optimization)
      CONFIG_MBEDTLS_SSL_TLS1_3_MIDDLEBOX_COMPAT: "n"       # Prevents middlebox compatibility mode (avoids sending unnecessary extensions)

brazen jolt Jul 9, 2025, 2:54 AM

#

The whole thing?

grand forge Jul 9, 2025, 2:54 AM

#

yeah add that entire section

brazen jolt Jul 9, 2025, 2:54 AM

#

saved

grand forge Jul 9, 2025, 2:55 AM

#

ok hit install - wirelessly

#

this will rebuild quite a few files because its changing stuff in core

#

it wont be everything though. so not as long as first build but will take a few mins

brazen jolt Jul 9, 2025, 2:56 AM

#

So this downgrades it from v1.3 to v1.2?

grand forge Jul 9, 2025, 2:56 AM

#

yes i think so

#

but hopefully 1.2 will work to authenticate the certificate

brazen jolt Jul 9, 2025, 2:57 AM

#

Yeah, I tried this the other day:

esp32:
  board: esp32-s3-devkitc-1
  cpu_frequency: 240MHz
  variant: esp32s3
  flash_size: 16MB
  framework:
    type: esp-idf
#    type: arduino
    version: recommended
    sdkconfig_options:
      CONFIG_ESP32S3_DATA_CACHE_64KB: "y"
      CONFIG_ESP32S3_DATA_CACHE_LINE_64B: "y"
      CONFIG_ESP32S3_INSTRUCTION_CACHE_32KB: "y"

      # Moves instructions and read only data from flash into PSRAM on boot.
      # Both enabled allows instructions to execute while a flash operation is in progress without needing to be placed in IRAM.
      # Considerably speeds up mWW at the cost of using more PSRAM.
      CONFIG_SPIRAM_RODATA: "y"
      CONFIG_SPIRAM_FETCH_INSTRUCTIONS: "y"

      CONFIG_BT_ALLOCATION_FROM_SPIRAM_FIRST: "y"
      CONFIG_BT_BLE_DYNAMIC_ENV_MEMORY: "y"

      CONFIG_MBEDTLS_EXTERNAL_MEM_ALLOC: "y"
      CONFIG_MBEDTLS_SSL_PROTO_TLS1_3: "y"  # TLS1.3 support isn't enabled by default in IDF 5.1.5

grand forge Jul 9, 2025, 2:58 AM

#

yeah looks like the same sort of idea

brazen jolt Jul 9, 2025, 3:03 AM

#

One of the other things I'd like to try to do is get this to use a custom wake word, without having to say "hey" or "ok". Just a single word, like "Nabu" or whatever else I want. Just like Amazon did with Alexa.

#

But that's for another time 🙂

grand forge Jul 9, 2025, 3:04 AM

#

custom wake words with microwakeword are not friendly to make currently

brazen jolt Jul 9, 2025, 3:06 AM

#

Is it easier with openWakeWord or just as difficult?

grand forge Jul 9, 2025, 3:07 AM

#

it is easier but converting the voice pe to support OWW is NOT easy or recomended. you end up loosing functionality

brazen jolt Jul 9, 2025, 3:07 AM

#

Ah

grand forge Jul 9, 2025, 3:07 AM

#

there are some examples but they are out of date now and not really been updated

brazen jolt Jul 9, 2025, 3:08 AM

#

Such is the world of OpenSource 🙂

grand forge Jul 9, 2025, 3:08 AM

#

with OWW the device has to constantly stream audio back to home assistant to process it. whereas microwakeword runs on the device itself

brazen jolt Jul 9, 2025, 3:08 AM

#

Wow! Now that's cool.

grand forge Jul 9, 2025, 3:09 AM

#

microwakeword is awesome and works super well but customising it is not really there yet

brazen jolt Jul 9, 2025, 3:09 AM

#

I'm still debating on whether to keep Ollama or not.

grand forge Jul 9, 2025, 3:09 AM

#

i use ollama to run my llm's

brazen jolt Jul 9, 2025, 3:10 AM

#

It seemed highly recommended so I installed it.

grand forge Jul 9, 2025, 3:10 AM

#

yeah, its pretty well supported

#

ai stuff is in heavy development currently within HA so keeping to something thats well supported is a good idea 🙂

brazen jolt Jul 9, 2025, 3:13 AM

#

Makes sense.

After I get this working right, my next thing is to fix my automation. I think my logic is off. It's a simple "lighting" automation (which seems to be where everyone starts out 😄 )

grand forge Jul 9, 2025, 3:13 AM

#

yup, light automations are a big thing

brazen jolt Jul 9, 2025, 3:14 AM

#

I say "simple" but it's based on sun elevation, weather, etc.

grand forge Jul 9, 2025, 3:14 AM

#

i do like walking around the house at night and lights come on/off following me around

brazen jolt Jul 9, 2025, 3:14 AM

#

I'm new to YAML (and to HA) so it's a learning curve, but I need the practice.

#

Trying to find the right bulbs & motion sensors has been rough. I want devices that remain local & aren't cloud based, but right now I have a mixture of both.

grand forge Jul 9, 2025, 3:16 AM

#

look at stuff that runs esphome 🙂 that way if you want you can customise it with your new found skills 🙂

brazen jolt Jul 9, 2025, 3:17 AM

#

grand forge look at stuff that runs esphome 🙂 that way if you want you can customise it wit...

And getting mDNS to traverse between subnets has been challenging.

Good point.

grand forge Jul 9, 2025, 3:19 AM

#

for motion I have stuff from everything smart home. the EP1 and EPL are great devices. apollo automation make some good stuff too but i have personally not used it.

#

hows the build going btw?

#

still churning away?

brazen jolt Jul 9, 2025, 3:19 AM

#

Still building.... it's at the HTTP server portion.

#

But moving pretty good.

#

Since you're experienced with this... is it possible to get this to communicate with a Mumble server?

grand forge Jul 9, 2025, 3:23 AM

#

the vpe? no

brazen jolt Jul 9, 2025, 3:24 AM

#

I'll have to see if there's a way to get the TTS or STT to work through a Mumble connection. I just wish I knew programming 😄

grand forge Jul 9, 2025, 3:24 AM

#

what exactly do you mean?

#

you want the output to also be tts'ed to mumble?

brazen jolt Jul 9, 2025, 3:26 AM

#

I have my own Mumble server setup. I thought it would be cool to be able to have this working sort of like a "bot", where if a person was speaking, or typing to it, it would trigger within the Mumble chat either by audio or text.

grand forge Jul 9, 2025, 3:28 AM

#

i havent seen anyone make a mumble integration for HA as of yet

brazen jolt Jul 9, 2025, 3:28 AM

#

This setup is a family setup so some of the family members who don't live in the house, could utilize it for when we're all in chat together.

brazen jolt Jul 9, 2025, 3:28 AM

#

grand forge i havent seen anyone make a mumble integration for HA as of yet

Yeah, I didn't think so.

grand forge Jul 9, 2025, 3:29 AM

#

i dont know anything about the mumble api. i used a mumble server briefly for something like 16 years ago. and have had no experience with it since

brazen jolt Jul 9, 2025, 3:30 AM

#

Most don't anymore. Most use Discord 😛

grand forge Jul 9, 2025, 3:30 AM

#

yeah discord has really taken over the space

brazen jolt Jul 9, 2025, 3:30 AM

#

But for a local chat program, it's nice.

#

Easily setup & all local.

grand forge Jul 9, 2025, 3:31 AM

#

i remember it being a complete pain to set up. the way certs worked for it back then was a mess.

#

i guess its probably easier now

brazen jolt Jul 9, 2025, 3:31 AM

#

IDK. I have mine using my RADIUS & MySQL.

grand forge Jul 9, 2025, 3:32 AM

#

if someone were inclined you could probably use OWW to add an assistant you could call

#

not sure on the practical uses

brazen jolt Jul 9, 2025, 3:33 AM

#

Interesting........ it would be a nuance thing, just for "home" use.

#

So many are more interested in 'cloud-based' anymore.

grand forge Jul 9, 2025, 3:35 AM

#

or you could build on top of the voip integration style. could summon it with a chat command. be able to back and forth then use another command to "hang up"

brazen jolt Jul 9, 2025, 3:35 AM

#

This thing is moving pretty good but sheesh it's a lot 😄

grand forge Jul 9, 2025, 3:36 AM

#

yeah building esphome stuff is a big part of why i moved my install from the home assistant yellow runniing a cm4 over to a vm on a n150 cpu

#

VPE is particually brutal as its huge

brazen jolt Jul 9, 2025, 3:36 AM

#

I will say, regarding the VPE, it's nice to see it has a physical switch to mute the mic.

grand forge Jul 9, 2025, 3:37 AM

#

yes its a physical cut off. that was a big part of the requirements for privacy reasons

brazen jolt Jul 9, 2025, 3:37 AM

#

Yeah, you can't trust that a push-button will actually shut off the mic.

grand forge Jul 9, 2025, 3:38 AM

#

its not a software controlled shut off. it physically disconnects the mic connection

grand forge Jul 9, 2025, 3:38 AM

#

brazen jolt Yeah, you can't trust that a push-button will actually shut off the mic.

yup

brazen jolt Jul 9, 2025, 3:39 AM

#

I loved it when people thought their phones weren't listening.... yet were in wonder when their phones showed them ads about things they were talking about with other people.

#

I keep waiting for Google to say, "God bless you" every time I sneeze. 😄

grand forge Jul 9, 2025, 3:41 AM

#

brazen jolt I loved it when people thought their phones weren't listening.... yet were in wo...

tbh this is mostly a misnomer. people and their friends have looked at things close to what they were talking about anyway

#

i am sure it has been done or at least expirimenteed with but there are more efficient ways of knowing what to advertise to someone than listening to them

brazen jolt Jul 9, 2025, 3:42 AM

#

IDK, I'd be talking with someone about a topic and be like, "You know, let me look that up" & immediately the search would have that exact thing I was curious about.

#

Maybe it's just that intuitive.

#

Seems fishy

grand forge Jul 9, 2025, 3:43 AM

#

"any sufficiently advanced technology is indistinguishable from magic"

brazen jolt Jul 9, 2025, 3:45 AM

#

This is currently building 'mbedtls'

#

It looks like it's generating the bootloader files now.

grand forge Jul 9, 2025, 3:47 AM

#

once it finishes you can just leave the log open in the browser and try asking it the time and see what it does 😛

brazen jolt Jul 9, 2025, 3:47 AM

#

If it's smart, it'll tell me to go to bed 😄

grand forge Jul 9, 2025, 3:48 AM

#

lol

brazen jolt Jul 9, 2025, 3:49 AM

#

Just finished building the esp32s3 image. It wasn't long after that last time.

grand forge Jul 9, 2025, 3:49 AM

#

nice

brazen jolt Jul 9, 2025, 3:51 AM

#

Out of curiosity, why does it rebuild the code every time you make a change to the YAML?

grand forge Jul 9, 2025, 3:52 AM

#

the yaml is basically compiler instructions

brazen jolt Jul 9, 2025, 3:52 AM

#

Looks like it might be done.

grand forge Jul 9, 2025, 3:53 AM

#

it changes the way the esphome software is built which then runs on the esp32

#

cool

brazen jolt Jul 9, 2025, 3:54 AM

#

No errors & it had no issue uploading due to the IP addition.

#

But should it respond when I say, "Ok, Nabu"?

grand forge Jul 9, 2025, 3:54 AM

#

should do

#

you might have to check the assistant is set in the integration

brazen jolt Jul 9, 2025, 3:56 AM

#

Wake word is greyed out in the Configuration.

#

So reboot?

grand forge Jul 9, 2025, 3:56 AM

#

might have to remove from integration and readd it again

brazen jolt Jul 9, 2025, 3:56 AM

#

grand forge Jul 9, 2025, 3:57 AM

#

its showing as unavailable

brazen jolt Jul 9, 2025, 4:02 AM

#

So now what?

grand forge Jul 9, 2025, 4:02 AM

#

remove it from the esphome integration again

#

then restart home assistant and the VPE then re-add it to the integration by ip

brazen jolt Jul 9, 2025, 4:05 AM

#

When I unplug & plug in the VPE, nothing happens. No LEDs, nothing.

#

Let me try again.

#

Nothing.

grand forge Jul 9, 2025, 4:06 AM

#

well thats not good

brazen jolt Jul 9, 2025, 4:07 AM

#

Waiting for HA

#

Added the device back

#

ESPHome Builder says "Online"

grand forge Jul 9, 2025, 4:09 AM

#

on the builder tool you can click "logs" and open its live log from there if its able to connect

brazen jolt Jul 9, 2025, 4:12 AM

#

INFO ESPHome 2025.6.3
INFO Reading configuration /config/esphome/first-floor-iot-hav-0a5b17.yaml...
INFO Starting log output from 192.168.50.243 using esphome API
INFO Successfully resolved first-floor-iot-hav-0a5b17 @ 192.168.50.243 in 0.000s
INFO Successfully connected to first-floor-iot-hav-0a5b17 @ 192.168.50.243 in 0.066s
INFO Successful handshake with first-floor-iot-hav-0a5b17 @ 192.168.50.243 in 0.070s
[00:10:17][C][wifi:613]: WiFi:
[00:10:17][C][wifi:434]:   Local MAC: 20:F8:3B:0A:5B:17
[00:10:17][C][wifi:439]:   SSID: [redacted]
[00:10:17][C][wifi:442]:   IP Address: 192.168.50.243
[00:10:17][C][wifi:446]:   BSSID: [redacted]
[00:10:17][C][wifi:446]:   Hostname: 'first-floor-iot-hav-0a5b17'
[00:10:17][C][wifi:455]:   Subnet: 255.255.255.0
[00:10:17][C][wifi:455]:   Gateway: 192.168.50.1
[00:10:17][C][wifi:455]:   DNS1: 192.168.5.11
[00:10:17][C][wifi:455]:   DNS2: 192.168.100.1
[00:10:17][C][logger:211]: Logger:
[00:10:17][C][logger:211]:   Max Level: DEBUG
[00:10:17][C][logger:211]:   Initial Level: DEBUG
[00:10:17][C][logger:217]:   Log Baud Rate: 115200
[00:10:17][C][logger:217]:   Hardware UART: USB_SERIAL_JTAG
[00:10:17][C][logger:224]:   Task Log Buffer Size: 768
[00:10:17][C][captive_portal:089]: Captive Portal:
[00:10:17][C][esphome.ota:073]: Over-The-Air updates:
[00:10:17][C][esphome.ota:073]:   Address: 192.168.50.243:3232
[00:10:17][C][esphome.ota:073]:   Version: 2
[00:10:17][C][esphome.ota:080]:   Password configured
[00:10:17][C][safe_mode:018]: Safe Mode:
[00:10:17][C][safe_mode:019]:   Boot considered successful after 60 seconds
[00:10:17][C][safe_mode:019]:   Invoke after 10 boot attempts
[00:10:17][C][safe_mode:019]:   Remain for 300 seconds
[00:10:17][C][api:182]: API Server:
[00:10:17][C][api:182]:   Address: 192.168.50.243:6053
[00:10:17][C][api:187]:   Using noise encryption: YES
[00:10:17][C][mdns:122]: mDNS:
[00:10:17][C][mdns:122]:   Hostname: first-floor-iot-hav-0a5b17

#

I need to call it a night..... it's after midnight.

grand forge Jul 9, 2025, 4:14 AM

#

fair enough

brazen jolt Jul 9, 2025, 4:14 AM

#

Thanks for the help. Not sure what to do next but that's for tomorrow 🙂

#

Have a good night.

brazen jolt Jul 9, 2025, 12:08 PM

#

Morning,

Just a FYI but this is all the device shows after last night:

grand forge Jul 9, 2025, 5:58 PM

#

brazen jolt Morning, Just a FYI but this is all the device shows after last night:

can you post the full yaml that you flashed?

brazen jolt Jul 9, 2025, 8:44 PM

#

esphome:
  name: first-floor-iot-hav-0a5b17
  friendly_name: first-floor-iot-hav-0a5b17

esp32:
  board: esp32-s3-devkitc-1
  variant: esp32s3
  flash_size: 16MB
  framework:
    type: esp-idf
    version: recommended
    sdkconfig_options:
      CONFIG_ESP32S3_DEFAULT_CPU_FREQ_240: "y"
      CONFIG_ESP32S3_DATA_CACHE_64KB: "y"
      CONFIG_ESP32S3_DATA_CACHE_LINE_64B: "y"
      CONFIG_ESP32S3_INSTRUCTION_CACHE_32KB: "y"

      CONFIG_BT_ALLOCATION_FROM_SPIRAM_FIRST: "y"
      CONFIG_BT_BLE_DYNAMIC_ENV_MEMORY: "y"

      CONFIG_MBEDTLS_EXTERNAL_MEM_ALLOC: "y"
      CONFIG_MBEDTLS_SSL_PROTO_TLS1_3: "n"

      CONFIG_MBEDTLS_SSL_PROTO_TLS1_2: "y"

      CONFIG_MBEDTLS_SSL_MIN_MINOR_VERSION: "3"
      CONFIG_MBEDTLS_SSL_MAX_MINOR_VERSION: "3"

      CONFIG_MBEDTLS_SSL_TLS1_3_KEY_SHARE: "n"
      CONFIG_MBEDTLS_SSL_TLS1_3_PSK_EXCHANGE: "n"

      CONFIG_MBEDTLS_SSL_TLS1_3_COMPATIBILITY_MODE: "n"
      CONFIG_MBEDTLS_SSL_TLS1_3_MIXED_MODE: "n"

      CONFIG_MBEDTLS_SSL_TLS1_3_EARLY_DATA: "n"
      CONFIG_MBEDTLS_SSL_TLS1_3_MIDDLEBOX_COMPAT: "n"

# Enable logging
logger:

# Enable Home Assistant API
api:
  encryption:
    key: "<KEY>"

ota:
  - platform: esphome
    password: "<PASSWD>"

wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_password
  manual_ip: 
    static_ip: 192.168.50.243
    gateway: 192.168.50.1
    subnet: 255.255.255.0
    dns1: 192.168.5.11
    dns2: 192.168.100.1

  # Enable fallback hotspot (captive portal) in case wifi connection fails
  ap:
    ssid: "First-Floor-Iot-Hav-0A5B17"
    password: "<PW>"

captive_portal:

grand forge Jul 9, 2025, 9:46 PM

#

brazen jolt ``` esphome: name: first-floor-iot-hav-0a5b17 friendly_name: first-floor-iot...

okay, its missing the package to import the code from the vpe repo

#

did you remove it?

#

1 moment ill rewrite some stuff

grand forge Jul 9, 2025, 9:52 PM

#

brazen jolt ``` esphome: name: first-floor-iot-hav-0a5b17 friendly_name: first-floor-iot...

📎 message.txt

#

replace XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX with the key from yours that you redacted

brazen jolt Jul 9, 2025, 10:00 PM

#

grand forge okay, its missing the package to import the code from the vpe repo

No. I didn't. What's there is what was there before adding in what you gave me.

grand forge Jul 9, 2025, 10:01 PM

#

ok, thats strange. in any case replace your yaml with the version i just posted except bring across your api encryption key

#

for some reason it must have defaulted to a basic esphome config instead of the voicepe factory starting point.

#

probably my fault that i missed it when you posted before

#

whatever the case we have found the issue

#

hopefully anyway

brazen jolt Jul 9, 2025, 10:05 PM

#

It's all good. Trying that now.

#

Not sure why it's complaining about this:

#

NVM... I see it

#

I had duplicate lines 🙂

grand forge Jul 9, 2025, 10:11 PM

#

other than the encryption key you should be replacing everything you had with what i sent

brazen jolt Jul 10, 2025, 12:01 AM

#

This thing is still grinding.

grand forge Jul 10, 2025, 12:05 AM

#

brazen jolt This thing is still grinding.

dam, need to consider changing out that hardware sooner rather than later

brazen jolt Jul 10, 2025, 12:28 AM

#

I'll be building my new system soon & this one will become the Proxmox server.

#

I'm getting a lot of these type warnings:

components/esp-tflite-micro/tensorflow/lite/micro/kernels/sub.cc:91:53:   required from here
components/esp-tflite-micro/tensorflow/lite/kernels/internal/reference/sub.h:308:62: warning: declaration of 'const tflite::ArithmeticParams& params' shadows a parameter [-Wshadow]
  308 |       [](T input1_val, T input2_val, const ArithmeticParams& params) {
      |                                      ~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~

grand forge Jul 10, 2025, 12:40 AM

#

yeah warnings are fine

brazen jolt Jul 10, 2025, 1:53 AM

#

Well, it finally reached the "Creating esp32s3 image", so hopefully it'll be done soon 😄

#

Well, it's done.

grand forge Jul 10, 2025, 2:01 AM

#

now we hope it works

brazen jolt Jul 10, 2025, 2:02 AM

#

Well, it recognized the wake word.... & understood what I asked.... but I got this:

📎 message.txt

#

Why would I see a bunch of "Enabling power supply." outputs, like these:

[22:01:12][D][power_supply:035]: Enabling power supply.
[22:01:12][D][power_supply:035]: Enabling power supply.
[22:01:12][D][power_supply:035]: Enabling power supply.
[22:01:13][D][power_supply:035]: Enabling power supply.
[22:01:13][D][voice_assistant:598]: Event Type: 4
[22:01:13][D][voice_assistant:636]: Speech recognised as: "what time is it"
[22:01:13][D][voice_assistant:598]: Event Type: 5
[22:01:13][D][voice_assistant:641]: Intent started
[22:01:13][D][power_supply:035]: Enabling power supply.
[22:01:13][D][power_supply:035]: Enabling power supply.
[22:01:14][D][power_supply:035]: Enabling power supply.
[22:01:14][D][power_supply:035]: Enabling power supply.
[22:01:14][D][power_supply:035]: Enabling power supply.

#

Is that because the lights are flashing or spinning?

grand forge Jul 10, 2025, 2:05 AM

#

power supply stuff is just verbose logging. i wouldnt worry about it

#

so looks like its still not able to verify the cert

brazen jolt Jul 10, 2025, 2:07 AM

#

At least everything is back:

grand forge Jul 10, 2025, 2:09 AM

#

yup thats because its now including the package with all the device specific config

brazen jolt Jul 10, 2025, 2:10 AM

#

I have the 'ca.pem' file directly in the /config/esphome folder, if that has any bearing on anything.

grand forge Jul 10, 2025, 2:10 AM

#

nope, i dont think there is any way to actually include the cert file where it will be used by this call

#

there are ways of adding it to a http request component but the media player does its own request and not through a seperate component

brazen jolt Jul 10, 2025, 2:15 AM

#

Is it this or could it have something to do with the pipeline config? I'm not sure where the "media player" is located, on the VPE or in HA itself.

grand forge Jul 10, 2025, 2:16 AM

#

media player is the esphome componenent that plays stuff

#

so this comment on the issue previously mentioned - https://github.com/esphome/home-assistant-voice-pe/issues/315#issuecomment-2973240267

seems to hint that they had to build the cert file in a particular way

#

something about chain order? most clients apprantly dont care but some do

#

you might have to adjust the cert file that you have on the HA server, does that make any sense to you?

brazen jolt Jul 10, 2025, 2:21 AM

#

I'm not sure. I guess I'd have to see what they mean.

I did see this in ChatGPT:

.

🔧 Option 2: Trust Custom Root CA (Advanced)
If you must use HTTPS (e.g., external or you require encryption):

Export your root CA cert (used to sign the HA server cert).

Embed it in the ESPHome config using:

yaml
Copy
Edit
ssl_ca_cert: |
  -----BEGIN CERTIFICATE-----
  ...
  -----END CERTIFICATE-----
Or, if you compile ESPHome outside HA, inject the root CA into the build.

🔧 Option 3: Update ESPHome / ESP-IDF
If you're on an older ESPHome or ESP-IDF version, upgrade it to ensure it includes the latest CA root bundle.

You can do this by updating ESPHome via the Home Assistant Add-on Store.

🔧 Option 4: Correct ESP Clock (if applicable)
If your device doesn’t have accurate time (especially on boot), TLS cert verification may fail.

Ensure an sntp time source is available (ESPHome does this by default with time:).

yaml
Copy
Edit
time:
  - platform: homeassistant
    id: home_time

#

Is "Option 2" even a thing? I mean, I can cat the 'ca.pem' file & insert the info as it's suggesting, if that's a thing.

grand forge Jul 10, 2025, 2:24 AM

#

I think its a hallucination

#

the only thing that i have seen that makes any sense is that comment i linked. and that the cert file you are using in HA is formatted in such a way that its accepted by most but not all clients (in this case the vpe)

brazen jolt Jul 10, 2025, 2:29 AM

#

I asked this 😄

Is "Option 2" an actual Home Assitant Voice PE syntax or is that just a guess?


ChatGPT said:
Great question — you're right to double-check that, because ESPHome syntax (used by HA Voice PE devices) doesn't directly support ssl_ca_cert or embedded CA certificates in YAML config like that out of the box.

So to clarify:

🔴 “Option 2” is not valid syntax in ESPHome YAML directly.
That part was a general concept from the ESP-IDF level, not something ESPHome currently exposes via YAML.

ESPHome does not provide a built-in way to specify a custom CA bundle via YAML (as of mid-2025).

The ESPHome voice_assistant and media_player components currently rely on the built-in CA store compiled into the firmware at build time.

This means ESPHome only trusts certificates in its bundled root CA list (typically derived from the ESP x509 bundle).

And this was a suggestion LOL:

✅ Valid Ways to Handle It in ESPHome / Voice PE
Here’s what’s actually supported and recommended:

✅ Use http:// Instead of https://
If you host HA locally, set your voice_assistant: component to use HTTP. This avoids TLS verification entirely.

Example:

yaml
Copy
Edit
voice_assistant:
  microphone: mic
  speaker: speaker
  media_player: speaker
  use_wake_word: true
  noise_suppression_level: 2
  auto_gain: 31
  tts:
    platform: home_assistant
    url: "http://homeassistant.local:8123"
This is real, valid syntax, and using http:// works reliably for local networks.

grand forge Jul 10, 2025, 2:32 AM

#

yeah i wouldnt trust chatgpt

#

its just wrong

brazen jolt Jul 10, 2025, 2:33 AM

#

I wonder if I need to be using the server's IP & not the loopback address in the ''configuration.yaml",

http:
  ssl_certificate: /ssl/ha_server.crt
  ssl_key: /ssl/ha_server.key
  use_x_forwarded_for: true
  trusted_proxies:
    - 127.0.0.1
    - ::1
    - 172.30.33.0/24

#

That's the reverse proxy settings, if I follow the doc

grand forge Jul 10, 2025, 2:40 AM

#

ok so in the documentation it says pem files should be used in the HA config

#

  ssl_certificate: /etc/letsencrypt/live/hass.example.com/fullchain.pem
  ssl_key: /etc/letsencrypt/live/hass.example.com/privkey.pem

#

this is an example using lets encrypt but the point stands

brazen jolt Jul 10, 2025, 2:41 AM

#

Which is what I have.

grand forge Jul 10, 2025, 2:42 AM

#

brazen jolt I wonder if I need to be using the server's IP & not the loopback address in the...

here you are showing you using .crt and .key files?

#

i dont know enough about certs to tell if there is a difference

brazen jolt Jul 10, 2025, 2:43 AM

#

The "http:" portion I shared is what I'm using already.

grand forge Jul 10, 2025, 2:44 AM

#

yes and i am suggesting why this could be an issue

#

#

these files are
.crt
and
.key
files

#

the documentation implies that they should be .pem files one of which is the fullchain.pem and the other is the privkey.pem

#

also the full chain apprantly can be built in different orders which has been known to cause the same error you are seeing

brazen jolt Jul 10, 2025, 2:49 AM

#

Yeah... I'm looking at that now. I have all 3 files on HA so I can create the "fullchain.pem" file from the 'ca.pem'.

I'm going to look at that now.

#

I created the 'fullchain.pem' file & I'm rebooting HA Now.

#

Yeah, no change:

[22:59:07][D][esp-idf:000][ann_read]: E (3574089) esp-x509-crt-bundle: Failed to verify certificate
[22:59:07][D][esp-idf:000][ann_read]: E (3574090) esp-tls-mbedtls: mbedtls_ssl_handshake returned -0x3000
[22:59:07][D][esp-idf:000][ann_read]: I (3574091) esp-tls-mbedtls: Failed to verify peer certificate!
[22:59:07][D][esp-idf:000][ann_read]: E (3574091) esp-tls: Failed to open new connection
[22:59:07][D][esp-idf:000][ann_read]: E (3574091) transport_base: Failed to open a new connection
[22:59:07][D][esp-idf:000][ann_read]: E (3574092) HTTP_CLIENT: Connection failed, sock < 0
[22:59:07][E][audio_reader:120][ann_read]: Failed to open URL
[22:59:07][E][speaker_media_player.pipeline:112]: Media reader encountered an error: ESP_ERR_HTTP_CONNECT
[22:59:07][E][speaker_media_player:326]: The announcement pipeline's file reader encountered an error.

grand forge Jul 10, 2025, 3:00 AM

#

hows does your HA configuration http section look now?

brazen jolt Jul 10, 2025, 3:05 AM

#

The 'configuration.yaml' http section:

# Enable HTTPS
http:
  ssl_certificate: /ssl/ha_fullchain.pem
  ssl_key: /ssl/ha_server.key
  use_x_forwarded_for: true
  trusted_proxies:
    - 127.0.0.1
    - ::1
    - 172.30.33.0/24

I'm running a 'openssl' check on the file.

#

I create the 'ha_fullchain.pem' file & it had both the CA & CRT info in it but there was a "fullchain.pem" file that just has the CRT info.

#

Now my HA is in recovery mode.

#

I'm restarting it again.

grand forge Jul 10, 2025, 3:12 AM

#

i am trying to work how a full chain works. and its not just a matter of the right stuff being there but it being there in the correct order

#

#

so its the "full chain" starting with the server then moving up

brazen jolt Jul 10, 2025, 3:14 AM

#

Mine is self-signed so I don't think there's any "intermediates".

#

It's just the server & my CA

#

I've got my HA working normal again.

grand forge Jul 10, 2025, 3:15 AM

#

what did you do? revert to what you had orginally?

brazen jolt Jul 10, 2025, 3:17 AM

#

I had a 'fullchain.pem' file (the original) & my 'ha_fullchain.pem' file (which has both the ca.pem & ha_server.crt combined). When I tried to use the original file, it went into recovery mode, so I put the 'ha_fullchain.pem' file back into that "http:" section.

#

So HA is normal again.

grand forge Jul 10, 2025, 3:19 AM

#

in the ha_fullchain.pem file that has both. what order are they in within the file?

#

the pem file needs not only both. but them to be in the correct order

#

so it should look like this

brazen jolt Jul 10, 2025, 3:26 AM

#

This is what I get from a check:

➜  /ssl openssl crl2pkcs7 -nocrl -certfile ha_fullchain.pem | openssl pkcs7 -print_certs -noout
subject=C=US, ST=State, L=City, O=SoHo, OU=Home, CN=homeassistant.domain.net 
issuer=C=US, ST=State, L=City, O=SoHo, OU=Home, CN=InternalCA 


subject=C=US, ST=State, L=City, O=SoHo, OU=Home, CN=InternalCA 
issuer=C=US, ST=State, L=City, O=SoHo, OU=Home, CN=InternalCA

grand forge Jul 10, 2025, 3:27 AM

#

look at the file yourself

#

you have the seperate cert files so you know what each one looks like

brazen jolt Jul 10, 2025, 3:28 AM

#

I did, & the contents are just like you posted.

grand forge Jul 10, 2025, 3:28 AM

#

ok

#

and the vpe logs are still showing the
mbedtls_ssl_handshake returned -0x3000
error?

brazen jolt Jul 10, 2025, 3:29 AM

#

[23:01:40][D][esp-idf:000][ann_read]: E (3727851) esp-x509-crt-bundle: Failed to verify certificate
[23:01:40][D][esp-idf:000][ann_read]: E (3727851) esp-tls-mbedtls: mbedtls_ssl_handshake returned -0x3000
[23:01:40][D][esp-idf:000][ann_read]: I (3727851) esp-tls-mbedtls: Failed to verify peer certificate!
[23:01:40][D][esp-idf:000][ann_read]: E (3727851) esp-tls: Failed to open new connection
[23:01:40][D][esp-idf:000][ann_read]: E (3727851) transport_base: Failed to open a new connection
[23:01:40][D][esp-idf:000][ann_read]: E (3727852) HTTP_CLIENT: Connection failed, sock < 0
[23:01:40][E][audio_reader:120][ann_read]: Failed to open URL
[23:01:40][E][speaker_media_player.pipeline:112]: Media reader encountered an error: ESP_ERR_HTTP_CONNECT
[23:01:40][E][speaker_media_player:326]: The announcement pipeline's file reader encountered an error.

#

I think once I can get it to verify the cert, it'll work.

#

I need to call it a night again, but I'll try again tomorrow 🙂

Thanks again. I'm sure this is annoying for you but the help is appreciated 🙂

#

Have a good night.

grand forge Jul 10, 2025, 3:33 AM

#

gotcha, when you come back i have something you can try

#

in the http section of home assistant config next to the certs add
ssl_profile: intermediate

#

it defaults to "modern" which has less backward compatibility. given we are trying to force 1.2 then this might be an issue

#

although we are reaching the end of the line a little bit here tbh... this is something that was never designed to work and it may just not work. others have gotten some stuff working but that was not with the added complication of the self signed cert

brazen jolt Jul 10, 2025, 11:49 PM

#

Greetings:

[19:48:58][D][esp-idf:000][ann_read]: E (46737471) esp-x509-crt-bundle: Failed to verify certificate
[19:48:58][D][esp-idf:000][ann_read]: E (46737472) esp-tls-mbedtls: mbedtls_ssl_handshake returned -0x3000
[19:48:58][D][esp-idf:000][ann_read]: I (46737472) esp-tls-mbedtls: Failed to verify peer certificate!
[19:48:58][D][esp-idf:000][ann_read]: E (46737472) esp-tls: Failed to open new connection
[19:48:58][D][esp-idf:000][ann_read]: E (46737472) transport_base: Failed to open a new connection
[19:48:58][D][esp-idf:000][ann_read]: E (46737473) HTTP_CLIENT: Connection failed, sock < 0
[19:48:58][E][audio_reader:120][ann_read]: Failed to open URL
[19:48:58][E][speaker_media_player.pipeline:112]: Media reader encountered an error: ESP_ERR_HTTP_CONNECT
[19:48:58][E][speaker_media_player:326]: The announcement pipeline's file reader encountered an error.

So, unfortunately that didn't work either.

grand forge Jul 10, 2025, 11:56 PM

#

dam, I am pretty much out of ideas at this point though. there may just not be a why of making it work correctly (at least at the moment).

brazen jolt Jul 11, 2025, 1:13 AM

#

It's looking like I'd be forced to revert to HTTP and abandon the HTTPS idea. 😦

#

I get that this is all behind my FW but there's still the WiFi that could potentially be sniffed.

#

Although I'm not surrounded by people who know how to do that sort of thing in this complex LMAO

grand forge Jul 11, 2025, 1:16 AM

#

yup, we gave it a good go but some things are just not an option

#After home assistant has automatically updated my home assistant voice's firmware, Possibly broken.