#Can't finish setting up Voice PE with separate IOT WLAN/VLAN

1 messages · Page 1 of 1 (latest)

hearty zodiac
#

So I have a VLAN setup, my main public network with most regular computing devices (phone, laptop, desktop, etc), and a IOT VLAN which has no internet access. My HA install (HassOS running as a VM on my FreeBSD NAS) has 2 network interfaces, one for Public, and one for IOT. I have corresponding WiFi networks for public and IOT VLANs.

I just got my Voice PE from Seeed (yay!), and the Android app via BT configured the IOT WiFi, on my router I can see it's on the network with an IP, but I get nothing from HomeAssistant saying a new device is discovered, nor is it listed in Devices.

I have Core 2024.12.5, Supervisor 2024.12.0, OS 14.1, Frontend 20241127.8.

Anyway I can try and add it via Integration? I don't see any integration already installed that seems to be related, when I try and manually add it.

The LEDs were blue and rotating, but as I finish typing this they've gone all on as white, and are now flashing all on/off white every few seconds.

broken turret
#

Hello @hearty zodiac,
Segmented networks are not officially supported within HA.

HA is designed and expects a flat subnet to work as intended.

This is because every segmented network is different for IP's and number of segments and firewalls and sharing rules and about 650495849085 other things.
This does not mean you can't use them or that they can't be made to work, it means that to get them working you are the support structure on your own subnet(s) .

hearty zodiac
#

Just how do I manually add this integration and IP/Hostname to get my HA install to connect to it?

#

Just like I can do with ESPHome, or really all the rest of the integrations (in general)

#

Or is there another forum I should go post in to get more technically minded help?

broken turret
#

I don't have mine yet (This is the one HA just released, right?), so specifically I don't know, but it's ESPHome, isn't it? Did you look at the HA website for the device?

hearty zodiac
#

And I'm pointed to this forum, as one of the support spots

broken turret
#

OK, well you have this post, we'll see who responds.I'm interested as well as mine is in the mail...

hearty zodiac
#

My ESPHome via the Terminal & SSH Add-On, can ping the device OK

#

And just a comment from me, personally, your initial reply was very "f-off, we don't support you because you're a non-standard setup, go away" feel to it, when I was used to a much more open "well, that's not our normal setup, no guarantees, but have you tried X, or Y, maybe look at log Z"

#

So for me, it could have been much more welcoming of a reply

broken turret
#

Sorry. I tend to deal in facts not feelings. I'm working on that.
The statement is still true. It's unsupported config and it may be difficult to answer your question because of that. I myself have 2 subnets... Just setting expectations. Unsupported does not mean you can't do it or that you will get no support, It's that the question/answer may be more complicated than you think.

hearty zodiac
#

I get not necessarily dealing with feelings...but if I'm already talking about VLAN setups and such, I would think you'd think I'm fairly technically savvy, and maybe a more measured "well, we don't officially support that, but..." kind of reply?

#

And it certainly was plenty complicated to setup initially, lol

#

complicated by issues with FreeBSD and the underlying VLAN capabilities and how it gets configured, etc

broken turret
#

I believe you, but there are many people here who had someone set their subnets BC they saw a YT video and thought it was the thing to do, but their router password is stil admin12345

#

OK, lets see who has one of these set up and we will learn together... (You are the first one in the wild I have heard about besides the comped ones for insiders).

hearty zodiac
#

Ha! Totally.

#

I'm hoping it's something simple. Or it can be a simple "enable/add this integration"

frank island
#

Is it just an ESPHome?

broken turret
#

I thought it was , but read back. I asked him.

hearty zodiac
frank island
#

I'm not talking about the device builder, just "Add Integration -> ESPHome"

#

Enter the IP in the host field

broken turret
#

I would expect HA to see it as an esphome device and adopt it.

hearty zodiac
#

ESPHome became ESPHomeBuilder, right?

#

Oh, wait. Hm.

#

I see what you mean

frank island
#

The Addon is the builder

hearty zodiac
#

yeah

broken turret
#

(unless it's on the wrong subnet. ha ha)

hearty zodiac
#

Hm. Can't connect to ESP. Please make sure your YAML file contains an 'api:' line.

#

LOL, nope, I don't do subnetting

#

just VLAN

#

and for some reason while I can ping the device, I can't get any HTTP to come up

broken turret
#

I'm sure that's not a networking thing...

hearty zodiac
#

Seems more of an ESPHome integration (not builder) thing

hearty zodiac
#

sigh

#

This always seems to happen to me... :P

broken turret
tepid cliff
#

if you try to re-flash using the following link with your device connected via usb to your computer. and add to your wifi upon completion. If the device does not then autodect to allow you to add to HA try restarting your HA instance.

hearty zodiac
#

I do have esptools

#

what's the instructions for that?

tepid cliff
hearty zodiac
tepid cliff
#

yes 0x0 👍

finite mountain
#

Mine connected to WiFi on the one vlan just fine and then the esphome step hung in the app. Now I can’t finish that step. I can see it’s connected to WiFi and got an IP but HA doesn’t find it. No idea how to continue and don’t even see how to do a factory reset to try and start over

tepid cliff
#

have you tried restarting HA at all to see if it then picks it up ?

#

also if you powercycle the device by removing the usb

finite mountain
tepid cliff
#

once it is connected to wifi, HA should detect it via the ESPHome integration, sometimes a reboot will solve it.

finite mountain
tepid cliff
#

if you go to the ESPHome integration and add device , entering the ip address is it still the same as previous attempt?

finite mountain
broken turret
#

I didn't see that coming...

tepid cliff
#

this is on the left in the device page

hearty zodiac
#

So I emailed voice-pe@home-assistant.io and heard back, ```The version the device shipped with unfortunately has a bug where it will crash when the internet connection is not reliable (or in this case, missing if the VLAN did not have internet access) The current version resolves that.

As this is an ESPHome based device, logs can be viewed using the same USB connection you will use to update the firmware. There is no need to open the device or connect to the serial port.```

hearty zodiac
hearty zodiac
#

Still have it set into a boot loop, and after flashing multiple times, can't seem to get it back into pairing mode. Just stays stuck. Tried replying to the support email, but if anyone knows how to erase or reset the ESP32 settings storage, that might help out.

#

Huh, ok, so just erase_flash and then reflash seems to have done it, nice

#

Oh got it! Ok, so here's what I needed to do:

In the app, do the Add and setup the WiFi.
Then after it is connected, the Android app popped up "Add to ESPHome", but wanted a hostname. So I looked up the IP on my router, input that on my phone, and that added it fine.
So now I'm on my desktop browser, and seeing the device, so I can work through the rest of the setup that way :)

#

And when I start going through the setup on HA device page, it's doing the white ring, and then boot looping now. Again. WTF :(

#

I guess it really hates not being able to connect to the internet

ocean ice
hearty zodiac
hearty zodiac
#

So a new preview firmware out, tried that, got the same issue sigh

spice falcon