Reaching wt32-ESPhome device

ESPHome
1

Hi,

ESPHome is installed on a wt32 (ESP32) device; a static IP 192.168.2.246 was configured in the yaml. Now a new network has been configured and I can’t reach the device. Network-topography is as follows:

router: network 192.168.2.xxx
|
| the device (192.168.2.246)
|
unifi cloud gateway. In router’s network: 192.168.2.124
| own network: 192.168.1.xxx
|
|
raspi (192.168.1.xxx) with home assistant.

  • The raspi receives and displays data from the ESPHome device.
  • In HA ESPhome builder, the device is shown as offline.
  • Logs show ResolveTimeoutAPIError.
  • The device replies to ping from the xxx.xxx.2.xxx network.
  • The device doesn’t react to web-browsing to its IP-adress, from neither of the networks.
  • Configuring routes in the router is not supported.

I would very much like to avoid having to deconstruct the device in order to re-flash it via usb, and I am afraid putting the raspi back in the xxx.xxx.1.xx network might mess up other things.

  • is there any other way to reach the device via the networks?
  • Is there a way to directly connect a Linux-Notebook to the device via ethernet cable and reconfigure it?

Thank you very much for your help!

2

Discovery across subnets/VLANs won’t work unless you enable the Gateway mDNS proxy on the Unifi Gateway (Settings - Network). You can either allow all services across all VLANS or just include the VLANS you want to include.

Even then, mDNS across subnets/VLANs is iffy at best. While I know you said you don’t want to move anything, having HA and all the ESPHome devices on the same VLAN will make your life much easier.

3

Thank you very much @pkscout, that is exactly my plan, to put the device in the …1… network and I have tried that first. Unfortunately, with its static IP (…2…) it cannot be contacted in that network, either. That is why now I‘m looking for ways to reconfigure the ESP-device. Is there an option to connect to it without using USB? Is there a stand alone ESPhome-software to program a device connected to a notebook via direct link ethernet?

4

Yes and I recommend to use that even if you didn’t have this problem.
You could try to temporarily configure your notebook’s Ethernet adapter to same subnet as the ESP device.

5

Thanks @Karosm for the hint, I wasn‘t aware of that and will try it.

6

If the Pi has a static IP, then you need to configure it with a new static IP in the same subnet as the VLAN on which the ESP device resides. If you’re not familiar with networking concepts, you’re better off just having one VLAN and putting everything on it.

7

Thanks @pkscout , that‘s not my problem. So far I haven‘t succeeded trying to change the static IP on the device. Will try esphome Host now.

8

Alright, I finally made it. The wt32 was completely stuck, so I had to re-flash it with a new esphome, which was done via command-line-esphome on a linux notebook while connected via usb. Took me hours, but it’s working after all. Praise be to chatgpt, who guided me with never wavering patience through the bash-jungle.

9

Hi, good that it got solved!

Also: please take the time to mark the post that holds the answer.
You do that by selecting the three dots under the post:

image

Then select the check box:

image
By doing so:

  • this thread can be useful to other users as well (this thread comes up as solution when starting a thread which is similar to yours).
  • this prevents that someone else steps in trying to help

Thanks for giving back to the community! :+1: