It should work right away. The URL is transferred via API
I changed it in the config file. Restarted HA (full restart)
In Settings --> System --> Network it complains:
Invalid local network URL
You have configured an HTTPS certificate in Home Assistant. This means that your internal URL needs to be set to a domain covered by the certificate.
All I changed was https to http on the internal_url but the domain:port on remained the same
But I proceed anyway - LOL
I have one unit that is set up for debugging. After everything above the URL still shows https. Is this because it’s looking at the external_url as opposed to the internal_url ?
Thank you again!
Well, I’m no help here - if your HA is locked to HTTPS, guess the URL should be HTTPS.
The property satellites remain though…
The big Q is does the API communicate the internl_URL or external_URL. If it’s the external - well then guess I’m barking up the wrong tree. 
Yup. I guess it’s time to visit HA Discord now. There’s plenty of bigger brains then mine.
1 Like
it works well… but I still have the satellite with ESP32-S3 in the bathroom that captures the wakeword first ((or rather… as I said both devices receive and understand the wakeword but the satellite listens first, blocking my Raspeaker) even though it is in another room when the house is very quiet and blocks the Respeaker (of course if I disconnect the satellite or speak in a low voice the Raspeeker takes over).I have to find a way to cover the microphone of that satellite. Maybe I also have to correct the satellite settings.
Currently on the satellite I have set:
auto_gain: 31dBFS
noise_suppression_level: 2
volume_multiplier: 4.0
I have already tried to change by lowering the values but for now no big change.
what I’m thinking is that the satellite being closer to the router has a better response time to the request
even if I actually find the satellite with S3 more comfortable because it takes up less space and can be inserted in some particular spaces because of the orientable microphone (as you can see in the photo in the ceiling). The Respeaker is fantastic… but I don’t know how much it can be worth even compared to the price (which between shipping and VAT comes to about 40 euros/dolars against the 7 euros/dolars of the S3)
As I mentioned, they both use ESP32-S3.
I don’t know what magical unicorns made your INMP441. I just know for sure that your satellite is exceptional. Or maybe it’s the geometry of your walls/ceiling, or something else… But my experience, and experience of thousands of others is telling completely different story.
Having problems with my satellite’s with the latest ESP update. They can’t update. I’ll hope the pictures are explaining? 
Thanks in advance.
Geez, it got updated like an hour ago!
Don’t use 2025.5 yet. PE also has troubles updating. With Respeaker, it will take some time.
Use 2025.4 so far.
Got mine (ESP32 to 2025.5) this morning. But won’t update. Somewhere a yaml fault…
Please read carefully.
You need ESPHome 2024.4 so far. It won’t work on ESPHome 2025.5.
Thanks. I’ll wait patiently 
1 Like
Fixed for Respeaker and Koala.
2 Likes
when are these updates valid? I mean: is it worth updating considering that you can have problems with your devices? Ok, you were good at updating quickly… but I don’t really know how much this risk is worth?
I also have an entity that was initially disabled on respeaker… the identity is: update_respeaker_firmware
Since yesterday it shows me an update…
better to keep it disabled? Better to update?
To be clear: no problems with devices. Don’t mix up add-on version and satellite firmware version. Problems were happening when you’re trying to reinstall firmware to the satellite. But devices are still fully operable.
By now, you can update your ESPHome add-on to 2025.5.0. Newest Respeaker/Koala firmware is built with 2025.5.0.
1 Like
may I add only those lines?
# 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"
version: 2025.5.0
min_version: 2025.5.0
without having to copy and rewrite everything?
No, there’s much more. External components, microphone, Microwakeword and Voice Assistant configuration.
Hi! Completely reinstalled ESPHome builder today and got error.
Trying to build project for Respeaker Lite 2.
There is no need now to use external components for mic, micro_wake_word and etc?
Maybe my M5 Atom Echo is also great… if placed close together (as in the photo) 95% of the time the atom echo is activated by the wakeword and the Respeaker receives the wakeword but: Error: duplicate_wake_up_detected - Duplicate wake-up detected for Okay Nabu.
It detects the double wake word but does not wake-up.
At this point I have a doubt that my unit has some problem if you all tell me that the Respeaker is much more reactive and faster.
Without other satellites or nearby it works without problems.
Well on direct comparison Respeaker will be slower, definitely. Because unlike raw audio on simple microphones, on Respeaker the voice gets processed by XMOS - so it doesn’t matter how fast it will happen, it’s added delay. And there’s no mechanism as of now to know the real distance from user to device - so first come first serve.