I have a couple chinese devices that use the Tuya app/platform that i’ve successfully integrated into home assistant locally with the LocalTuya integration.
However, following best security/privacy practices I’ve started segmenting my network into vlans, leaving the default one as “privileged” and creating two other vlans (and wifi SSIDs) named IoT for devices that need to connect to the internet but shouldn’t talk with anyone else in the local network (except home assistant iself) and NoT for devices that should not talk with absolutely no one but home assistant, local or remote.
I added several devices but so far I wasn’t able to make add those devices to localtuya on either one of those vlans. Not even in the one that has access to the internet. I can control them using the cloud, so they do connect to the internet, but I can’t add them to local tuya even if I manually specify the IP/id/localid myself.
Has anyone succeeded on adding to localtuya devices on other vlans? And if you did, were you able to eventually disconnect those devices from the internet for good?
I was able to do it eventually. I’m not sure what was the cause, but I lifted all security on the vlans momentarily, added the device into localtuya, and then added back the firewall rules (namely, devices in the NoT vlan can’t talk with anyone but home assistant, and don’t have access to the internet).
It seems to work fine. I’ll give it some time because I heard some reports of tuya devices freezing if disconnected from the network for long.
Just came across this as I’ve been the same.
All my original local tuya devices go offline when I move HomeAssistant to a vlan. Omada.
Will set up a test HomeAssistant and test further but really not sure what else in the acl or firewall settings I can adjust
Hi!
I know this is old but … did it work properly?
I recently moved to Omada (EAP653UR + ER7212PC) and am having issues with my Tuya devices. They seem to connect well, but after 10-12 hours they stop renewing DHCP leases and stop responding to ping in the Lan.
Those devices with easy access, a power cycle will recover them, but the ones with difficult access I have to delete them using the app and add them back again, what causes deleting scenes and the annoyance of having to do it manual.
Of course Tuya/SmartLife support is useless.
Looking for info about it I found this post, so I have moved the devices to a SSID in the default vlan and will see if it works in a few hours.
But eben if it does … were you able to make it work properly with VLANs?
My issue is not not being able to connect, but losing the connection after a number of hours/number of DHCP renewals.
Thanks
They work fine for me. Although it’s true that I usually assign static IPs to all my smart home devices. I use ubiquity equipment FWIW.
I have a “NoT” wifi that runs on vlan without internet access. When I want to add a new tuya device I momentarily lift that restriction so it can connect to the tuya servers, then I collect all the information I need about the deviceId, what switches and sensors it has and they id’s, add them to local tuya and enable the vlan restrictions again so they no longer connect to the internet.
Yeah, I assign static IP addresses too, but if the device stops renewing it when needed …
I had them on a non-vlan SSID and working fine ever since. I moved one of them the the VLAN SSID and will see, I don’t know, maybe it decided to work now XDDD