#esp32-s3-box-3 voice assistant setup failing

1 messages · Page 1 of 1 (latest)

echo bluff
#

I'm trying to set up an ESP32-S3-Box-3 as a Home Assistant voice satellite. It connects to the network, but when it gets to the part where it is supposed to set up the voice assistant, it fails. The error is "The voice assistant is unable to connect to Home Assistant". I have a flat network with no vlans or any kind of special configuration. I'm accessing home assistant over http. I'm running Home Assistant OS v 2025.7.4 on a PC. I'm not sure what steps to take to try to get past this.

pallid lion
#

settings - system - network
check thee "Home Assistant URL" section
see if there is any issues there

echo bluff
#

I've seen a lot of advice to turn the "automatic" switch on there (settings - system - network). I don't have an "automatic" switch. In the hostname section, I have "homeassistant" right now. I've tried "homeassistant", "homeassistant.local" and "<ip v 4 address of my HA server>" all without success. I've tried, but have been unable to enter something like "http://<ip v4 adress>:8123". Whenever I add ":8123" to any of my entries, I get "Invalid static hostname 'homeassistant.local:8123'"

pallid lion
#

the hostname section is not where you should be looking

#

its the "Home Assistant URL" section

echo bluff
#

Under settings - system - network, I see these sections: hostname, configure network interfaces, network adapter, and network discovery. Is "Home Assistant URL" under one of these?

pallid lion
#

you said your running HAOS right?

echo bluff
#

Yes. I'm running HAOS.

pallid lion
#

the home assistant URL section should be right in the middle. i dont know why it would be missing

#

you could try a full hardware restart of the server (not just restarting home assistant)

echo bluff
#

I did a full restart of the PC running Home Assistant. I opened a different browser to avoid cache issues. Unfortunately I still don't see the Home Assistant URL section. For what it's worth, I do have administrator rights and the advanced options tick mark is checked on.

#

Sounds like I'm in Here there be dragons space?

pallid lion
#

have you made any changes in your home assistants configuration.yaml ?

echo bluff
#

I made a few changes many months ago. None in at least 2 months now.

#

Wait. ... I did turn off my settings for using https connections as a way of trying to resolve this issue. I used to enable duckdns and lets' encrypt to allow https access to my Home Assistant. I turned that off because I saw some posts suggesting that the problem I am having could be because I only need http access. That's all that I have working now.

#

That change was maybe a week or two ago.

pallid lion
#

i am guessing there is something missing from when you made the https turning off change

echo bluff
#

The Home Assistant URL section under settings - system - network has not shown either before or after I made the https change. Until today, I did not know that I should be expecting to see the Home Assistant URL section on that page. I don't know why I don't see it, but I don't know that I have ever seen it. Certainly I haven't seen it since I've been trying to set up my voice assistant, so, for at least 3-4 months now. I am glad to know that I am missing something. Now I can try to find out why it's not showing. I do appreciate the insight.

pallid lion
echo bluff
#

Sure:

pallid lion
#

so i am guessing thate here:

#http:
#  ssl_certificate: /ssl/fullchain.pem
#  ssl_key: /ssl/privkey.pem
#  use_x_forwarded_for: true
#  trusted_proxies:
#    - 172.30.33.0/24
#http:
#  use_x_forwarded_for: true
#  trusted_proxies:
#    - 172.30.33.0/24
#  ip_ban_enabled: true
#  login_attempts_threshold: 4```

first is when you had https setup and 2nd is what you had prior to doing that. you could try bringing have the older section.
echo bluff
#

Actually, the 2nd (http:) section was the one I was using before I turned all of that off. the top section is older and hasn't been active for a long time. All of that aside, you're suggesting I re-enable the second section and re-enable https access?

pallid lion
# 
#http:
#  use_x_forwarded_for: true
#  trusted_proxies:
#    - 172.30.33.0/24
#  ip_ban_enabled: true
#  login_attempts_threshold: 4

re-enabling this doesnt itself enable https

echo bluff
#

Ok. I'm confused, then. (not necessarily a place I haven't been before).

#

So, you're suggesting re-enabling this section, then?

pallid lion
#

yes

#

not totally sure if it will help

#

but it shouldnt hurt

echo bluff
#

I'm not being unresponsive. I'm failing to re-enable the https access. I'll have to work on undoing the work I did to undo https access. It will take awhile. I do want to be certain to say "thank you" for your help. I know what I need to see, I just have to figure out how to see it.

pallid lion
#

use triple backticks around pasted stuff to avoid the formating problems

#

hope you can get it figured out

echo bluff
#

good advice. I'm not having formatting problems, but am having problems getting Lets's Encrypt to work.

#

You know the saying ... Never Give Up, Never Surrender. 😆

modern jewel
echo bluff
#

I haven't actually "fixed" this , but I do have a work around that allows me to set up a voice assistant. The issue is that my Home Assistant instance (Home Assistant OS running on a PC) was not showing the "Home Assistant URL section under settings - system - network". I found a reference to setting internal_url and/or external_url directly in the configuration.yaml file. So, I added the lines

#

homeassistant:

#

internal_url: <ip address of HA server>:8123