Can't add devices to Phoscon anymore

Hi,

Everything has been working fine for ages, then all of a sudden, a few sensors stopped responding. Now I cannot re-discover any of these and I cannot add any new device. I’ve tried a few different lights and sensors. It just never finds anything when adding lights or sensors. Everything else that is still connected is working fine.

I tried: update, reboot, new batteries, new sensors, new smart plugs, etc

The deCONZ UI does seem to find something, but it’s like it’s not finishing the process and not adding it to Phoscon UI
image

Any ideas?

Let´s investigate.
I need a couple of information:
Firmware version, deCONZ version, native setup?,
If you run a ConBee II, you use an extension cable?
Can you please post a screenshot from the networksettings of your gateway from deCONZ? (find it under the smal mixer look like button in the upper panel)

Hi,

Thanks for helping.

Firmware is 26720700

I had been using the latest beta when I noticed the problem, v20.18. Then I tried rolling back to 20.17 and 20.16. Slightly different behaviors - in 20.16 the sensor would sometimes be found, but it would be the wrong model and the values would be wrong and it wouldn’t detect motion.

Docker setup
This is my compose file

version: "3.8"

services:

  deconz:
    image: deconzcommunity/deconz:2.17.01
    network_mode: host
    restart: always
    volumes:
      - /etc/localtime:/etc/localtime:ro    
      - ./deconz:/opt/deCONZ   # persistent configuration
    devices:
      - /dev/ttyAMA0:/dev/ttyAMA0 
    environment: 
      DECONZ_WEB_PORT: 80 
      DECONZ_WS_PORT: 443
      DECONZ_DEVICE: /dev/ttyAMA0 
      DECONZ_VNC_MODE: 1
      DECONZ_VNC_PORT: 5900
      DECONZ_NOVNC_PORT: 6080
      DECONZ_VNC_PASSWORD: "xxxxx"

I am using the Raspbee II HAT, not the ConBee II

Network Settings

Thanks again for helping out

How many routers VS sensors do you have?

I have 30+ Lights and smartplugs, 21 Sensors, and, 12 switches

Can you share some logs?

You can find out what logs and how in #deconz .

Might need to be more specific about the logs as there are thousands of lines in very short time.

Here is a sample that I think should include me enabling pairing and resetting the sensor. But I don’t know what lines I should be searching for

13:21:54:660 APS-DATA.request id: 213, addrmode: 0x02, addr: 0x1484, profile: 0x0104, cluster: 0x0702, ep: 0x01 -> 0x01 queue: 0 len: 5 tx.options 0x04
13:21:54:659 	payload: 000000257d0900000000
13:21:54:656 ZCL attribute report 0x70B3D52B6000F290 for cluster: 0x0702, ep: 0x01, frame control: 0x08, mfcode: 0x0000 
13:21:54:654 [INFO] - No button map for: TS011F, unicast to: 0x0000, endpoint: 0x01, cluster: 0x0702, command: 0x0A, payload: 000000257D0900000000, zclSeq: 239
13:21:54:650 	asdu: 08ef0a000000257d0900000000
13:21:54:647 APS-DATA.indication srcAddr: 0x1484, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0702, lqi: 255, rssi: -71
13:21:54:485 Poll light node Light 5 - Landing
13:21:54:483 poll node 00:15:8d:00:04:6f:5b:e6-01
13:21:54:473 skip create link for 0xD0B0 (lqi: 0) - 0x518D (lqi: 1)
13:21:54:470 skip create link for 0xD0B0 (lqi: 0) - 0x6344 (lqi: 0)
13:21:54:467 APS-DATA.request id: 209 erase from queue
13:21:54:465 APS-DATA.indication request id: 209 -> finished
13:21:54:464 	asdu: 01001e1203594c06ffff2e2100e65b6f04008d1500a2242500012f594c06ffff2e21001a9f6a22004b1200446325000200594c06ffff2e21008ca86a22004b12008d51a5000000
13:21:54:462 APS-DATA.indication srcAddr: 0xd0b0, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 255, rssi: -49
13:21:54:413 APS-DATA.confirm request id: 209 -> confirmed, timeout 99362550
13:21:54:412 APS-DATA.confirm id: 209, status: 0x00 SUCCESS
13:21:54:375 	asdu (length: 2): 0112
13:21:54:374 APS-DATA.request id: 209, addrmode: 0x03, addr: 0x70b3d52b6000f608, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
2x			
13:21:53:332 rule event /config/localtime: 13:21:51.400 -> 13:21:53.327 (1927ms)
13:21:53:331 Force read attributes for ZHASwitch SensorNode Switch - Landing
13:21:53:329 Idle timer triggered
13:21:53:328 Poll light node Jimmys Lamp
13:21:53:327 poll node 00:12:4b:00:22:d6:88:be-01
13:21:52:752 Poll light node Plug 9 - Grow PS
13:21:52:751 poll node 84:71:27:ff:fe:8d:95:76-01
13:21:52:326 Skip idle timer callback, too early: elapsed 926 msec
13:21:51:877 Poll light node Light 6 - Office Lamp
13:21:51:875 poll node 00:15:8d:00:02:d6:15:a3-01
13:21:51:400 rule event /config/localtime: 13:21:50.326 -> 13:21:51.400 (1074ms)
13:21:51:396 DB SELECT manufacturername FROM nodes WHERE mac LIKE '00:12:4b:00:21:f0:92:48%' COLLATE NOCASE: GLEDOPTO
13:21:51:393 sql exec SELECT manufacturername FROM nodes WHERE mac LIKE '00:12:4b:00:21:f0:92:48%' COLLATE NOCASE
13:21:51:390 Tuya debug 7 : Missing manufacture name for 0x00124b0021f09248
3x			
13:21:51:376 No Tuya productId entry found for manufacturername: _TZ3000_cphmq0q7
13:21:51:372 DB SELECT manufacturername FROM nodes WHERE mac LIKE '84:71:27:ff:fe:8d:97:ba%' COLLATE NOCASE: _TZ3000_cphmq0q7
13:21:51:368 sql exec SELECT manufacturername FROM nodes WHERE mac LIKE '84:71:27:ff:fe:8d:97:ba%' COLLATE NOCASE
13:21:51:365 Tuya debug 7 : Missing manufacture name for 0x847127fffe8d97ba
13:21:51:362 DB SELECT manufacturername FROM nodes WHERE mac LIKE '00:12:4b:00:22:72:c1:ca%' COLLATE NOCASE: GLEDOPTO
13:21:51:357 sql exec SELECT manufacturername FROM nodes WHERE mac LIKE '00:12:4b:00:22:72:c1:ca%' COLLATE NOCASE
13:21:51:354 Tuya debug 7 : Missing manufacture name for 0x00124b002272c1ca
3x			
13:21:51:339 No Tuya productId entry found for manufacturername: _TZ3000_cphmq0q7
13:21:51:334 DB SELECT manufacturername FROM nodes WHERE mac LIKE '84:71:27:ff:fe:8d:95:76%' COLLATE NOCASE: _TZ3000_cphmq0q7
13:21:51:331 sql exec SELECT manufacturername FROM nodes WHERE mac LIKE '84:71:27:ff:fe:8d:95:76%' COLLATE NOCASE
13:21:51:327 Tuya debug 7 : Missing manufacture name for 0x847127fffe8d9576
13:21:50:984 Poll light node Light 7 - Office Ceiling
13:21:50:982 poll node 00:17:88:01:09:24:67:08-0b
13:21:50:826 Daylight now: goldenHour1, status: 160, daylight: 1, dark: 0
13:21:50:634 APS-DATA.request id: 191 erase from queue
13:21:50:633 APS-DATA.indication request id: 191 -> finished
13:21:50:631 	asdu: 00001e0f03594c06ffff2e21004892f021004b1200705025010375594c06ffff2e210076958dfeff277184e21d2501019f594c06ffff2e2100ba8ee922004b1200e28d25010401
13:21:50:629 APS-DATA.indication srcAddr: 0xd0b0, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 255, rssi: -49
13:21:50:572 APS-DATA.confirm request id: 191 -> confirmed, timeout 99358711
13:21:50:571 APS-DATA.confirm id: 191, status: 0x00 SUCCESS
13:21:50:536 	asdu (length: 2): 000f
13:21:50:534 APS-DATA.request id: 191, addrmode: 0x03, addr: 0x70b3d52b6000f608, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
13:21:50:327 rule event /config/localtime: 13:21:49.326 -> 13:21:50.326 (1000ms)
13:21:50:146 Poll light node Siren 2 - Kitchen
13:21:50:144 poll node 5c:02:72:ff:fe:e7:ab:df-01
3x			
13:21:49:422 Websocket 10.0.0.101:56618 send message: {"attr":{"id":"21","lastannounced":"2022-05-29T14:01:31Z","lastseen":"2022-09-16T12:21Z","manufacturername":"_TZ3000_cphmq0q7","modelid":"TS011F","name":"Plug 9 - Grow PS","swversion":"67","type":"On/Off plug-in unit","uniqueid":"84:71:27:ff:fe:8d:95:76-01"},"e":"changed","id":"21","r":"lights","t":"event","uniqueid":"84:71:27:ff:fe:8d:95:76-01"} (ret = 348)
13:21:49:420 	payload: 01002043
13:21:49:419 ZCL attribute report 0x847127FFFE8D9576 for cluster: 0x0000, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
13:21:49:418 [INFO] - No button map for: TS011F, unicast to: 0x0000, endpoint: 0x01, cluster: BASIC (0x0000), command: 0x0A, payload: 01002043, zclSeq: 29
2x			
13:21:49:414 Update Sensor 0x847127FFFE8D9576 Basic Cluster
13:21:49:413 Node data 0x847127fffe8d9576 profileId: 0x0104, clusterId: 0x0000
13:21:49:412 	asdu: 181d0a01002043
13:21:49:410 APS-DATA.indication srcAddr: 0x1de2, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0000, lqi: 255, rssi: -41
13:21:49:327 rule event /config/localtime: 13:21:48.326 -> 13:21:49.326 (1000ms)
13:21:49:253 Poll light node Mossys Lamp
13:21:49:250 poll node 00:12:4b:00:22:d6:86:ec-01
3x			
13:21:48:496 Websocket 10.0.0.101:56618 send message: {"e":"changed","id":"29","r":"sensors","state":{"current":0,"lastupdated":"2022-09-16T12:21:48.491","power":0,"voltage":234},"t":"event","uniqueid":"84:71:27:ff:fe:8d:95:76-01-0b04"} (ret = 182)
13:21:48:495 	payload: 050521ea00
13:21:48:494 ZCL attribute report 0x847127FFFE8D9576 for cluster: 0x0B04, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
13:21:48:492 [INFO] - No button map for: TS011F, unicast to: 0x0000, endpoint: 0x01, cluster: 0x0B04, command: 0x0A, payload: 050521EA00, zclSeq: 28
13:21:48:490 0x847127FFFE8D9576: update ZCL value 0x01/0x0B04/0x0505 after 0 s
13:21:48:488 Node data 0x847127fffe8d9576 profileId: 0x0104, clusterId: 0x0B04
13:21:48:486 	asdu: 181c0a050521ea00
13:21:48:485 APS-DATA.indication srcAddr: 0x1de2, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0B04, lqi: 255, rssi: -41
13:21:48:389 Poll ZHAPower sensor node Power 7
13:21:48:388 poll node 84:71:27:ff:fe:8d:97:ba-01-0b04
13:21:48:326 rule event /config/localtime: 13:21:47.326 -> 13:21:48.326 (1000ms)
13:21:47:550 Poll ZHAPower sensor node Power 29
13:21:47:548 poll node 84:71:27:ff:fe:8d:95:76-01-0b04
13:21:47:326 rule event /config/localtime: 13:21:46.326 -> 13:21:47.326 (1000ms)
13:21:46:788 APS-DATA.request id: 172 erase from queue
13:21:46:787 APS-DATA.indication request id: 172 -> finished
13:21:46:786 	asdu: ff001e0c03594c06ffff2e2100ec86d622004b120084002500002f594c06ffff2e21009bb2e7feff72025c3e8f25010301594c06ffff2e2100ba978dfeff2771848b4ba501012f
13:21:46:784 APS-DATA.indication srcAddr: 0xd0b0, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 255, rssi: -49
13:21:46:737 APS-DATA.confirm request id: 172 -> confirmed, timeout 99354873
13:21:46:735 APS-DATA.confirm id: 172, status: 0x00 SUCCESS
13:21:46:697 	asdu (length: 2): ff0c
13:21:46:695 APS-DATA.request id: 172, addrmode: 0x03, addr: 0x70b3d52b6000f608, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
13:21:46:681 Poll ZHAConsumption sensor node Consumption 28
13:21:46:679 poll node 84:71:27:ff:fe:8d:95:76-01-0702
13:21:46:327 rule event /config/localtime: 13:21:45.326 -> 13:21:46.326 (1000ms)
3x			
13:21:46:225 Websocket 10.0.0.101:56618 send message: {"e":"changed","id":"90","r":"sensors","state":{"consumption":9750,"lastupdated":"2022-09-16T12:21:46.225"},"t":"event","uniqueid":"70:b3:d5:2b:60:00:f1:4e-01-0702"} (ret = 165)
13:21:46:223 	asdu: 18a00100000025cf0300000100
13:21:46:221 APS-DATA.indication srcAddr: 0xf456, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0702, lqi: 255, rssi: -43
13:21:46:214 aps request id: 168 finished, erase from queue
13:21:46:190 APS-DATA.confirm request id: 168 -> erase from queue
13:21:46:188 APS-DATA.confirm id: 168, status: 0x00 SUCCESS
3x			
13:21:46:146 Websocket 10.0.0.101:56618 send message: {"e":"changed","id":"89","r":"sensors","state":{"current":384,"lastupdated":"2022-09-16T12:21:46.123","power":78,"voltage":235},"t":"event","uniqueid":"70:b3:d5:2b:60:00:f1:4e-01-0b04"} (ret = 185)
13:21:46:143 	asdu (length: 5): 10a0000000
13:21:46:141 APS-DATA.request id: 168, addrmode: 0x03, addr: 0x70b3d52b6000f14e, profile: 0x0104, cluster: 0x0702, ep: 0x01 -> 0x01 queue: 0 len: 5 tx.options 0x00
13:21:46:120 APS-DATA.request id: 164 erase from queue
13:21:46:119 	asdu: 189f0105050021eb00
13:21:46:118 APS-DATA.indication srcAddr: 0xf456, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0B04, lqi: 255, rssi: -43
13:21:46:099 APS-DATA.confirm request id: 164 -> erase from queue
13:21:46:097 APS-DATA.confirm id: 164, status: 0x00 SUCCESS
13:21:46:086 	asdu: 189e0701000000
13:21:46:085 APS-DATA.indication srcAddr: 0xf456, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0006, lqi: 255, rssi: -43
13:21:46:054 aps request id: 162 finished, erase from queue
13:21:46:033 APS-DATA.confirm request id: 162 -> erase from queue
13:21:46:032 APS-DATA.confirm id: 162, status: 0x00 SUCCESS
13:21:45:994 Delay APS request id: 164 to 0xF456, profile: 0x0104 cluster: 0x0B04 node already has busy 1
3x			
13:21:45:986 Websocket 10.0.0.101:56618 send message: {"e":"changed","id":"89","r":"sensors","state":{"current":384,"lastupdated":"2022-09-16T12:21:45.959","power":78,"voltage":236},"t":"event","uniqueid":"70:b3:d5:2b:60:00:f1:4e-01-0b04"} (ret = 185)
13:21:45:983 Delay APS request id: 164 to 0xF456, profile: 0x0104 cluster: 0x0B04 node already has busy 1
13:21:45:981 	asdu (length: 5): 109f000505
13:21:45:978 APS-DATA.request id: 164, addrmode: 0x03, addr: 0x70b3d52b6000f14e, profile: 0x0104, cluster: 0x0B04, ep: 0x01 -> 0x01 queue: 1 len: 5 tx.options 0x00
13:21:45:957 APS-DATA.request id: 158 erase from queue
13:21:45:956 	asdu: 189d010b0500214e00
13:21:45:955 APS-DATA.indication srcAddr: 0xf456, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0B04, lqi: 255, rssi: -41
13:21:45:932 APS-DATA.confirm request id: 158 -> erase from queue
13:21:45:931 APS-DATA.confirm id: 158, status: 0x00 SUCCESS
2x			
13:21:45:919 Delay APS request id: 162 to 0xF456, profile: 0x0104 cluster: 0x0006 node already has busy 1
13:21:45:918 	asdu (length: 11): 109e060000001001002c01
13:21:45:917 APS-DATA.request id: 162, addrmode: 0x03, addr: 0x70b3d52b6000f14e, profile: 0x0104, cluster: 0x0006, ep: 0x01 -> 0x01 queue: 1 len: 11 tx.options 0x00
13:21:45:914 	asdu: 189c098b000000
13:21:45:913 APS-DATA.indication srcAddr: 0xf456, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0006, lqi: 255, rssi: -41
13:21:45:894 aps request id: 154 finished, erase from queue
13:21:45:862 APS-DATA.confirm request id: 154 -> erase from queue
13:21:45:860 APS-DATA.confirm id: 154, status: 0x00 SUCCESS
13:21:45:829 GW firmware version: 0x26720700
13:21:45:821 Delay APS request id: 158 to 0xF456, profile: 0x0104 cluster: 0x0B04 node already has busy 1
3x			
13:21:45:814 Websocket 10.0.0.101:56618 send message: {"e":"changed","id":"89","r":"sensors","state":{"current":384,"lastupdated":"2022-09-16T12:21:45.813","power":79,"voltage":236},"t":"event","uniqueid":"70:b3:d5:2b:60:00:f1:4e-01-0b04"} (ret = 185)
13:21:45:811 Delay APS request id: 158 to 0xF456, profile: 0x0104 cluster: 0x0B04 node already has busy 1
13:21:45:810 	asdu: 189b01080500218001
13:21:45:808 APS-DATA.indication srcAddr: 0xf456, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0B04, lqi: 255, rssi: -41
3x			
13:21:45:780 Websocket 10.0.0.101:56618 send message: {"e":"changed","id":"89","r":"sensors","state":{"current":384,"lastupdated":"2022-09-16T12:21:45.775","power":79,"voltage":236},"t":"event","uniqueid":"70:b3:d5:2b:60:00:f1:4e-01-0b04"} (ret = 185)
13:21:45:778 Delay APS request id: 158 to 0xF456, profile: 0x0104 cluster: 0x0B04 node already has busy 1
13:21:45:777 	asdu (length: 5): 109d000b05
13:21:45:775 APS-DATA.request id: 158, addrmode: 0x03, addr: 0x70b3d52b6000f14e, profile: 0x0104, cluster: 0x0B04, ep: 0x01 -> 0x01 queue: 1 len: 5 tx.options 0x00
13:21:45:772 APS-DATA.request id: 152 erase from queue
13:21:45:771 	asdu: 189b01080500218001
13:21:45:770 APS-DATA.indication srcAddr: 0xf456, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0B04, lqi: 255, rssi: -43
13:21:45:753 Poll ZHAConsumption sensor node Consumption 6
13:21:45:752 poll node 84:71:27:ff:fe:8d:97:ba-01-0702
13:21:45:751 APS-DATA.confirm id: 152, status: 0x00, match: 0
13:21:45:750 APS-DATA.confirm id: 152, status: 0x00 SUCCESS
13:21:45:738 APS-DATA.confirm request id: 152 -> erase from queue
13:21:45:737 APS-DATA.confirm id: 152, status: 0x00 SUCCESS
2x			
13:21:45:657 Delay APS request id: 154 to 0xF456, profile: 0x0104 cluster: 0x0006 node already has busy 1
3x			
13:21:45:591 Websocket 10.0.0.101:56618 send message: {"e":"changed","id":"29","r":"sensors","state":{"current":0,"lastupdated":"2022-09-16T12:21:45.583","power":0,"voltage":235},"t":"event","uniqueid":"84:71:27:ff:fe:8d:95:76-01-0b04"} (ret = 182)
13:21:45:589 	payload: 0805210000
13:21:45:587 ZCL attribute report 0x847127FFFE8D9576 for cluster: 0x0B04, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
13:21:45:585 [INFO] - No button map for: TS011F, unicast to: 0x0000, endpoint: 0x01, cluster: 0x0B04, command: 0x0A, payload: 0805210000, zclSeq: 27
13:21:45:582 0x847127FFFE8D9576: update ZCL value 0x01/0x0B04/0x0508 after 0 s
13:21:45:580 Node data 0x847127fffe8d9576 profileId: 0x0104, clusterId: 0x0B04
13:21:45:577 	asdu: 181b0a0805210000
13:21:45:575 APS-DATA.indication srcAddr: 0x1de2, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0B04, lqi: 255, rssi: -40
2x			
13:21:45:556 Delay APS request id: 154 to 0xF456, profile: 0x0104 cluster: 0x0006 node already has busy 1
13:21:45:554 	asdu (length: 6): 109c08000000
13:21:45:552 APS-DATA.request id: 154, addrmode: 0x03, addr: 0x70b3d52b6000f14e, profile: 0x0104, cluster: 0x0006, ep: 0x01 -> 0x01 queue: 1 len: 6 tx.options 0x00
13:21:45:550 APS-DATA.request id: 150 erase from queue
13:21:45:548 APS-DATA.indication request id: 150 -> finished
13:21:45:546 	asdu: 57000300034ef100602bd5b37001000003594c06ffff2e2100014ef100602bd5b37001040b03594c06ffff2e2100014ef100602bd5b37001060003594c06ffff2e210001
13:21:45:544 APS-DATA.indication srcAddr: 0xf456, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8033, lqi: 255, rssi: -41
13:21:45:508 APS-DATA.confirm request id: 150 -> confirmed, timeout 99353559
13:21:45:505 APS-DATA.confirm id: 150, status: 0x00 SUCCESS
3x			
13:21:45:492 Websocket 10.0.0.101:56618 send message: {"attr":{"id":"90","lastannounced":null,"lastseen":"2022-09-16T12:21Z","manufacturername":"_TZ3000_okaz9tjs","modelid":"TS011F","name":"Consumption 90","swversion":"20B+TZSKT11BS105","type":"ZHAConsumption","uniqueid":"70:b3:d5:2b:60:00:f1:4e-01-0702"},"e":"changed","id":"90","r":"sensors","t":"event","uniqueid":"70:b3:d5:2b:60:00:f1:4e-01-0702"} (ret = 348)
3x			
13:21:45:479 Websocket 10.0.0.101:56618 send message: {"attr":{"id":"89","lastannounced":null,"lastseen":"2022-09-16T12:21Z","manufacturername":"_TZ3000_okaz9tjs","modelid":"TS011F","name":"Power 89","swversion":"20B+TZSKT11BS105","type":"ZHAPower","uniqueid":"70:b3:d5:2b:60:00:f1:4e-01-0b04"},"e":"changed","id":"89","r":"sensors","t":"event","uniqueid":"70:b3:d5:2b:60:00:f1:4e-01-0b04"} (ret = 336)
3x			
13:21:45:470 Websocket 10.0.0.101:56618 send message: {"e":"changed","id":"34","r":"lights","state":{"alert":"none","on":true,"reachable":true},"t":"event","uniqueid":"70:b3:d5:2b:60:00:f1:4e-01"} (ret = 142)
13:21:45:466 Delay APS request id: 152 to 0xF456, profile: 0x0104 cluster: 0x0B04 node already has busy 1
3x			
13:21:45:452 Websocket 10.0.0.101:56618 send message: {"attr":{"id":"34","lastannounced":null,"lastseen":"2022-09-16T12:21Z","manufacturername":"_TZ3000_okaz9tjs","modelid":"TS011F","name":"Fridge","swversion":"20B+TZSKT11BS105","type":"Smart plug","uniqueid":"70:b3:d5:2b:60:00:f1:4e-01"},"e":"changed","id":"34","r":"lights","t":"event","uniqueid":"70:b3:d5:2b:60:00:f1:4e-01"} (ret = 325)
13:21:45:450 Delay APS request id: 152 to 0xF456, profile: 0x0104 cluster: 0x0B04 node already has busy 1
13:21:45:448 	asdu (length: 5): 109b000805
13:21:45:446 APS-DATA.request id: 152, addrmode: 0x03, addr: 0x70b3d52b6000f14e, profile: 0x0104, cluster: 0x0B04, ep: 0x01 -> 0x01 queue: 1 len: 5 tx.options 0x00
13:21:45:439 	asdu: 189a010000001001
13:21:45:436 APS-DATA.indication srcAddr: 0xf456, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0006, lqi: 255, rssi: -41
13:21:45:414 aps request id: 149 finished, erase from queue
13:21:45:388 APS-DATA.confirm request id: 149 -> erase from queue
13:21:45:385 APS-DATA.confirm id: 149, status: 0x00 SUCCESS
13:21:45:343 Delay APS request id: 150 to 0xF456, profile: 0x0000 cluster: 0x0033 node already has busy 1
13:21:45:339 	asdu (length: 2): 5700
13:21:45:337 APS-DATA.request id: 150, addrmode: 0x03, addr: 0x70b3d52b6000f14e, profile: 0x0000, cluster: 0x0033, ep: 0x00 -> 0x00 queue: 1 len: 2 tx.options 0x04
13:21:45:333 	asdu (length: 5): 109a000000
13:21:45:331 APS-DATA.request id: 149, addrmode: 0x03, addr: 0x70b3d52b6000f14e, profile: 0x0104, cluster: 0x0006, ep: 0x01 -> 0x01 queue: 0 len: 5 tx.options 0x00
13:21:45:327 rule event /config/localtime: 13:21:44.326 -> 13:21:45.326 (1000ms)
13:21:44:883 Poll light node Light 3 - Front Door
13:21:44:881 poll node 00:15:8d:00:03:60:80:1b-01
13:21:44:326 rule event /config/localtime: 13:21:43.326 -> 13:21:44.326 (1000ms)
13:21:44:044 Poll light node Light 15 - Hall
13:21:44:041 poll node 00:15:8d:00:03:88:52:63-01
13:21:43:327 rule event /config/localtime: 13:21:42.326 -> 13:21:43.326 (1000ms)
13:21:43:147 Poll light node Siren 1 - Office
13:21:43:144 poll node 5c:02:72:ff:fe:e7:b2:9b-01
13:21:42:950 APS-DATA.request id: 137 erase from queue
13:21:42:947 APS-DATA.indication request id: 137 -> finished
13:21:42:945 	asdu: fe001e0903594c06ffff2e210008672409018817004b0d25010101594c06ffff2e21001b806003008d15002bc92500026f594c06ffff2e210064f300602bd5b3709343a5010286
13:21:42:942 APS-DATA.indication srcAddr: 0xd0b0, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 255, rssi: -49
13:21:42:893 APS-DATA.confirm request id: 137 -> confirmed, timeout 99351032
13:21:42:892 APS-DATA.confirm id: 137, status: 0x00 SUCCESS
13:21:42:856 	asdu (length: 2): fe09
13:21:42:854 APS-DATA.request id: 137, addrmode: 0x03, addr: 0x70b3d52b6000f608, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
3x			
13:21:42:470 Websocket 10.0.0.101:56618 send message: {"e":"changed","id":"29","r":"sensors","state":{"current":23,"lastupdated":"2022-09-16T12:21:42.465","power":0,"voltage":235},"t":"event","uniqueid":"84:71:27:ff:fe:8d:95:76-01-0b04"} (ret = 183)
13:21:42:469 	payload: 050521eb00
13:21:42:468 ZCL attribute report 0x847127FFFE8D9576 for cluster: 0x0B04, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
13:21:42:466 [INFO] - No button map for: TS011F, unicast to: 0x0000, endpoint: 0x01, cluster: 0x0B04, command: 0x0A, payload: 050521EB00, zclSeq: 26
13:21:42:464 0x847127FFFE8D9576: update ZCL value 0x01/0x0B04/0x0505 after 0 s
13:21:42:462 Node data 0x847127fffe8d9576 profileId: 0x0104, clusterId: 0x0B04
13:21:42:461 	asdu: 181a0a050521eb00
13:21:42:459 APS-DATA.indication srcAddr: 0x1de2, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0B04, lqi: 255, rssi: -40
13:21:42:326 rule event /config/localtime: 13:21:41.363 -> 13:21:42.326 (963ms)
13:21:42:252 Poll light node Plug 6 - Veg Fan
13:21:42:251 poll node 00:12:4b:00:22:e9:8e:ba-01
3x			
13:21:42:070 Websocket 10.0.0.101:56618 send message: {"e":"changed","id":"86","r":"sensors","state":{"consumption":6000,"lastupdated":"2022-09-16T12:21:42.069"},"t":"event","uniqueid":"70:b3:d5:2b:60:00:f6:08-01-0702"} (ret = 165)
13:21:42:067 	asdu: 18990100000025580200000100
13:21:42:065 APS-DATA.indication srcAddr: 0xd0b0, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0702, lqi: 255, rssi: -49
13:21:42:054 aps request id: 130 finished, erase from queue
13:21:42:043 APS-DATA.confirm request id: 130 -> erase from queue
13:21:42:041 APS-DATA.confirm id: 130, status: 0x00 SUCCESS
3x			
13:21:41:993 Websocket 10.0.0.101:56618 send message: {"e":"changed","id":"85","r":"sensors","state":{"current":61,"lastupdated":"2022-09-16T12:21:41.973","power":0,"voltage":235},"t":"event","uniqueid":"70:b3:d5:2b:60:00:f6:08-01-0b04"} (ret = 183)
13:21:41:992 	asdu (length: 5): 1099000000
13:21:41:990 APS-DATA.request id: 130, addrmode: 0x03, addr: 0x70b3d52b6000f608, profile: 0x0104, cluster: 0x0702, ep: 0x01 -> 0x01 queue: 0 len: 5 tx.options 0x00
13:21:41:971 APS-DATA.request id: 126 erase from queue
13:21:41:969 	asdu: 18980105050021eb00
13:21:41:968 APS-DATA.indication srcAddr: 0xd0b0, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0B04, lqi: 255, rssi: -49
13:21:41:949 APS-DATA.confirm request id: 126 -> erase from queue
13:21:41:947 APS-DATA.confirm id: 126, status: 0x00 SUCCESS
13:21:41:936 	asdu: 18970701000000
13:21:41:934 APS-DATA.indication srcAddr: 0xd0b0, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0006, lqi: 255, rssi: -49
13:21:41:894 aps request id: 124 finished, erase from queue
13:21:41:886 APS-DATA.confirm request id: 124 -> erase from queue
13:21:41:884 APS-DATA.confirm id: 124, status: 0x00 SUCCESS
13:21:41:860 Delay APS request id: 126 to 0xD0B0, profile: 0x0104 cluster: 0x0B04 node already has busy 1
3x			
13:21:41:830 Websocket 10.0.0.101:56618 send message: {"e":"changed","id":"85","r":"sensors","state":{"current":61,"lastupdated":"2022-09-16T12:21:41.822","power":0,"voltage":236},"t":"event","uniqueid":"70:b3:d5:2b:60:00:f6:08-01-0b04"} (ret = 183)
13:21:41:828 Delay APS request id: 126 to 0xD0B0, profile: 0x0104 cluster: 0x0B04 node already has busy 1
13:21:41:825 	asdu (length: 5): 1098000505
13:21:41:822 APS-DATA.request id: 126, addrmode: 0x03, addr: 0x70b3d52b6000f608, profile: 0x0104, cluster: 0x0B04, ep: 0x01 -> 0x01 queue: 1 len: 5 tx.options 0x00
13:21:41:818 	asdu: 1896010b0500210000
13:21:41:816 APS-DATA.indication srcAddr: 0xd0b0, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0B04, lqi: 255, rssi: -49
13:21:41:814 aps request id: 122 finished, erase from queue
13:21:41:796 APS-DATA.confirm request id: 122 -> erase from queue
13:21:41:795 APS-DATA.confirm id: 122, status: 0x00 SUCCESS
2x			
13:21:41:744 Delay APS request id: 124 to 0xD0B0, profile: 0x0104 cluster: 0x0006 node already has busy 1
13:21:41:743 	asdu (length: 11): 1097060000001001002c01
13:21:41:742 APS-DATA.request id: 124, addrmode: 0x03, addr: 0x70b3d52b6000f608, profile: 0x0104, cluster: 0x0006, ep: 0x01 -> 0x01 queue: 1 len: 11 tx.options 0x00
13:21:41:739 	asdu: 1895098b000000
13:21:41:738 APS-DATA.indication srcAddr: 0xd0b0, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0006, lqi: 255, rssi: -49
13:21:41:734 aps request id: 119 finished, erase from queue
13:21:41:719 APS-DATA.confirm request id: 119 -> erase from queue
13:21:41:717 APS-DATA.confirm id: 119, status: 0x00 SUCCESS
13:21:41:700 Delay APS request id: 122 to 0xD0B0, profile: 0x0104 cluster: 0x0B04 node already has busy 1
3x			
13:21:41:689 Websocket 10.0.0.101:56618 send message: {"e":"changed","id":"85","r":"sensors","state":{"current":61,"lastupdated":"2022-09-16T12:21:41.664","power":0,"voltage":236},"t":"event","uniqueid":"70:b3:d5:2b:60:00:f6:08-01-0b04"} (ret = 183)
13:21:41:687 Delay APS request id: 122 to 0xD0B0, profile: 0x0104 cluster: 0x0B04 node already has busy 1
13:21:41:686 	asdu (length: 5): 1096000b05
13:21:41:683 APS-DATA.request id: 122, addrmode: 0x03, addr: 0x70b3d52b6000f608, profile: 0x0104, cluster: 0x0B04, ep: 0x01 -> 0x01 queue: 1 len: 5 tx.options 0x00

You never see this line ? with “info”

22:07:27:577 send permit join, duration: X

Sure:

Yes, I get this line

send permit join, duration: 65

Here is 3 mins of logs in which I tried to pair an Aqara motion sensor

https://drive.google.com/file/d/1L2pps-6mul2EZDsnp7OS9LmSF5ECjHUD

The most recent change I made was adding 6 smart plugs about 4 weeks ago (specifically, _TZ3000_okaz9tjs zigbee smart plugs). I didn’t have any problem then other than needing to get a DDF file in the GitHub forums to get the energy metering working properly. These 6 plugs and almost every other device still on the network seem to be functioning perfectly. And I had also re-paired one or two sensors since then that had become unresponsive.
This issue only seemed to present itself a few days ago when I tried to re-pair an unresponsive sensor again.

I don’t see device announce at all in your logs.

And no connexion error …
You are using the cable extension ?

I am using the Raspbee II HAT, not the USB stick

What can I search for in my logs to help solve this now?

You have enabled flag “error” and “error _l2” in your logs ? because it’s strange not seen this kind of error if you have connexion issue Zigbee Error Codes in the Log · dresden-elektronik/deconz-rest-plugin Wiki · GitHub

You have tried the hidden backup or a previous zigbee backup ? Network lost issues · dresden-elektronik/deconz-rest-plugin Wiki · GitHub

But even with configuration issue, you need to have more information in your logs.

Hi,
I’m not getting any logs when I view only error and error_l2 and try to pair.
Is there something else I can search for in the logs? Sorry, I’m not familiar with these logs and what to look for.

I’m hesitant to try loading backups now in case I break the rest of my house. I need a day or two when I can tackle something like that. Does this secret Zigbee configuration page only load network settings? Will it change my list of lights and sensors to what it was at the time of backup? Nothing looks scrambled or changed in the PANID or Network Key in the list shown on that page.

I’m also wondering if I can try replacing my Raspbee II HAT with a spare I have, but I think I will have to repair everything if I do that.

Yes only network setting, but if there is a problem in the network key, it will impact all devices. But as router haven’t issue I don’t think it s from that.

I’m also wondering if I can try replacing my Raspbee II HAT with a spare I have, but I think I will have to repair everything if I do that

No just make a backup in phoscon / gateway / backup, and you will be able to restore the same network on the new raspbee.

But you haven’t changed something recently ?

  • enabled bluetooth or wifi on the raspberry ?
  • changed the channel ?

Thank you,

I will have to wait a few days to try some of these troubleshooting steps when I have time to complete the process and fix everything I break. So anything you can give me to try, I will do it all on the same day.

I can’t think of anything I changed like that. I have deCONZ running on a dedicated Pi3 and rarely go near it, for this very reason. There has never been bluetooth or wifi active on this Pi.

The last thing I did with any of this was to add 9 smart plugs about 3-4 weeks ago. These all paired without issue. I had to find a custom DDF file from the forums to make the energy measurements work, but everything else went smoothly. I updated my software version at the time I was pairing these plugs from 20.17 to 20.18. I have never changed the channel since the day I bought it.

After adding the plugs, a few sensors started losing connection, but I re-paired those without issue.

Since these problems revealed themselves, I have also done apt update and upgrade etc

It’s very strange. This exact thing happened to a friend of mine about 2 months ago. He couldn’t fix it and jumped ship to Zigbee2MQQT

Hi all, I‘m not that highly sophisticated expert, but I think a solid user (ConBee II stick with ~100 devices) and I occasionally just made an observation over the last week.
I found the option ‚source routing‘ in the setup, and looking at your screenshoot above, you seems having it also enabled, and gave it a try, as I have 1-2 devices with a bad connect.
But the experience I made was the opposite from what I awaited. I had multiple ‚outages‘, in terms of that 2-3 shutters (of > 10) randomly didn‘t work any longer or also, that pressing light buttons, triggered the lights with a delay of 5-10 seconds, also randomly.
I just switched ‚source routing‘ OFF again yesterday morning and now all these problems are gone.
Thus maybe switch OFF this option and give it a try without?
PS. I didn‘t learn new devices to the setup during this test phase.

See it as only my ‚five cents‘ when reading here, resp. seeing the screenshot.

Thanks, well spotted. Unfortunately, things are still the same 2 days since disabling source routing.

1 Like