#Tuya Local and devices changing subnets

1 messages · Page 1 of 1 (latest)

pure kettle
#

Some time ago I installed Local Tuya, obtained device keys from the Tuya cloud, and went ahead and deleted the devices from the Tuya cloud. All worked well locally. Now I've had to move the devices to a different SSID, on a different local subnet from HA. I had to use the Smart Life app (Android), remove each device, get it into pairing mode, Add Device using the new SSID, and poke holes in the firewall until it could be added successfully. In HA in the Local Tuya integration I did Configure / Edit a Device and for each device set its new IP address, leaving the existing local key. After restarting HA the HA devices are not connected to the actual devices (toggle switches disabled, no new logbook entries, etc). My Tuya Cloud account doesn't seem to be authorized any more. Is it likely that re-adding the devices caused new local keys to be generated and that's why it isn't working? Although, wireshark doesn't show HA even attempting to reach the new device IP address, so maybe it's even more fundamental than the device key.
I enabled debug logging for the integration and restarted HA. It does log that it is "Trying to connect to" the new IP address on port 6668, but fails after 30 seconds - but wireshark (tcpdump running on the openwrt router) isn't even seeing the attempt!
HA can connect to an ohmax outlet on the same subnet and wireshark does show that, so it is possible to connect - but that's MQTT, probably HA is just replying on a connection which was earlier opened from the device to HA.
Argh. Often while typing up a problem I'll see the answer, but not this time 😦
Hell, it's only 4 light switches, I should just junk them and buy Zigbees.