My setup:
- Raspberry 5 with Openhabian
- Openhab 5.1.3
- Tuya Binding 5.1.3
For controlling an air conditioner without WLAN, I have bought a IR module based on Tuya. Following the instructions I configured the Tuya binding, which was working well up to the point where channels should be discovered. I have three new things now:
- The Tuya project
- The physical device (“Intelligent IR”)
- A subdevice (“Air Conditioner”), resulting from the training with the original remote control
All things are reported “online”, but for none of them any channels are discovered.
The communication seems to be ok, in the logs (on DEBUG) I can see that there is ongoing communication
2026-06-04 09:44:25.514 [DEBUG] [b.binding.tuya.internal.local.handlers.TuyaDecoder] - udpListener: Received MessageWrapper{commandType=REQ_DEVINFO, content='om":"app","ip":"192.168.2.191"}'}
On startup I can see that the binding seems to query the channels, but fails
2026-06-04 08:49:24.969 [DEBUG] [b.binding.tuya.internal.local.handlers.TuyaDecoder] - udpListener: Received MessageWrapper{commandType=REQ_DEVINFO, content='om":"app","ip":"192.168.2.191"}'}
2026-06-04 08:49:28.088 [DEBUG] [ab.binding.tuya.internal.handler.TuyaDeviceHandler] - bf5bdd4476c876a253c5rz: no status DPs - polling disabled
2026-06-04 08:49:28.099 [DEBUG] [org.openhab.binding.tuya.internal.local.TuyaDevice] - bf5bdd4476c876a253c5rz/192.168.2.92:6668: channel connected
2026-06-04 08:49:28.100 [DEBUG] [b.binding.tuya.internal.local.handlers.TuyaEncoder] - bf5bdd4476c876a253c5rz/192.168.2.92:6668: Sending SESS_KEY_NEG_START, payload D80A502AECB9DC5ADAE7EBB2DC5557EE
2026-06-04 08:49:28.112 [DEBUG] [b.binding.tuya.internal.local.handlers.TuyaDecoder] - bf5bdd4476c876a253c5rz/192.168.2.92:6668: Received MessageWrapper{commandType=SESS_KEY_NEG_RESPONSE, content='[B@59a8f016'}
2026-06-04 08:49:28.113 [DEBUG] [b.binding.tuya.internal.local.handlers.TuyaEncoder] - bf5bdd4476c876a253c5rz/192.168.2.92:6668: Sending SESS_KEY_NEG_FINISH, payload 074D4C213EB3EAD61DFB5E3F7A555220902555446B03B6BB92EC8FFE76590FBB
2026-06-04 08:49:28.114 [DEBUG] [ab.binding.tuya.internal.handler.TuyaDeviceHandler] - bf5bdd4476c876a253c5rz: connected
2026-06-04 08:49:28.115 [DEBUG] [b.binding.tuya.internal.local.handlers.TuyaEncoder] - bf5bdd4476c876a253c5rz/192.168.2.92:6668: Sending DP_QUERY, payload {protocol=5, t=1780555768, data={ctype=0, dps=[], cid=bf5bdd4476c876a253c5rz}}
2026-06-04 08:49:28.131 [INFO ] [b.binding.tuya.internal.local.handlers.TuyaDecoder] - bf5bdd4476c876a253c5rz/192.168.2.92:6668: DP_QUERY not supported. Trying to request with CONTROL.
2026-06-04 08:49:28.132 [DEBUG] [b.binding.tuya.internal.local.handlers.TuyaDecoder] - bf5bdd4476c876a253c5rz/192.168.2.92:6668: Received MessageWrapper{commandType=DP_QUERY_NOT_SUPPORTED, content='{}'}
2026-06-04 08:49:28.133 [DEBUG] [ab.binding.tuya.internal.handler.TuyaDeviceHandler] - 'tuya:tuyaDevice:bf5bdd4476c876a253c5rz' switching to control instead of query
2026-06-04 08:49:28.134 [DEBUG] [b.binding.tuya.internal.local.handlers.TuyaEncoder] - bf5bdd4476c876a253c5rz/192.168.2.92:6668: Sending CONTROL_NEW, payload {protocol=5, t=1780555768, data={ctype=0, dps={}, cid=bf5bdd4476c876a253c5rz}}
2026-06-04 08:49:28.146 [DEBUG] [b.binding.tuya.internal.local.handlers.TuyaDecoder] - bf5bdd4476c876a253c5rz/192.168.2.92:6668: Received MessageWrapper{commandType=CONTROL_NEW, content=''}
So I tried to create the channel manually based on the commands and states I have found on the device debug page of the Tuya project, but failed completely. I have tried both Standard and DP Instructions, but without any success.
Any suggestions how to proceed? I’m lost 
Looking on the Tuya side I can see that all calls to GET:/v1.1/devices/{device_id}/specifications are reported as failed. But no further information, e.g. if it is a 4XX or 5XX HTTP Status Code. Also the DEBUG logs in Openhab are giving no hint.