Cannot pair Tuya devices anymore

deCONZ General Support
1

Hello!
I’m using deCONZ for a two years now (~ 100 nodes) on a RPi3 with a Raspbee-II (0x26780700) without any major problems until now.

For some reason, I can’t pair Tuya-based devices anymore, although I’m already using some of them. I’ve tried to pair a new water irrigation valve (_TZE200_htnnfasr) and nothing happens. The device remains in pairing mode and nothing appears in the deCONZ-gui or Phoscon App.

I’ve already tried without Source Routing and even moved the new device next to the RPi.

I’m already using the same kind of device for several months without any problems in initial pairing and daily usage.

First I thought the valve could be defective and therefore I’ve bought a different model (RTX ZVG1) which should be supported. But it shows the same behaviour.

In the meantime, I have paired a few Hue bulbs without any problems and the remaining devices also work flawlessly, even the Tuya-based ones. So the problem shouldn’t be hardware related.

I’ve tried to gather relevant debug logs but can’t see the main problem. Maybe someone can spot the problem?

deCONZ version is 2.21.2

06:17:04:436 poll node 00:17:88:01:08:47:d6:b3-0b
06:17:04:437 Poll light node WZ-E7
06:17:04:996 APS-DATA.indication srcAddr: 0xc8e4, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8001, lqi: 255, rssi: -73
06:17:05:138 APS-DATA.indication srcAddr: 0x5f13, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x0013, lqi: 255, rssi: -68
06:17:05:139 0x390B nwk changed to 0x5F13
06:17:05:140 device announce 0x84BA20FFFE323BFB (0x5F13) mac capabilities 0x80
06:17:05:140 set fast probe address to 0x84BA20FFFE323BFB (0x5F13)
06:17:05:141 FP indication 0x0000 / 0x0013 (0x84BA20FFFE323BFB / 0x5F13)
06:17:05:141                       ...     (0x84BA20FFFE323BFB / 0x5F13)
06:17:05:141 device announce 0x84BA20FFFE323BFB (0x5F13) mac capabilities 0x80
06:17:05:141 DEV Tick.Join: event/device.anounce
06:17:05:142 DEV Tick: fast poll 0x84BA20FFFE323BFB, mac capabilities: 0x80
06:17:05:329 poll node 00:17:88:01:08:48:5f:89-0b
06:17:05:330 Poll light node WZ-E11
06:17:05:536 APS-DATA.indication srcAddr: 0x324b, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0019, lqi: 255, rssi: -48
06:17:05:537 0xA4C13800AA204DE3: update ZCL value 0x01/0x0019/0x1000 after 0 s
06:17:05:538 APS-DATA.request id: 172, addrmode: 0x03, addr: 0xa4c13800aa204de3, profile: 0x0104, cluster: 0x0019, ep: 0x01 -> 0x01 queue: 0 len: 4 tx.options 0x04
06:17:05:590 API error 3, /lights/65, resource, /lights/65, not available
06:17:05:626 APS-DATA.confirm id: 172, status: 0x00 SUCCESS
06:17:05:626 APS-DATA.confirm request id: 172 -> erase from queue
06:17:05:627 aps request id: 172 finished, erase from queue
06:17:06:006 [1] get node descriptor for 0x84ba20fffe323bfb
06:17:06:007 ZDP get node descriptor for 0x5F13
06:17:06:007 APS-DATA.request id: 174, addrmode: 0x03, addr: 0x84ba20fffe323bfb, profile: 0x0000, cluster: 0x0002, ep: 0x00 -> 0x00 queue: 0 len: 3 tx.options 0x00
06:17:06:169 poll node 00:17:88:01:06:84:21:da-0b
06:17:06:170 Poll light node VG5
06:17:06:266 APS-DATA.confirm id: 174, status: 0x00 SUCCESS
06:17:06:266 APS-DATA.confirm request id: 174 -> confirmed, timeout 125957001
06:17:06:456 APS-DATA.indication srcAddr: 0x5f13, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8002, lqi: 232, rssi: -63
06:17:06:456 APS-DATA.indication request id: 174 -> finished
06:17:06:457 APS-DATA.request id: 174 erase from queue
06:17:06:457 DB pushZdpDescriptorDb()
06:17:06:457 DB save zll database items 0x00000881
06:17:06:458 DB sql exec UPDATE devices SET nwk = 24339 WHERE mac = '84:ba:20:ff:fe:32:3b:fb';INSERT INTO devices (mac,nwk,timestamp) SELECT '84:ba:20:ff:fe:32:3b:fb', 24339, strftime('%s','now') WHERE (SELECT changes() = 0);
06:17:06:476 DB saved in 18 ms
06:17:06:477 APS-DATA.request id: 178, addrmode: 0x02, addr: 0x5f13, profile: 0x0000, cluster: 0x0005, ep: 0x00 -> 0x00 queue: 0 len: 3 tx.options 0x00
06:17:06:478 FP indication 0x0000 / 0x8002 (0x84BA20FFFE323BFB / 0x5F13)
06:17:06:478                       ...     (0x84BA20FFFE323BFB / 0x5F13)
06:17:06:478 ZDP indication search sensors 0x84BA20FFFE323BFB (0x5F13) cluster 0x8002
06:17:06:479 ZDP indication search sensors 0x84BA20FFFE323BFB (0x5F13) clear timeout on cluster 0x8002
06:17:06:552 [2] get active endpoints for 0x84ba20fffe323bfb
06:17:06:553 ZDP get active endpoints for 0x5F13
06:17:06:555 APS-DATA.request id: 179, addrmode: 0x03, addr: 0x84ba20fffe323bfb, profile: 0x0000, cluster: 0x0005, ep: 0x00 -> 0x00 queue: 1 len: 3 tx.options 0x00
06:17:06:626 APS-DATA.confirm id: 178, status: 0x00 SUCCESS
06:17:06:627 APS-DATA.confirm request id: 178 -> confirmed, timeout 125957472
06:17:06:678 APS-DATA.confirm id: 179, status: 0x00 SUCCESS
06:17:06:678 APS-DATA.confirm request id: 179 -> confirmed, timeout 125957550
06:17:06:976 APS-DATA.indication srcAddr: 0x5f13, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8005, lqi: 255, rssi: -61
06:17:06:977 APS-DATA.indication request id: 178 -> finished
06:17:06:977 APS-DATA.request id: 178 erase from queue
06:17:06:978 FP indication 0x0000 / 0x8005 (0x84BA20FFFE323BFB / 0x5F13)
06:17:06:979                       ...     (0x84BA20FFFE323BFB / 0x5F13)
06:17:06:979 ZDP indication search sensors 0x84BA20FFFE323BFB (0x5F13) cluster 0x8005
06:17:06:980 ZDP indication search sensors 0x84BA20FFFE323BFB (0x5F13) clear timeout on cluster 0x8005
06:17:07:008 Daylight now: goldenHour1, status: 160, daylight: 1, dark: 0
06:17:07:045 poll node 00:17:88:01:08:3d:ac:57-0b
06:17:07:048 Poll light node WZ-W5
06:17:07:196 APS-DATA.indication srcAddr: 0x5f13, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8005, lqi: 255, rssi: -70
06:17:07:196 APS-DATA.indication request id: 179 -> finished
06:17:07:197 APS-DATA.request id: 179 erase from queue
06:17:07:197 FP indication 0x0000 / 0x8005 (0x84BA20FFFE323BFB / 0x5F13)
06:17:07:197                       ...     (0x84BA20FFFE323BFB / 0x5F13)
06:17:07:198 ZDP indication search sensors 0x84BA20FFFE323BFB (0x5F13) cluster 0x8005
06:17:07:506 Skip idle timer callback, too early: elapsed 949 msec
06:17:07:948 poll node a4:c1:38:00:aa:20:4d:e3-01
06:17:07:949 Poll light node GHecke
06:17:08:556 APS-DATA.indication srcAddr: 0x5f13, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x0002, lqi: 240, rssi: -70
06:17:08:556 APS-DATA.request id: 194, addrmode: 0x02, addr: 0x5f13, profile: 0x0000, cluster: 0x8002, ep: 0x00 -> 0x00 queue: 0 len: 17 tx.options 0x04
06:17:08:606 skip verify rule Rule ON for sensor 00:00:00:00:01:76:96:12-f2 (available = 0, node = (nil), sensorNode = (nil))
06:17:08:676 APS-DATA.confirm id: 194, status: 0x00 SUCCESS
06:17:08:676 aps request id: 194 finished, erase from queue
06:17:08:706 skip verify rule Rule OFF for sensor 00:00:00:00:01:76:96:12-f2 (available = 0, node = (nil), sensorNode = (nil))
06:17:08:832 poll node 00:17:88:01:08:41:3c:b2-0b
06:17:08:832 Poll light node WZ-E3
06:17:09:556 APS-DATA.indication srcAddr: 0x6a86, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x000C, lqi: 255, rssi: -70
06:17:09:557 54:ef:44:10:00:62:81:ef-01-000c/state/airqualityppb expression: Item.val = Attr.val --> 243
06:17:09:558 [INFO] - No button map for: lumi.airmonitor.acn01, unicast to: 0x0000, endpoint: 0x01, cluster: 0x000C, command: 0x0A, payload: 55003900007343, zclSeq: 79
06:17:09:558 ZCL attribute report 0x54EF4410006281EF for cluster: 0x000C, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
06:17:09:559 	payload: 55003900007343
06:17:09:559 Websocket 192.168.37.200:60072 send message: {"attr":{"id":"30","lastannounced":null,"lastseen":"2023-06-15T04:17Z","manufacturername":"LUMI","modelid":"lumi.airmonitor.acn01","name":"DG-Temp-Bad","swversion":"0.0.0_0029","type":"ZHAAirQuality","uniqueid":"54:ef:44:10:00:62:81:ef-01-000c"},"e":"changed","id":"30","r":"sensors","t":"event","uniqueid":"54:ef:44:10:00:62:81:ef-01-000c"} (ret = -1097822472)
06:17:09:560 Websocket 192.168.37.216:52868 send message: {"attr":{"id":"30","lastannounced":null,"lastseen":"2023-06-15T04:17Z","manufacturername":"LUMI","modelid":"lumi.airmonitor.acn01","name":"DG-Temp-Bad","swversion":"0.0.0_0029","type":"ZHAAirQuality","uniqueid":"54:ef:44:10:00:62:81:ef-01-000c"},"e":"changed","id":"30","r":"sensors","t":"event","uniqueid":"54:ef:44:10:00:62:81:ef-01-000c"} (ret = -1097822472)
06:17:09:561 Websocket 192.168.37.200:60072 send message: {"e":"changed","id":"30","r":"sensors","state":{"airquality":"moderate","airqualityppb":243,"lastupdated":"2023-06-15T04:17:09.557"},"t":"event","uniqueid":"54:ef:44:10:00:62:81:ef-01-000c"} (ret = -1097822472)
06:17:09:562 Websocket 192.168.37.216:52868 send message: {"e":"changed","id":"30","r":"sensors","state":{"airquality":"moderate","airqualityppb":243,"lastupdated":"2023-06-15T04:17:09.557"},"t":"event","uniqueid":"54:ef:44:10:00:62:81:ef-01-000c"} (ret = -1097822472)
06:17:09:563 Websocket 192.168.37.200:60072 send message: {"attr":{"id":"29","lastannounced":null,"lastseen":"2023-06-15T04:17Z","manufacturername":"LUMI","modelid":"lumi.airmonitor.acn01","name":"DG-Temp-Bad","swversion":"0.0.0_0029","type":"ZHAHumidity","uniqueid":"54:ef:44:10:00:62:81:ef-01-0405"},"e":"changed","id":"29","r":"sensors","t":"event","uniqueid":"54:ef:44:10:00:62:81:ef-01-0405"} (ret = -1097822472)
06:17:09:564 Websocket 192.168.37.216:52868 send message: {"attr":{"id":"29","lastannounced":null,"lastseen":"2023-06-15T04:17Z","manufacturername":"LUMI","modelid":"lumi.airmonitor.acn01","name":"DG-Temp-Bad","swversion":"0.0.0_0029","type":"ZHAHumidity","uniqueid":"54:ef:44:10:00:62:81:ef-01-0405"},"e":"changed","id":"29","r":"sensors","t":"event","uniqueid":"54:ef:44:10:00:62:81:ef-01-0405"} (ret = -1097822472)
06:17:09:565 Websocket 192.168.37.200:60072 send message: {"attr":{"id":"28","lastannounced":null,"lastseen":"2023-06-15T04:17Z","manufacturername":"LUMI","modelid":"lumi.airmonitor.acn01","name":"DG-Temp-Bad","swversion":"0.0.0_0029","type":"ZHATemperature","uniqueid":"54:ef:44:10:00:62:81:ef-01-0402"},"e":"changed","id":"28","r":"sensors","t":"event","uniqueid":"54:ef:44:10:00:62:81:ef-01-0402"} (ret = -1097822472)
06:17:09:566 Websocket 192.168.37.216:52868 send message: {"attr":{"id":"28","lastannounced":null,"lastseen":"2023-06-15T04:17Z","manufacturername":"LUMI","modelid":"lumi.airmonitor.acn01","name":"DG-Temp-Bad","swversion":"0.0.0_0029","type":"ZHATemperature","uniqueid":"54:ef:44:10:00:62:81:ef-01-0402"},"e":"changed","id":"28","r":"sensors","t":"event","uniqueid":"54:ef:44:10:00:62:81:ef-01-0402"} (ret = -1097822472)
06:17:09:673 poll node 00:17:88:01:09:b1:6b:c8-0b
06:17:09:673 Poll light node LWaU
06:17:10:366 APS-DATA.indication srcAddr: 0x5f13, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0000, lqi: 255, rssi: -70
06:17:10:367 Node data 0x84ba20fffe323bfb profileId: 0x0104, clusterId: 0x0000
06:17:10:370 FP indication 0x0104 / 0x0000 (0x84BA20FFFE323BFB / 0x5F13)
06:17:10:371                       ...     (0x84BA20FFFE323BFB / 0x5F13)
06:17:10:372 ZCL attribute report 0x84BA20FFFE323BFB for cluster: 0x0000, ep: 0x01, frame control: 0x08, mfcode: 0x0000 
06:17:10:372 	payload: 01002048e2ff201fe4ff2000
06:17:10:373 APS-DATA.request id: 204, addrmode: 0x02, addr: 0x5f13, profile: 0x0104, cluster: 0x0000, ep: 0x01 -> 0x01 queue: 0 len: 5 tx.options 0x04
06:17:10:454 APS-DATA.confirm id: 204, status: 0x00 SUCCESS
06:17:10:455 APS-DATA.confirm request id: 204 -> erase from queue
06:17:10:457 aps request id: 204 finished, erase from queue
06:17:10:496 APS-DATA.indication srcAddr: 0x5f13, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0000, lqi: 255, rssi: -70
06:17:10:497 Node data 0x84ba20fffe323bfb profileId: 0x0104, clusterId: 0x0000
06:17:10:500 FP indication 0x0104 / 0x0000 (0x84BA20FFFE323BFB / 0x5F13)
06:17:10:501                       ...     (0x84BA20FFFE323BFB / 0x5F13)
06:17:10:502 ZCL attribute report 0x84BA20FFFE323BFB for cluster: 0x0000, ep: 0x01, frame control: 0x08, mfcode: 0x0000 
06:17:10:502 	payload: dfff420ae7681d2c12e8681d2c12
06:17:10:503 APS-DATA.request id: 207, addrmode: 0x02, addr: 0x5f13, profile: 0x0104, cluster: 0x0000, ep: 0x01 -> 0x01 queue: 0 len: 5 tx.options 0x04
06:17:10:554 poll node 00:17:88:01:08:4b:de:27-0b
06:17:10:555 Poll light node WZ-B5
06:17:10:586 APS-DATA.confirm id: 207, status: 0x00 SUCCESS
06:17:10:589 APS-DATA.confirm request id: 207 -> erase from queue
06:17:10:601 aps request id: 207 finished, erase from queue
06:17:11:016 APS-DATA.indication srcAddr: 0x5f13, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0xEF00, lqi: 255, rssi: -70
06:17:11:017 FP indication 0x0104 / 0xEF00 (0x84BA20FFFE323BFB / 0x5F13)
06:17:11:017                       ...     (0x84BA20FFFE323BFB / 0x5F13)
06:17:11:017 APS-DATA.request id: 212, addrmode: 0x02, addr: 0x5f13, profile: 0x0104, cluster: 0xEF00, ep: 0x01 -> 0x01 queue: 0 len: 5 tx.options 0x04
06:17:11:156 APS-DATA.confirm id: 212, status: 0x00 SUCCESS
06:17:11:156 APS-DATA.confirm request id: 212 -> erase from queue
06:17:11:157 aps request id: 212 finished, erase from queue
06:17:11:226 APS-DATA.indication srcAddr: 0x5f13, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0xEF00, lqi: 255, rssi: -70
06:17:11:227 FP indication 0x0104 / 0xEF00 (0x84BA20FFFE323BFB / 0x5F13)
06:17:11:228                       ...     (0x84BA20FFFE323BFB / 0x5F13)
06:17:11:229 APS-DATA.request id: 215, addrmode: 0x02, addr: 0x5f13, profile: 0x0104, cluster: 0xEF00, ep: 0x01 -> 0x01 queue: 0 len: 5 tx.options 0x04
06:17:11:356 APS-DATA.confirm id: 215, status: 0x00 SUCCESS
06:17:11:356 APS-DATA.confirm request id: 215 -> erase from queue
06:17:11:396 APS-DATA.indication srcAddr: 0x5f13, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0xEF00, lqi: 255, rssi: -70
06:17:11:397 APS-DATA.request id: 215 erase from queue
06:17:11:397 FP indication 0x0104 / 0xEF00 (0x84BA20FFFE323BFB / 0x5F13)
06:17:11:398                       ...     (0x84BA20FFFE323BFB / 0x5F13)
06:17:11:398 APS-DATA.request id: 218, addrmode: 0x02, addr: 0x5f13, profile: 0x0104, cluster: 0xEF00, ep: 0x01 -> 0x01 queue: 0 len: 5 tx.options 0x04
06:17:11:446 poll node 00:17:88:01:09:6c:70:e7-0b
06:17:11:447 Poll light node WZ-K1
06:17:11:507 Wait 4s till query finished
06:17:11:576 APS-DATA.confirm id: 218, status: 0x00 SUCCESS
06:17:11:576 APS-DATA.confirm request id: 218 -> erase from queue
06:17:11:606 APS-DATA.indication srcAddr: 0x5f13, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0xEF00, lqi: 255, rssi: -70
06:17:11:606 APS-DATA.request id: 218 erase from queue
06:17:11:607 FP indication 0x0104 / 0xEF00 (0x84BA20FFFE323BFB / 0x5F13)
06:17:11:607                       ...     (0x84BA20FFFE323BFB / 0x5F13)
06:17:11:608 APS-DATA.request id: 221, addrmode: 0x02, addr: 0x5f13, profile: 0x0104, cluster: 0xEF00, ep: 0x01 -> 0x01 queue: 0 len: 5 tx.options 0x04
06:17:11:970 APS-DATA.confirm id: 221, status: 0x00 SUCCESS
06:17:11:971 APS-DATA.confirm request id: 221 -> erase from queue
06:17:12:006 APS-DATA.indication srcAddr: 0x5f13, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0xEF00, lqi: 255, rssi: -71
06:17:12:007 APS-DATA.request id: 221 erase from queue
06:17:12:007 FP indication 0x0104 / 0xEF00 (0x84BA20FFFE323BFB / 0x5F13)
06:17:12:008                       ...     (0x84BA20FFFE323BFB / 0x5F13)
06:17:12:008 APS-DATA.request id: 224, addrmode: 0x02, addr: 0x5f13, profile: 0x0104, cluster: 0xEF00, ep: 0x01 -> 0x01 queue: 0 len: 5 tx.options 0x04
06:17:12:010 saved node state in 0 ms
06:17:12:011 sync() in 0 ms
06:17:12:060 GW firmware version: 0x26780700
06:17:12:176 APS-DATA.confirm id: 224, status: 0x00 SUCCESS
06:17:12:176 APS-DATA.confirm request id: 224 -> erase from queue
06:17:12:186 aps request id: 224 finished, erase from queue
06:17:12:218 APS-DATA.indication srcAddr: 0x5f13, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x000A, lqi: 255, rssi: -70
06:17:12:220 APS-DATA.request id: 227, addrmode: 0x02, addr: 0x5f13, profile: 0x0104, cluster: 0x000A, ep: 0x01 -> 0x01 queue: 0 len: 11 tx.options 0x00
06:17:12:221 FP indication 0x0104 / 0x000A (0x84BA20FFFE323BFB / 0x5F13)
06:17:12:222                       ...     (0x84BA20FFFE323BFB / 0x5F13)
06:17:12:296 APS-DATA.confirm id: 227, status: 0x00 SUCCESS
06:17:12:296 APS-DATA.confirm request id: 227 -> erase from queue
06:17:12:332 poll node 00:17:88:01:08:4a:78:ed-0b
06:17:12:332 Poll light node WZ-E6
06:17:12:339 aps request id: 227 finished, erase from queue
06:17:12:506 Wait 3s till query finished
06:17:13:174 poll node 00:17:88:01:08:44:45:2e-0b
06:17:13:175 Poll light node WZ-B4
06:17:13:506 Wait 2s till query finished
06:17:14:006 poll node 00:17:88:01:06:84:16:ac-0b
06:17:14:007 Poll light node VG3
06:17:14:506 Wait 1s till query finished
06:17:14:896 poll node 00:17:88:01:08:41:36:e4-0b
06:17:14:897 Poll light node WZ-B2
06:17:15:406 Tuya Time sync request: 0x84ba20fffe323bfb
06:17:15:407 Send Tuya command 0x24, data: 0066648a90cb648aaceb
06:17:15:407 add task 580228 type 41 to 0x84BA20FFFE323BFB cluster 0xEF00 req.id 240
06:17:15:408 FP indication 0x0104 / 0xEF00 (0x84BA20FFFE323BFB / 0x5F13)
06:17:15:408                       ...     (0x84BA20FFFE323BFB / 0x5F13)
06:17:15:486 Erase task req-id: 240, type: 41 zcl seqno: 98 send time 0, profileId: 0x0104, clusterId: 0xEF00
06:17:15:507 poll node 00:17:88:01:0b:b3:8e:42-0b
2

Can you share a screenshot of your deconz gui?

3

Where did you find that this model is supported. AFAIK there is no DDF officially distributed at this time that support all the various clones ( "_TZE200_81isopgh", "_TZE200_akjefhj5") : RTX ZVG1 smart water valve · Issue #5248 · dresden-elektronik/deconz-rest-plugin · GitHub

How can you be sure that it’s this model and not a clone with another manufacturername if you can’t pair it ?

1 Like
4

It’s not the same thing.
You can have device not included in the API (or phoscon), but not visible in deconz (the GUI) it’s another story

06:17:06:006 [1] get node descriptor for 0x84ba20fffe323bfb
06:17:06:552 [2] get active endpoints for 0x84ba20fffe323bfb

I can be wrong, but if you can see this debug line it mean the device is visible on deconz (and not yet in the API, the device can be unsupported)

5

Well, I’ve got another identical device (same seller, I’ve actually bought two devices at the same time) which was paired a year ago (_htnnfasr) without any problems.

Regarding the RTX valve, okay, I might be wrong about support but shouldn’t pairing work anyway?

6

Here are the network settings:

image
image947×576 93.7 KB

… and my current nodes:

image
image1077×772 107 KB

7

But I can’t see the device anywhere, neither in the GUI, nor in the API or the zll.db.

Anyway, I’ve also tried to pair with a different kind of valve (_htnnfasr) and the behaviour remains the same: No device visible in either API or GUI, although I’ve already paired a similar device a year ago (which still works without any problems).

8

Strange because you have this in log :

06:17:06:457 DB pushZdpDescriptorDb()
06:17:06:457 DB save zll database items 0x00000881
06:17:06:458 DB sql exec UPDATE devices SET nwk = 24339 WHERE mac = '84:ba:20:ff:fe:32:3b:fb';INSERT INTO devices (mac,nwk,timestamp) SELECT '84:ba:20:ff:fe:32:3b:fb', 24339, strftime('%s','now') WHERE (SELECT changes() = 0);
06:17:06:476 DB saved in 18 ms
9

Oh, missed that, sorry :wink:
But it didn’t create a corresponding node for the new device. I’ve only found the old one in the DB:

"30934045"	"84:71:27:ff:fe:d3:21:ef-01"	"73"	"normal"	"GVentilGarten"	""	"1"	"TS0601"	"_TZE200_htnnfasr"	""	"{""attr/id"":""73"",""attr/lastannounced"":null,""attr/lastseen"":""2023-06-14T20:58Z"",""attr/manufacturername"":""_TZE200_htnnfasr"",""attr/modelid"":""TS0601"",""attr/name"":""GVentilGarten"",""attr/swversion"":null,""attr/type"":""On/Off output"",""attr/uniqueid"":""84:71:27:ff:fe:d3:21:ef-01"",""state/on"":false,""state/reachable"":true}"

Maybe my installation somehow fails to process any (or a specific) DDF file?

image
image752×544 31.1 KB

In my /usr/share/deCONZ/devices/tuya folder, a file named _TZE200_htnnfasr_water_valve.json (dated 03-31-2023) exists:

{
  "schema": "devcap1.schema.json",
  "manufacturername": "_TZE200_htnnfasr",
  "modelid": "TS0601",
  "vendor": "LIDL",
  "product": "Smart watering timer",
  "sleeper": false,
  "status": "Gold",
  "subdevices": [
    {
      "type": "$TYPE_ON_OFF_OUTPUT",
      "restapi": "/lights",
      "uuid": [
        "$address.ext",
        "0x01"
      ],
      "items": [
        {
          "name": "attr/id"
        },
        {
          "name": "attr/lastannounced"
        },
        {
          "name": "attr/lastseen"
        },
        {
          "name": "attr/manufacturername"
        },
        {
          "name": "attr/modelid"
        },
        {
          "name": "attr/name"
        },
        {
          "name": "attr/swversion"
        },
        {
          "name": "attr/type"
        },
        {
          "name": "attr/uniqueid"
        },
        {
          "name": "state/on",
          "refresh.interval": 300,
          "read": {
            "fn": "tuya"
          },
          "write": {
            "dpid": 1,
            "dt": "0x10",
            "eval": "Item.val == 1 ? 1 : 0;",
            "fn": "tuya"
          },
          "parse": {
            "dpid": 1,
            "eval": "Item.val = Attr.val;",
            "fn": "tuya"
          },
	  "default": 0
        },
        {
          "name": "state/reachable"
        }
      ]
    },
    {
      "type": "$TYPE_OPEN_CLOSE_SENSOR",
      "restapi": "/sensors",
      "uuid": [
        "$address.ext",
        "0x01",
        "0x0500"
      ],
      "items": [
        {
          "name": "attr/id"
        },
        {
          "name": "attr/lastannounced"
        },
        {
          "name": "attr/lastseen"
        },
        {
          "name": "attr/manufacturername"
        },
        {
          "name": "attr/modelid"
        },
        {
          "name": "attr/name"
        },
        {
          "name": "attr/swversion"
        },
        {
          "name": "attr/type"
        },
        {
          "name": "attr/uniqueid"
        },
		{
          "name": "config/battery",
          "parse": {
            "dpid": 11,
            "eval": "Item.val = Attr.val;",
            "fn": "tuya"
          },
          "default": 100
        },
        {
          "name": "config/duration",
          "description": "The duration the valve stays open.",
          "write": {
            "dpid": 5,
            "dt": "0x2b",
            "eval": "Attr.val = Item.val;",
            "fn": "tuya"
          },
          "parse": {
            "dpid": 5,
            "eval": "Item.val = Attr.val;",
            "fn": "tuya"
          }
        },
        {
          "name": "config/locked",
          "description": "Read: frost lock status. Write: frost lock reset.",
          "write": {
            "dpid": 109,
            "dt": "0x10",
            "eval": "Item.val == 1 ? 1 : 0;",
            "fn": "tuya"
          },
          "parse": {
            "dpid": 108,
            "eval": "Item.val == 1 ? 0 : 1;",
            "fn": "tuya"
          },
          "default": 0
        },
        {
          "name": "config/reachable"
        },
        {
          "name": "state/lastupdated"
        },
        {
          "name": "state/seconds_remaining",
          "description": "The remaining time the valve is open in seconds.",
          "parse": {
            "dpid": 6,
            "eval": "Item.val = Attr.val * 60;",
            "fn": "tuya"
          }
        }
      ]
    }
  ],
  "bindings": [
    {
      "bind": "unicast",
      "src.ep": 1,
      "dst.ep": 1,
      "cl": "0x0006",
      "report": [
        {
          "at": "0x0000",
          "dt": "0x10",
          "min": 1,
          "max": 300
        }
      ]
    },
    {
      "bind": "unicast",
      "src.ep": 1,
      "dst.ep": 1,
      "cl": "0x0006",
      "report": [
        {
          "at": "0x0000",
          "dt": "0x10",
          "min": 1,
          "max": 300
        }
      ]
    }
  ]
}
10

Device are firstly visible in deconz, mean they are joined the zigbee network.
After that deconz make magic to include the device in the API (if supported)

So the first thing to have is the device visible in deconz.

Have you tried the panel “Node list” ? and searching with mac adress ?

1 Like
11

Ahh, okay. That wasn’t clear to me:

image
image1242×130 26.3 KB

Does this mean, a DDF for that device is needed? But in this case, I don’t even know the device name or anything, a potential DDF could refer to.

I was a little bit confused because in the past, Tuya devices got added anyway, even if they can’t be (correctly) controlled.

12

I’ve learned a lot :wink: Thanks anyone.

It was indeed “as easy” as following BabalsYou’s link: RTX ZVG1 smart water valve · Issue #5248 · dresden-elektronik/deconz-rest-plugin · GitHub

Creating a basic DDF worked for me.

To be more precise, that’s the DDF which is working fine for me: RTX ZVG1 smart water valve · Issue #5248 · dresden-elektronik/deconz-rest-plugin · GitHub

13

According to the “node list”, your device need to be visible in deconz (the GUI) but the inclusion was incomplete, incomplete in deconz, so in the API too.