Philips Hue Motion sensors disconnect from the network

[ccorderod]

Bug Report

What happened

I have 10+ philips hue motion sensors paired to my network. I move them all from a philips hue bridge (along with some light bulbs) where them have been working for a while without any problem.
Some of the motion sensors disconnect from time to time from the network now; sometimes they reconnect without doing anything, sometimes not.
This happen even with a hue motion sensor very close to the coordinator.
If they don't, I have to force remove them from the network and pair them again.
The network support more than 100 devices and those are the only devices with this behaviour.

What did you expect to happen

Once a hue motion sensor connect, it should keep connected.

How to reproduce it (minimal and precise)

Difficult to reproduce, as the disconnections are random.

Debug Info

philips hue motion sensors with latest firmware version from Philips
zigbee2mqtt version: 1.8.0 latest dev
CC253X firmware version: P-2 coordinator, latest firmware
2 CC2530+CC2591 on the network running latest routing firmware

[Koenkk]

I'm having the same problem (#2518 (comment)), currently waiting for the problem to manifest itself again, then I can start looking into it.

[WouterJN]

Same issue here with Hue Switches and Motion Sensor.

[papanirual]

Same issue here with Hue outdoor motion sensors. At the moment I am still unable to repair two of them. I removed them from the database of zigbee2mqtt and tried to repair them, but the only thing happening is that there is a line in the log that the device announced itself, without the usual pairing procedure.

Looking forward to any fix - many thanks in advance!

[Koenkk]

Update from my side, right before it stops working it seems that the devices leaves the network:

debug 2020-01-11 10:30:40: Device 'veranda_occupancy_sensor' announced itself
warn  2020-01-11 10:30:40: Device '0x001788010644f56d' left the network

Then it joins again:

info  2020-01-11 10:30:40: Device 'veranda_occupancy_sensor' joined
info  2020-01-11 10:30:40: Starting interview of 'veranda_occupancy_sensor'

But this fails:

error 2020-01-11 10:32:01: Failed to interview 'veranda_occupancy_sensor', device has not successfully been paired

Going to dive further into it.

Question to all: what coordinators and coordinator firmware do you use?

[ccorderod]

Coordinator: CC1352P_2 firmware: 20191106
Most of my hue motion sensors are able to join again, but leave randomly again.
@Koenkk : is there is any way to log with DEBUG=* npm start but only logging one sensor? My network is too big to run zb2m with Debug enabled as it create enormous log files :-(.

[Koenkk]

Thats not possible, but setting it to DEBUG=zigbee-herdsman:controller* should give the required info.

[hi1000]

CC253X firmware version: 20190608
Philips Hue (9290012607) firmware version: 6.1.0.18912 and 6.1.1.27575
Bugs: After reboot the coordinator, cannot receive Philips motion sensor's message

Log File:
2020-01-13.15-39-50/log.txt:1/13/2020, 3:41:50 PM - warn: Failed to configure r_MotionD1 (0x0017880104b78b01) ('Error: Timed out after 10000 ms') (attempt #1)
2020-01-13.15-39-50/log.txt:1/13/2020, 3:41:50 PM - warn: This can be ignored if the device is working properly

[papanirual]

CC26X2R1_20191106, Coordinator firmware version: '{"type":"zStack3x0","meta":{"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20191106}}' zigbee2mqtt version 1.8.0-dev (commit #f04e01f) Koen Kanters schrieb am 11.01.2020 um 22:41:

…

Update from my side, right before it stops working it seems that the devices leaves the network: |debug 2020-01-11 10:30:40: Device 'veranda_occupancy_sensor' announced itself warn 2020-01-11 10:30:40: Device '0x001788010644f56d' left the network | Then it joins again: |info 2020-01-11 10:30:40: Device 'veranda_occupancy_sensor' joined info 2020-01-11 10:30:40: Starting interview of 'veranda_occupancy_sensor' | But this fails: |error 2020-01-11 10:32:01: Failed to interview 'veranda_occupancy_sensor', device has not successfully been paired | Going to dive further into it. Question to all: what coordinators and coordinator firmware do you use? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#2693?email_source=notifications&email_token=ALFQYXOUTQSGBPNQMEAT5B3Q5I4J7A5CNFSM4KEFQ5EKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIWLXII#issuecomment-573356961>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALFQYXIT3BSEEL4US2Q4ULDQ5I4J7ANCNFSM4KEFQ5EA>.

[sti0]

Did you have some Osram plugs in your network? In #1474 it's described that Osram plugs prevent a re-join of some devices (maily Hue motion sensors). By myself I got two Osram plugs in the network and Hue motion and Hue dimmer are randomly disconnected. After I removed the plugs from the network it seems to be stable.

[GJT]

CC1352P-2
Coordinator firmware version: '{"type":"zStack3x0","meta":
{"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20191106}}'

same problem, no Osram devices.

[emilklindt]

I was experiencing this same problem with the Hue Dimmer Switches, as described here.

A week ago I tried changing the channel of my coordinator to use Zigbee channel 25. After searching for interfering WiFi access points near my apartment, I found that the default channel was quite populated.

So it seems to be an issue with interference, from my best guess. Can anyone verify this?

[Koenkk]

Mine dropped off again today, pushed a possible fix in the latest dev branch, fingers crossed 🤞