Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Philips Hue Motion sensors disconnect from the network #2693

Closed
ccorderod opened this issue Jan 8, 2020 · 254 comments
Closed

Philips Hue Motion sensors disconnect from the network #2693

ccorderod opened this issue Jan 8, 2020 · 254 comments
Labels
stale Stale issues

Comments

@ccorderod
Copy link

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
Copy link
Owner

Koenkk commented Jan 8, 2020

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

@Koenkk Koenkk mentioned this issue Jan 10, 2020
Closed
@WouterJN
Copy link

Same issue here with Hue Switches and Motion Sensor.

@papanirual
Copy link

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
Copy link
Owner

Koenkk commented Jan 11, 2020

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
Copy link
Author

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
Copy link
Owner

Koenkk commented Jan 12, 2020

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

@Koenkk Koenkk mentioned this issue Jan 12, 2020
Closed
@hi1000
Copy link

hi1000 commented Jan 13, 2020

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
Copy link

papanirual commented Jan 13, 2020 via email

@sti0
Copy link
Contributor

sti0 commented Jan 17, 2020

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
Copy link

GJT commented Jan 18, 2020 •
edited
Loading

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
Copy link

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 added a commit to Koenkk/zigbee-herdsman that referenced this issue Jan 18, 2020
@Koenkk
Rediscover route when defaultResponse fails. Koenkk/zigbee2mqtt#2693
920b4a2
@Koenkk
Copy link
Owner

Koenkk commented Jan 18, 2020

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

@peterforeman
Copy link

Running on latest (not -dev), saw this:

[...]
zigbee2mqtt:info  2020-01-24 18:18:40: MQTT publish: topic 'zigbee2mqtt-beneden/motion_tuin', payload '{"battery":96,"linkquality":33,"occupancy":false,"temperature":3.34,"illuminance":3242,"device":{"friendlyName":"motion_tuin","model":"9290019758","ieeeAddr":"0x001788010644892e","networkAddress":43045,"type":"EndDevice","manufacturerID":4107,"manufacturerName":"Philips","powerSource":"Battery","applicationVersion":2,"stackVersion":1,"zclVersion":1,"hardwareVersion":1,"dateCode":"20180828","softwareBuildID":"6.1.0.25261"}}'
zigbee2mqtt:info  2020-01-24 18:19:04: Device 'motion_tuin' joined
zigbee2mqtt:info  2020-01-24 18:19:04: MQTT publish: topic 'zigbee2mqtt-beneden/bridge/log', payload '{"type":"device_connected","message":{"friendly_name":"motion_tuin"}}'
zigbee2mqtt:info  2020-01-24 18:19:04: Starting interview of 'motion_tuin'
zigbee2mqtt:info  2020-01-24 18:19:04: MQTT publish: topic 'zigbee2mqtt-beneden/bridge/log', payload '{"type":"pairing","message":"interview_started","meta":{"friendly_name":"motion_tuin"}}'
zigbee2mqtt:error 2020-01-24 18:20:24: Failed to interview 'motion_tuin', device has not successfully been paired
zigbee2mqtt:info  2020-01-24 18:20:24: MQTT publish: topic 'zigbee2mqtt-beneden/bridge/log', payload '{"type":"pairing","message":"interview_failed","meta":{"friendly_name":"motion_tuin"}}'

Updated to latest-dev now and will pair again. Let's see how long it will last this time ;-)

@hi1000
Copy link

hi1000 commented Jan 29, 2020

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.

@WouterJN
Copy link

WouterJN commented Feb 1, 2020

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

When will this be released in the main branch?

@Koenkk
Copy link
Owner

Koenkk commented Feb 1, 2020

@WouterJN in Zigbee2mqtt 1.10 scheduled for Wednesday/Thursday.

@Koenkk
Copy link
Owner

Koenkk commented Feb 1, 2020

Mine hasn't dropped of since 2 weeks so things seem to have improved.

@pepp86
Copy link

pepp86 commented Feb 6, 2020 •
edited
Loading

I have reconnected my two philips hue motion sensor yesterday with latest dev and they are lost again during the evening.

Sorry - my fault. My HA System did not show the right value.

@ccorderod
Copy link
Author

@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.

@ccorderod
Copy link
Author

@Koenkk Not sure if this will help you in any way, but here you go an extract:
2020-02-21T08:20:30.487Z zigbee-herdsman:controller:log Starting with options '{"network":{"networkKeyDistribute":false,"networkKey":[x,x,x,x,x,x,x,x,x,x,x,x,x,x,x,x,],"panID":7100,"extendedPanID":[y,y,y,y,y,y,y,y,y,y],"channelList":[20]},"serialPort":{"baudRate":115200,"rtscts":true,"path":"/dev/ttyACM0"},"databasePath":"/opt/zigbee2mqtt/data/database.db","databaseBackupPath":"/opt/zigbee2mqtt/data/database.db.backup","backupPath":"/opt/zigbee2mqtt/data/coordinator_backup.json"}' 2020-02-21T08:20:31.884Z zigbee-herdsman:controller:log Disable joining 2020-02-21T08:21:57.627Z zigbee-herdsman:controller:endpoint DefaultResponse 0x0017880104b4e792/2 1030(10, {"timeout":10000,"defaultResponseTimeout":15000,"manufacturerCode":null,"disableDefaultResponse":true}) 2020-02-21T08:21:57.671Z zigbee-herdsman:controller:endpoint DefaultResponse 0x0017880104b4e792/2 1024(10, {"timeout":10000,"defaultResponseTimeout":15000,"manufacturerCode":null,"disableDefaultResponse":true}) 2020-02-21T10:29:48.443Z zigbee-herdsman:controller:endpoint DefaultResponse 0x0017880104b4e792/2 1024(10, {"timeout":10000,"defaultResponseTimeout":15000,"manufacturerCode":null,"disableDefaultResponse":true}) 2020-02-21T10:29:51.724Z zigbee-herdsman:controller:log Device '0x0017880104b4e792' joined 2020-02-21T10:29:51.725Z zigbee-herdsman:controller:log Device '0x0017880104b4e792' accepted by handler 2020-02-21T10:29:51.725Z zigbee-herdsman:controller:log Not interviewing '0x0017880104b4e792', completed 'true', in progress 'false' 2020-02-21T10:29:51.736Z zigbee-herdsman:controller:log Device announce '0x0017880104b4e792' 2020-02-21T10:29:58.155Z zigbee-herdsman:controller:endpoint DefaultResponse 0x0017880104b4e792/2 1030(10, {"timeout":10000,"defaultResponseTimeout":15000,"manufacturerCode":null,"disableDefaultResponse":true}) 2020-02-21T10:34:05.249Z zigbee-herdsman:controller:endpoint DefaultResponse 0x0017880104b4e792/2 1024(10, {"timeout":10000,"defaultResponseTimeout":15000,"manufacturerCode":null,"disableDefaultResponse":true}) 2020-02-21T10:34:08.874Z zigbee-herdsman:controller:log Device announce '0x0017880104b4e792' 2020-02-21T10:39:04.785Z zigbee-herdsman:controller:endpoint DefaultResponse 0x0017880104b4e792/2 1024(10, {"timeout":10000,"defaultResponseTimeout":15000,"manufacturerCode":null,"disableDefaultResponse":true})
Please note this is only an extract. there are hundreds of records with DefaultResponse, as well as many device announcement records. The hue motion sensor also joined and was accepted a few more times than what I have included on the post.
Let me know if you need anything else on my side.
By the way, I have moved the hue motion sensors to a hue bridge but the one showed on the log in the meantime as my setup is mostly useless without them. Thank you.

@ccorderod
Copy link
Author

@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 ...
2020-02-21T11:01:59.354Z zigbee-herdsman:controller:endpoint DefaultResponse 0x0017880104b4e792/2 1030(10, {"timeout":10000,"defaultResponseTimeout":15000,"manufacturerCode":null,"disableDefaultResponse":true}) 2020-02-21T11:01:59.443Z zigbee-herdsman:controller:endpoint DefaultResponse 0x0017880104b4e792/2 1024(10, {"timeout":10000,"defaultResponseTimeout":15000,"manufacturerCode":null,"disableDefaultResponse":true}) 2020-02-21T11:02:04.384Z zigbee-herdsman:controller:endpoint DefaultResponse 0x0017880104b4e792/2 1024(10, {"timeout":10000,"defaultResponseTimeout":15000,"manufacturerCode":null,"disableDefaultResponse":true}) 2020-02-21T11:02:07.651Z zigbee-herdsman:controller:log Device announce '0x0017880104b4e792' 2020-02-21T11:02:09.341Z zigbee-herdsman:controller:endpoint DefaultResponse 0x0017880104b4e792/2 1024(10, {"timeout":10000,"defaultResponseTimeout":15000,"manufacturerCode":null,"disableDefaultResponse":true}) 2020-02-21T11:02:14.282Z zigbee-herdsman:controller:endpoint DefaultResponse 0x0017880104b4e792/2 1024(10, {"timeout":10000,"defaultResponseTimeout":15000,"manufacturerCode":null,"disableDefaultResponse":true}) 2020-02-21T11:02:19.252Z zigbee-herdsman:controller:endpoint DefaultResponse 0x0017880104b4e792/2 1024(10, {"timeout":10000,"defaultResponseTimeout":15000,"manufacturerCode":null,"disableDefaultResponse":true}) 2020-02-21T11:02:22.505Z zigbee-herdsman:controller:log Device announce '0x0017880104b4e792' 2020-02-21T11:03:22.900Z zigbee-herdsman:controller:log Device announce '0x0017880104b4e792' 2020-02-21T11:04:22.306Z zigbee-herdsman:controller:log Device announce '0x0017880104b4e792' 2020-02-21T11:05:56.998Z zigbee-herdsman:controller:log Device announce '0x0017880104b4e792' 2020-02-21T11:05:56.999Z zigbee-herdsman:controller:log Device '0x0017880104b4e792' joined 2020-02-21T11:05:57.000Z zigbee-herdsman:controller:log Device '0x0017880104b4e792' accepted by handler 2020-02-21T11:05:57.000Z zigbee-herdsman:controller:log Not interviewing '0x0017880104b4e792', completed 'true', in progress 'false' 2020-02-21T11:07:01.082Z zigbee-herdsman:controller:log Device '0x0017880104b4e792' joined 2020-02-21T11:07:01.082Z zigbee-herdsman:controller:log Device '0x0017880104b4e792' accepted by handler 2020-02-21T11:07:01.082Z zigbee-herdsman:controller:log Not interviewing '0x0017880104b4e792', completed 'true', in progress 'false' 2020-02-21T11:07:01.089Z zigbee-herdsman:controller:log Device announce '0x0017880104b4e792' 2020-02-21T11:17:34.210Z zigbee-herdsman:controller:log Device announce '0x0017880104b4e792' 2020-02-21T11:22:00.076Z zigbee-herdsman:controller:log Device announce '0x0017880104b4e792' 2020-02-21T11:27:21.481Z zigbee-herdsman:controller:log Device '0x0017880104b4e792' joined 2020-02-21T11:27:21.481Z zigbee-herdsman:controller:log Device '0x0017880104b4e792' accepted by handler 2020-02-21T11:27:21.482Z zigbee-herdsman:controller:log Not interviewing '0x0017880104b4e792', completed 'true', in progress 'false' 2020-02-21T11:27:21.483Z zigbee-herdsman:controller:log Device '0x0017880104b4e792' joined 2020-02-21T11:27:21.483Z zigbee-herdsman:controller:log Device '0x0017880104b4e792' accepted by handler 2020-02-21T11:27:21.483Z zigbee-herdsman:controller:log Not interviewing '0x0017880104b4e792', completed 'true', in progress 'false' 2020-02-21T11:27:21.484Z zigbee-herdsman:controller:log Device announce '0x0017880104b4e792' 2020-02-21T11:35:47.820Z zigbee-herdsman:controller:log Device announce '0x0017880104b4e792' 2020-02-21T11:37:30.182Z zigbee-herdsman:controller:log Device announce '0x0017880104b4e792' 2020-02-21T11:50:35.146Z zigbee-herdsman:controller:log Device announce '0x0017880104b4e792' 2020-02-21T11:52:46.654Z zigbee-herdsman:controller:log Device '0x0017880104b4e792' joined 2020-02-21T11:52:46.655Z zigbee-herdsman:controller:log Device '0x0017880104b4e792' accepted by handler 2020-02-21T11:52:46.655Z zigbee-herdsman:controller:log Not interviewing '0x0017880104b4e792', completed 'true', in progress 'false' 2020-02-21T11:52:47.392Z zigbee-herdsman:controller:log Device announce '0x0017880104b4e792' 2020-02-21T11:53:09.056Z zigbee-herdsman:controller:log Device announce '0x0017880104b4e792' 2020-02-21T11:58:37.810Z zigbee-herdsman:controller:log Device '0x0017880104b4e792' joined 2020-02-21T11:58:37.810Z zigbee-herdsman:controller:log Device '0x0017880104b4e792' accepted by handler 2020-02-21T11:58:37.811Z zigbee-herdsman:controller:log Not interviewing '0x0017880104b4e792', completed 'true', in progress 'false' 2020-02-21T11:58:39.007Z zigbee-herdsman:controller:log Device announce '0x0017880104b4e792' 2020-02-21T12:03:54.281Z zigbee-herdsman:controller:log Device announce '0x0017880104b4e792'

@GJT
Copy link

GJT commented Feb 21, 2020

same for me after upgrade, when i try to reconfigure I get this:

zigbee2mqtt:error 2020-02-21 19:12:32: Failed to configure 'zb_sensor_kueche', attempt 1 (Error: Bind 0x001788010213f153/2 genPowerCfg from '0x00124b001ca61201/1' failed (Error: AREQ - ZDO - bindRsp after 10000ms)
at Endpoint. (/zigbee2mqtt-1.10.0/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:235:23)
at Generator.throw ()
at rejected (/zigbee2mqtt-1.10.0/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:6:65))

@Koenkk
Copy link
Owner

Koenkk commented Feb 23, 2020

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?

@ccorderod
Copy link
Author

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 :-(.

@Koenkk
Copy link
Owner

Koenkk commented Feb 24, 2020

@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

@Koenkk
Copy link
Owner

Koenkk commented Feb 26, 2020

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

@ccorderod
Copy link
Author

Thank you @Koenkk. I use a cc1352-P2 coordinator. Let's see TI answer to your ticket. Thank you for the update.

@jstott1070
Copy link

jstott1070 commented Dec 7, 2022 via email

@dakota-tech
Copy link

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.

@mrdago
Copy link

mrdago commented Dec 14, 2022

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.
It would be interesting if someone else has the same experience in his setup.

@MattWestb
Copy link

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 !!!

@Dokw0N
Copy link

Dokw0N commented Dec 17, 2022 •
edited
Loading

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).
Interesting to me because my previous assumption was that the issue is caused by the device, as these sensors are the only part of all my automations that are causing problems and we are discussing them here. However, z2m (or mosquitto) seem to play a role in it as well since one force remove led to instant recognition and pairing.

@denveronly
Copy link

denveronly commented Dec 17, 2022 •
edited
Loading

My zigbee coordinator history is big
I used cc2531 stick, then used modkam sls coordinator, used zigstar coordinator, tried local development of 2652p chip on board miniPi. They all had phillips hue disconnections after 1-3 days
Now my current setup is sonoff zigbee dongle E version which i really love it is stable and has exellent LQI on all devices previous coords didnt provide
Also i tried different batteries inside my Hue with higher voltage
And the thing is i paired two Phillips hue outdoor motion sensors and they work a month without any problem
So i guess maybe it is all about LQI?
Anyone have Hue disconnections with Sonoff dongle “E”?

@Dokw0N
Copy link

Dokw0N commented Dec 17, 2022

@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.

@denveronly
Copy link

@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
Had multiple provlems on other coordinators i described i tested

@Dokw0N
Copy link

Dokw0N commented Dec 17, 2022

According to lsusb: Bus 001 Device 003: ID 10c4:ea60 Silicon Labs CP210x UART Bridge @denveronly

@denveronly
Copy link

denveronly commented Dec 17, 2022 •
edited
Loading

According to lsusb: Bus 001 Device 003: ID 10c4:ea60 Silicon Labs CP210x UART Bridge @denveronly

Mine also has silicon labs chip (E version)
And have disconnect issues dissapear

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

@dakota-tech
Copy link

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?

@NicSee22
Copy link

NicSee22 commented Jan 8, 2023

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.
Tried moving my Sonoff dongle closer to the device and so far it's stayed connected for about 6 weeks. I'm hoping that's resolved it, but time will tell.

@miklosbagi
Copy link

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.
I have 11 of these devices, and 3 outdoors, none of them dropped off ever since.
Not sure what makes the difference, this is a ZHA + ZZH! Stick on HassOS setup.

@ricardopaiva
Copy link

My Philips Hue Motion Sensor has been working fine for a couple of weeks.
All I’ve done was to move the coordinator to a different place so that the connection to the sensor is better.
That seems to have solved the issue for now.

@MattWestb MattWestb mentioned this issue Jan 23, 2023
Closed
@github-actions
Copy link
Contributor

github-actions bot commented Feb 8, 2023

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

@github-actions github-actions bot added the stale Stale issues label Feb 8, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Feb 16, 2023
@lougreenwood lougreenwood mentioned this issue Mar 12, 2023
Open
@jeeftor
Copy link

jeeftor commented Apr 23, 2023

image

image

I just noticed these both had dropped... after being connected for only a short time... so I guess event hough this issue is stale - I'll see about updating my zigbee stick...

I really want to move away from the Hue Bridge - but it seems to at least keep the motion sensors connected...

@jeeftor
Copy link

jeeftor commented Apr 23, 2023

Also it appears my firmware is a few versions out of date -> so maybe I need to update it (most likely)

@jeeftor
Copy link

jeeftor commented May 25, 2023

Well just had another sensor drop 16 hrs ago
Is there a way to keep joining mode always on for specific sensors?

@miklosbagi
Copy link

miklosbagi commented May 25, 2023 •
edited
Loading

Is there a way to keep joining mode always on for specific sensors?

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 :)

@jeeftor
Copy link

jeeftor commented May 30, 2023

MQTT discovery should add the devices for you again and again...

@Cjkeenan
Copy link

Cjkeenan commented Sep 2, 2023

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?

@denveronly
Copy link

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

@jeeftor
Copy link

jeeftor commented Sep 8, 2023

My fix which is not ideal is to just allow anything to join the network so when things drop - they can easily re-join

@DJTerentjev
Copy link
Contributor

only if you are using E verison of sonoff ezsp

Could you please confirm this sensor working stable with E verison of sonoff ezsp?

@slugzero slugzero mentioned this issue Dec 16, 2023
Merged
@digitalresistor
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
stale Stale issues
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests