[tuya] automatic discovery

Add-ons Bindings
,
1

I have a working openHAB 4.3.5 installation with the Tuya binding from SmartHome/J with two devices.
Yesterday I got a new Tuya device (Cecotec EnergySilence Aero 5400).
I integrated the new device into Tuya Smart, and it also appears under my account in the Tuya developer platform.
Unfortunately, it isn’t detected as a new device in openHAB 4.

Since openHAB 5 will be released soon, I set up a test server with the current build and the Tuya binding. My idea was to then manually add the device to openHAB 4 using the data from the devices detected by openHAB 5.

Unfortunately, with the current version, no devices are detected at all, not even the two devices that work under openHAB 4.

For each device I get debug logs from the tuya binding like:
2025-06-19 11:43:06.694 [DEBUG] [.internal.local.handlers.TuyaDecoder] - udpListener: Received MessageWrapper{commandType=UDP_NEW, content=‘DiscoveryMessage{ip=‘10.1.5.47’, deviceId=’|cut out|‘, active=2, ability=0, mode=0, encrypt=true, productKey=‘npfinze0zsvta7aj’, version=‘3.5’, token= true, wf_cfg=true}’}

Anyone have any idea what’s going wrong here ?

2

Your iot.tuya.com IoT core trial has expired or reached quota and needs to be renewed probably. It’s a shame that the Tuya binding doesn’t give any sort of error. It’s a shame you need an expiring trial or a paid plan just to get the local keys you need to use Tuya devices. It’s a shame that the Tuya binding doesn’t persistently cache the cloud data.

I was thinking of fixing at least some of this in the Tuya binding that’s gone into the 5.0.0 openhab-addons collection. Along with a whole load of other stuff…

3

Thank you very much, I would never have looked there. My IoT Core trial account has actually expired. I’ve now tried to renew it.
Edit: The new device was recognized immediately after the extension.