Steven Ellis

Thanks for the tips. I can see the logs from my working units. For the AP42 Units I get ``` 2022-09-28 18:00:27 DEBUG (MainThread) [custom_components.echonetlite.config_flow] IP address is 192.168.100.34 2022-09-28...

Refreshed environment to - echonetlite Version 3.6.2 - hass 2022.9.7 Same issues trying to add my new units.

Running inside the hass container image via `podman exec -it hass /bin/sh` ``` # python3 -m asyncio asyncio REPL 3.10.5 (main, Jun 22 2022, 13:51:01) [GCC 11.2.1 20220219] on linux...

Trying for the other nodes with my laptop on the same VLAN ``` >>> await server.discover("192.168.100.32") ECHONETLite Message Received from 192.168.100.32 - Processed data is {'EHD1': 16, 'EHD2': 129, 'TID':...

Back on my normal VLAN I can get a response from 2 of the 4 units ``` >>> await server.discover("192.168.100.32") ECHONETLite Message Received from 192.168.100.32 - Processed data is {'EHD1':...

Ports are definately open on the target devices ``` $ nmap -p 80,3160 192.168.100.32 Starting Nmap 7.92 ( https://nmap.org ) at 2022-10-01 16:53 NZDT Nmap scan report for officeaircon.home.net (192.168.100.32)...

Ok so I can hit that UDP port on all 4 of my devices. ``` nmap -sU -v 192.168.100.31 -p 3160 Starting Nmap 7.70 ( https://nmap.org ) at 2022-10-02 09:45...

I've tried some more troubleshooting and if I have a physical linux machine with a VNIC connected to the VLAN I'm all good and your simple debug tool shows discovery...

@vorezal There is a side issue with this approach where you're using a tool like rclone to backup Google Photos (see #4421). You can't simply rename / change the extension...