Issues adding a device

[phyzical]

Hey,

so i added one of these https://expo.ifreeq.com/products/s11 onto the tuya smart app. it works as expected and was able to import it via the tuya HA plugin into HA and the scenes work as expected.

Figured i would give tuya-local a crack, less latency, less external factors ect.

Connected my account and the dropdown populated with the above device and the subdevices for it (the configured IR devices)

The ip was not found but the rest was, i used the mac address in the smart app to find the ip address of the device in question.

but when i try to add the hub itself or a subdevice i keep getting "failed to connect", Ha logs show

2025-08-06 22:36:08.675 ERROR (MainThread) [custom_components.tuya_local.device] Failed to refresh device state for Test.
2025-08-06 22:35:04.461	logstream=stderr	
2025-08-06 22:35:04.460 WARNING (MainThread) [custom_components.tuya_local.config_flow] Could not find device: bf68fXXXXXXXX

I also used tinytuya to verify and the ip address and device id matched as expected

Failed to send discovery broadcast from 192.168.69.248 to 255.255.255.255:7000: [Errno 65] No route to host
Sending broadcast discovery packet failed, certain v3.5 devices will not be found!
Unknown v3.3 Device   Product ID = keym4vvjXXXXXXXX  [Valid Broadcast]:
    Address = 192.168.69.157   Device ID = bf68fXXXXXXXX (len:22)  Local Key =   Version = 3.3  Type = default, MAC = 
    No Stats for 192.168.69.157: DEVICE KEY required to poll for status
New Broadcast from App at 192.168.69.248 - {'from': 'app', 'ip': '192.168.69.248'}
Scan completed in 18.0832 seconds                 
                    
Scan Complete!  Found 1 devices.
Broadcasted: 1
Versions: 3.3: 1

I run HA on a container that runs on a seperate network interface via unraid but it does have access to the 192.168.69 subnet where the device is. if that matters at all, i did verify i can ping this device from a shell on the HA container console

root@b11f2244aacc:/# ping 192.168.69.157
PING 192.168.69.157 (192.168.69.157) 56(84) bytes of data.
64 bytes from 192.168.69.157: icmp_seq=1 ttl=254 time=24.4 ms
64 bytes from 192.168.69.157: icmp_seq=2 ttl=254 time=50.9 ms
64 bytes from 192.168.69.157: icmp_seq=3 ttl=254 time=67.3 ms
--- 192.168.69.157 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 24.405/47.540/67.322/17.680 ms

• i made sure the smart app was was fully closed
• -> i will try again tomorrow to rule out the "worked 12 hours later"
• i never configured the other local tuya app, i did install the HACS part but then uninstalled it.

Does anyone have any suggestions on how to debug this further?

sadly i do not have any other tuya devices to test with at this time, im at the start of the Automation journey

Thanks!

[phyzical]

small update,

• Same issue next day so the 12 hours later was a nogo for me.
• i forgot that i had a robot vaccum that was tuya compatible, sadly it too runs into the same issue as the above fails to connect

[make-all]

IR "subdevices" are not real devices, and cannot be supported in general by this integration. Only the S11 itself has any chance of working. See #522 for tips on resolving connection issues.

[phyzical]

hmm okay i did see this list, i guess the only one i havnt tried is #334

thanks for the response