Deconz-rest-plugin: Cannot pair IKEA TRADFRI LED1837R5 / GU10

Created on 8 Jul 2020  路  29Comments  路  Source: dresden-elektronik/deconz-rest-plugin

I have an issue paring my IKEA TRADFRI LED1837R5.

No matter what I'll do, I cannot get them paired. For paring, Deconz/the Pi is directly placed on the Lamp (with an powerbank), so distance should be no issue.

Fresh ones (directly out of the box) do also not start a pairing process on the first power on.

I've tried resetting them:

  • 6 times on/off. This does not work. Simply no reaction.
  • I've bought an Philips Dimmer Switch (https://www.reddit.com/r/tradfri/comments/dm0rv3/psa_moving_tradfri_gu10_bulbls_from_hue_hub_to/). This does reset the bulb (seems so, it does do the on/on/flickering thing) but the bulb doesn't do any paring.

I've tried different ways on the Deconz side...

  • Start paring before resetting the bulb
  • Start paring after resetting the bulb
  • Start paring while resetting the bulb
  • Set paring time to 10 minutes

How to get them paired? Other devices word fine.

_Originally posted by @excedra in https://github.com/dresden-elektronik/deconz-rest-plugin/issues/2238#issuecomment-653782561_

User Question Waiting on Info stale
Source
picture excedra

All 29 comments

Hi!
What does the logging show?

Can you also provide some info about your environment in terms of versions, install method and hardware?

Mimiix picture Mimiix on 8 Jul 2020

Hardware: ConBee II
Version: 2.05.77 /22.5.2020
Firmware: 264A0700

Running on an Orange pi zero with Debian 10.4.
Installed usind the deb-package via apt/repo.

Date is correct on the system.
Zigbee-Channel is currently 11

The reset using the Philips Dimming Remote was at 15:12:20:

15:12:20:334 Mgmt_Lqi_req zdpSeq: 131 to 0x680AE2FFFE6EA49A start index 0
15:12:20:334 APS-DATA.request id: 162, addrmode: 0x03, addr: 0x680ae2fffe6ea49a, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 1 len: 2 tx.options 0x00
15:12:20:361 APS-DATA.confirm id: 162, status: 0x00 SUCCESS
15:12:20:361 APS-DATA.confirm request id: 162 -> confirmed, timeout 13588768
15:12:20:375 APS-DATA.indication srcAddr: 0x9226, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 255, rssi: -61
15:12:20:375 APS-DATA.indication request id: 162 -> finished
15:12:20:376 APS-DATA.request id: 162 erase from queue
15:12:20:376 ZDP status = 0x00 -> SUCCESS
15:12:20:376 ZDP Mgmt_Lqi_rsp zdpSeq: 131 from 0x680AE2FFFE6EA49A total: 5, startIndex: 0, listCount: 3
15:12:20:376 * neighbor: 0x00212EFFFF059482 (0x0000), LQI: 163, relation: 0x02 rxOnWHenIdle: 1
15:12:20:376 * neighbor: 0x680AE2FFFE43F767 (0x05E7), LQI: 73, relation: 0x02 rxOnWHenIdle: 1
15:12:20:376 * neighbor: 0x04CF8CDF3C763F7A (0xF0A7), LQI: 150, relation: 0x00 rxOnWHenIdle: 1
15:12:21:532 Current channel 11
15:12:21:537 CTRL got nwk update id 1
15:12:21:542 Device TTL 1387 s flags: 0x7
15:12:22:734 Mgmt_Lqi_req zdpSeq: 134 to 0x680AE2FFFE6EA49A start index 3
15:12:22:734 APS-DATA.request id: 175, addrmode: 0x03, addr: 0x680ae2fffe6ea49a, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 1 len: 2 tx.options 0x00
15:12:22:758 APS-DATA.confirm id: 175, status: 0x00 SUCCESS
15:12:22:759 APS-DATA.confirm request id: 175 -> confirmed, timeout 13588768
15:12:22:773 APS-DATA.indication srcAddr: 0x9226, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 255, rssi: -59
15:12:22:774 APS-DATA.indication request id: 175 -> finished
15:12:22:774 APS-DATA.request id: 175 erase from queue
15:12:22:774 ZDP status = 0x00 -> SUCCESS
15:12:22:774 ZDP Mgmt_Lqi_rsp zdpSeq: 134 from 0x680AE2FFFE6EA49A total: 5, startIndex: 3, listCount: 2
15:12:22:774 * neighbor: 0x680AE2FFFEC3D80A (0xBEEF), LQI: 160, relation: 0x01 rxOnWHenIdle: 0
15:12:22:774 * neighbor: 0x001788010872FE40 (0xDEC2), LQI: 116, relation: 0x01 rxOnWHenIdle: 0
15:12:25:613 Mgmt_Lqi_req zdpSeq: 137 to 0x00212EFFFF059482 start index 0
15:12:25:613 APS-DATA.request id: 191, addrmode: 0x03, addr: 0x00212effff059482, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 1 len: 2 tx.options 0x00
15:12:25:629 APS-DATA.confirm id: 191, status: 0x00 SUCCESS
15:12:25:629 APS-DATA.confirm request id: 191 -> confirmed, timeout 13588768
15:12:25:635 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 255, rssi: -59
15:12:25:635 APS-DATA.indication request id: 191 -> finished
15:12:25:635 APS-DATA.request id: 191 erase from queue
15:12:25:636 ZDP status = 0x00 -> SUCCESS
15:12:25:636 ZDP Mgmt_Lqi_rsp zdpSeq: 137 from 0x00212EFFFF059482 total: 2, startIndex: 0, listCount: 2
15:12:25:636 * neighbor: 0x04CF8CDF3C763F7A (0xF0A7), LQI: 252, relation: 0x02 rxOnWHenIdle: 1
15:12:25:636 * neighbor: 0x680AE2FFFE6EA49A (0x9226), LQI: 252, relation: 0x02 rxOnWHenIdle: 1
15:12:27:700 GW update firmware not found: deCONZ_ConBeeII_0x26490700.bin.GCF
15:12:28:662 Mgmt_Lqi_req zdpSeq: 140 to 0x680AE2FFFE43F767 start index 0
15:12:28:662 APS-DATA.request id: 207, addrmode: 0x03, addr: 0x680ae2fffe43f767, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 1 len: 2 tx.options 0x00
15:12:28:685 APS-DATA.confirm id: 207, status: 0x00 SUCCESS
15:12:28:685 APS-DATA.confirm request id: 207 -> confirmed, timeout 12622568
15:12:28:722 APS-DATA.indication srcAddr: 0x05e7, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 255, rssi: -61
15:12:28:722 APS-DATA.indication request id: 207 -> finished
15:12:28:722 APS-DATA.request id: 207 erase from queue
15:12:28:722 ZDP status = 0x00 -> SUCCESS
15:12:28:722 ZDP Mgmt_Lqi_rsp zdpSeq: 140 from 0x680AE2FFFE43F767 total: 3, startIndex: 0, listCount: 3
15:12:28:722 * neighbor: 0x00212EFFFF059482 (0x0000), LQI: 32, relation: 0x02 rxOnWHenIdle: 1
15:12:28:722 * neighbor: 0x680AE2FFFE6EA49A (0x9226), LQI: 68, relation: 0x02 rxOnWHenIdle: 1
15:12:28:722 * neighbor: 0x04CF8CDF3C763F7A (0xF0A7), LQI: 37, relation: 0x02 rxOnWHenIdle: 1
15:12:32:501 Mgmt_Lqi_req zdpSeq: 145 to 0x680AE2FFFE6EA49A start index 0
15:12:32:501 APS-DATA.request id: 228, addrmode: 0x03, addr: 0x680ae2fffe6ea49a, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 1 len: 2 tx.options 0x00
15:12:32:522 APS-DATA.confirm id: 228, status: 0x00 SUCCESS
15:12:32:522 APS-DATA.confirm request id: 228 -> confirmed, timeout 13595880
15:12:32:537 APS-DATA.indication srcAddr: 0x9226, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 255, rssi: -61
15:12:32:537 APS-DATA.indication request id: 228 -> finished
15:12:32:538 APS-DATA.request id: 228 erase from queue
15:12:32:538 ZDP status = 0x00 -> SUCCESS
15:12:32:538 ZDP Mgmt_Lqi_rsp zdpSeq: 145 from 0x680AE2FFFE6EA49A total: 5, startIndex: 0, listCount: 3
15:12:32:538 * neighbor: 0x00212EFFFF059482 (0x0000), LQI: 162, relation: 0x02 rxOnWHenIdle: 1
15:12:32:538 * neighbor: 0x680AE2FFFE43F767 (0x05E7), LQI: 73, relation: 0x02 rxOnWHenIdle: 1
15:12:32:538 * neighbor: 0x04CF8CDF3C763F7A (0xF0A7), LQI: 150, relation: 0x00 rxOnWHenIdle: 1
15:12:34:901 Mgmt_Lqi_req zdpSeq: 148 to 0x680AE2FFFE6EA49A start index 3
15:12:34:901 APS-DATA.request id: 242, addrmode: 0x03, addr: 0x680ae2fffe6ea49a, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 1 len: 2 tx.options 0x00
15:12:34:925 APS-DATA.confirm id: 242, status: 0x00 SUCCESS
15:12:34:925 APS-DATA.confirm request id: 242 -> confirmed, timeout 13595880
15:12:34:941 APS-DATA.indication srcAddr: 0x9226, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 255, rssi: -61
15:12:34:941 APS-DATA.indication request id: 242 -> finished
15:12:34:941 APS-DATA.request id: 242 erase from queue
15:12:34:941 ZDP status = 0x00 -> SUCCESS
15:12:34:941 ZDP Mgmt_Lqi_rsp zdpSeq: 148 from 0x680AE2FFFE6EA49A total: 5, startIndex: 3, listCount: 2
15:12:34:942 * neighbor: 0x680AE2FFFEC3D80A (0xBEEF), LQI: 160, relation: 0x01 rxOnWHenIdle: 0
15:12:34:942 * neighbor: 0x001788010872FE40 (0xDEC2), LQI: 116, relation: 0x01 rxOnWHenIdle: 0
15:12:37:697 GW update firmware not found: deCONZ_ConBeeII_0x26490700.bin.GCF
15:12:37:933 Mgmt_Lqi_req zdpSeq: 151 to 0x00212EFFFF059482 start index 0
15:12:37:933 APS-DATA.request id: 2, addrmode: 0x03, addr: 0x00212effff059482, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 1 len: 2 tx.options 0x00
15:12:37:950 APS-DATA.confirm id: 2, status: 0x00 SUCCESS
15:12:37:950 APS-DATA.confirm request id: 2 -> confirmed, timeout 12622568
15:12:37:956 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 255, rssi: -61
15:12:37:956 APS-DATA.indication request id: 2 -> finished
15:12:37:956 APS-DATA.request id: 2 erase from queue
15:12:37:956 ZDP status = 0x00 -> SUCCESS
15:12:37:956 ZDP Mgmt_Lqi_rsp zdpSeq: 151 from 0x00212EFFFF059482 total: 2, startIndex: 0, listCount: 2
15:12:37:956 * neighbor: 0x04CF8CDF3C763F7A (0xF0A7), LQI: 252, relation: 0x02 rxOnWHenIdle: 1
15:12:37:956 * neighbor: 0x680AE2FFFE6EA49A (0x9226), LQI: 252, relation: 0x02 rxOnWHenIdle: 1
15:12:41:294 Mgmt_Lqi_req zdpSeq: 154 to 0x680AE2FFFE43F767 start index 0
15:12:41:294 APS-DATA.request id: 20, addrmode: 0x03, addr: 0x680ae2fffe43f767, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 1 len: 2 tx.options 0x00
15:12:41:317 APS-DATA.confirm id: 20, status: 0x00 SUCCESS
15:12:41:317 APS-DATA.confirm request id: 20 -> confirmed, timeout 12622568
15:12:41:353 APS-DATA.indication srcAddr: 0x05e7, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 255, rssi: -62
15:12:41:353 APS-DATA.indication request id: 20 -> finished
15:12:41:353 APS-DATA.request id: 20 erase from queue
15:12:41:353 ZDP status = 0x00 -> SUCCESS
15:12:41:353 ZDP Mgmt_Lqi_rsp zdpSeq: 154 from 0x680AE2FFFE43F767 total: 3, startIndex: 0, listCount: 3
15:12:41:354 * neighbor: 0x00212EFFFF059482 (0x0000), LQI: 32, relation: 0x02 rxOnWHenIdle: 1
15:12:41:354 * neighbor: 0x680AE2FFFE6EA49A (0x9226), LQI: 68, relation: 0x02 rxOnWHenIdle: 1
15:12:41:354 * neighbor: 0x04CF8CDF3C763F7A (0xF0A7), LQI: 37, relation: 0x02 rxOnWHenIdle: 1
15:12:45:134 Mgmt_Lqi_req zdpSeq: 159 to 0x680AE2FFFE6EA49A start index 0
15:12:45:134 APS-DATA.request id: 41, addrmode: 0x03, addr: 0x680ae2fffe6ea49a, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 1 len: 2 tx.options 0x00
15:12:45:157 APS-DATA.confirm id: 41, status: 0x00 SUCCESS
15:12:45:157 APS-DATA.confirm request id: 41 -> confirmed, timeout 13616408
15:12:45:171 APS-DATA.indication srcAddr: 0x9226, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 255, rssi: -61
15:12:45:171 APS-DATA.indication request id: 41 -> finished
15:12:45:171 APS-DATA.request id: 41 erase from queue
15:12:45:171 ZDP status = 0x00 -> SUCCESS
15:12:45:171 ZDP Mgmt_Lqi_rsp zdpSeq: 159 from 0x680AE2FFFE6EA49A total: 5, startIndex: 0, listCount: 3
15:12:45:171 * neighbor: 0x00212EFFFF059482 (0x0000), LQI: 162, relation: 0x02 rxOnWHenIdle: 1
15:12:45:171 * neighbor: 0x680AE2FFFE43F767 (0x05E7), LQI: 73, relation: 0x02 rxOnWHenIdle: 1
15:12:45:172 * neighbor: 0x04CF8CDF3C763F7A (0xF0A7), LQI: 150, relation: 0x00 rxOnWHenIdle: 1
15:12:46:514 APS-DATA.request id: 48, addrmode: 0x02, addr: 0xfffc, profile: 0x0000, cluster: 0x0036, ep: 0x00 -> 0x00 queue: 1 len: 3 tx.options 0x00
15:12:46:514 send permit join, duration: 59
15:12:46:576 APS-DATA.confirm id: 48, status: 0x00 SUCCESS
15:12:46:598 aps request id: 48 finished, erase from queue
15:12:47:478 Mgmt_Lqi_req zdpSeq: 162 to 0x680AE2FFFE6EA49A start index 3
15:12:47:478 APS-DATA.request id: 55, addrmode: 0x03, addr: 0x680ae2fffe6ea49a, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 1 len: 2 tx.options 0x00
15:12:47:501 APS-DATA.confirm id: 55, status: 0x00 SUCCESS
15:12:47:501 APS-DATA.confirm request id: 55 -> confirmed, timeout 12753112
15:12:47:605 APS-DATA.indication srcAddr: 0x9226, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 255, rssi: -59
15:12:47:605 APS-DATA.indication request id: 55 -> finished
15:12:47:606 APS-DATA.request id: 55 erase from queue
15:12:47:606 ZDP status = 0x00 -> SUCCESS
15:12:47:606 ZDP Mgmt_Lqi_rsp zdpSeq: 162 from 0x680AE2FFFE6EA49A total: 5, startIndex: 3, listCount: 2
15:12:47:606 * neighbor: 0x680AE2FFFEC3D80A (0xBEEF), LQI: 160, relation: 0x01 rxOnWHenIdle: 0
15:12:47:606 * neighbor: 0x001788010872FE40 (0xDEC2), LQI: 116, relation: 0x01 rxOnWHenIdle: 0
15:12:47:607 GW update firmware not found: deCONZ_ConBeeII_0x26490700.bin.GCF
15:12:50:358 Mgmt_Lqi_req zdpSeq: 165 to 0x00212EFFFF059482 start index 0
15:12:50:358 APS-DATA.request id: 71, addrmode: 0x03, addr: 0x00212effff059482, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 1 len: 2 tx.options 0x00
15:12:50:375 APS-DATA.confirm id: 71, status: 0x00 SUCCESS
15:12:50:375 APS-DATA.confirm request id: 71 -> confirmed, timeout 12753112
15:12:50:381 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 255, rssi: -59
15:12:50:381 APS-DATA.indication request id: 71 -> finished
15:12:50:381 APS-DATA.request id: 71 erase from queue
15:12:50:382 ZDP status = 0x00 -> SUCCESS
15:12:50:382 ZDP Mgmt_Lqi_rsp zdpSeq: 165 from 0x00212EFFFF059482 total: 2, startIndex: 0, listCount: 2
15:12:50:382 * neighbor: 0x04CF8CDF3C763F7A (0xF0A7), LQI: 252, relation: 0x02 rxOnWHenIdle: 1
15:12:50:382 * neighbor: 0x680AE2FFFE6EA49A (0x9226), LQI: 252, relation: 0x02 rxOnWHenIdle: 1
15:12:53:718 Mgmt_Lqi_req zdpSeq: 168 to 0x680AE2FFFE43F767 start index 0
15:12:53:718 APS-DATA.request id: 88, addrmode: 0x03, addr: 0x680ae2fffe43f767, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 1 len: 2 tx.options 0x00
15:12:53:740 APS-DATA.confirm id: 88, status: 0x00 SUCCESS
15:12:53:740 APS-DATA.confirm request id: 88 -> confirmed, timeout 12753112
15:12:53:778 APS-DATA.indication srcAddr: 0x05e7, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 255, rssi: -61
15:12:53:778 APS-DATA.indication request id: 88 -> finished
15:12:53:778 APS-DATA.request id: 88 erase from queue
15:12:53:778 ZDP status = 0x00 -> SUCCESS
15:12:53:778 ZDP Mgmt_Lqi_rsp zdpSeq: 168 from 0x680AE2FFFE43F767 total: 3, startIndex: 0, listCount: 3
15:12:53:778 * neighbor: 0x00212EFFFF059482 (0x0000), LQI: 32, relation: 0x02 rxOnWHenIdle: 1
15:12:53:778 * neighbor: 0x680AE2FFFE6EA49A (0x9226), LQI: 68, relation: 0x02 rxOnWHenIdle: 1
15:12:53:778 * neighbor: 0x04CF8CDF3C763F7A (0xF0A7), LQI: 36, relation: 0x02 rxOnWHenIdle: 1
15:12:55:017 aps request id: 33 prf: 0x0000 cl: 0x0021 timeout (confirmed: 1) to 0x001788010872FE40 (0xDEC2)
15:12:55:095 aps request id: 33 finished, erase from queue
15:12:57:657 GW update firmware not found: deCONZ_ConBeeII_0x26490700.bin.GCF
15:12:57:733 Mgmt_Lqi_req zdpSeq: 172 to 0x680AE2FFFE6EA49A start index 0
15:12:57:733 APS-DATA.request id: 109, addrmode: 0x03, addr: 0x680ae2fffe6ea49a, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
15:12:57:755 APS-DATA.confirm id: 109, status: 0x00 SUCCESS
15:12:57:756 APS-DATA.confirm request id: 109 -> confirmed, timeout 12152552
15:12:57:770 APS-DATA.indication srcAddr: 0x9226, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 255, rssi: -62
15:12:57:770 APS-DATA.indication request id: 109 -> finished
15:12:57:770 APS-DATA.request id: 109 erase from queue
15:12:57:770 ZDP status = 0x00 -> SUCCESS
15:12:57:770 ZDP Mgmt_Lqi_rsp zdpSeq: 172 from 0x680AE2FFFE6EA49A total: 5, startIndex: 0, listCount: 3
15:12:57:770 * neighbor: 0x00212EFFFF059482 (0x0000), LQI: 162, relation: 0x02 rxOnWHenIdle: 1
15:12:57:770 * neighbor: 0x680AE2FFFE43F767 (0x05E7), LQI: 73, relation: 0x02 rxOnWHenIdle: 1
15:12:57:770 * neighbor: 0x04CF8CDF3C763F7A (0xF0A7), LQI: 150, relation: 0x00 rxOnWHenIdle: 1
15:12:59:812 Mgmt_Lqi_req zdpSeq: 174 to 0x680AE2FFFE6EA49A start index 3
15:12:59:812 APS-DATA.request id: 120, addrmode: 0x03, addr: 0x680ae2fffe6ea49a, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
15:12:59:858 APS-DATA.confirm id: 120, status: 0x00 SUCCESS
15:12:59:858 APS-DATA.confirm request id: 120 -> confirmed, timeout 13525104
15:12:59:872 APS-DATA.indication srcAddr: 0x9226, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 255, rssi: -62
15:12:59:872 APS-DATA.indication request id: 120 -> finished
15:12:59:872 APS-DATA.request id: 120 erase from queue
15:12:59:872 ZDP status = 0x00 -> SUCCESS
15:12:59:872 ZDP Mgmt_Lqi_rsp zdpSeq: 174 from 0x680AE2FFFE6EA49A total: 5, startIndex: 3, listCount: 2
15:12:59:872 * neighbor: 0x680AE2FFFEC3D80A (0xBEEF), LQI: 160, relation: 0x01 rxOnWHenIdle: 0
15:12:59:872 * neighbor: 0x001788010872FE40 (0xDEC2), LQI: 116, relation: 0x01 rxOnWHenIdle: 0

excedra picture excedra on 8 Jul 2020

First things first: please update to 0.78. There is some fix in there for IKEA bulbs. This might be affected. Also make sure to update firmware.

After updating: Check if you can add the light with Phoscon , searching lights. If you still can't : Please provide me a log of the search:)

Mimiix picture Mimiix on 8 Jul 2020

OK, Updated. Now on 2.05.78 / 22.5.2020 and Firmware 26580700 - but still no change...

Reset of the bulb was at 17:48:50.

17:48:47:992 APS-DATA.confirm id: 71, status: 0x00 SUCCESS
17:48:47:992 APS-DATA.confirm request id: 71 -> confirmed, timeout 31509648
17:48:47:998 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 239, rssi: -64
17:48:47:999 APS-DATA.indication request id: 71 -> finished
17:48:47:999 APS-DATA.request id: 71 erase from queue
17:48:47:999 ZDP status = 0x00 -> SUCCESS
17:48:47:999 ZDP Mgmt_Lqi_rsp zdpSeq: 52 from 0x00212EFFFF059482 total: 3, startIndex: 0, listCount: 2
17:48:47:999 * neighbor: 0x680AE2FFFE6EA49A (0x9226), LQI: 243, relation: 0x02 rxOnWHenIdle: 1
17:48:47:999 * neighbor: 0x04CF8CDF3C763F7A (0xF0A7), LQI: 255, relation: 0x02 rxOnWHenIdle: 1
17:48:48:987 Current channel 11
17:48:48:992 CTRL got nwk update id 1
17:48:48:996 Device TTL 3372 s flags: 0x7
17:48:50:232 APS-DATA.indication srcAddr: 0xdec2, srcEp: 0x02 dstAddrMode: 2, profile: 0x0104, cluster: 0xFC00, lqi: 239, rssi: -64
17:48:50:233 no button map for: RWL021 ep: 0x02 cl: 0xFC00 cmd: 0x00 pl[0]: 001
17:48:50:238 APS-DATA.indication srcAddr: 0xdec2, srcEp: 0x01 dstAddrMode: 1, profile: 0x0104, cluster: 0x0006, lqi: 239, rssi: -64
17:48:50:358 Mgmt_Lqi_req zdpSeq: 54 to 0x00212EFFFF059482 start index 2
17:48:50:358 APS-DATA.request id: 88, addrmode: 0x03, addr: 0x00212effff059482, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 1 len: 2 tx.options 0x00
17:48:50:375 APS-DATA.confirm id: 88, status: 0x00 SUCCESS
17:48:50:375 APS-DATA.confirm request id: 88 -> confirmed, timeout 34908552
17:48:50:382 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 121, rssi: 4
17:48:50:382 APS-DATA.indication request id: 88 -> finished
17:48:50:382 APS-DATA.request id: 88 erase from queue
17:48:50:382 ZDP status = 0x00 -> SUCCESS
17:48:50:382 ZDP Mgmt_Lqi_rsp zdpSeq: 54 from 0x00212EFFFF059482 total: 3, startIndex: 2, listCount: 1
17:48:50:382 * neighbor: 0x680AE2FFFE43F767 (0x05E7), LQI: 36, relation: 0x02 rxOnWHenIdle: 1
17:48:50:947 APS-DATA.indication srcAddr: 0xdec2, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x0013, lqi: 239, rssi: -64
17:48:50:947 ZDP device announce: 0x001788010872FE40, 0xDEC2, 0x80
17:48:50:948 DeviceAnnce of SensorNode: 0x001788010872FE40 [1]
17:48:50:985 APS-DATA.indication srcAddr: 0xdec2, srcEp: 0x02 dstAddrMode: 2, profile: 0x0104, cluster: 0xFC00, lqi: 239, rssi: -64
17:48:50:986 no button map for: RWL021 ep: 0x02 cl: 0xFC00 cmd: 0x00 pl[0]: 001
17:48:52:989 don't close database yet, keep open for 900 seconds
17:48:53:718 Mgmt_Lqi_req zdpSeq: 56 to 0x680AE2FFFE43F767 start index 0
17:48:53:718 APS-DATA.request id: 107, addrmode: 0x03, addr: 0x680ae2fffe43f767, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 1 len: 2 tx.options 0x00
17:48:53:739 APS-DATA.confirm id: 107, status: 0x00 SUCCESS
17:48:53:739 APS-DATA.confirm request id: 107 -> confirmed, timeout 34831200
17:48:53:782 APS-DATA.indication srcAddr: 0x05e7, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 239, rssi: -64
17:48:53:782 APS-DATA.indication request id: 107 -> finished
17:48:53:782 APS-DATA.request id: 107 erase from queue
17:48:53:782 ZDP status = 0x00 -> SUCCESS
17:48:53:782 ZDP Mgmt_Lqi_rsp zdpSeq: 56 from 0x680AE2FFFE43F767 total: 3, startIndex: 0, listCount: 3
17:48:53:782 * neighbor: 0x00212EFFFF059482 (0x0000), LQI: 46, relation: 0x02 rxOnWHenIdle: 1
17:48:53:782 * neighbor: 0x680AE2FFFE6EA49A (0x9226), LQI: 77, relation: 0x02 rxOnWHenIdle: 1
17:48:53:782 * neighbor: 0x04CF8CDF3C763F7A (0xF0A7), LQI: 31, relation: 0x02 rxOnWHenIdle: 1
17:48:55:638 APS-DATA.request id: 118, addrmode: 0x02, addr: 0xfffd, profile: 0x0000, cluster: 0x0000, ep: 0x00 -> 0x00 queue: 1 len: 11 tx.options 0x00
17:48:55:639 send NWK_addr_req to 0xF0D1B80000148FC3, last seen 0 s, last seen by neighbors 0 s
17:48:55:717 APS-DATA.confirm id: 118, status: 0x00 SUCCESS
17:48:57:558 Mgmt_Lqi_req zdpSeq: 60 to 0x680AE2FFFE6EA49A start index 0
17:48:57:558 APS-DATA.request id: 128, addrmode: 0x03, addr: 0x680ae2fffe6ea49a, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 2 len: 2 tx.options 0x00
17:48:57:581 APS-DATA.confirm id: 128, status: 0x00 SUCCESS
17:48:57:581 APS-DATA.confirm request id: 128 -> confirmed, timeout 34222712
17:48:57:595 APS-DATA.indication srcAddr: 0x9226, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 215, rssi: -67
17:48:57:595 APS-DATA.indication request id: 128 -> finished
17:48:57:595 APS-DATA.request id: 128 erase from queue
17:48:57:595 ZDP status = 0x00 -> SUCCESS
17:48:57:595 ZDP Mgmt_Lqi_rsp zdpSeq: 60 from 0x680AE2FFFE6EA49A total: 5, startIndex: 0, listCount: 3
17:48:57:595 * neighbor: 0x00212EFFFF059482 (0x0000), LQI: 153, relation: 0x02 rxOnWHenIdle: 1
17:48:57:595 * neighbor: 0x680AE2FFFE43F767 (0x05E7), LQI: 82, relation: 0x02 rxOnWHenIdle: 1
17:48:57:595 * neighbor: 0x04CF8CDF3C763F7A (0xF0A7), LQI: 152, relation: 0x00 rxOnWHenIdle: 1
17:48:58:991 don't close database yet, keep open for 900 seconds
17:48:59:958 Mgmt_Lqi_req zdpSeq: 62 to 0x680AE2FFFE6EA49A start index 3
17:48:59:958 APS-DATA.request id: 140, addrmode: 0x03, addr: 0x680ae2fffe6ea49a, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 2 len: 2 tx.options 0x00
17:48:59:979 APS-DATA.confirm id: 140, status: 0x00 SUCCESS
17:48:59:979 APS-DATA.confirm request id: 140 -> confirmed, timeout 34831200
17:48:59:992 APS-DATA.indication srcAddr: 0x9226, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 207, rssi: -68
17:48:59:992 APS-DATA.indication request id: 140 -> finished
17:48:59:992 APS-DATA.request id: 140 erase from queue
17:48:59:992 ZDP status = 0x00 -> SUCCESS
17:48:59:992 ZDP Mgmt_Lqi_rsp zdpSeq: 62 from 0x680AE2FFFE6EA49A total: 5, startIndex: 3, listCount: 2
17:48:59:992 * neighbor: 0x680AE2FFFEC3D80A (0xBEEF), LQI: 160, relation: 0x01 rxOnWHenIdle: 0
17:48:59:992 * neighbor: 0x001788010872FE40 (0xDEC2), LQI: 107, relation: 0x01 rxOnWHenIdle: 0
17:49:02:838 Mgmt_Lqi_req zdpSeq: 64 to 0x00212EFFFF059482 start index 0
17:49:02:839 APS-DATA.request id: 155, addrmode: 0x03, addr: 0x00212effff059482, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 2 len: 2 tx.options 0x00
17:49:02:857 APS-DATA.confirm id: 155, status: 0x00 SUCCESS
17:49:02:857 APS-DATA.confirm request id: 155 -> confirmed, timeout 35589208
17:49:02:863 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 0, rssi: 1
17:49:02:864 APS-DATA.indication request id: 155 -> finished
17:49:02:864 APS-DATA.request id: 155 erase from queue
17:49:02:864 ZDP status = 0x00 -> SUCCESS
17:49:02:864 ZDP Mgmt_Lqi_rsp zdpSeq: 64 from 0x00212EFFFF059482 total: 3, startIndex: 0, listCount: 2
17:49:02:864 * neighbor: 0x680AE2FFFE6EA49A (0x9226), LQI: 220, relation: 0x02 rxOnWHenIdle: 1
17:49:02:864 * neighbor: 0x04CF8CDF3C763F7A (0xF0A7), LQI: 255, relation: 0x02 rxOnWHenIdle: 1
17:49:04:991 don't close database yet, keep open for 900 seconds
17:49:05:238 Mgmt_Lqi_req zdpSeq: 66 to 0x00212EFFFF059482 start index 2
17:49:05:238 APS-DATA.request id: 168, addrmode: 0x03, addr: 0x00212effff059482, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 2 len: 2 tx.options 0x00
17:49:05:255 APS-DATA.confirm id: 168, status: 0x00 SUCCESS
17:49:05:255 APS-DATA.confirm request id: 168 -> confirmed, timeout 31176400
17:49:05:262 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 121, rssi: 4
17:49:05:262 APS-DATA.indication request id: 168 -> finished
17:49:05:262 APS-DATA.request id: 168 erase from queue
17:49:05:262 ZDP status = 0x00 -> SUCCESS
17:49:05:262 ZDP Mgmt_Lqi_rsp zdpSeq: 66 from 0x00212EFFFF059482 total: 3, startIndex: 2, listCount: 1
17:49:05:262 * neighbor: 0x680AE2FFFE43F767 (0x05E7), LQI: 31, relation: 0x02 rxOnWHenIdle: 1
17:49:08:038 aps request id: 95 prf: 0x0000 cl: 0x0000 timeout (confirmed: 1) to 0x680AE2FFFE43F767 (0xFFFD)
17:49:08:118 aps request id: 95 finished, erase from queue
17:49:08:599 Mgmt_Lqi_req zdpSeq: 68 to 0x680AE2FFFE43F767 start index 0
17:49:08:599 APS-DATA.request id: 184, addrmode: 0x03, addr: 0x680ae2fffe43f767, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 1 len: 2 tx.options 0x00
17:49:08:622 APS-DATA.confirm id: 184, status: 0x00 SUCCESS
17:49:08:622 APS-DATA.confirm request id: 184 -> confirmed, timeout 31176400
17:49:08:656 APS-DATA.indication srcAddr: 0x05e7, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 207, rssi: -68
17:49:08:656 APS-DATA.indication request id: 184 -> finished
17:49:08:656 APS-DATA.request id: 184 erase from queue
17:49:08:656 ZDP status = 0x00 -> SUCCESS
17:49:08:656 ZDP Mgmt_Lqi_rsp zdpSeq: 68 from 0x680AE2FFFE43F767 total: 3, startIndex: 0, listCount: 3
17:49:08:657 * neighbor: 0x00212EFFFF059482 (0x0000), LQI: 47, relation: 0x02 rxOnWHenIdle: 1
17:49:08:657 * neighbor: 0x680AE2FFFE6EA49A (0x9226), LQI: 76, relation: 0x02 rxOnWHenIdle: 1
17:49:08:657 * neighbor: 0x04CF8CDF3C763F7A (0xF0A7), LQI: 31, relation: 0x02 rxOnWHenIdle: 1
17:49:10:033 don't close database yet, keep open for 900 seconds
17:49:12:438 Mgmt_Lqi_req zdpSeq: 71 to 0x680AE2FFFE6EA49A start index 0
17:49:12:438 APS-DATA.request id: 203, addrmode: 0x03, addr: 0x680ae2fffe6ea49a, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 1 len: 2 tx.options 0x00
17:49:12:462 APS-DATA.confirm id: 203, status: 0x00 SUCCESS
17:49:12:462 APS-DATA.confirm request id: 203 -> confirmed, timeout 34377288
17:49:12:478 APS-DATA.indication srcAddr: 0x9226, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 207, rssi: -68
17:49:12:478 APS-DATA.indication request id: 203 -> finished
17:49:12:478 APS-DATA.request id: 203 erase from queue
17:49:12:478 ZDP status = 0x00 -> SUCCESS
17:49:12:478 ZDP Mgmt_Lqi_rsp zdpSeq: 71 from 0x680AE2FFFE6EA49A total: 5, startIndex: 0, listCount: 3
17:49:12:478 * neighbor: 0x00212EFFFF059482 (0x0000), LQI: 149, relation: 0x02 rxOnWHenIdle: 1
17:49:12:478 * neighbor: 0x680AE2FFFE43F767 (0x05E7), LQI: 82, relation: 0x02 rxOnWHenIdle: 1
17:49:12:478 * neighbor: 0x04CF8CDF3C763F7A (0xF0A7), LQI: 152, relation: 0x00 rxOnWHenIdle: 1
17:49:14:838 Mgmt_Lqi_req zdpSeq: 73 to 0x680AE2FFFE6EA49A start index 3
17:49:14:838 APS-DATA.request id: 216, addrmode: 0x03, addr: 0x680ae2fffe6ea49a, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 1 len: 2 tx.options 0x00
17:49:14:861 APS-DATA.confirm id: 216, status: 0x00 SUCCESS
17:49:14:861 APS-DATA.confirm request id: 216 -> confirmed, timeout 34369808
17:49:14:874 APS-DATA.indication srcAddr: 0x9226, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 207, rssi: -68
17:49:14:874 APS-DATA.indication request id: 216 -> finished
17:49:14:874 APS-DATA.request id: 216 erase from queue
17:49:14:875 ZDP status = 0x00 -> SUCCESS
17:49:14:875 ZDP Mgmt_Lqi_rsp zdpSeq: 73 from 0x680AE2FFFE6EA49A total: 5, startIndex: 3, listCount: 2
17:49:14:875 * neighbor: 0x680AE2FFFEC3D80A (0xBEEF), LQI: 160, relation: 0x01 rxOnWHenIdle: 0
17:49:14:875 * neighbor: 0x001788010872FE40 (0xDEC2), LQI: 107, relation: 0x01 rxOnWHenIdle: 0
17:49:17:719 Mgmt_Lqi_req zdpSeq: 75 to 0x00212EFFFF059482 start index 0
17:49:17:719 APS-DATA.request id: 230, addrmode: 0x03, addr: 0x00212effff059482, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 1 len: 2 tx.options 0x00
17:49:17:749 don't close database yet, keep open for 900 seconds
17:49:17:752 APS-DATA.confirm id: 230, status: 0x00 SUCCESS
17:49:17:752 APS-DATA.confirm request id: 230 -> confirmed, timeout 34369808
17:49:17:758 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 121, rssi: 4
17:49:17:759 APS-DATA.indication request id: 230 -> finished
17:49:17:759 APS-DATA.request id: 230 erase from queue
17:49:17:759 ZDP status = 0x00 -> SUCCESS
17:49:17:759 ZDP Mgmt_Lqi_rsp zdpSeq: 75 from 0x00212EFFFF059482 total: 3, startIndex: 0, listCount: 2
17:49:17:759 * neighbor: 0x680AE2FFFE6EA49A (0x9226), LQI: 220, relation: 0x02 rxOnWHenIdle: 1
17:49:17:759 * neighbor: 0x04CF8CDF3C763F7A (0xF0A7), LQI: 255, relation: 0x02 rxOnWHenIdle: 1
17:49:20:119 Mgmt_Lqi_req zdpSeq: 77 to 0x00212EFFFF059482 start index 2
17:49:20:119 APS-DATA.request id: 243, addrmode: 0x03, addr: 0x00212effff059482, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 1 len: 2 tx.options 0x00
17:49:20:133 APS-DATA.confirm id: 243, status: 0x00 SUCCESS
17:49:20:133 APS-DATA.confirm request id: 243 -> confirmed, timeout 34629320
17:49:20:140 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 121, rssi: 4
17:49:20:140 APS-DATA.indication request id: 243 -> finished
17:49:20:140 APS-DATA.request id: 243 erase from queue
17:49:20:140 ZDP status = 0x00 -> SUCCESS
17:49:20:140 ZDP Mgmt_Lqi_rsp zdpSeq: 77 from 0x00212EFFFF059482 total: 3, startIndex: 2, listCount: 1
17:49:20:140 * neighbor: 0x680AE2FFFE43F767 (0x05E7), LQI: 33, relation: 0x02 rxOnWHenIdle: 1
17:49:22:517 APS-DATA.indication srcAddr: 0xbeef, srcEp: 0x01 dstAddrMode: 1, profile: 0x0104, cluster: 0x0006, lqi: 255, rssi: -56
17:49:22:519 button 1002 On with timed off
17:49:22:531 rule event /sensors/8/state/lastupdated: 0 -> 0
17:49:22:531 trigger rule 10 - pir-fsm-trigger-8
17:49:22:543 rule event /sensors/8/state/lastupdated: 0 -> 0
17:49:22:543 trigger rule 10 - pir-fsm-trigger-8
17:49:22:548 rule event /sensors/10/state/lastupdated: 0 -> 0
17:49:22:548 trigger rule 1 - pir-fsm-state-start
17:49:22:550 APS-DATA.request id: 3, addrmode: 0x01, addr: 0x0001, profile: 0x0104, cluster: 0x0006, ep: 0x01 -> 0xFF queue: 1 len: 3 tx.options 0x00
17:49:22:551 delayed group sending
17:49:22:553 rule event /sensors/10/state/lastupdated: 0 -> 0
17:49:22:553 trigger rule 1 - pir-fsm-state-start
17:49:22:554 delayed group sending
17:49:22:554 delayed group sending
17:49:22:555 delayed group sending
17:49:22:555 delayed group sending
17:49:22:555 delayed group sending
17:49:22:559 rule event /sensors/11/state/status: 0 -> 1
17:49:22:567 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x01 dstAddrMode: 1, profile: 0x0104, cluster: 0x0006, lqi: 239, rssi: -64
17:49:22:571 delayed group sending
17:49:22:571 delayed group sending
17:49:22:571 delayed group sending
17:49:22:584 rule event /groups/1/state/any_on: 0 -> 1
17:49:22:670 APS-DATA.request id: 6, addrmode: 0x01, addr: 0x0001, profile: 0x0104, cluster: 0x0008, ep: 0x01 -> 0xFF queue: 2 len: 6 tx.options 0x00
17:49:22:690 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x01 dstAddrMode: 1, profile: 0x0104, cluster: 0x0008, lqi: 0, rssi: 1
17:49:22:771 APS-DATA.request id: 8, addrmode: 0x01, addr: 0x0001, profile: 0x0104, cluster: 0x0006, ep: 0x01 -> 0xFF queue: 3 len: 3 tx.options 0x00
17:49:22:786 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x01 dstAddrMode: 1, profile: 0x0104, cluster: 0x0006, lqi: 121, rssi: 4
17:49:22:871 APS-DATA.request id: 11, addrmode: 0x01, addr: 0x0001, profile: 0x0104, cluster: 0x0008, ep: 0x01 -> 0xFF queue: 4 len: 6 tx.options 0x00
17:49:22:886 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x01 dstAddrMode: 1, profile: 0x0104, cluster: 0x0008, lqi: 0, rssi: 1
17:49:23:004 don't close database yet, keep open for 900 seconds
17:49:23:138 APS-DATA.confirm id: 3, status: 0x00 SUCCESS
17:49:23:138 APS-DATA.confirm request id: 3 -> erase from queue
17:49:23:159 aps request id: 3 finished, erase from queue
17:49:23:248 APS-DATA.confirm id: 6, status: 0x00 SUCCESS
17:49:23:248 APS-DATA.confirm request id: 6 -> erase from queue
17:49:23:318 aps request id: 6 finished, erase from queue
17:49:23:358 APS-DATA.confirm id: 8, status: 0x00 SUCCESS
17:49:23:358 APS-DATA.confirm request id: 8 -> erase from queue
17:49:23:398 aps request id: 8 finished, erase from queue
17:49:23:467 APS-DATA.confirm id: 11, status: 0x00 SUCCESS
17:49:23:467 APS-DATA.confirm request id: 11 -> erase from queue
17:49:23:470 Set sensor check interval to 100 milliseconds
17:49:23:478 Mgmt_Lqi_req zdpSeq: 79 to 0x680AE2FFFE43F767 start index 0
17:49:23:479 APS-DATA.request id: 24, addrmode: 0x03, addr: 0x680ae2fffe43f767, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 2 len: 2 tx.options 0x00
17:49:23:479 aps request id: 11 finished, erase from queue
17:49:23:499 APS-DATA.confirm id: 24, status: 0x00 SUCCESS
17:49:23:499 APS-DATA.confirm request id: 24 -> confirmed, timeout 34830960
17:49:23:532 APS-DATA.indication srcAddr: 0x05e7, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 255, rssi: -57
17:49:23:532 APS-DATA.indication request id: 24 -> finished
17:49:23:532 APS-DATA.request id: 24 erase from queue
17:49:23:532 ZDP status = 0x00 -> SUCCESS
17:49:23:532 ZDP Mgmt_Lqi_rsp zdpSeq: 79 from 0x680AE2FFFE43F767 total: 3, startIndex: 0, listCount: 3
17:49:23:532 * neighbor: 0x00212EFFFF059482 (0x0000), LQI: 44, relation: 0x02 rxOnWHenIdle: 1
17:49:23:533 * neighbor: 0x680AE2FFFE6EA49A (0x9226), LQI: 76, relation: 0x02 rxOnWHenIdle: 1
17:49:23:533 * neighbor: 0x04CF8CDF3C763F7A (0xF0A7), LQI: 31, relation: 0x02 rxOnWHenIdle: 1
17:49:27:318 Mgmt_Lqi_req zdpSeq: 82 to 0x680AE2FFFE6EA49A start index 0
17:49:27:319 APS-DATA.request id: 43, addrmode: 0x03, addr: 0x680ae2fffe6ea49a, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 1 len: 2 tx.options 0x00
17:49:27:340 APS-DATA.confirm id: 43, status: 0x00 SUCCESS
17:49:27:340 APS-DATA.confirm request id: 43 -> confirmed, timeout 34830960
17:49:27:356 APS-DATA.indication srcAddr: 0x9226, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 239, rssi: -64
17:49:27:356 APS-DATA.indication request id: 43 -> finished
17:49:27:356 APS-DATA.request id: 43 erase from queue
17:49:27:356 ZDP status = 0x00 -> SUCCESS

excedra picture excedra on 8 Jul 2020

I don't see any hints deconz entered pairing mode nor any device makes any attempt to pair. How do you pair, Phoscon lights search?

SwoopX picture SwoopX on 10 Jul 2020

I have TRADFRI LED1737R5/LED1739R5 GU10, in my case I had a similar problem. Try to reset the button not with 6 turn off and on, but with 7. Strange but this way it was working for me.

ursusHU picture ursusHU on 16 Jul 2020

@ursusHU I think it was the reset problems with the WS2.0. From the release note:
"WS 2.0 opal bulb V-2.0.023.
Improvement ImageID updated in attribute.
Improvement factory reset time is aligned with existing devices."
I don't know if the the LED1537R6/LED1739R5 its the WS2.0 but the new version with glass its and with the update firmware its behaving like other Ikea bulb. Most Ikea bulbs have getting Z3 upgrade and fixes and some old (CWS1.0 = The old LL RGBW) have also getting fixes the last month.

MattWestb picture MattWestb on 16 Jul 2020

@SwoopX: Can you please provide my the parameters for deCONZ for the loggin you need? I am not familiar with the logs of deCONZ/Zigbee. Then I will re-run this.

excedra picture excedra on 16 Jul 2020

Similar here.

Resetting bulb w 6x on/off works fine. Additional on/off and it pairs. But only one bulb pairs, not able to pair additional ones.

Running a Conbee II on a Pi 4B w Home Assistant. 2.05.78 and 264A0700 (shows available update 26580700 but does not complete it).

Hessenpower01 picture Hessenpower01 on 16 Jul 2020

To answer your last question @Hessenpower01 : You can't use the HA addon to update the firmware. See https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/Update-deCONZ-manually#update-in-docker

and https://github.com/home-assistant/hassio-addons/issues/1347

Mimiix picture Mimiix on 16 Jul 2020
👍1

@Hessenpower01 Its normal with (my 2 years experience of) deCONZ need a reboot after some pared devices and also after some time running you must restart for paring to working.
@Mimiix / Dennis it's some for writing in the wicki or putting on the todo list with expiring date for a very old bugg (firmware lock or in the core).

MattWestb picture MattWestb on 16 Jul 2020

@MattWestb The HA addon isn't anything we manage. They are working on it. It is in the wiki.

Mimiix picture Mimiix on 16 Jul 2020

@MattWestb The HA addon isn't anything we manage. They are working on it. It is in the wiki.

This bug was present in the Phoscon-GW official downloaded image from DE that i was first installed for more then 2 years ago (https://phoscon.de/en/raspbee/sdcard).
And if its also present in the HA addon i have not tested then i running it stand alone but i think its more then likely then its one dervat of the core code in Phoscon.
If you don't believe my:
1 do some time travel in all the slated issues and you finding many cases that coming from this bug direct or indirect.
2 make a new install and trying the scenario out.
3 make the same as 2 but with one older version.
4 (most likely) Slat the case.
Or IF you believe my: flagging the case at bugg and putting one experens date on it (< 2 years pleas and not automatic slat).

And can you pleas forwarding the info to Redacted by Mimiix. I do not allow sharing of other peoples personal information. No need for it in any way.

MattWestb picture MattWestb on 17 Jul 2020

@excedra Well, it seems that you already enabled almost all debug output that is possbile, so from that perspective, there's probably not more that can be done. Another approach to be tried could be to enter joining directly via deconz GUI.

SwoopX picture SwoopX on 17 Jul 2020

@MattWestb I am not sure what you are on about. The bug you refer to is pickedup in the HA addon. The firmware itself can be updated trough that button on the stand alone images.

If you have any issue or want to discuss your problems on this git: Open a seperate issue on your own.

Mimiix picture Mimiix on 17 Jul 2020

I was addressing Hessenpower01s problem with Paring not working after some time and its well documented and the root its in the firmware and / or deCONZ so you getting the paring problem in phoscon, old web app and in deconz-rest-plugin.
And i was as a community member trying to helping other member with one very well known problem.
By the way in the post before it was only referring to official info from Amazon,de (DEs selling contact) and FCC-ID (RaspBee II FCC cert) and the company registration in germany so its no secrets at all for EU citizens as you and my but perhaps not for other.

MattWestb picture MattWestb on 17 Jul 2020

My reply is unrelated to the this particular case and only to your messages. I understand that the information is open, but i won't allow sharing personal information of anyone else in any case. This includes open information.

As i said before: If you have stuff to say, open a own issue on this git page. I don't mind the subject, but you can't hijack other peoples issues. This will be my last reply on this issue of this subject and it won't help @excedra to solve his issue.

Mimiix picture Mimiix on 17 Jul 2020

Thanks all for the help. What made it work:

  • updated FW with Raspbian
  • prolonged the search period from 1 minute to 3 minutes
  • switched off the IKEA Access Point (even if bulb wasn't paired to)

pairing procedure:

  • bulb off
  • start pairing in Deconz
  • put bulb in reset mode (6x on/ off), no additional on/ off!
  • wait ...

this way it seems to work stable for me.

Hessenpower01 picture Hessenpower01 on 17 Jul 2020

Sounds great Hessenpower01 and i hope you have a stale system for your lights.
True updating the firmware in the bulbs 2 its normally helping.
One more thing: Make sure that the Ikea GW and deCONZ is using different channels.
To find the Ikea GW channel open the old wep app "Wireless Light Control", upper right menu, settings. Then in the lower part its "Reset Devices via Touchlink". Klick on scan for Devices.
You getting one list with lights and ther channel and network ID. If you see 2 devices with different network id and the same channel then its best / easiest reconfiguration deCONZs channel.
Edit: Sorry Touchlink its not implemented in CornBee II so its not working for you !!

MattWestb picture MattWestb on 17 Jul 2020

@Hessenpower01 That 3 minutes is imho something that is underrated. I have done that instantly as 1 min seems way to short. Glad you fixed it.

@excedra Can you try and see what @Hessenpower01's method does for you :)?

Mimiix picture Mimiix on 17 Jul 2020

@Mimiix: Yes - and no. Finally got them paired. BUT:

  • Resetting them with the Philips Remote does not work. The bulb starts the dimming, but with the switch on/off method, it comtinues the dimming longer and powers doesn, then goes dimming on. This is the paring.
  • Resetting them as instructed by IKEA (and many others in tuturials, etc.) with delays and other options does not work. You have to hammer the switch on and of as fast as possible. (from the ON state 12 times: 6 offs and 6 ons).
  • Start pairing before the reset of the bulb. 1 minute for paring is fine.
  • After paring the first one, i've tried paring two of them at the same time. That does not work. (but resetting them together works).
    But...

All of this worked only after I completly resetted my deconz and started a new network. Now all is fine.

excedra picture excedra on 21 Jul 2020

Great that you have getting you system up and running.
Ikea bulbs can being one PITA to resetting and some was having bugs that its fixed the last month with new firmware so look if deCONZ can upgrade the firmware in you bulbs.
If the OTA upgrade not working first restart deCONZ and wait little and aktivate the OTA updater plugin and then repower one bulb at the time (taking around one hour / bulb).

MattWestb picture MattWestb on 21 Jul 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

stale[bot] picture stale[bot] on 12 Aug 2020

@excedra may I ask you how did you reset the deConz? I have a very similar problem, but would like to avoid reinstalling my whole RPI.

ursusHU picture ursusHU on 17 Aug 2020

I can confirming that LED1837R5 (and problerly all other IKEA WS2 lights) can doing some very strange things and not being able to resetting them and therefore not getting paired.
I was having 3 in one groupe and was reconfiguration one of them then the binding was not done correct (of my). Was sending one reset to the device and it was leaving the network and flashing for conformation it have being reseted. Was doing little more things and some minutes later i was trying to pairing it but no reaction from it (no blinking after 6 on/off or fading then being in pairing mode after power on). Was trying on / off reset for 30 minutes without success.
Was using the old webbapp and stretching for touchlink devices and its there on channel 20 with one unique panid (if ZB3 devices is failing pairing they going in find and bind mode and its having doing that = own network). Blinking the device and its the right one and then sending reset and its confirming it with flashing the light. Paring it and all is OK.
That the device is making its own network then can't pairing is OK, but refusing being reseted with "on/off" is not and very bad behaviour !!!

One great thing having one RaspBee I that have working touchlink in the firmware and the old webb app :-))
If its dying i have one HUE remote dimmer for security for doing touch resets of bad devices.

MattWestb picture MattWestb on 6 Sep 2020

As there hasn't been any response in 21 days, this issue has been automatically marked as stale. At OP: Please either close this issue or keep it active It will be closed in 7 days if no further activity occurs.

stale[bot] picture stale[bot] on 29 Sep 2020

The Seven on-off in a rapid sequence did it for me

jppataki picture jppataki on 4 Oct 2020
👍1

As there hasn't been any response in 21 days, this issue has been automatically marked as stale. At OP: Please either close this issue or keep it active It will be closed in 7 days if no further activity occurs.

stale[bot] picture stale[bot] on 1 Nov 2020

As there hasn't been any response in 28 days, this issue will be closed. @ OP: If this issue is solved post what fixed it for you. If it isn't solved, request to get this opened again.

stale[bot] picture stale[bot] on 9 Nov 2020
Was this page helpful?
0 / 5 - 0 ratings

Related issues

1onar picture 1onar  路  5Comments
tenholde picture tenholde  路  3Comments
7wells picture 7wells  路  4Comments
salopette picture salopette  路  4Comments
horchi picture horchi  路  5Comments