deconz-rest-plugin: Unreachable lumi.ctrl_neutral2

I’ve got a lumi.ctrl_neutral2 switch (end device) which cannot be reached from deCONZ, even though it’s active on the network. The switch seems stuck in a loop, where it requests the attributes of the Time cluster from the coordinator, but doesn’t receive any answer. After a couple of times, it gives up, leaves and rejoins the network, connecting to a different parent. deCONZ insists that the node is known by 0 neighbours. Sending a command to the switch results in error 0xA7 - no clue what that means?

Below the deCONZ log (filtered on the switch’s MAC address) and the Wireshark dump (filtered on the switch’s NWK address):

Aug 27 18:58:06 pi2 deCONZ[4989]: 18:58:05:183 APS-DATA.indication srcAddr: 0x00158d000239145e, dstAddrMode: 2, profile: 0x0104, cluster: 0x000A, lqi: 231, rssi: -62
Aug 27 18:58:06 pi2 deCONZ[4989]: 18:58:05:527 add task 378160 type 21 to 0x00158D000239145E cluster 0x0004 req.id 129
Aug 27 18:58:06 pi2 deCONZ[4989]: 18:58:05:528 APS-DATA.request id: 129, addrmode: 0x03, addr: 0x00158d000239145e, profile: 0x0104, cluster: 0x0004, ep: 0x03 queue: 0 len: 4
Aug 27 18:58:24 pi2 deCONZ[4989]: 18:58:22:082 Node 0x00158D000239145E is known by 0 neighbors, last seen 16 s
Aug 27 18:59:08 pi2 deCONZ[4989]: 18:59:04:626 Node 0x00158D000239145E is known by 0 neighbors, last seen 59 s
Aug 27 18:59:08 pi2 deCONZ[4989]: 18:59:07:186 APS-DATA.indication srcAddr: 0x00158d000239145e, dstAddrMode: 2, profile: 0x0104, cluster: 0x000A, lqi: 223, rssi: -63
Aug 27 18:59:49 pi2 deCONZ[4989]: 18:59:48:571 Node 0x00158D000239145E is known by 0 neighbors, last seen 41 s
Aug 27 19:00:14 pi2 deCONZ[4989]: 19:00:09:301 APS-DATA.indication srcAddr: 0x00158d000239145e, dstAddrMode: 2, profile: 0x0104, cluster: 0x000A, lqi: 223, rssi: -63
Aug 27 19:00:39 pi2 deCONZ[4989]: 19:00:36:883 Node 0x00158D000239145E is known by 0 neighbors, last seen 27 s
Aug 27 19:00:39 pi2 deCONZ[4989]: 19:00:38:974 APS-DATA.indication srcAddr: 0x00158d000239145e, dstAddrMode: 2, profile: 0x0000, cluster: 0x0013, lqi: 191, rssi: -67
Aug 27 19:00:39 pi2 deCONZ[4989]: 19:00:38:975 DeviceAnnce of LightNode: 0x00158d000239145e Permit Join: 0
Aug 27 19:00:39 pi2 deCONZ[4989]: 19:00:38:975 DeviceAnnce of SensorNode: 0x00158D000239145E [1]
Aug 27 19:00:39 pi2 deCONZ[4989]: 19:00:38:975 DeviceAnnce of SensorNode: 0x00158D000239145E [1]
Aug 27 19:00:39 pi2 deCONZ[4989]: 19:00:38:975 device announce 0x00158D000239145E (0x7F15) mac capabilities 0x84
Aug 27 19:00:39 pi2 deCONZ[4989]: 19:00:38:975 set fast probe address to 0x00158D000239145E (0x7F15)
Aug 27 19:00:46 pi2 deCONZ[4989]: 19:00:45:276 add task 378937 type 21 to 0x00158D000239145E cluster 0x0004 req.id 129
Aug 27 19:00:46 pi2 deCONZ[4989]: 19:00:45:276 APS-DATA.request id: 129, addrmode: 0x03, addr: 0x00158d000239145e, profile: 0x0104, cluster: 0x0004, ep: 0x02 queue: 2 len: 4
Aug 27 19:00:46 pi2 deCONZ[4989]: 19:00:46:181 add task 378941 type 21 to 0x00158D000239145E cluster 0x0004 req.id 133
Aug 27 19:00:46 pi2 deCONZ[4989]: 19:00:46:181 APS-DATA.request id: 133, addrmode: 0x03, addr: 0x00158d000239145e, profile: 0x0104, cluster: 0x0004, ep: 0x03 queue: 2 len: 4
Aug 27 19:01:13 pi2 deCONZ[4989]: 19:01:11:215 APS-DATA.indication srcAddr: 0x00158d000239145e, dstAddrMode: 2, profile: 0x0104, cluster: 0x000A, lqi: 207, rssi: -65
Aug 27 19:01:25 pi2 deCONZ[4989]: 19:01:23:419 Node 0x00158D000239145E is known by 0 neighbors, last seen 12 s
Aug 27 19:02:09 pi2 deCONZ[4989]: 19:02:07:354 Node 0x00158D000239145E is known by 0 neighbors, last seen 56 s
Aug 27 19:02:16 pi2 deCONZ[4989]: 19:02:13:228 APS-DATA.indication srcAddr: 0x00158d000239145e, dstAddrMode: 2, profile: 0x0104, cluster: 0x000A, lqi: 199, rssi: -66
Aug 27 19:02:24 pi2 deCONZ[4989]: 19:02:24:107 add task 379420 type 14 to 0x00158D000239145E cluster 0x0006 req.id 121
Aug 27 19:02:25 pi2 deCONZ[4989]: 19:02:24:109 APS-DATA.request id: 121, addrmode: 0x03, addr: 0x00158d000239145e, profile: 0x0104, cluster: 0x0006, ep: 0x02 queue: 2 len: 3
Aug 27 19:02:30 pi2 deCONZ[4989]: 19:02:29:052 0x00158D000239145E error APSDE-DATA.confirm: 0xA7 on task
Aug 27 19:02:51 pi2 deCONZ[4989]: 19:02:51:154 Node 0x00158D000239145E is known by 0 neighbors, last seen 37 s
Aug 27 19:03:17 pi2 deCONZ[4989]: 19:03:15:254 APS-DATA.indication srcAddr: 0x00158d000239145e, dstAddrMode: 2, profile: 0x0104, cluster: 0x000A, lqi: 191, rssi: -67
Aug 27 19:03:41 pi2 deCONZ[4989]: 19:03:37:882 Node 0x00158D000239145E is known by 0 neighbors, last seen 22 s
Aug 27 19:04:20 pi2 deCONZ[4989]: 19:04:17:282 APS-DATA.indication srcAddr: 0x00158d000239145e, dstAddrMode: 2, profile: 0x0104, cluster: 0x000A, lqi: 255, rssi: -53
Aug 27 19:04:28 pi2 deCONZ[4989]: 19:04:24:650 Node 0x00158D000239145E is known by 0 neighbors, last seen 7 s
Aug 27 19:04:40 pi2 deCONZ[4989]: 19:04:39:276 add task 380084 type 21 to 0x00158D000239145E cluster 0x0004 req.id 214
Aug 27 19:04:40 pi2 deCONZ[4989]: 19:04:39:277 APS-DATA.request id: 214, addrmode: 0x03, addr: 0x00158d000239145e, profile: 0x0104, cluster: 0x0004, ep: 0x02 queue: 1 len: 4
Aug 27 19:05:14 pi2 deCONZ[4989]: 19:05:08:650 Node 0x00158D000239145E is known by 0 neighbors, last seen 51 s
Aug 27 19:05:54 pi2 deCONZ[4989]: 19:05:52:315 Node 0x00158D000239145E is known by 0 neighbors, last seen 95 s
Aug 27 19:06:03 pi2 deCONZ[4989]: 19:06:01:408 APS-DATA.indication srcAddr: 0x00158d000239145e, dstAddrMode: 2, profile: 0x0000, cluster: 0x0013, lqi: 191, rssi: -67
Aug 27 19:06:03 pi2 deCONZ[4989]: 19:06:01:409 DeviceAnnce of LightNode: 0x00158d000239145e Permit Join: 0
Aug 27 19:06:03 pi2 deCONZ[4989]: 19:06:01:409 DeviceAnnce of SensorNode: 0x00158D000239145E [1]
Aug 27 19:06:03 pi2 deCONZ[4989]: 19:06:01:409 DeviceAnnce of SensorNode: 0x00158D000239145E [1]
Aug 27 19:06:03 pi2 deCONZ[4989]: 19:06:01:410 device announce 0x00158D000239145E (0x7F15) mac capabilities 0x84
Aug 27 19:06:03 pi2 deCONZ[4989]: 19:06:01:410 set fast probe address to 0x00158D000239145E (0x7F15)
Aug 27 19:06:03 pi2 deCONZ[4989]: 19:06:03:277 read attributes of 0x00158D000239145E cluster: 0x0000: [ 19:06:03:277 0x4000 19:06:03:277 ]
Aug 27 19:06:03 pi2 deCONZ[4989]: 19:06:03:277 add task 380490 type 19 to 0x00158D000239145E cluster 0x0000 req.id 113
Aug 27 19:06:03 pi2 deCONZ[4989]: 19:06:03:277 add task 380491 type 21 to 0x00158D000239145E cluster 0x0004 req.id 114
Aug 27 19:06:03 pi2 deCONZ[4989]: 19:06:03:277 APS-DATA.request id: 113, addrmode: 0x03, addr: 0x00158d000239145e, profile: 0x0104, cluster: 0x0000, ep: 0x02 queue: 0 len: 5
Aug 27 19:06:03 pi2 deCONZ[4989]: 19:06:03:327 delay sending request 114 dt 0 ms to 0x00158D000239145E, cluster 0x0004
Aug 27 19:06:03 pi2 deCONZ[4989]: 19:06:03:327 delay sending request 114 cluster 0x0004 to 0x00158d000239145e
Aug 27 19:06:06 pi2 deCONZ[4989]: 19:06:03:403 APS-DATA.request id: 114, addrmode: 0x03, addr: 0x00158d000239145e, profile: 0x0104, cluster: 0x0004, ep: 0x02 queue: 1 len: 4
Aug 27 19:06:06 pi2 deCONZ[4989]: 19:06:04:027 read attributes of 0x00158D000239145E cluster: 0x0000: [ 19:06:04:027 0x4000 19:06:04:027 ]
Aug 27 19:06:06 pi2 deCONZ[4989]: 19:06:04:027 add task 380495 type 19 to 0x00158D000239145E cluster 0x0000 req.id 118
Aug 27 19:06:06 pi2 deCONZ[4989]: 19:06:04:027 add task 380496 type 21 to 0x00158D000239145E cluster 0x0004 req.id 119
Aug 27 19:06:06 pi2 deCONZ[4989]: 19:06:04:027 APS-DATA.request id: 118, addrmode: 0x03, addr: 0x00158d000239145e, profile: 0x0104, cluster: 0x0000, ep: 0x03 queue: 0 len: 5
Aug 27 19:06:06 pi2 deCONZ[4989]: 19:06:04:029 delay sending request 119 dt 0 ms to 0x00158D000239145E, cluster 0x0004
Aug 27 19:06:06 pi2 deCONZ[4989]: 19:06:04:029 delay sending request 119 cluster 0x0004 to 0x00158d000239145e
Aug 27 19:06:06 pi2 deCONZ[4989]: 19:06:04:126 delay sending request 119 dt 0 ms to 0x00158D000239145E, cluster 0x0004
Aug 27 19:06:06 pi2 deCONZ[4989]: 19:06:04:126 delay sending request 119 cluster 0x0004 to 0x00158d000239145e
Aug 27 19:06:06 pi2 deCONZ[4989]: 19:06:04:161 APS-DATA.request id: 119, addrmode: 0x03, addr: 0x00158d000239145e, profile: 0x0104, cluster: 0x0004, ep: 0x03 queue: 1 len: 4

wireshark.pcapng.zip

About this issue

Original URL
State: closed
Created 6 years ago
Comments: 20 (7 by maintainers)

Most upvoted comments

BTW, is it possible to add the source endpoint to the APS-DATA.indication messages (I assume from the deCONZ core program)?

Sure, I’ll add it to the debug prints.

manup on Sep 2, 2018

They might use the a non responsive time cluster as indication to rejoin the network, same as Philips end-devices do when they don’t receive zcl default response for their reports. A solution might be to just implement the time server on our side (or at least the responses which they expect).

In the last days I was quite busy to implement full nodes restore right after deCONZ starts, this is nearly finished and works quite well in my test networks (34, 80 and 105 nodes), hope to get the next release out this week.

Also I found a serious bug in the firmware (all versions) which will be fixed in 26220500, it caused the ZDO/ZDP module of the firmware to be blocked until next restart. As for the IKEA/OSRAM meshing I’m tempted to disable the many-to-one route record feature, it seems to cause more harm than good. All the other optimizations within deCONZ of the past releases should already provide a stable network, so it should be safe to disable it and just rely on good’ol mesh routing.

manup on Aug 29, 2018