-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Philips Hue Motion sensors disconnect from the network #2693
Comments
I'm having the same problem (#2518 (comment)), currently waiting for the problem to manifest itself again, then I can start looking into it. |
Same issue here with Hue Switches and Motion Sensor. |
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! |
Update from my side, right before it stops working it seems that the devices leaves the network:
Then it joins again:
But this fails:
Going to dive further into it. Question to all: what coordinators and coordinator firmware do you use? |
Coordinator: CC1352P_2 firmware: 20191106 |
Thats not possible, but setting it to |
CC253X firmware version: 20190608 Log File: |
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>.
|
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. |
CC1352P-2 same problem, no Osram devices. |
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? |
Mine dropped off again today, pushed a possible fix in the latest dev branch, fingers crossed 🤞 |
Running on latest (not -dev), saw this:
Updated to latest-dev now and will pair again. Let's see how long it will last this time ;-) |
I setup three zigbee coordinators in the same big room. They are use the different channels and different keys but the same pan_id and ext_pan_id. |
When will this be released in the main branch? |
@WouterJN in Zigbee2mqtt 1.10 scheduled for Wednesday/Thursday. |
Mine hasn't dropped of since 2 weeks so things seem to have improved. |
Sorry - my fault. My HA System did not show the right value. |
@Koenkk Hue motion sensors started to drop off the network again yesterday after upgrading to 1.10.0-dev yesterday. Unfortunatly I can't tell wich version I was running previously (it was dev, but I do not know the build #). Will restart z2m with DEBUG=zigbee-herdsman:controller* trying to catch a drop. |
@Koenkk Not sure if this will help you in any way, but here you go an extract: |
@Koenkk Apologies for so much post, but I just got a drop :-). Hue motion sensor keeps announcing itself, join, is accepted, not interviewed, join again ... |
same for me after upgrade, when i try to reconfigure I get this:
|
I've tweaked the route discovery a bit therefore it could be a one-time thing (and afterwards it should improve). Could you try repairing it once for now and monitor if it drops off again? |
Hi @Koenkk I upgraded to latest dev a few minutes ago. The motion sensor has been working just a few minutes and dropped again. The funny thing is come to live again from time to time, and drop again :-(. |
@ccorderod can you update to the latest dev branch and sniff the traffic when this happens? https://www.zigbee2mqtt.io/how_tos/how_to_sniff_zigbee_traffic.html |
For CC26xR1 and CC1352-P2 users, I believe this is an issue with the firmware itself, I've asked TI for support: https://e2e.ti.com/support/wireless-connectivity/zigbee-and-thread/f/158/t/883629 |
Thank you @Koenkk. I use a cc1352-P2 coordinator. Let's see TI answer to your ticket. Thank you for the update. |
So I have a question. I have noticed some say that the sensor disappeared but later rejoined. So I setup a second Zigbee2MQTT installation and I had 2 sensors fall of my primary installation and they showed up the next morning attached to the second network even though that installation did not have permit to join set to true. I did manually set it prior to test join a device but disabled when I was done. So I'm starting to wonder if I should not rename the device (leave as 0x...) after it's joined so that when/if it does rejoin the device ID is still there an things may continue to work. This would not be ideal but I'm question if this may be a solution for the Hue sensors. |
I'm fighting with the device re-connections of the Philips motion sensor several month now. At the end I supposed that the issue is related to my network setup. It seemed to me, that the sensor tried to optimize the route to the coordinator by a regular switch to the "best" repeater connection. As I run two repeater with a comparable distance to the Philips device I moved one repeater much more close to the motion sensor. Since that time I can't anymore observe device re-connections. Everything is operating well as expected. |
I have 2 SML001 in my living room and both is real jumpers and if they is finding one worse router as parent as they is having they is jumping to it also then they is having 10 better around. The good thing is as long they is having one router jumping to then is not leaving the network. I have not putting them in the back box for bad Zigbee devices (all other Philips HUE and no Zigbee 3 devices is there) but then i finding some good light sensors that is not so expensive then they is going in there 2 !!! |
Promised update in case something breaks: yesterday one of my movement/light automations stopped working so I wired a debug node to the motion sensor in node red to find that it stopped sending any payload. Double checking with the zigbee2mqtt frontend yielded that same result. I reconnected the device and everything is working as expected again. One interesting find was that I had to force remove the broken connection from z2m and then reset/reconnect the device in order to get it working again (friendly name had to be reassigned). |
My zigbee coordinator history is big |
@denveronly Im using the SONOFF Zigbee 3.0 USB Dongle Plus with the most recent firmware and it has been very reliable for 6 out of my 7 motion sensors for a month now (except for the small hickup yesterday, which was fixed within minutes). Just my experience, maybe it can help you. |
Are you using the Plus E version (newer chip) or older ordinary version i have not a single problem on E version Sonoff |
According to lsusb: |
Mine also has silicon labs chip (E version) I guess it is all about LQI or different i/o mode with silicon labs chip. Almost 90% other coordinators use Texas instruments chips. Native Phillips use cortex chip. So maybe thats thr hardware problem we were facing |
I decided to split my network to see if the number of devices has anything to do with it. Added another CC2650P to my network. Added a couple routers and some Phillips sensors and within a week things were still falling off both. So I swapped out the second CC2650P for a Conbee II that I had good luck with before. Added the handful of devices to it and both CC2650P and Conbee II networks that have Phillips sensors on them have both been solid. Makes no sense as some are running on both adapters. But it's been working so no complaints expect for the question of why? |
I only have one Philips Hue device - an outdoor PIR. Had trouble with it losing connectivity evey week or two. Tried all sorts of things such as updating firmware and switching from ZHA to Zigbee2MQTT, but nothing helped. |
Folks, I've had this issue originally with ZHA back some time ago, and all I did was: remove the device from the network, disconnect the battery, leave it be for 15 mins. Re-reg. |
My Philips Hue Motion Sensor has been working fine for a couple of weeks. |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days |
Also it appears my firmware is a few versions out of date -> so maybe I need to update it (most likely) |
Well just had another sensor drop 16 hrs ago |
That would be passlist - but how this works in HA without having to add devices one by one via the UI, I have no idea :) |
MQTT discovery should add the devices for you again and again... |
This just happened to one of my sensors again. This time it stayed connected for a couple of months, but it seems random when it disconnects. Has anyone found any sort of fix? |
It downt have fixes right now only if you are using E verison of sonoff ezsp |
My fix which is not ideal is to just allow anything to join the network so when things drop - they can easily re-join |
Could you please confirm this sensor working stable with E verison of sonoff ezsp? |
I am using the Sonoff E version of the stick in multi mode (so it also does thread) and my Hue motion sensors keep dropping off the network, sometimes they come back (as long as I leave "join" enabled), other times they don't. |
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
The text was updated successfully, but these errors were encountered: