Tuya Devices constantly toggle between ONLINE and ONLINE: Waiting for device wake up after update to openHAB 5.1.0

san4esmc · January 27, 2026, 2:20pm

Just a note here for everyone waiting for a fix: this behavior was fixed fully (as far as we could test it) in this PR [tuya] Avoid refresh if no measurables on status update by san4esmc · Pull Request #20030 · openhab/openhab-addons · GitHub

So it should be available in next upcoming release. I can build a JAR with latest sources for anyone willing to test it

san4esmc · January 27, 2026, 2:25pm

I don’t know about docker releases, tbh. I’m pretty sure you can replace JAR in docker also (maybe a bit more hussle needed here). You can get the JAR I’m using locally with a fix here: https://drive.google.com/file/d/1mH3e-O-GfqLh1DR3Uqr7oFNdSwCZy3iW/view?usp=sharing

Wikibear · January 27, 2026, 3:04pm

Great! Thanks. I will give a try. Don’t hesitate with docker its same like other installations… Same folder. So will test this.

Wikibear · January 27, 2026, 4:40pm

Thing ‘tuya:tuyaDevice:11662454c45bbed9743d’ changed from ONLINE: Waiting for device wake up to ONLINE
info_circle 17:36:13.505	INFO	
openhab.event.ThingStatusInfoChangedEvent
Thing ‘tuya:tuyaDevice:34563405c45bbef59d1a’ changed from ONLINE: Waiting for device wake up to ONLINE
info_circle 17:36:15.229	INFO	
openhab.event.ThingStatusInfoChangedEvent
Thing ‘tuya:tuyaDevice:11662454c45bbed9743d’ changed from ONLINE to ONLINE: Waiting for device wake up
info_circle 17:36:15.523	INFO	
openhab.event.ThingStatusInfoChangedEvent
Thing ‘tuya:tuyaDevice:34563405c45bbef59d1a’ changed from ONLINE to ONLINE: Waiting for device wake up
info_circle 17:36:16.235	INFO	
openhab.event.ThingStatusInfoChangedEvent
Thing ‘tuya:tuyaDevice:11662454c45bbed9743d’ changed from ONLINE: Waiting for device wake up to ONLINE
info_circle 17:36:16.531	INFO	
openhab.event.ThingStatusInfoChangedEvent
Thing ‘tuya:tuyaDevice:34563405c45bbef59d1a’ changed from ONLINE: Waiting for device wake up to ONLINE
info_circle 17:36:17.705	INFO

Looks that this isn’t fixed for me.

san4esmc · January 28, 2026, 10:49am

What device is that?

You can also try to enable debug logging for addon and post that logs here - at least that was how I discovered that addon was incorrectly sending requests to device waiting for response (which never happened as device just ignored it) and then was dropping the connection

Wikibear · January 28, 2026, 2:24pm

Should be a light device… Maybe switch. Dunno… I will switch over to debug mode as you requested. Overall the log show less information about status change after update. But it’s not fully gone as I show. The biggest problem is that all my lights aren’t responsive enough if I switch many lights in the same time on. Some lights stay off or on after switching. Many thanks for your help! Will send a report ASAP.

Wikibear · January 29, 2026, 7:14pm

info_circle 19:16:56.421	INFO	
openhab.event.ThingStatusInfoChangedEvent
Thing 'tuya:tuyaDevice:11662454c45bbed9743d' changed from ONLINE: Waiting for device wake up to ONLINE
ant 19:16:56.435	DEBUG	
org.openhab.binding.tuya.internal.local.handlers.TuyaDecoder
11662454c45bbed9743d/192.168.2.42:6668: Received MessageWrapper{commandType=DP_QUERY, content='TcpStatusPayload{protocol=-1, devId='11662454c45bbed9743d', gwId='', uid='', t=0, dps={1=stop, 2=100.0, 3=100.0, 5=false, 7=closing, 8=cancel, 9=0.0, 10=0.0, 11=0.0}, data=Data{dps={}}}'}
ant 19:16:56.436	DEBUG	
org.openhab.binding.tuya.internal.handler.TuyaDeviceHandler
Could not find channel for dp '10' in thing 'tuya:tuyaDevice:11662454c45bbed9743d'
ant 19:16:56.566	DEBUG	
org.openhab.binding.tuya.internal.local.TuyaDevice
34563405c45bbef59d1a/192.168.2.230:6668: reconnect
ant 19:16:56.570	DEBUG	
org.openhab.binding.tuya.internal.local.TuyaDevice
34563405c45bbef59d1a/192.168.2.230:6668: channel connected
ant 19:16:56.570	DEBUG	
org.openhab.binding.tuya.internal.handler.TuyaDeviceHandler
34563405c45bbef59d1a: connected
ant 19:16:56.571	DEBUG	
org.openhab.binding.tuya.internal.local.handlers.TuyaEncoder
34563405c45bbef59d1a/192.168.2.230:6668: Sending DP_QUERY, payload {devId=34563405c45bbef59d1a, uid=34563405c45bbef59d1a, t=1769624216, dps=[], gwId=34563405c45bbef59d1a}
info_circle 19:16:56.571	INFO	
openhab.event.ThingStatusInfoChangedEvent
Thing 'tuya:tuyaDevice:34563405c45bbef59d1a' changed from ONLINE: Waiting for device wake up to ONLINE
ant 19:16:56.586	DEBUG	
org.openhab.binding.tuya.internal.local.handlers.TuyaDecoder
34563405c45bbef59d1a/192.168.2.230:6668: Received MessageWrapper{commandType=DP_QUERY, content='TcpStatusPayload{protocol=-1, devId='34563405c45bbef59d1a', gwId='', uid='', t=0, dps={1=false, 2=false, 7=0.0, 8=0.0, 102=0.0, 103=0.0, 104=2193.0, 105=1.0, 106=1657.0, 107=30727.0, 108=88695.0, 109=235.0}, data=Data{dps={}}}'}
info_circle 19:16:57.178	INFO	
openhab.event.ItemStateChangedEvent
Item 'DDDruckerVyperPower' changed from 65 to 154 (source: org.openhab.core.thing$mqtt:homeassistant_zigbee2mqtt_5F0xa4c1380747f9d023:MQTTBroker:zigbee2mqtt_5F0xa4c1380747f9d023:power)
ant 19:16:57.436	DEBUG	
org.openhab.binding.tuya.internal.local.handlers.TuyaEncoder
11662454c45bbed9743d/192.168.2.42:6668: Sending DP_REFRESH, payload {dpId=[]}
ant 19:16:57.587	DEBUG	
org.openhab.binding.tuya.internal.local.handlers.TuyaEncoder
34563405c45bbef59d1a/192.168.2.230:6668: Sending DP_REFRESH, payload {dpId=[]}
info_circle 19:16:58.138	INFO	
openhab.event.ItemStateChangedEvent
Item 'DDDruckerMegaCurrent' changed from 0.55 to 0.75 (source: org.openhab.core.thing$mqtt:homeassistant_zigbee2mqtt_5F0xa4c138d7c37833c8:MQTTBroker:zigbee2mqtt_5F0xa4c138d7c37833c8:current)
info_circle 19:16:58.150	INFO	
openhab.event.ItemStateChangedEvent
Item 'DDDruckerMegaPower' changed from 70 to 85 (source: org.openhab.core.thing$mqtt:homeassistant_zigbee2mqtt_5F0xa4c138d7c37833c8:MQTTBroker:zigbee2mqtt_5F0xa4c138d7c37833c8:power)
ant 19:16:58.195	DEBUG	
org.openhab.binding.tuya.internal.local.handlers.TuyaEncoder
bf94f65611a47eb778egyo/192.168.2.68:6668: Sending DP_REFRESH, payload {dpId=[]}
ant 19:16:58.242	DEBUG	
org.openhab.binding.tuya.internal.local.handlers.TuyaDecoder
bf94f65611a47eb778egyo/192.168.2.68:6668: Received MessageWrapper{commandType=DP_REFRESH, content=''}
ant 19:16:58.436	DEBUG	
org.openhab.binding.tuya.internal.local.handlers.TuyaEncoder
11662454c45bbed9743d/192.168.2.42:6668: Sending DP_REFRESH, payload {dpId=[]}
ant 19:16:58.437	DEBUG	
org.openhab.binding.tuya.internal.local.TuyaDevice
11662454c45bbed9743d192.168.2.42: Connection seems to be dead.
ant 19:16:58.437	DEBUG	
org.openhab.binding.tuya.internal.local.TuyaDevice
11662454c45bbed9743d/192.168.2.42:6668: channel closed
ant 19:16:58.437	DEBUG	
org.openhab.binding.tuya.internal.handler.TuyaDeviceHandler
11662454c45bbed9743d: disconnected
info_circle 19:16:58.438	INFO	
openhab.event.ThingStatusInfoChangedEvent
Thing 'tuya:tuyaDevice:11662454c45bbed9743d' changed from ONLINE to ONLINE: Waiting for device wake up
ant 19:16:58.584	DEBUG	
org.openhab.binding.tuya.internal.local.handlers.TuyaEncoder
bf5f8691d4146a6cd2mhbp/192.168.2.74:6668: Sending DP_REFRESH, payload {dpId=[]}
ant 19:16:58.587	DEBUG	
org.openhab.binding.tuya.internal.local.handlers.TuyaEncoder
34563405c45bbef59d1a/192.168.2.230:6668: Sending DP_REFRESH, payload {dpId=[]}
ant 19:16:58.587	DEBUG	
org.openhab.binding.tuya.internal.local.TuyaDevice
34563405c45bbef59d1a192.168.2.230: Connection seems to be dead.
ant 19:16:58.587	DEBUG	
org.openhab.binding.tuya.internal.local.TuyaDevice
34563405c45bbef59d1a/192.168.2.230:6668: channel closed
ant 19:16:58.588	DEBUG	
org.openhab.binding.tuya.internal.handler.TuyaDeviceHandler
34563405c45bbef59d1a: disconnected
info_circle 19:16:58.589	INFO	
openhab.event.ThingStatusInfoChangedEvent
Thing 'tuya:tuyaDevice:34563405c45bbef59d1a' changed from ONLINE to ONLINE: Waiting for device wake up
ant 19:16:58.676	DEBUG	
org.openhab.binding.tuya.internal.local.handlers.TuyaDecoder
bf5f8691d4146a6cd2mhbp/192.168.2.74:6668: Received MessageWrapper{commandType=DP_REFRESH, content=''}
ant 19:16:59.439	DEBUG	
org.openhab.binding.tuya.internal.local.TuyaDevice
11662454c45bbed9743d/192.168.2.42:6668: reconnect
ant 19:16:59.443	DEBUG	
org.openhab.binding.tuya.internal.local.TuyaDevice
11662454c45bbed9743d/192.168.2.42:6668: channel connected
ant 19:16:59.444	DEBUG	
org.openhab.binding.tuya.internal.handler.TuyaDeviceHandler
11662454c45bbed9743d: connected
info_circle 19:16:59.444	INFO	
openhab.event.ThingStatusInfoChangedEvent
Thing 'tuya:tuyaDevice:11662454c45bbed9743d' changed from ONLINE: Waiting for device wake up to ONLINE
ant 19:16:59.445	DEBUG	
org.openhab.binding.tuya.internal.local.handlers.TuyaEncoder
11662454c45bbed9743d/192.168.2.42:6668: Sending DP_QUERY, payload {devId=11662454c45bbed9743d, uid=11662454c45bbed9743d, t=1769624219, dps=[], gwId=11662454c45bbed9743d}
flag 19:16:59.457	WARN	
org.openhab.binding.tuya.internal.cloud.TuyaOpenAPI
Request failed: Result{timestamp=1769624219440, code=1106, msg=permission deny, success=false, result=null}, no token received
ant 19:16:59.464	DEBUG	
org.openhab.binding.tuya.internal.local.handlers.TuyaDecoder
11662454c45bbed9743d/192.168.2.42:6668: Received MessageWrapper{commandType=DP_QUERY, content='TcpStatusPayload{protocol=-1, devId='11662454c45bbed9743d', gwId='', uid='', t=0, dps={1=stop, 2=100.0, 3=100.0, 5=false, 7=closing, 8=cancel, 9=0.0, 10=0.0, 11=0.0}, data=Data{dps={}}}'}
ant 19:16:59.465	DEBUG	
org.openhab.binding.tuya.internal.handler.TuyaDeviceHandler
Could not find channel for dp '10' in thing 'tuya:tuyaDevice:11662454c45bbed9743d'
ant 19:16:59.589	DEBUG	
org.openhab.binding.tuya.internal.local.TuyaDevice
34563405c45bbef59d1a/192.168.2.230:6668: reconnect
ant 19:16:59.592	DEBUG	
org.openhab.binding.tuya.internal.local.TuyaDevice
34563405c45bbef59d1a/192.168.2.230:6668: channel connected
ant 19:16:59.593	DEBUG	
org.openhab.binding.tuya.internal.handler.TuyaDeviceHandler
34563405c45bbef59d1a: connected
ant 19:16:59.593	DEBUG	
org.openhab.binding.tuya.internal.local.handlers.TuyaEncoder
34563405c45bbef59d1a/192.168.2.230:6668: Sending DP_QUERY, payload {devId=34563405c45bbef59d1a, uid=34563405c45bbef59d1a, t=1769624219, dps=[], gwId=34563405c45bbef59d1a}
info_circle 19:16:59.593	INFO	
openhab.event.ThingStatusInfoChangedEvent
Thing 'tuya:tuyaDevice:34563405c45bbef59d1a' changed from ONLINE: Waiting for device wake up to ONLINE
ant 19:16:59.609	DEBUG	
org.openhab.binding.tuya.internal.local.handlers.TuyaDecoder
34563405c45bbef59d1a/192.168.2.230:6668: Received MessageWrapper{commandType=DP_QUERY, content='TcpStatusPayload{protocol=-1, devId='34563405c45bbef59d1a', gwId='', uid='', t=0, dps={1=false, 2=false, 7=0.0, 8=0.0, 102=0.0, 103=0.0, 104=2193.0, 105=1.0, 106=1657.0, 107=30727.0, 108=88695.0, 109=235.0}, data=Data{dps={}}}'}
info_circle 19:16:59.991	INFO	
openhab.event.GroupItemStateChangedEvent
Item 'TemperaturPool' changed from 0.5950000166893005 to 0.6125 through MyStromBKWTemperature
info_circle 19:16:59.991	INFO	
openhab.event.ItemStateChangedEvent
Item 'MyStromBKWTemperature' changed from 3.180000066757202 °C to 3.25 °C (source: org.openhab.core.thing$mystrom:mystromplug:MyStromBKW:temperature)
info_circle 19:17:00.182	INFO	
openhab.event.ItemStateChangedEvent
Item 'DDDruckerVyperCurrent' changed from 1.42 to 0.7 (source: org.openhab.core.thing$mqtt:homeassistant_zigbee2mqtt_5F0xa4c1380747f9d023:MQTTBroker:zigbee2mqtt_5F0xa4c1380747f9d023:current)
ant 19:17:00.465	DEBUG	
org.openhab.binding.tuya.internal.local.handlers.TuyaEncoder
11662454c45bbed9743d/192.168.2.42:6668: Sending DP_REFRESH, payload {dpId=[]}
ant 19:17:00.610	DEBUG	
org.openhab.binding.tuya.internal.local.handlers.TuyaEncoder
34563405c45bbef59d1a/192.168.2.230:6668: Sending DP_REFRESH, payload {dpId=[]}
ant 19:17:00.755	DEBUG	
org.openhab.binding.tuya.internal.local.TuyaDevice
bfbcfb99c42883be3avx98192.168.2.222: Connection seems to be dead.
ant 19:17:00.755	DEBUG	
org.openhab.binding.tuya.internal.local.TuyaDevice
bfbcfb99c42883be3avx98/192.168.2.222:6668: channel closed
ant 19:17:00.756	DEBUG	
org.openhab.binding.tuya.internal.handler.TuyaDeviceHandler
bfbcfb99c42883be3avx98: disconnected
info_circle 19:17:00.756	INFO	
openhab.event.ThingStatusInfoChangedEvent
Thing 'tuya:tuyaDevice:bfbcfb99c42883be3avx98' changed from ONLINE to ONLINE: Waiting for device wake up
ant 19:17:01.465	DEBUG	
org.openhab.binding.tuya.internal.local.handlers.TuyaEncoder
11662454c45bbed9743d/192.168.2.42:6668: Sending DP_REFRESH, payload {dpId=[]}
ant 19:17:01.466	DEBUG	
org.openhab.binding.tuya.internal.local.TuyaDevice
11662454c45bbed9743d192.168.2.42: Connection seems to be dead.
ant 19:17:01.466	DEBUG	
org.openhab.binding.tuya.internal.local.TuyaDevice
11662454c45bbed9743d/192.168.2.42:6668: channel closed
ant 19:17:01.466	DEBUG	
org.openhab.binding.tuya.internal.handler.TuyaDeviceHandler
11662454c45bbed9743d: disconnected
info_circle 19:17:01.467	INFO	
openhab.event.ThingStatusInfoChangedEvent
Thing 'tuya:tuyaDevice:11662454c45bbed9743d' changed from ONLINE to ONLINE: Waiting for device wake up
ant 19:17:01.611	DEBUG	
org.openhab.binding.tuya.internal.local.handlers.TuyaEncoder
34563405c45bbef59d1a/192.168.2.230:6668: Sending DP_REFRESH, payload {dpId=[]}
ant 19:17:01.612	DEBUG	
org.openhab.binding.tuya.internal.local.TuyaDevice
34563405c45bbef59d1a192.168.2.230: Connection seems to be dead.
ant 19:17:01.612	DEBUG	
org.openhab.binding.tuya.internal.local.TuyaDevice
34563405c45bbef59d1a/192.168.2.230:6668: channel closed
ant 19:17:01.612	DEBUG	
org.openhab.binding.tuya.internal.handler.TuyaDeviceHandler
34563405c45bbef59d1a: disconnected
info_circle 19:17:01.613	INFO	
openhab.event.ThingStatusInfoChangedEvent
Thing 'tuya:tuyaDevice:34563405c45bbef59d1a' changed from ONLINE to ONLINE: Waiting for device wake up
ant 19:17:01.758	DEBUG	
org.openhab.binding.tuya.internal.local.TuyaDevice
bfbcfb99c42883be3avx98/192.168.2.222:6668: reconnect
info_circle 19:17:02.178	INFO	
openhab.event.ItemStateChangedEvent
Item 'DDDruckerVyperPower' changed from 154 to 62 (source: org.openhab.core.thing$mqtt:homeassistant_zigbee2mqtt_5F0xa4c1380747f9d023:MQTTBroker:zigbee2mqtt_5F0xa4c1380747f9d023:power)
ant 19:17:02.205	DEBUG	
org.openhab.binding.tuya.internal.TuyaDiscoveryService
Tried to start scan but API for bridge 'tuya:project:TuyaCloudProject_neu' is not connected.
ant 19:17:02.467	DEBUG	
org.openhab.binding.tuya.internal.local.TuyaDevice
11662454c45bbed9743d/192.168.2.42:6668: reconnect
ant 19:17:02.472	DEBUG	
org.openhab.binding.tuya.internal.local.TuyaDevice
11662454c45bbed9743d/192.168.2.42:6668: channel connected
ant 19:17:02.472	DEBUG	
org.openhab.binding.tuya.internal.handler.TuyaDeviceHandler
11662454c45bbed9743d: connected
ant 19:17:02.473	DEBUG	
org.openhab.binding.tuya.internal.local.handlers.TuyaEncoder
11662454c45bbed9743d/192.168.2.42:6668: Sending DP_QUERY, payload {devId=11662454c45bbed9743d, uid=11662454c45bbed9743d, t=1769624222, dps=[], gwId=11662454c45bbed9743d}
info_circle 19:17:02.475	INFO	
openhab.event.ThingStatusInfoChangedEvent
Thing 'tuya:tuyaDevice:11662454c45bbed9743d' changed from ONLINE: Waiting for device wake up to ONLINE


Hope that this will help out. Power plug and a blind.

san4esmc · January 30, 2026, 8:04pm

Can you also, please, provide Product ID for both devices? You can find it in thing:

Wikibear · January 31, 2026, 11:40am

vnya2spfopsh9lro
3r8gc33pnqsxfe1g
1sge49ixkb5nfhn3

DiegoGR · February 3, 2026, 9:07pm

Hi

I have also an issue with one of my RGBW led bulbs not working properly with the status ONLINE / “Waiting for device wake up”. They are:

GY Lightning G150 RGBW / ID xczbo26yiwk4cmbs / Works fine and never showed “Waiting for device wake up”
Ledvance G95 RGBW (Wifi-Matter) / ID ktljrdu99ytvgfvi / I have never managed to make it work, always showing “Waiting for device wake up”

Both are included in my TUYA proyect and work fine with the android app.

I have tried your JAR file and it doesn’t work for me, unfortunately.

Thank you and regards

Diego

san4esmc · February 5, 2026, 7:58am

So a quick check on this gives this sequence for one device:

We send DP_REFRESH to get updated state from device two times, but don’t receive any response and coclude that connection is dead. So device is not responding for DP_REFRESH in time. Earlier we had an issue that DP_REFRESH was sent to devices which had no read only DPs, which was incorrect, cause such devices will not respond to it. At the same time your devices have read only DPs, which means they should respond to DP_REFRESH command

So for me it looks like some flaw in device firmware rather then issue in addon itself.

You can also try to enable trace logging and we can check more precisely what’s happening

DiegoGR · February 6, 2026, 4:38pm

This is what I get from Tuya Product ID ktljrdu99ytvgfvi asigned to the Ledvance Smart+ Matter led bulb:

2026-02-06 17:24:18.214 [WARN ] [uya.internal.TuyaChannelTypeProvider] - Don't know how to build a channel type for schema entry sleep_mode type raw - using string
2026-02-06 17:24:18.215 [WARN ] [uya.internal.TuyaChannelTypeProvider] - Don't know how to build a channel type for schema entry wakeup_mode type raw - using string
2026-02-06 17:24:18.216 [WARN ] [uya.internal.TuyaChannelTypeProvider] - Don't know how to build a channel type for schema entry power_memory type raw - using string
2026-02-06 17:24:18.217 [WARN ] [uya.internal.TuyaChannelTypeProvider] - Don't know how to build a channel type for schema entry switch_gradient type raw - using string
2026-02-06 17:24:18.218 [WARN ] [uya.internal.TuyaChannelTypeProvider] - Don't know how to build a channel type for schema entry random_timing type raw - using string

And this was I get when a set to TRACE

2026-02-06 17:30:25.970 [TRACE] [.internal.local.handlers.TuyaDecoder] - udpListener: Protocol version '3.1'
2026-02-06 17:30:25.970 [TRACE] [.internal.local.handlers.TuyaDecoder] - Set protocol version to 3.5
2026-02-06 17:30:25.970 [TRACE] [.internal.local.handlers.TuyaDecoder] - udpListener: Decoded raw payload: 7B226970223A223139322E3136382E312E3535222C2267774964223A2262666535613365323839376435653964646636796671222C2275756964223A2262363062303363633262643966303031222C22616374697665223A322C2261626C696C7479223A302C22656E6372797074223A747275652C2270726F647563744B6579223A226B657938753534713964747275356A77222C2276657273696F6E223A22332E35222C22746F6B656E223A747275652C2277665F636667223A747275652C22636C69656E744C696E6B223A327D
2026-02-06 17:30:25.971 [TRACE] [.internal.local.handlers.TuyaDecoder] - udpListener: Received MessageWrapper{commandType=UDP_NEW, content='DiscoveryMessage{ip='192.168.1.55', deviceId='bfe5a3e2897d5e9ddf6yfq', active=2, ability=0, mode=0, encrypt=true, productKey='key8u54q9dtru5jw', version='3.5', token= true, wf_cfg=true}'}
2026-02-06 17:30:26.292 [TRACE] [nding.tuya.internal.local.TuyaDevice] - bf20162b0e49295b5fcvma: connecting
2026-02-06 17:30:26.464 [TRACE] [nding.tuya.internal.local.TuyaDevice] - bf20162b0e49295b5fcvma: connecting
2026-02-06 17:30:26.480 [TRACE] [nding.tuya.internal.local.TuyaDevice] - bf20162b0e49295b5fcvma/192.168.1.56:6668: Failed to connect: connection timed out after 1000 ms: /192.168.1.56:6668
2026-02-06 17:30:27.293 [TRACE] [nding.tuya.internal.local.TuyaDevice] - bf20162b0e49295b5fcvma/192.168.1.56:6668: Failed to connect: connection timed out after 1000 ms: /192.168.1.56:6668
2026-02-06 17:30:27.467 [TRACE] [nding.tuya.internal.local.TuyaDevice] - bf20162b0e49295b5fcvma/192.168.1.56:6668: Failed to connect: connection timed out after 1000 ms: /192.168.1.56:6668
2026-02-06 17:30:27.481 [TRACE] [nding.tuya.internal.local.TuyaDevice] - bf20162b0e49295b5fcvma: connecting
2026-02-06 17:30:27.766 [TRACE] [nding.tuya.internal.util.NetworkUtil] - Local IPv4 address is: 192.168.1.40
2026-02-06 17:30:27.766 [TRACE] [.internal.local.handlers.TuyaEncoder] - udpDiscoverySender: Sending REQ_DEVINFO, payload {from=app, ip=192.168.1.40}
2026-02-06 17:30:27.767 [TRACE] [.internal.local.handlers.TuyaEncoder] - udpDiscoverySendernull: Sending encoded '00006699000000000001000000250000003EEDD95F5E0FC1317B26E71659A6F1C45AA74482517BE77B82A42888DAEF5D92FBA0333BD16DC98D52626424027239EF324EBBDC0E391C1CC9B6E1DD9BC7ED00009966'
2026-02-06 17:30:27.767 [TRACE] [.internal.local.handlers.TuyaDecoder] - udpListener: Received encoded '00006699000000000001000000250000003EEDD95F5E0FC1317B26E71659A6F1C45AA74482517BE77B82A42888DAEF5D92FBA0333BD16DC98D52626424027239EF324EBBDC0E391C1CC9B6E1DD9BC7ED00009966'
2026-02-06 17:30:27.767 [TRACE] [.internal.local.handlers.TuyaDecoder] - udpListener: Protocol version '3.5'
2026-02-06 17:30:27.767 [TRACE] [.internal.local.handlers.TuyaDecoder] - udpListener: Decoded raw payload: 6F6D223A22617070222C226970223A223139322E3136382E312E3430227D
2026-02-06 17:30:27.768 [DEBUG] [.internal.local.handlers.TuyaDecoder] - udpListener: Received MessageWrapper{commandType=REQ_DEVINFO, content='om":"app","ip":"192.168.1.40"}'}
2026-02-06 17:30:28.294 [TRACE] [nding.tuya.internal.local.TuyaDevice] - bf20162b0e49295b5fcvma: connecting
2026-02-06 17:30:28.469 [TRACE] [nding.tuya.internal.local.TuyaDevice] - bf20162b0e49295b5fcvma: connecting
2026-02-06 17:30:28.483 [TRACE] [nding.tuya.internal.local.TuyaDevice] - bf20162b0e49295b5fcvma/192.168.1.56:6668: Failed to connect: connection timed out after 1000 ms: /192.168.1.56:6668
2026-02-06 17:30:29.296 [TRACE] [nding.tuya.internal.local.TuyaDevice] - bf20162b0e49295b5fcvma/192.168.1.56:6668: Failed to connect: connection timed out after 1000 ms: /192.168.1.56:6668
2026-02-06 17:30:29.471 [TRACE] [nding.tuya.internal.local.TuyaDevice] - bf20162b0e49295b5fcvma/192.168.1.56:6668: Failed to connect: connection timed out after 1000 ms: /192.168.1.56:6668
2026-02-06 17:30:29.483 [TRACE] [nding.tuya.internal.local.TuyaDevice] - bf20162b0e49295b5fcvma: connecting
2026-02-06 17:30:30.297 [TRACE] [nding.tuya.internal.local.TuyaDevice] - bf20162b0e49295b5fcvma: connecting
2026-02-06 17:30:30.472 [TRACE] [nding.tuya.internal.local.TuyaDevice] - bf20162b0e49295b5fcvma: connecting
2026-02-06 17:30:30.485 [TRACE] [nding.tuya.internal.local.TuyaDevice] - bf20162b0e49295b5fcvma/192.168.1.56:6668: Failed to connect: connection timed out after 1000 ms: /192.168.1.56:6668

Wikibear · February 6, 2026, 9:43pm

I have two devices they are same. Blinds for my windows battery powered. They have a distance round about 1m. One blind device working without issue and the other not. An I have no clue why.

krishgcek · February 7, 2026, 9:57am

I also have similar issues. I am using a separate server with fast api and tinytuya and read current, voltage and power of the socket, then the results are also updated in openhab.

mjagdis · February 7, 2026, 12:41pm

Ledvance Smart+ Matter led bulb

That’s a Matter device not a Tuya device. There is no local Tuya API. You have to talk to it via Matter.

DiegoGR · February 7, 2026, 1:09pm

The problem is that I don’t manage to discover using Matter OH Binding, whatever I have tried. This is the first I tried.

After getting bored with Matter, I uninstalled from Smart+ Android App and tried to link with Tuya Smart App, and It worked! I generate a Matter code with Smart +, and discovered with Tuya App, which asked for the matter code. Now it is included in my Tuya Project and it is discovered by OH Tuya Binding, but it is always in this “land of nowhere state” with status Online and message “Waiting for device wake up”

I guess that as it is an WIFI equipment, besides Matter, TUYA should bind it…or not?.

Thanks

mjagdis · February 7, 2026, 9:57pm

No. The Tuya binding only implements the local Tuya API. It does not implement a Matter API. The binding discovers the device because it is listed by your Tuya Project but has no way to talk to it. Hoping that it will work because the underlying transport is WiFi is like putting diesel in your petrol car and hoping it will work because it uses an engine.

DiegoGR · February 8, 2026, 8:59am

Thanks Mike

Now I fully understand. I shall try again with Matter Binding.

Regards

Diego

Ruben_Perez · February 12, 2026, 4:45pm

I am not sure if you have commented that, I have the same problem. I have 3 ceiling fans that works correctly, and two heaters that not. Just watching on Tuya Developer Plattform, the Devices that doesn’t work are the ones that appears as “Controllable” in Device Permisions, and the devices that work are “Read”. And also, The Read ones can be changed, but not from “Controllable” to Read…