search

Koenkk / zigbee2mqtt

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

Ikea Tradfri LED1903C5/LED1835C6 won't pair (nothing in logs) #4949

Closed nielsrune closed 3 years ago

nielsrune commented 3 years ago

What happened

I'm switching from tradfri gateway to zigbee2mqtt. All other bulb has been paired but my single Tradfri LED1835C6. Nothing at all is shown in the log of zigbee2mqtt. I have followed the suggestions at https://www.zigbee2mqtt.io/information/FAQ.html#no-logging-is-shown-at-all The bulbs firmware was up to date on the Tradfri Gateway.

What did you expect to happen

Expected the bulb to start pairing.

How to reproduce it (minimal and precise)

Try to pair new (< 1 month old) Ikea Tradfri LED1535C6.

Debug info

Zigbee2MQTT version: 1.16.1 Adapter hardware: CC26X2R1 (Electrolama zig-a-zig-ah, newly bought, latest firmware CC26X2R1_20201026.hex) Adapter firmware version: CC26X2R1_20201026.hex

System is a new Raspberry Pi 4 model B running Rasberry Pi OS. Home Assistant Supervised 0.117.5

Tried Touchlink scan. At first run nothing is found. Further runs fails with Error: Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)

io53 commented 3 years ago

The trådfri e14 is very picky with the timings when resetting. Try to wait 1 full second (or a bit more) in the off state, and keep the on state very short when doing the reset procedure.

nielsrune commented 3 years ago

Good news and bad news:

I tried one more according to io53s suggestion waiting a little more in the off state. As before, I could get the bulb to glow, ie. paring mode. But the bulb would still not show up in zigbee2mqtt.

But then I tried - more or less in a desperate action - to switch the config to:

experimental:
  new_api: false

Then after doing the reset procedure, the bulb immediately paired. Pairing survived switching new_api back to true

I'm still new to the whole smart home thing, so I havn't a clue yet as to the difference in old vs new api. But it seems like a bug or at least a quirk, that maybe should be put on https://www.zigbee2mqtt.io/devices/LED1903C5_LED1835C6.html

hdoedens commented 3 years ago

I am having the exact same issue. Two brand new TRADFRI lamps (bulbs). I have reset the bulbs more than ten times now. I place it very close to the coordinator but there is no logging, and no paring. I tried the suggestion above: disabling the new_api but no success. I guess @nielsrune was lucky?

I think I have tried every suggestion now but nothing is working. What could I try or how can I see what is going on? Debug logging of the zigbee2mqtt container is not showing anything.

I have many more TRADFRI devices, remotes and lamps, they all pair at first try.

waldher commented 3 years ago

I'm having similar issues. I'm able to pair a brand new LED1835C6 with the Tradfri Gateway, with which I've updated its firmware to 2.3.050, but I'm not able to pair it with zigbee2mqtt, despite having bulbs in the past do this without issue. I've also tried two different LED1835C6's now, so it's not isolated to one bulb.

waldher commented 3 years ago

An update on my previous comment: At first, setting

experimental:
  new_api: false

in the HomeAssistant plugin configuration didn't save. After setting it again, I can confirm that it does indeed pair right away after a bulb reset using firmware 2.3.050. (If you don't know what firmware you have on your bulb, you'll need to first pair the bulb with a Tradfri Gateway to update it)

MattWestb commented 3 years ago

I was have the same problems some time. First the bulb not being reseted but working with little tryings. Some time its timing out after being reseted and starting one own networks as zigbee lights is doing (LL and Zigbee 3 standard). Its normal on channel 11 with default pan-ID then touchlink scanning from deCONZ. Reseting it with touchlink can helping getting it being detected. The large problem is if not having the default LL channels in the config (11. 15. 20 and 25 is moderate for lights in LL and zigbee 3) then it can the coordinator is not scanning the channel and not finding it. Theoretically all channels should working but using one of the primary ones its making it more successful then working with lights.

nielsrune commented 3 years ago

I'm glad to hear @waldher got his bulbs working in the same way.

I don't recall my procedure exactly, but it may have been the same:

@hdoedens would you care to try again, as it seems I wasn't just lucky..

Also, I can confirm that my firmware is 2.3.050 and the bulb was previously connected to a Trådfri gateway. Also, try to remove the bulb from the gateway before resetting.

@MattWestb My dongle is the zig-a-zig-ahh. Before getting the bulb to pair, I tried both scanning and resetting over touchlink. But it seems to not work with the dongle. The seller, Omar, wrote something like he too didn't got touchlink to work. But I can see that I have channel: 11 in the configurations advance section. I didn't touch the default config but setting a custom network_key

MattWestb commented 3 years ago

What i have reading that is some problems with the firmware of all TI coordinators that is making TL not working all the time. Then its working its being very nicely implanted in the web front end.

hdoedens commented 3 years ago

I tried the procedure as described by @nielsrune again, several times. I completely stopped and started zigbee2mqtt to be sure sure the new settings would have effect. As soon as the log was quiet I reset the Tradfri bulb, but nothing showed up in the log and the bulb keeps glowing. When I click the a Tradfri remote a few times, that will bind to the bulb immediately and the bulb respons to the Tradfri remote. Still nothing in the log (but that makes sense as it is not paired with zigbee2mqtt).

Maybe this has something to do with my settings or the version I am running. I'm running the edge version as the binding of remote to Zigbee devices is broken in the stable version. This is my config:

data_path: /share/zigbee2mqtt
external_converters: []
devices: devices.yaml
groups: groups.yaml
homeassistant: true
permit_join: true
mqtt:
  base_topic: zigbee2mqtt
  server: 'mqtt://core-mosquitto'
  user: *******
  password: ***********
serial:
  port: /dev/ttyACM1
advanced:
  log_level: debug
  pan_id: 6755
  channel: 11
  network_key:
    - 1
    - 3
    - 5
    - 7
    - 9
    - 11
    - 13
    - 15
    - 0
    - 2
    - 4
    - 6
    - 8
    - 10
    - 12
    - 13
  availability_blocklist: []
  availability_passlist: []
device_options: {}
blocklist: []
passlist: []
queue: {}
frontend:
  port: 8099
experimental:
  new_api: false
socat:
  enabled: false
  master: 'pty,raw,echo=0,link=/dev/ttyZ2M,mode=777'
  slave: 'tcp-listen:8485,keepalive,nodelay,reuseaddr,keepidle=1,keepintvl=1,keepcnt=5'
  restartdelay: 1
  initialdelay: 1
  options: '-d -d'
  log: false

Note the non-default pan_id. As I was having trouble to pair right from the start and I migrated some software but used the same hardware I thought it would help to change the pan_id to have a fresh start. I don't know the firmware version of the bulb's that won't pair as I do not have an IKEA bridge. The hardware I am using is a Texas Instruments CC2531.

Any help is more than appreciated...

MattWestb commented 3 years ago

@hdoedens The PAN-ID is only the "name" of the network and one resetted device is looking for all PAN-IDs if not having one hard coded from the factory (closed system) so its very OK. Channel 11 is the first channel lights is looking at for joining and also the best if having problems.

I have only resetting the light more times until they was pairing but it was not in Z2M.

I have reading that one Z2M user with CC-2531 was enabling debug logging and the pairing wos start working and disabling it it was stopping working. You can trying it and see if its working. Touch link resetting of the bulb can also being worth testing. And you have the new web frontend installed so testing how and if its helping.

How large is your CC2531 system ? Normally they is working up to 30 - 40 devices then hitting the wall ;-(

hdoedens commented 3 years ago

@MattWestb Glad to hear my settings are OK :) I have tried the Touchlink several times, but I think that only works with Philips devices. I already tried with and without debug logging on. No success... I currently have 11 devices paired with the CC2531.

One question: How close do you have the bulb to the coordinator when pairing? I have tried both very close (a few centimeters away) en just met them hang on the ceiling.

MattWestb commented 3 years ago

Touchlink is working on all IKEA devices. I was trying resetting one IKEA E27 WW with deCONZ and wast taking the wrong one and was resetting one IKEA GU10 WS in my kitchen 6 meters away that is paired with my IKEA GW :-(( Philips HUE is TL only working after being re powered if having newer firmware.

If doing touchlink pairing (that you is not doing) you need being very near but with classical pairing (that's what Z2M is doing) its good being near but its normal communication so normal working range suld being OK bet nearer is better / safer. Your network is not too large for your CC-2531 and you have no strange things in your config that is making the world bad for it. The CC-253X have normally pretty bad radio and antenna but if you is near it should working without problem but i knowing that's not the fact in this case.

You can trying doing the normal 6 x on - of with short on and long off and then the bulb is blinking you is power it off for some seconds and then on and see if you can pairing it (some saying its need being repowered after being reseted for being in pairing mode).

nielsrune commented 3 years ago

When I click the a Tradfri remote a few times, that will bind to the bulb immediately and the bulb respons to the Tradfri remote. Still nothing in the log (but that makes sense as it is not paired with zigbee2mqtt). @hdoedens

Maybe the bulb is somehow still paired to your remote. Try to reset the remote with four clicks on the button next to the battery and wait 10 seconds. Maybe even remove the battery from the remote before doing the reset of the bulb. Just to make sure the remote is detached from the bulb.

MattWestb commented 3 years ago

If the remote (that was touchlink pared with the bulb) can controlling the bulb then the bulb was not resetted and have all network settings from the remote stored. One bulb that is not reserted (in zigbee term not factory new) can not joining one classical (with trustcenter) zigbee network. Only with touchlink network can stealing it and force it joining its to one new network.

hdoedens commented 3 years ago

Because I have no GUI at the moment I tried to factory reset the bulb by placing it within centimeters of the coordinator and sending zigbee2mqtt/bridge/config/touchlink/factory_reset whitout payload:

Zigbee2MQTT:info  2020-11-24 11:45:53: Starting touchlink factory reset...
Zigbee2MQTT:info  2020-11-24 11:45:53: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"reset_started","meta":{"status":"started"},"type":"touchlink"}'
Zigbee2MQTT:warn  2020-11-24 11:46:05: Failed to factory reset device through Touchlink
Zigbee2MQTT:info  2020-11-24 11:46:05: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"reset_failed","meta":{"status":"failed"},"type":"touchlink"}'

I have tried to reset the bulb using Touchlink many times both while first resetting it using the on/off method (while it was glowing) and also when it was just on.

hdoedens commented 3 years ago

One thing I notice: After I have reset the bulb I still can control it using the remote?!

Had the reset procedure changed on new bulbs?

hdoedens commented 3 years ago

I think I've got it: I was reading a bit closer for the reset procedure. As some mention to click the bulb 7-times off and on 'to be sure to reset it'... that 7th time actually ruins the reset procedure. You have wait IN the 6th on state to reset it properly. Once I did that the bulb paired immediately!

Maybe good to add this little detail to the docs of the Tradfri devices.

Thanks for the help everyone!

MattWestb commented 3 years ago

I think if you can still control the bulb with the remote both have not being reseted. Then resetting one remote (pressing pairing button x 4 and led is blinking for some seconds) its making one new network if not being paired with one GW. The network key and pan-id is being random generated so not colliding with other remotes around.

Great that you was getting the bulb resetted so you cud getting it paired !!!

hdoedens commented 3 years ago

After all it had nothing to do with the new front-end as the second bulb I paired was with the new_api setting to true

I have opened pull request https://github.com/Koenkk/zigbee2mqtt.io/pull/464 for this to improve docs

github-actions[bot] commented 3 years ago

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

stevenbrown1862 commented 2 years ago

This is absolutely right. I've spent an afternoon switching the light to make it reset and I always did that 7th time to make sure. Whatever you do stick to the 6 times exactly.

JacekKac commented 1 year ago

hi guys, i have the same problem as you, don't know what to do now. I am able to put the bulb into pairing mode: fast blinking bulb, but in zigbee2mqtt nothing happens after allowing devices to join.

hdoedens commented 1 year ago

Have you upgraded your zitbeen stick tot the latest firmware?

Jackfritt commented 1 year ago

Damn had the same problem and you really have to leave it in on state at 6 time. Dont try a 7. time. I looks like the same blinking but its different and doesn´t pair then! So watch out to stop at the 6. time and leave it on. After that it paired like a dream :) Thx guys for this little diffrence....