I’ve updated do 13.0.01 and am not able to pair Hue Motion Sensor.
After adding a device to Deconz via Phoscon it’s Not reachable for all the times but it have good route connection.
I have a few Hue & Aqara sensors but only this new one have a problems.
That sensor is very close about 4 routers (SHP-13, Ikea Trådfri)
What might be a problem?
21:06:25:212 Bind response success for 0x00178801032b8c3b ep: 0x02 cluster: 0x0001
21:06:24:773 Bind response success for 0x00178801032b8c3b ep: 0x02 cluster: 0x0402
21:06:22:128 Bind response success for 0x00178801032b8c3b ep: 0x02 cluster: 0x0400
21:06:20:564 Bind response success for 0x00178801032b8c3b ep: 0x02 cluster: 0x0406
21:06:18:714  get node descriptor for 0x00178801032b8c3b
21:06:18:518 0x00178801032B8C3B error APSDE-DATA.confirm: 0xE1 on task
21:06:18:155 Bind response success for 0x00178801032b8c3b ep: 0x02 cluster: 0x0000
21:06:17:847 discard double entry in binding queue (size: 5) for for 0x00178801032B8C3B, cluster 0x0402
21:06:17:845 discard double entry in binding queue (size: 5) for for 0x00178801032B8C3B, cluster 0x0400
21:06:17:842 discard double entry in binding queue (size: 5) for for 0x00178801032B8C3B, cluster 0x0406
21:06:17:842 discard double entry in binding queue (size: 5) for for 0x00178801032B8C3B, cluster 0x0001
21:06:17:841 discard double entry in binding queue (size: 5) for for 0x00178801032B8C3B, cluster 0x0000
21:06:17:838 device announce 0x00178801032B8C3B (0x7045) mac capabilities 0x80
21:06:17:838 ... (0x00178801032B8C3B / 0x7045)
21:06:17:838 FP indication 0x0000 / 0x0013 (0x00178801032B8C3B / 0x7045)
21:06:17:838 set fast probe address to 0x00178801032B8C3B (0x7045)
21:06:17:837 device announce 0x00178801032B8C3B (0x7045) mac capabilities 0x80
21:06:17:835 DeviceAnnce of SensorNode: 0x00178801032B8C3B 
21:06:17:833 DeviceAnnce of SensorNode: 0x00178801032B8C3B 
21:06:17:830 DeviceAnnce of SensorNode: 0x00178801032B8C3B 
20:50:47:440 DEV found DDF for 0x00178801032B8C3B, path: /usr/share/deCONZ/devices/philips/sml001_motion_sensor.json
20:50:44:667 SensorNode 75 set node 0x00178801032b8c3b
20:50:44:666 SensorNode 74 set node 0x00178801032b8c3b
20:50:44:665 SensorNode 73 set node 0x00178801032b8c3b
I had the same issue already with old 12.x version.
After deleting and pairing again it finally worked. Sometimes the sensor was shown as not reachable at all, sometimes light-level and temperature was missing.
But after multiple retries it finally worked.
Not in my case. I trying to delete and pair again all day.
I see in GUI that it recognized as 2 devices - on/off and presence sensor.
There is the 0xE1 error in your logs. Did you check the recommendations regarding this error?
I didn’t but I read now. So this code mean interference issues. But I pair aquaria sensor next to this Hue Motion and it works properly. So only error is with Hue Motion which is not reachable.
Can you please give details to your system:
For further conversation, it is useful to have the answers to these questions available. Even though this list of questions may seem extensive and overwhelming at first glance, we ask you to answer all questions. This way we can localize causes of the problem and answer questions faster.
The deCONZ and firmware versions can be found in the Phoscon App: Menu > Settings > Gateway, and also in the deCONZ GUI: Menu > Help > About deCONZ.
- host system (Raspberry Pi 3B+ / 4B / PC / NAS):
- execution method (Raspbian / Ubuntu / Home Assistant deCONZ add-on / Marthoc Docker container / Windows / Virtual Machine):
- firmware version (format 26xxyy00):
- deCONZ Version (Format 2.xx.yy):
- device (ConBee I / ConBee II / RaspBee I / RaspBee II):
- Is the ConBee I / II connected to a USB 2.0 or USB 3.0 (blue) socket? - only relevant for ConBee I/II:
- Is a USB extension used? (yes / no) - only relevant for ConBee I/II:
- Are other USB or serial devices connected to the host system? (yes / no) - If yes: which ones?):
- Is a home automation system, other software or third-party apps used in addition to deCONZ / Phoscon App? (yes / no) - If yes: which ones?):
- Have you tried changing the Zigbee channel or other settings as a solution? (yes / no) - If yes: which ones?):
- If Raspberry Pi: which power supply is used? (original / manufacturer+model) Specify volts and amps: (e.g. 5.0V, 1.0A):
- if Raspberry Pi: On which image base is the system set up?: (Phoscon / Raspbian / Raspberry Pi OS / Home Assistant …):
- If Raspberry Pi: Is an SD card or an SSD used?:
- If Raspberry Pi: Which way was deCONZ installed? (APT repository / dpkg / via a plug-in).
@marithpl if there’s 0xE1, there’s interference. Before that is fixed, we can’t know for sure it’s a bug. Now the 0xe1 is most likely to be the cause of this.
- Synology NAS
- Marthoc Docker Container
- Latest firmware 26660700
- 2.13.00 / 2.13.01 / 2.12.03 (I’ve rollback)
- Conbee II
- USB 2.0 with extension cable
- HA, Deconz, Phoscon
- No I didn’t
Honestly I’ve a problem with 2 of 3 devices I last connected - this Hue Sensor and Ikea Float which have long delays.
Edited: The Ikea Floalt also have 0xE1 error.
21:32:25:297 0xD0CF5EFFFE2C0F01 error APSDE-DATA.confirm: 0xE1 on task
I have about 51 nodes and only these 2 not works properly
For topic 2.: Its important to know the current firmware number you are using . The Format is 26xxyy00. The firmware version can be found in the Phoscon App: Menu > Settings > Gateway, and also in the deCONZ GUI: Menu > Help > About deCONZ.
For topic 7: What do you mean? You use an USB extension cable for the ConBee II yes or no?
For topic 8: Are other USB or serial devices connected to your Synology?
For topic 9: Obviously you are using Home Assistant on top of deCONZ.
The problem can most likely be fixed by manually rewriting the firmware of the ConBee II on a native system while deCONZ is closed, preferably on a Linux system.
The easiest way to do this is with a Raspberry Pi and a separate SD card. Just write our Image with Desktop to the SD card and use these commands:
sudo GCFFlasher_internal -t 60 -d /dev/ttyACM0 -f deCONZ_ConBeeII_0x26720700.bin.GCF
More information can be found here:
With this system it can be checked whether in the Phoscon App under Menu > Gateway > General > Firmware a version in the format 26xx0700 is available - and not “Firmware not connected”. If yes, a device can also be tried to be connected and controlled as a test.
It is always important to use the recommended USB extension for the ConBee II, especially if other USB devices are connected. Then connect this extension to a USB 2.0 port (not blue).
So my firmware is not latest? Phoscon doesn’t show there is newer firmware, isn’t it?
I have a linux computer, please tell mi if I unplug conbee from NAS and connect to linux for updating I will lost my all devices?
Is there any changelog what was changed between 26660700 and latest 26720700?
Not in any case you see the firmware update in the Phoscon App but you can always update manually (see the link in my last post).
You can update as i wrote and bring back the stick to your installation without loosing devices because they are in the database on your normal system (NAS).
The changelog is here:
Conbee II firmware is updated =>
Philips Hue Motion is still in Not reachable status. I’ve deleted and pair again this device.
Are you still see the 0xE1 error?
At its extension the ConBee II should have distance to USB devices, SSD, metal, radio, routers or other electronics. In case of seeing the 0xE1 error, a different position of the ConBee II can bring improvements even if the current position seems optimal.
How would a firmware fix a non reachable issue?
The 0xe1 needs to be solved before seeking anywhere else.
I paried a sensor close to Conbee II (about 5cm away).
Move to the destination place and it’s seems to work.
It’s wired because I have a lot of devices which is so far from Conbee or other routers.
This sensor is in the middle of the house. But thanks for your time and help @Mimiix @ich
We investigate here, please be patient.
have similar issues with three Hue Outdoor Motion sensors I’ve purchased recently.
I’ll try to list configuration, logs etc below for troubleshooting.
I’ve managed to pair by upgrading ConBee II (26720700) and reverting Docker image used to marthoc/deconz:stable (2.12.06) and performing multiple pairing attempts. A hunch is that there is quite a lot of traffic which might cause packet drops(?) which results in a partial/failed pairing.
Pairing had no success/fail factor due to proximity to ConBee.
@Mimiix: I got several logs (enabled logging as requested in chat above) They are quite long, should I zip and direct PM? (new to the forum)
- Marthoc Docker (Docker compose)
- v2.13.1-beta (didn’t work) / 2.12.06 (worked, required multiple attempts)
- ConBee II
- USB 3.0
- Yes, Dream Link WH1080 Weather Station
- Home Assistant
- N/A (not raspberry pi)
- N/A (not raspberry pi)
- N/A (not raspberry pi)
- N/A (not raspberry pi)