Unable to pair Philips Hue Motion Sensor with Conbee II

nowisk · October 3, 2021, 2:59pm

I’m currently unable to pair the Philips Hue motion sensor with the Conbee II despite several attempts.

Firmware version: 0x26720700
deConz: v2.12.6

Steps taken to resolve:

I’ve tried pairing the device with both my raspberry pi running Home Assistant OS and my Windows machine. I’ve also tried using a USB extension cable and selecting different ZigBee channels to avoid WiFi interference.

As far as I can tell the device is being detected during pairing, but is not being recognized properly. This is what I see in the deConz GUI:

hue-sensor

This is some of what I managed to pull out of the logs:

07:37:35:508 APS-DATA.request id: 233, addrmode: 0x03, addr: 0x00212effff0774ee, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
07:37:35:519 APS-DATA.confirm id: 233, status: 0x00 SUCCESS
07:37:35:519 APS-DATA.confirm request id: 233 -> confirmed, timeout 876717861
07:37:35:527 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 0, rssi: 0
07:37:35:527 	asdu: 2e00010001ee7407ffff2e21002bba090b01881700f9e8120001ff
07:37:35:528 APS-DATA.indication request id: 233 -> finished
07:37:35:528 APS-DATA.request id: 233 erase from queue
07:37:35:528 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
07:37:35:530 neigbor 0x001788010b09ba2b is unknown child
07:37:36:078 CTRL skip creating node 0x001788010B09BA2B while permit join is disabled
07:37:37:764 APS-DATA.request id: 244, addrmode: 0x03, addr: 0x00212effff0774ee, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
07:37:37:776 APS-DATA.confirm id: 244, status: 0x00 SUCCESS
07:37:37:776 APS-DATA.confirm request id: 244 -> confirmed, timeout 876720118
07:37:37:783 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 0, rssi: 0
07:37:37:783 	asdu: 2f00010001ee7407ffff2e21002bba090b01881700f9e8120001ff
07:37:37:783 APS-DATA.indication request id: 244 -> finished
07:37:37:784 APS-DATA.request id: 244 erase from queue
07:37:37:784 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
07:37:37:784 neigbor 0x001788010b09ba2b is unknown child
07:37:38:322 CTRL skip creating node 0x001788010B09BA2B while permit join is disabled
07:37:39:638 APS-DATA.request id: 253, addrmode: 0x02, addr: 0xfffc, profile: 0x0000, cluster: 0x0036, ep: 0x00 -> 0x00 queue: 0 len: 3 tx.options 0x00
07:37:39:638 send permit join, duration: 59
07:37:39:639 APS-DATA.request id: 254, addrmode: 0x02, addr: 0xfffc, profile: 0xA1E0, cluster: 0x0021, ep: 0xF2 -> 0xF2 queue: 1 len: 6 tx.options 0x00
07:37:40:012 APS-DATA.request id: 1, addrmode: 0x03, addr: 0x00212effff0774ee, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 2 len: 2 tx.options 0x00
07:37:40:023 APS-DATA.confirm id: 1, status: 0x00 SUCCESS
07:37:40:024 APS-DATA.confirm request id: 1 -> confirmed, timeout 876722366
07:37:40:031 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 0, rssi: 0
07:37:40:031 	asdu: 3000010001ee7407ffff2e21002bba090b01881700f9e8120001ff
07:37:40:031 APS-DATA.indication request id: 1 -> finished
07:37:40:032 APS-DATA.request id: 1 erase from queue
07:37:40:032 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
07:37:40:032 neigbor 0x001788010b09ba2b is unknown child
07:37:40:295 APS-DATA.confirm id: 253, status: 0x00 SUCCESS
07:37:40:306 APS-DATA.confirm id: 254, status: 0x00 SUCCESS
07:37:40:386 aps request id: 253 finished, erase from queue
07:37:40:480 aps request id: 254 finished, erase from queue
07:37:40:576 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 2, node: 0xE8F9
07:37:40:576 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 1, node: 0xE8F9
07:37:40:576 new node - ext: 0x001788010b09ba2b, nwk: 0xE8F9
07:37:40:603 GW update firmware not found: deCONZ_ConBeeII_0x26660700.bin.GCF
07:37:42:821 APS-DATA.request id: 14, addrmode: 0x03, addr: 0x00212effff0774ee, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
07:37:42:833 APS-DATA.confirm id: 14, status: 0x00 SUCCESS
07:37:42:833 APS-DATA.confirm request id: 14 -> confirmed, timeout 876725175
07:37:42:841 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 0, rssi: 0
07:37:42:841 	asdu: 3100010001ee7407ffff2e21002bba090b01881700f9e8120001ff
07:37:42:841 APS-DATA.indication request id: 14 -> finished
07:37:42:841 APS-DATA.request id: 14 erase from queue
07:37:42:842 void deCONZ::zmNode::setFetched(deCONZ::RequestId, bool) fetched item: 8, node: 0x0000
07:37:44:557 Daylight now: sunriseEnd, status: 150, daylight: 1, dark: 0

I’m not really sure if this is an issue with deConz/Conbee or the device itself. I have not tried pairing this with a Hue bridge since I didn’t think that would be needed.

TheNON75 · October 4, 2021, 4:48pm

Hi,
It is a battery device that needs longer time to report everything about itself.
You may click in the deconz gui manually to read basic cluster, but then you ave to keep the device awake, otherwise it is sleeping to conserve battery

In addition the newest firmware is recommended.

nowisk · October 5, 2021, 11:24am

I’m pretty sure 0x26720700 is the latest firmware. If the device needs longer to report everything then I’m not sure what else I can do, since I can’t change how long the Phoscon web app will scan for.

I’ve also tried using the Read Node Descriptor and Read Power Descriptor in the gui but this didn’t seem to do anything either. I made sure that the device was awake by checking that the amber LED on the front was flashing.

Arot · November 23, 2021, 9:34am

Did you solve the problem?
I have the same with the outdoor motion sensor.

Michael · November 23, 2021, 3:07pm

same outdoor sensor not working, I can pair it though, but it stays with “unreachable” after that.

Mimiix · November 23, 2021, 3:17pm

@Arot @Michael are you on the latest beta 2.13.2?

Arot · November 23, 2021, 4:40pm

@Mimiix Yes the latest beta is installed.

Tamiami · December 4, 2021, 1:10pm

Same here, I guess. The Hue outdoor motion detector is connecting and afterwards not available. I have already one connected. One remark: If I try to pair, one of my lights is blincking. I estimate this could be the issue?

Update: And BETA dosen´t recognize the conbee 2 stick via Docker (DSM 7.0.1).
Update 2: The Conbee 2 was found after some modifications. With new 2.13.2 version the Hue motion detector is working

juggleking · April 28, 2023, 7:30am

I had the same issue. But upgrading to the latest deconzcommunity/deconz docker image fixed it. ( Using synology ).

I now get very bad refresh rates on the data the sensor is sending out. Any experience with that ?

Gautama · April 28, 2023, 8:32am

Maybe the connection isn´t that stable.
Have you looked at the LQI strengh?