Koenkk / zigbee2mqtt

Zigbee 🐝 to MQTT bridge 🌉, get rid of your proprietary Zigbee bridges 🔨
https://www.zigbee2mqtt.io
GNU General Public License v3.0
11.8k stars 1.64k forks source link

Phillips Hue Dimmer stops working periodically (requires re-pairing) #531

Closed HarrisonPace closed 5 years ago

HarrisonPace commented 5 years ago

Hey Folks,

I have setup the Hue Dimmer and it works really well for a period of a week or so and then drops connection and no longer works, its a brand new device (not a battery issue) and the input is been recorded by zigbee-shepherd. If I re-pair the device it starts to work again, however its become a very frustrating experience. All my Xioami Kit works wonderfully.

I have no idea how to debug this, given its a periodic issue which results in disconnection.

I have included the debug logs from Zigbee2MQTT: https://paste.debian.net/plain/1048814

After restarting Zigbee2MQTT I get:

Oct 25 00:24:12 Zigbee-Bridge npm[11951]: zigbee2mqtt:info 10/25/2018, 12:24:12 AM MQTT publish, topic: 'zigbee2mqtt/Living Room Light Remote', payload: '{"battery":100,"linkquality":5}'

Oct 25 00:24:28 Zigbee-Bridge npm[11951]: zigbee2mqtt:info 10/25/2018, 12:24:28 AM Device incoming...

Oct 25 00:24:28 Zigbee-Bridge npm[11951]: zigbee2mqtt:info 10/25/2018, 12:24:28 AM MQTT publish, topic: 'zigbee2mqtt/bridge/log', payload: '{"type":"pairing","message":"device incoming"}'

Oct 25 00:25:02 Zigbee-Bridge npm[11951]: zigbee2mqtt:error 10/25/2018, 12:25:02 AM Failed to configure Living Room Light Remote 0x0017880103e44c37

Koenkk commented 5 years ago

This could probably be a range issue. When keeping the dimmer close to the CC2531, does it also stop working after a few days?

tb-killa commented 5 years ago

I see this strange behaviour often on my two devices buts its randome timed. it seems to be that the device lost his state about the bindings and do them again and again. actually i check if we have to define the right structure of binding and reporting,

HarrisonPace commented 5 years ago

This could probably be a range issue. When keeping the dimmer close to the CC2531, does it also stop working after a few days?

Possibly, I have bought a router (Xiaomi Power Control) and placed it in between the CC2531 and the Phillips Hue DImmer. I have repaired it and I am now testing the Dimmer. I will report back on findings.

HarrisonPace commented 5 years ago

Well definitely not a range issue. Since using the router, (with link quality consistently above 50), I have experienced another two dropouts.

If anything the introduction of the router has increased the issue, but more likely I have just noticed it, since monitoring it more carefully.

To reconnect I have to enter pairing mode and restart zigbee2mqtt.

Koenkk commented 5 years ago

When leaving pairing mode on, do you also experience this?

HarrisonPace commented 5 years ago

Yes, this occurs even if

permit_join: true

is set.

Koenkk commented 5 years ago

This issue is quite hard to debug, honestly I don't know what to do now..

HarrisonPace commented 5 years ago

Yeah, at this stage, I'm thinking I will sell the Hue Dimmer, as I can't get it to work reliability, it tends to stop working on a 2-3 day basis. A couple of notes:

It's frustrating but I'm really not sure how to proceed from here.

nxdefiant commented 5 years ago

Had the same issue on the first day of zigbee2mqtt usage. Above steps worked to reestablish a connection.

RIMperator commented 5 years ago

I seem to have a similar or maybe even exact the same issue with a Philips Hue Dimmer. My Dimmer basically only works for a few minutes and then stops until it is repaired. What can I do to help isolate the issue?

HarrisonPace commented 5 years ago

What can I do to help isolate the issue?

Submit your debug output of zigbee-shepherd, (I'm expecting its still receiving commands its just not processing them for some reason), I couldn't isolate why.

chris-jennings commented 5 years ago

Submit your debug output of zigbee-shepherd, (I'm expecting its still receiving commands its just not processing them for some reason), I couldn't isolate why.

I just got the same dimmer. Model 324131137411 and it works for a variable amount of time then fails to show up in any Zigbee messages detected by my CC2531. I switched on debug messages and I fail to see any Zigbee packets being detected from the dimmer.

When I restart the zigbee2mqtt service and then repair (all 4 buttons until the green led comes on) then it will work again. I will then see these messages:

Feb 19 19:40:25 Plex npm[10073]: zigbee2mqtt:info 2019-2-19 19:40:25 MQTT publish: topic 'homeassistant/0x0017880104afcb62', payload '{"battery":100,"linkquality":65,"action":"down-press","brightness":205}'

A difficult one to troubleshoot. Perhaps I will need to sniff packets instead when the dimmer is not responding. Do these dimmers have some kind of code rotation or expected sync message? I note that the dimmer tracks the expected brightness internally, I'm not currently using this but I imagine a Hue bridge would sync this to the saved value after a re-pair or reset command.

HarrisonPace commented 5 years ago

I thought I would update this post with the log output from the newest version of zigbee2mqtt:

  zigbee2mqtt:info 3/7/2019, 5:46:23 PM MQTT publish: topic 'zigbee2mqtt/Living Room Switch', payload '{"battery":100,"voltage":3055,"linkquality":86,"click":"single"}'
  zigbee2mqtt:info 3/7/2019, 5:46:24 PM MQTT publish: topic 'zigbee2mqtt/Living Room Switch', payload '{"battery":100,"voltage":3055,"linkquality":81,"click":"single"}'
  zigbee2mqtt:warn 3/7/2019, 5:46:35 PM No converter available for '324131092621' with cid 'genOnOff', type 'cmdOffWithEffect' and data '{"cid":"genOnOff","data":{"effectid":0,"effectvariant":0}}'
  zigbee2mqtt:warn 3/7/2019, 5:46:35 PM Please see: https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html.
  zigbee2mqtt:warn 3/7/2019, 5:46:36 PM No converter available for '324131092621' with cid 'genOnOff', type 'cmdOn' and data '{"cid":"genOnOff","data":{}}'
  zigbee2mqtt:warn 3/7/2019, 5:46:36 PM Please see: https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html.
  zigbee2mqtt:warn 3/7/2019, 5:46:36 PM No converter available for '324131092621' with cid 'genOnOff', type 'cmdOn' and data '{"cid":"genOnOff","data":{}}'
  zigbee2mqtt:warn 3/7/2019, 5:46:36 PM Please see: https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html.
  zigbee2mqtt:warn 3/7/2019, 5:46:37 PM No converter available for '324131092621' with cid 'genOnOff', type 'cmdOffWithEffect' and data '{"cid":"genOnOff","data":{"effectid":0,"effectvariant":0}}'
  zigbee2mqtt:warn 3/7/2019, 5:46:37 PM Please see: https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html.
  zigbee2mqtt:warn 3/7/2019, 5:46:37 PM No converter available for '324131092621' with cid 'genOnOff', type 'cmdOffWithEffect' and data '{"cid":"genOnOff","data":{"effectid":0,"effectvariant":0}}'
  zigbee2mqtt:warn 3/7/2019, 5:46:37 PM Please see: https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html.
  zigbee2mqtt:error 3/7/2019, 5:46:40 PM Failed to ping 0x00158d00024f2328
  zigbee2mqtt:warn 3/7/2019, 5:46:41 PM Failed to configure Living Room Light Remote (0x0017880103e44c37) ('Error: Profile: 49246 is not supported.') (attempt #2)
  zigbee2mqtt:warn 3/7/2019, 5:46:41 PM This can be ignored if the device is working properly
  zigbee2mqtt:warn 3/7/2019, 5:46:49 PM No converter available for '324131092621' with cid 'genOnOff', type 'cmdOn' and data '{"cid":"genOnOff","data":{}}'
  zigbee2mqtt:warn 3/7/2019, 5:46:49 PM Please see: https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html.
  zigbee2mqtt:warn 3/7/2019, 5:46:51 PM Failed to configure Living Room Light Remote (0x0017880103e44c37) ('Error: Profile: 49246 is not supported.') (attempt #3)
  zigbee2mqtt:warn 3/7/2019, 5:46:51 PM This can be ignored if the device is working properly
  zigbee2mqtt:warn 3/7/2019, 5:47:00 PM No converter available for '324131092621' with cid 'genOnOff', type 'cmdOn' and data '{"cid":"genOnOff","data":{}}'
  zigbee2mqtt:warn 3/7/2019, 5:47:00 PM Please see: https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html.
  zigbee2mqtt:warn 3/7/2019, 5:47:04 PM No converter available for '324131092621' with cid 'genOnOff', type 'cmdOn' and data '{"cid":"genOnOff","data":{}}'
  zigbee2mqtt:warn 3/7/2019, 5:47:04 PM Please see: https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html.
  zigbee2mqtt:warn 3/7/2019, 5:47:05 PM No converter available for '324131092621' with cid 'genLevelCtrl', type 'cmdStep' and data '{"cid":"genLevelCtrl","data":{"stepmode":0,"stepsize":30,"transtime":9}}'
  zigbee2mqtt:warn 3/7/2019, 5:47:05 PM Please see: https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html.
  zigbee2mqtt:warn 3/7/2019, 5:47:05 PM No converter available for '324131092621' with cid 'genLevelCtrl', type 'cmdStep' and data '{"cid":"genLevelCtrl","data":{"stepmode":1,"stepsize":30,"transtime":9}}'
  zigbee2mqtt:warn 3/7/2019, 5:47:05 PM Please see: https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html.
  zigbee2mqtt:warn 3/7/2019, 5:47:06 PM No converter available for '324131092621' with cid 'genOnOff', type 'cmdOffWithEffect' and data '{"cid":"genOnOff","data":{"effectid":0,"effectvariant":0}}'
  zigbee2mqtt:warn 3/7/2019, 5:47:06 PM Please see: https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html.
  zigbee2mqtt:warn 3/7/2019, 5:47:11 PM No converter available for '324131092621' with cid 'genOnOff', type 'cmdOffWithEffect' and data '{"cid":"genOnOff","data":{"effectid":0,"effectvariant":0}}'
  zigbee2mqtt:warn 3/7/2019, 5:47:11 PM Please see: https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html.
  zigbee2mqtt:warn 3/7/2019, 5:47:13 PM No converter available for '324131092621' with cid 'genOnOff', type 'cmdOn' and data '{"cid":"genOnOff","data":{}}'
  zigbee2mqtt:warn 3/7/2019, 5:47:13 PM Please see: https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html.
  zigbee2mqtt:warn 3/7/2019, 5:47:14 PM No converter available for '324131092621' with cid 'genOnOff', type 'cmdOn' and data '{"cid":"genOnOff","data":{}}'
  zigbee2mqtt:warn 3/7/2019, 5:47:14 PM Please see: https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html.
  zigbee2mqtt:warn 3/7/2019, 5:47:14 PM No converter available for '324131092621' with cid 'genOnOff', type 'cmdOn' and data '{"cid":"genOnOff","data":{}}'
  zigbee2mqtt:warn 3/7/2019, 5:47:14 PM Please see: https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html.
  zigbee2mqtt:warn 3/7/2019, 5:47:15 PM No converter available for '324131092621' with cid 'genLevelCtrl', type 'cmdStep' and data '{"cid":"genLevelCtrl","data":{"stepmode":0,"stepsize":30,"transtime":9}}'
  zigbee2mqtt:warn 3/7/2019, 5:47:15 PM Please see: https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html.
  zigbee2mqtt:warn 3/7/2019, 5:47:15 PM No converter available for '324131092621' with cid 'genLevelCtrl', type 'cmdStep' and data '{"cid":"genLevelCtrl","data":{"stepmode":1,"stepsize":30,"transtime":9}}'
  zigbee2mqtt:warn 3/7/2019, 5:47:15 PM Please see: https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html.

I too wonder if there is a code rotation mechanism involved?

chris-jennings commented 5 years ago

I too wonder if there is a code rotation mechanism involved?

I would say that fault is not "stops periodically" but instead I think it is related to when the dimmer switch shows to red LED, or when I accidentally trigger a pairing of a nearby Hue light. I don't have any hard evidence except I am now more careful with when I press the Dimmer Switch buttons and not mash buttons when it doesn't respond initially. Now I haven't had to reset the Dimmer Switch for 5 days.

I will try and create the fault and see what are the required conditions.

HarrisonPace commented 5 years ago

Now I haven't had to reset the Dimmer Switch for 5 days.

I will try and create the fault and see what are the required conditions.

I hadn't needed to reset (repair) the dimmer for 2 weeks and then it will stop working all of sudden (exactly how you described), and I am careful not to press all buttons to initialize a re-pair. I think you may find the issue appear again in the near future unfortunately.

HarrisonPace commented 5 years ago

I think the issue has been resolved, I have not experienced any disconnects for more than 2 weeks and the latest release has completely reworked the Phillips Hue Remote Controls, so for now I'm going to close this issue. If I experience any problems in the future I may re-open the issue.

HarrisonPace commented 5 years ago

The behavior is sadly still occurring, I need to (infrequently) re-pair my remote and restart zigbee2mqtt service to fix the pairing issue. 🤔

Bastiencc commented 5 years ago

Hi guys I'm experencing the same issue @thehaxxa . Only solution to get my remote working again is to remove them, and re-pair. Sometime it's ok for days, sometime it's for hours or minutes :(

@Koenkk you have some ideas about this issues ?

Tell me if I can help for debug

Bastiencc commented 5 years ago

If it can help , I get that in log, you can see the "action":"on-null" instead of "action":"on-press":

Apr 05 10:28:48 raspberrypi npm[515]:   zigbee2mqtt:error 4/5/2019, 10:28:48 AM Cannot get the Node Descriptor of the Device: 0x0017880104af512e (Error: Timed out after 10000 ms)
Apr 05 10:28:57 raspberrypi npm[515]:   zigbee2mqtt:info 4/5/2019, 10:28:57 AM MQTT publish: topic 'zigbee2mqtt/salon_switch_canape', payload '{"battery":86,"linkquality":39,"duration":0,"counter":1,"brightness":255,"action":"on-null"}'
Koenkk commented 5 years ago

I'm not sure what's cause of this, @ugrug could you take a look at https://github.com/Koenkk/zigbee2mqtt/issues/531#issuecomment-480211038 ?

ugrug commented 5 years ago

I'll check it!

Bastiencc commented 5 years ago

Hi @Koenkk , @ugrug and @thehaxxa

I've updated to 1.3.0 and after remove/re-pair all my remote, it seems to work well : I have not experienced any disconnects since 2days.... Wait and see !

Thanks

HarrisonPace commented 5 years ago

I've updated to 1.3.0 and after remove/re-pair all my remote, it seems to work well : I have not experienced any disconnects since 2days.... Wait and see !

I waited almost 3 weeks before it disconnected again, I think there is some change that occurs during use. Hard to diagnose...

Bastiencc commented 5 years ago

In my case, it's the very first time I have no disconnect for severals days.

Edit : I get my first disconnect today, on two device... The issue is still here :( I press the 4 buttons and it works again

Bastiencc commented 5 years ago

This morining I get some disconnects. When I try to re-paire, I get :

Apr 16 11:00:17 raspberrypi npm[2520]:   zigbee2mqtt:error 4/16/2019, 11:00:17 AM Cannot get the Node Descriptor of the Device: 0x001788010408cd64 (Error: Timed out after 10000 ms)
Apr 16 11:00:37 raspberrypi npm[2520]:   zigbee2mqtt:error 4/16/2019, 11:00:37 AM Cannot get the Node Descriptor of the Device: 0x001788010408cd64 (Error: Timed out after 10000 ms)

or :

Apr 16 11:03:35 raspberrypi npm[2615]:   zigbee2mqtt:info 4/16/2019, 11:03:35 AM New device 'undefined' with address 0x001788010408cd64 connected!
Apr 16 11:03:35 raspberrypi npm[2615]:   zigbee2mqtt:info 4/16/2019, 11:03:35 AM MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"device_connected","message":"0x001788010408cd64","meta":{}}'
Apr 16 11:03:35 raspberrypi npm[2615]:   zigbee2mqtt:warn 4/16/2019, 11:03:35 AM Device with modelID 'undefined' is not supported.
Apr 16 11:03:35 raspberrypi npm[2615]:   zigbee2mqtt:warn 4/16/2019, 11:03:35 AM Please see: https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html

Maybe there is some update available for this dimmer ? I have no hue bridge, so I never updated them.

edit : when I try to remove battery, wait some sec, and put the battery back, the pairing process seems to be working better.

MattTheBrofessor commented 5 years ago

I have the same issue. I connected it a and only programmed the ON and OFF button. This worked fine for like a week but I hardly used it. Then I used Node-Red to program the dimmer, when this worked fine with a light that used the Hue Bridge. Then I used Zigbee2Mqtt to connect a bulb (tried INNR and Aqara) and then it started failing. Don't know if the two are connected.

My Hue Motion Sensor is also not working. It works just one time and then it disconnects. Both devices were updated to the last software version, so that should not be the problem.

Bastiencc commented 5 years ago

An other idea: I change my wifi channel to 11 (and zigbee still to channel 11), and now it seems to be good since 15 days...

stale[bot] commented 5 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

marothe commented 5 years ago

Having the same issue - the hue dimmer switch randomly loses connection and you have to re-pair them to Z2M. Did anybody of you guys find a solution for this?

nxdefiant commented 5 years ago

Only had this problem once so far...

Bastiencc commented 5 years ago

Same issue here... :(

Le mar. 17 sept. 2019 à 18:32, nxdefiant notifications@github.com a écrit :

Only had this problem once so far...

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/Koenkk/zigbee2mqtt/issues/531?email_source=notifications&email_token=AI2ORRF4473TNH2ZP4WFN6LQKEBCPA5CNFSM4F67TK62YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD65DZFQ#issuecomment-532298902, or mute the thread https://github.com/notifications/unsubscribe-auth/AI2ORRESWI4RDF6VBBPGF4LQKEBCPANCNFSM4F67TK6Q .

rm2kdev commented 4 years ago

Im having the same issue, i've made an extensive thread about my issue here (exact same as you guys 1.6.0)

https://github.com/Koenkk/zigbee-shepherd-converters/issues/637

I've ordered another ccusb to sniff

ahue commented 4 years ago

Same issue here. Re-pairing possible. Sometimes modelID is detected, sometimes 'undefined'. However pressing the switch does not cause it to light up green and no message is received by zigbee2mqtt. Got another one working again after endless trials but now two others fell out and I cant reproduce re-pairing strategy. Something with stopping zigbee2mqtt, resetting the switch and removing the battery I recall helped last time, but cannot reproduce now.

JohannCR commented 3 years ago

Same issue. Any progress ?

hacker-h commented 2 years ago

I can confirm the issue for latest 3.0.X firmware on CC2531

rrubin0 commented 2 years ago

Im experiencing this too. Repairing is fast but not easy to teach the wife to do. All hue lights and xiaomi devices work flawlessly. Im running latest-dev version.

jjimenezlopez commented 1 year ago

Same issue here, I have 4 dimmers and all of them have the same problem, they stop working after a few days. Can it be related with pairing other devices? I'm in the process of building my zigbee network and I pair new devices from time to time.

hacker-h commented 1 year ago

@jjimenezlopez Experiencing the issue after weeks of unchanged network with only ~10 devices on a sonoff 3.0 dongle, so this seems to be unrelated

hacker-h commented 1 year ago

The most interesting observation I made so far is that with two remotes at different locations/networks: One loses pairing randomly after a few weeks or even days or hours. The other one never loses it at all. Since both networks run with the same hardware, software, similar coordinator distance and similar devices in the network I suppose this could also be a hardware issue (some have it, some do not).

jjimenezlopez commented 1 year ago

@hacker-h thanks for the reply. I have a sonoff 3.0 dongle also.

Do you have the Hue bridge running? I wonder if that can affect some way.

hacker-h commented 1 year ago

I have no hue bridge, but I just rechecked the config and there is a major difference between the faulty and the working remote: the faulty runs on firmware version 6.1.1.28573, build date 20190410 the good one runs on firmware version 5.45.1.17846, build date 20160302 Can somebody else confirm this?

jjimenezlopez commented 1 year ago

I can confirm that my dimmer runs 6.1.1.28573 too! Not sure I can downgrade to try though…

rrubin0 commented 1 year ago

I’ve had this happen too but I just hold down all 4 buttons for a few seconds and it reboots , reconnects, and works fine again and the problem is intermittent and infrequent enough to get by. Sonoff 3 radio as well.

On Tue, Oct 18, 2022 at 1:51 PM Jose Jiménez @.***> wrote:

Same issue here, I have 4 dimmers and all of them have the same problem, they stop working after a few days. Can it be related with pairing other devices? I'm in the process of building my zigbee network and I pair new devices from time to time.

— Reply to this email directly, view it on GitHub https://github.com/Koenkk/zigbee2mqtt/issues/531#issuecomment-1282989399, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFCPURCUQBI3CTDKXOATGX3WD4ETDANCNFSM4F67TK6Q . You are receiving this because you commented.Message ID: @.***>

gerrytb commented 1 year ago

I am experimentign the same issue. The firmwares version of the dimmer is 6.1.1.28573 too. Z2M Version is 1.28.4

Has somebody find a solution?

culdaraul commented 1 year ago

I have similar issues. I have two "older" HUE DimSwitch and one "newer" model, the latter has no issues at all. The other two are giving me headaches - completely unreliable even if I'm 2m away from the Sonoff zigbee stick. I have couple of other zigbee devices (32 in total: hue lamps, sonoff relays, ikea switches and lamps) which are working flawlessly but I'm starting to hate Philips. These 2 older dimswitches are using the latest fw.

fdski commented 1 year ago

same problem here. My dimmer is pretty old, replaced the battery, it registers on the network, then nothing works. 4 button reset causes it to announce itself and that's all. Debug 2023-02-01 23:13:15Device '0x00178801020e72c0' announced itself Info 2023-02-01 23:13:15MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0x00178801020e72c0","ieee_address":"0x00178801020e72c0"},"type":"device_announce"}' Debug 2023-02-01 23:13:17Retrieving state of '0x00178801020e72c0' after reconnect and that's all, nothing works till next reset, then it announces itself and nothing again.

I tried the "reset factory" method from https://www.zigbee2mqtt.io/devices/324131092621.html