When I was creating this topic I felt as dump. But I see there is much more people with similar issue. My workaround was to pair very close to the conbee. But since this time I still see a problem with 2 devices which are very close to the conbee.
I am facing the exact same issue. My sensor worked perfectly for the last two years, but after upgrading to deCONZ v2.13.01 it became unreachable. I also tried pairing a brand new one, with the same result.
I have also problem using a new Philips Hue OUTDOOR motion sensor; pairing works but after that the status is always staying at “unreachable”, not reporting any motion.
The sensor itself works with a Hue bridge, firmware of the sensor is up to date. Shall I open a new issue for that or could this be related to the previous posts in here (since one of them also describes outdoor sensors)?
Edit: Sensor Firmware is 1.0.25261 (no firmware update available for that as per now)
@Mimiix yesterday I successfully migrated from the deprecated marthoc deconz docker image to the new one ( https://github.com/deconz-community/deconz-docker ) and was able to connect my Hue motion sensors again.
Many thanks for your support!
unfortunately not, the outdoor motion sensor still does not work for me. I can pair it, but it remains “unreachable”. Does the outdoor sensor work for anyone?
I assume yes, I updated to deconz latest beta and I am seeing ‘2.13.02 / 20/07/2021’ in the web interface… the sensor does show links to other devices in deconz, but status is still “not reachable”.