Zigbee2mqtt: IKEA Tradfri light weird behavior

Created on 17 Nov 2019  ·  24Comments  ·  Source: Koenkk/zigbee2mqtt

On each floor I have a Tradfri bulb. Ideal as a router since its placed pretty centrally. With Z2M 1.6 and below it was working fine. Once in a while it would "drop off" the network but simply powercyling resolved it. Nothing to worry about.

However, last week I updated to 1.7.0 and 1.7.1 and one of the lights is now being marked as unavailable. It cannot be pinged/shows LQI failed in the map. However, according to the map it still serves as a router and has connections to several other devices. It however cannot be controlled or queried, yet it routes. Odd.

I have tried:

  1. Removing it from the network, but this didn't work.
  2. Resetting / re-pairing it
  3. Pairing it to my Deconz stick: First run it was added, yet it could not be controlled (or perhaps I was to impatient
  4. Paired it again to the CC-stick, nothing changed.
  5. Tried removing it from database.db and all other files, eventually it got added again but with interview_failed.
  6. Paired it to Deconz again: It could control the light just fine. On. Off. Setting brightness. No problems here.. So the light is fine, something else must be causing this.
  7. Tried pairing it again to CC. Again, not working. Interview failed.
  8. I have also tried to powercycle all of the routers (a few bulbs and signal repeaters) but this didn't seem to make any difference.

When the bulb turns on, Z2M says that the bulb has announced itself. It briefly becomes "online" / available but it cannot be controlled and after a short while it turns unavailable again.

Debug Info

zigbee2mqtt version: 1.7.1+dev
CC253X firmware version: 20190619 (source routing)

stale
Source
picture syphernl

All 24 comments

It could be that the bulb immediately joins the Deconz network as it was connected to that before (I've seen this behaviour multiple times for TRADFRI devices).

Koenkk picture Koenkk on 18 Nov 2019

Once I turn it on again I immediately see:

info  2019-11-19 16:34:25: MQTT publish: topic 'zigbee2mqtt/lamp_overloop/availability', payload 'online'

And shortly thereafter:

error 2019-11-19 16:34:35: Failed to setup reporting for '0x000b57fffeda561e' - Error: AREQ - ZDO - bindRsp after 10000ms
    at Timeout.object.timer.setTimeout [as _onTimeout] (/srv/zigbee2mqtt/node_modules/zigbee-herdsman/dist/utils/waitress.js:44:24)
    at ontimeout (timers.js:436:11)
    at tryOnTimeout (timers.js:300:5)
    at listOnTimeout (timers.js:263:5)
    at Timer.processTimers (timers.js:223:10)
error 2019-11-19 16:34:45: Failed to read state of 'lamp_overloop' after reconnect
error 2019-11-19 16:35:00: Publish 'set' 'state' to 'lamp_overloop' failed: 'Error: Timeout - 27211 - 1 - 14 - 6 - 11 after 15000ms'

As a test I have the Deconz network open but I don't see it joining that network.

Pairing it again to Z2M results in:

info  2019-11-19 16:39:45: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"pairing","message":"interview_started","meta":{"friendly_name":"lamp_overloop"}}'
error 2019-11-19 16:39:46: Publish 'set' 'state' to 'lamp_overloop' failed: 'Error: Timeout - 27211 - 1 - 52 - 6 - 11 after 15000ms'
error 2019-11-19 16:40:21: Failed to interview 'lamp_overloop', device has not successfully been paired
syphernl picture syphernl on 19 Nov 2019

The reset procedure of IKEA bulb can be tricky sometimes, this screenshot is from a users who managed to pair his bulb after a lot of attempts:

image

Koenkk picture Koenkk on 19 Nov 2019

Yeah it is a bit tricky but I never had the issue I'm seeing now. I've done the off/on thing for a bunch of times now but the interview keeps on failing.

syphernl picture syphernl on 23 Nov 2019

Debug logs:
Immediate after turning on the bulb:

Turn on:

  serialport/bindings/poller received "readable" +13s
  serialport/binding-abstract read +13s
  serialport/bindings/unixRead Starting read +13s
  serialport/bindings/unixRead Finished read { bytesRead: 18,
  buffer:
   <Buffer fe 0e 61 02 02 00 02 06 03 9b 15 34 01 02 00 00 00 00 d1 fe 03 61 08 00 01 55 3e fe 03 61 08 00 01 55 3e fe 06 61 08 00 04 00 08 00 00 63 fe 03 61 08 ... > } bytes +0ms
  serialport/stream binding.read finished { bytesRead: 18 } +13s
  zigbee-herdsman:adapter:zStack:unpi:parser <-- [254,13,69,193,75,106,75,106,30,86,218,254,255,87,11,0,142,200] +13s
  zigbee-herdsman:adapter:zStack:unpi:parser --- parseNext [254,13,69,193,75,106,75,106,30,86,218,254,255,87,11,0,142,200] +0ms
  zigbee-herdsman:adapter:zStack:unpi:parser --> parsed 13 - 2 - 5 - 193 - [75,106,75,106,30,86,218,254,255,87,11,0,142] - 200 +0ms
  zigbee-herdsman:adapter:zStack:znp:AREQ <-- ZDO - endDeviceAnnceInd - {"srcaddr":27211,"nwkaddr":27211,"ieeeaddr":"0x000b57fffeda561e","capabilities":142} +13s
  zigbee-herdsman:controller:log Device announce '0x000b57fffeda561e' +13s
zigbee2mqtt:debug 2019-11-23 12:12:36: Device 'lamp_overloop' announced itself
winston:file written true false
  zigbee-herdsman:adapter:zStack:unpi:parser --- parseNext [] +1ms
zigbee2mqtt:debug 2019-11-23 12:12:36: Setup reporting for '0x000b57fffeda561e' - 1 - genOnOff
winston:file written true false
  zigbee-herdsman:adapter:zStack:znp:SREQ --> ZDO - bindReq - {"dstaddr":27211,"srcaddr":"0x000b57fffeda561e","srcendpoint":1,"clusterid":6,"dstaddrmode":3,"dstaddress":"0x00124b0018ed1774","dstendpoint":1} +13s
  zigbee-herdsman:adapter:zStack:unpi:writer --> frame [254,23,37,33,75,106,30,86,218,254,255,87,11,0,1,6,0,3,116,23,237,24,0,75,18,0,1,55] +13s
  serialport/stream _write 28 bytes of data +6ms
  serialport/binding-abstract write 28 bytes +7ms
  serialport/bindings/unixWrite Starting write 28 bytes offset 0 bytesToWrite 28 +13s
winston:file logged 102659 debug 2019-11-23 12:12:36: Device 'lamp_overloop' announced itself

  serialport/stream _read reading { start: 290, toRead: 65246 } +0ms
  serialport/binding-abstract read +1ms
winston:file logged 102742 debug 2019-11-23 12:12:36: Setup reporting for '0x000b57fffeda561e' - 1 - genOnOff

  serialport/bindings/unixRead Starting read +8ms
  serialport/bindings/unixWrite write returned: wrote 28 bytes +1ms
  serialport/bindings/unixWrite Finished writing 28 bytes +0ms
  serialport/stream binding.write write finished +1ms
  serialport/bindings/unixRead waiting for readable because of code: EAGAIN +0ms
  serialport/bindings/poller Polling for "readable" +8ms
  serialport/bindings/poller received "readable" +15ms
  serialport/binding-abstract read +15ms
  serialport/bindings/unixRead Starting read +15ms
  serialport/bindings/unixRead Finished read { bytesRead: 6,
  buffer:
   <Buffer fe 0e 61 02 02 00 02 06 03 9b 15 34 01 02 00 00 00 00 d1 fe 03 61 08 00 01 55 3e fe 03 61 08 00 01 55 3e fe 06 61 08 00 04 00 08 00 00 63 fe 03 61 08 ... > } bytes +0ms
  serialport/stream binding.read finished { bytesRead: 6 } +15ms
  zigbee-herdsman:adapter:zStack:unpi:parser <-- [254,1,101,33,0,69] +21ms
  zigbee-herdsman:adapter:zStack:unpi:parser --- parseNext [254,1,101,33,0,69] +0ms
  zigbee-herdsman:adapter:zStack:unpi:parser --> parsed 1 - 3 - 5 - 33 - [0] - 69 +0ms
  zigbee-herdsman:adapter:zStack:znp:SRSP <-- ZDO - bindReq - {"status":0} +13s
  zigbee-herdsman:adapter:zStack:unpi:parser --- parseNext [] +1ms
  serialport/stream _read reading { start: 296, toRead: 65240 } +1ms
  serialport/binding-abstract read +1ms
  serialport/bindings/unixRead Starting read +1ms
  serialport/bindings/unixRead waiting for readable because of code: EAGAIN +0ms
  serialport/bindings/poller Polling for "readable" +1ms
zigbee2mqtt:error 2019-11-23 12:12:46: Failed to setup reporting for '0x000b57fffeda561e' - Error: AREQ - ZDO - bindRsp after 10000ms
    at Timeout.object.timer.setTimeout [as _onTimeout] (/srv/zigbee2mqtt/node_modules/zigbee-herdsman/dist/utils/waitress.js:44:24)
    at ontimeout (timers.js:436:11)
    at tryOnTimeout (timers.js:300:5)
    at listOnTimeout (timers.js:263:5)
    at Timer.processTimers (timers.js:223:10)
winston:file written true false
winston:file logged 103155 error 2019-11-23 12:12:46: Failed to setup reporting for '0x000b57fffeda561e' - Error: AREQ - ZDO - bindRsp after 10000ms
    at Timeout.object.timer.setTimeout [as _onTimeout] (/srv/zigbee2mqtt/node_modules/zigbee-herdsman/dist/utils/waitress.js:44:24)
    at ontimeout (timers.js:436:11)
    at tryOnTimeout (timers.js:300:5)
    at listOnTimeout (timers.js:263:5)
    at Timer.processTimers (timers.js:223:10)

After setting the bulb to pairing mode with the 6 off's/on's:

serialport/bindings/poller received "readable" +10s                                                                                                                              [496/51876]
  serialport/binding-abstract read +10s
  serialport/bindings/unixRead Starting read +10s
  serialport/bindings/unixRead Finished read { bytesRead: 18,
  buffer:
   <Buffer fe 0e 61 02 02 00 02 06 03 9b 15 34 01 02 00 00 00 00 d1 fe 03 61 08 00 01 55 3e fe 03 61 08 00 01 55 3e fe 06 61 08 00 04 00 08 00 00 63 fe 03 61 08 ... > } bytes +0ms
  serialport/stream binding.read finished { bytesRead: 18 } +10s
  zigbee-herdsman:adapter:zStack:unpi:parser <-- [254,13,69,193,75,106,75,106,30,86,218,254,255,87,11,0,142,200] +10s
  zigbee-herdsman:adapter:zStack:unpi:parser --- parseNext [254,13,69,193,75,106,75,106,30,86,218,254,255,87,11,0,142,200] +0ms
  zigbee-herdsman:adapter:zStack:unpi:parser --> parsed 13 - 2 - 5 - 193 - [75,106,75,106,30,86,218,254,255,87,11,0,142] - 200 +0ms
  zigbee-herdsman:adapter:zStack:znp:AREQ <-- ZDO - endDeviceAnnceInd - {"srcaddr":27211,"nwkaddr":27211,"ieeeaddr":"0x000b57fffeda561e","capabilities":142} +10s
  zigbee-herdsman:controller:log Device announce '0x000b57fffeda561e' +10s
zigbee2mqtt:debug 2019-11-23 12:13:23: Device 'lamp_overloop' announced itself
winston:file written true false
  zigbee-herdsman:adapter:zStack:unpi:parser --- parseNext [] +1ms
winston:file logged 105967 debug 2019-11-23 12:13:23: Device 'lamp_overloop' announced itself

  serialport/stream _read reading { start: 650, toRead: 64886 } +1ms
  serialport/binding-abstract read +1ms
  serialport/bindings/unixRead Starting read +1ms
  serialport/bindings/unixRead waiting for readable because of code: EAGAIN +1ms
  serialport/bindings/poller Polling for "readable" +3ms
  serialport/bindings/poller received "readable" +1s
  serialport/binding-abstract read +1s
  serialport/bindings/unixRead Starting read +1s
  serialport/bindings/unixRead Finished read { bytesRead: 18,
  buffer:
   <Buffer fe 0e 61 02 02 00 02 06 03 9b 15 34 01 02 00 00 00 00 d1 fe 03 61 08 00 01 55 3e fe 03 61 08 00 01 55 3e fe 06 61 08 00 04 00 08 00 00 63 fe 03 61 08 ... > } bytes +0ms
  serialport/stream binding.read finished { bytesRead: 18 } +1s
  zigbee-herdsman:adapter:zStack:unpi:parser <-- [254,13,69,193,75,106,75,106,30,86,218,254,255,87,11,0,142,200] +1s
  zigbee-herdsman:adapter:zStack:unpi:parser --- parseNext [254,13,69,193,75,106,75,106,30,86,218,254,255,87,11,0,142,200] +0ms
  zigbee-herdsman:adapter:zStack:unpi:parser --> parsed 13 - 2 - 5 - 193 - [75,106,75,106,30,86,218,254,255,87,11,0,142] - 200 +0ms
  zigbee-herdsman:adapter:zStack:znp:AREQ <-- ZDO - endDeviceAnnceInd - {"srcaddr":27211,"nwkaddr":27211,"ieeeaddr":"0x000b57fffeda561e","capabilities":142} +1s
  zigbee-herdsman:controller:log Device announce '0x000b57fffeda561e' +1s
zigbee2mqtt:debug 2019-11-23 12:13:24: Device 'lamp_overloop' announced itself
winston:file written true false
  zigbee-herdsman:adapter:zStack:unpi:parser --- parseNext [] +0ms
winston:file logged 106034 debug 2019-11-23 12:13:24: Device 'lamp_overloop' announced itself

  serialport/stream _read reading { start: 668, toRead: 64868 } +2ms
  serialport/binding-abstract read +2ms
  serialport/bindings/unixRead Starting read +2ms
  serialport/bindings/unixRead waiting for readable because of code: EAGAIN +0ms
  serialport/bindings/poller Polling for "readable" +2ms
  serialport/bindings/poller received "readable" +1s
  serialport/binding-abstract read +1s
  serialport/bindings/unixRead Starting read +1s
  serialport/bindings/unixRead Finished read { bytesRead: 18,
  buffer:
   <Buffer fe 0e 61 02 02 00 02 06 03 9b 15 34 01 02 00 00 00 00 d1 fe 03 61 08 00 01 55 3e fe 03 61 08 00 01 55 3e fe 06 61 08 00 04 00 08 00 00 63 fe 03 61 08 ... > } bytes +0ms
  serialport/stream binding.read finished { bytesRead: 18 } +1s
  zigbee-herdsman:adapter:zStack:unpi:parser <-- [254,13,69,193,75,106,75,106,30,86,218,254,255,87,11,0,142,200] +1s
  zigbee-herdsman:adapter:zStack:unpi:parser --- parseNext [254,13,69,193,75,106,75,106,30,86,218,254,255,87,11,0,142,200] +0ms
  zigbee-herdsman:adapter:zStack:unpi:parser --> parsed 13 - 2 - 5 - 193 - [75,106,75,106,30,86,218,254,255,87,11,0,142] - 200 +0ms
  zigbee-herdsman:adapter:zStack:znp:AREQ <-- ZDO - endDeviceAnnceInd - {"srcaddr":27211,"nwkaddr":27211,"ieeeaddr":"0x000b57fffeda561e","capabilities":142} +1s
  zigbee-herdsman:controller:log Device announce '0x000b57fffeda561e' +1s
zigbee2mqtt:debug 2019-11-23 12:13:25: Device 'lamp_overloop' announced itself
winston:file written true false
  zigbee-herdsman:adapter:zStack:unpi:parser --- parseNext [] +1ms
winston:file logged 106101 debug 2019-11-23 12:13:25: Device 'lamp_overloop' announced itself

  serialport/stream _read reading { start: 686, toRead: 64850 } +1ms
  serialport/binding-abstract read +1ms                                                                                                                                            [434/51876]
  serialport/bindings/unixRead Starting read +1ms
  serialport/bindings/unixRead waiting for readable because of code: EAGAIN +1ms
  serialport/bindings/poller Polling for "readable" +2ms
  serialport/bindings/poller received "readable" +1s
  serialport/binding-abstract read +1s
  serialport/bindings/unixRead Starting read +1s
  serialport/bindings/unixRead Finished read { bytesRead: 18,
  buffer:
   <Buffer fe 0e 61 02 02 00 02 06 03 9b 15 34 01 02 00 00 00 00 d1 fe 03 61 08 00 01 55 3e fe 03 61 08 00 01 55 3e fe 06 61 08 00 04 00 08 00 00 63 fe 03 61 08 ... > } bytes +0ms
  serialport/stream binding.read finished { bytesRead: 18 } +1s
  zigbee-herdsman:adapter:zStack:unpi:parser <-- [254,13,69,193,75,106,75,106,30,86,218,254,255,87,11,0,142,200] +1s
  zigbee-herdsman:adapter:zStack:unpi:parser --- parseNext [254,13,69,193,75,106,75,106,30,86,218,254,255,87,11,0,142,200] +0ms
  zigbee-herdsman:adapter:zStack:unpi:parser --> parsed 13 - 2 - 5 - 193 - [75,106,75,106,30,86,218,254,255,87,11,0,142] - 200 +0ms
  zigbee-herdsman:adapter:zStack:znp:AREQ <-- ZDO - endDeviceAnnceInd - {"srcaddr":27211,"nwkaddr":27211,"ieeeaddr":"0x000b57fffeda561e","capabilities":142} +1s
  zigbee-herdsman:controller:log Device announce '0x000b57fffeda561e' +1s
zigbee2mqtt:debug 2019-11-23 12:13:26: Device 'lamp_overloop' announced itself
winston:file written true false
  zigbee-herdsman:adapter:zStack:unpi:parser --- parseNext [] +1ms
winston:file logged 106168 debug 2019-11-23 12:13:26: Device 'lamp_overloop' announced itself

  serialport/stream _read reading { start: 704, toRead: 64832 } +1ms
  serialport/binding-abstract read +2ms
  serialport/bindings/unixRead Starting read +2ms
  serialport/bindings/unixRead waiting for readable because of code: EAGAIN +0ms
  serialport/bindings/poller Polling for "readable" +2ms
  serialport/bindings/poller received "readable" +1s
  serialport/binding-abstract read +1s
  serialport/bindings/unixRead Starting read +1s
  serialport/bindings/unixRead Finished read { bytesRead: 18,
  buffer:
   <Buffer fe 0e 61 02 02 00 02 06 03 9b 15 34 01 02 00 00 00 00 d1 fe 03 61 08 00 01 55 3e fe 03 61 08 00 01 55 3e fe 06 61 08 00 04 00 08 00 00 63 fe 03 61 08 ... > } bytes +0ms
  serialport/stream binding.read finished { bytesRead: 18 } +1s
  zigbee-herdsman:adapter:zStack:unpi:parser <-- [254,13,69,193,75,106,75,106,30,86,218,254,255,87,11,0,142,200] +1s
  zigbee-herdsman:adapter:zStack:unpi:parser --- parseNext [254,13,69,193,75,106,75,106,30,86,218,254,255,87,11,0,142,200] +0ms
  zigbee-herdsman:adapter:zStack:unpi:parser --> parsed 13 - 2 - 5 - 193 - [75,106,75,106,30,86,218,254,255,87,11,0,142] - 200 +0ms
  zigbee-herdsman:adapter:zStack:znp:AREQ <-- ZDO - endDeviceAnnceInd - {"srcaddr":27211,"nwkaddr":27211,"ieeeaddr":"0x000b57fffeda561e","capabilities":142} +1s
  zigbee-herdsman:controller:log Device announce '0x000b57fffeda561e' +1s
zigbee2mqtt:debug 2019-11-23 12:13:27: Device 'lamp_overloop' announced itself
winston:file written true false
  zigbee-herdsman:adapter:zStack:unpi:parser --- parseNext [] +1ms
winston:file logged 106235 debug 2019-11-23 12:13:27: Device 'lamp_overloop' announced itself

  serialport/stream _read reading { start: 722, toRead: 64814 } +1ms
  serialport/binding-abstract read +1ms
  serialport/bindings/unixRead Starting read +2ms
  serialport/bindings/unixRead waiting for readable because of code: EAGAIN +0ms
  serialport/bindings/poller Polling for "readable" +3ms
  serialport/bindings/poller received "readable" +962ms
  serialport/binding-abstract read +963ms
  serialport/bindings/unixRead Starting read +962ms
  serialport/bindings/unixRead Finished read { bytesRead: 18,
  buffer:
   <Buffer fe 0e 61 02 02 00 02 06 03 9b 15 34 01 02 00 00 00 00 d1 fe 03 61 08 00 01 55 3e fe 03 61 08 00 01 55 3e fe 06 61 08 00 04 00 08 00 00 63 fe 03 61 08 ... > } bytes +0ms
  serialport/stream binding.read finished { bytesRead: 18 } +963ms
  zigbee-herdsman:adapter:zStack:unpi:parser <-- [254,13,69,193,75,106,75,106,30,86,218,254,255,87,11,0,142,200] +963ms
  zigbee-herdsman:adapter:zStack:unpi:parser --- parseNext [254,13,69,193,75,106,75,106,30,86,218,254,255,87,11,0,142,200] +0ms
  zigbee-herdsman:adapter:zStack:unpi:parser --> parsed 13 - 2 - 5 - 193 - [75,106,75,106,30,86,218,254,255,87,11,0,142] - 200 +1ms
  zigbee-herdsman:adapter:zStack:znp:AREQ <-- ZDO - endDeviceAnnceInd - {"srcaddr":27211,"nwkaddr":27211,"ieeeaddr":"0x000b57fffeda561e","capabilities":142} +965ms
  zigbee-herdsman:controller:log Device announce '0x000b57fffeda561e' +964ms
zigbee2mqtt:debug 2019-11-23 12:13:28: Device 'lamp_overloop' announced itself
winston:file written true false                                                                                                                                                    [373/51876]
  zigbee-herdsman:adapter:zStack:unpi:parser --- parseNext [] +0ms
winston:file logged 106302 debug 2019-11-23 12:13:28: Device 'lamp_overloop' announced itself

  serialport/stream _read reading { start: 740, toRead: 64796 } +2ms
  serialport/binding-abstract read +2ms
  serialport/bindings/unixRead Starting read +2ms
  serialport/bindings/unixRead waiting for readable because of code: EAGAIN +0ms
  serialport/bindings/poller Polling for "readable" +2ms
  serialport/bindings/poller received "readable" +3s
  serialport/binding-abstract read +3s
  serialport/bindings/unixRead Starting read +3s
  serialport/bindings/unixRead Finished read { bytesRead: 8,
  buffer:
   <Buffer fe 0e 61 02 02 00 02 06 03 9b 15 34 01 02 00 00 00 00 d1 fe 03 61 08 00 01 55 3e fe 03 61 08 00 01 55 3e fe 06 61 08 00 04 00 08 00 00 63 fe 03 61 08 ... > } bytes +0ms
  serialport/stream binding.read finished { bytesRead: 8 } +3s
  zigbee-herdsman:adapter:zStack:unpi:parser <-- [254,3,69,196,94,89,0,133] +3s
  zigbee-herdsman:adapter:zStack:unpi:parser --- parseNext [254,3,69,196,94,89,0,133] +0ms
  zigbee-herdsman:adapter:zStack:unpi:parser --> parsed 3 - 2 - 5 - 196 - [94,89,0] - 133 +1ms
  zigbee-herdsman:adapter:zStack:znp:AREQ <-- ZDO - srcRtgInd - {"dstaddr":22878,"relaycount":0,"relaylist":[]} +3s
  zigbee-herdsman:adapter:zStack:unpi:parser --- parseNext [] +0ms
  serialport/stream _read reading { start: 748, toRead: 64788 } +1ms
  serialport/binding-abstract read +1ms
  serialport/bindings/unixRead Starting read +1ms
  serialport/bindings/unixRead waiting for readable because of code: EAGAIN +0ms
  serialport/bindings/poller Polling for "readable" +1ms
  serialport/bindings/poller received "readable" +4ms
  serialport/binding-abstract read +4ms
  serialport/bindings/unixRead Starting read +4ms
  serialport/bindings/unixRead Finished read { bytesRead: 8,
  buffer:
   <Buffer fe 0e 61 02 02 00 02 06 03 9b 15 34 01 02 00 00 00 00 d1 fe 03 61 08 00 01 55 3e fe 03 61 08 00 01 55 3e fe 06 61 08 00 04 00 08 00 00 63 fe 03 61 08 ... > } bytes +0ms
  serialport/stream binding.read finished { bytesRead: 8 } +4ms
  zigbee-herdsman:adapter:zStack:unpi:parser <-- [254,3,69,196,94,89,0,133] +4ms
  zigbee-herdsman:adapter:zStack:unpi:parser --- parseNext [254,3,69,196,94,89,0,133] +0ms
  zigbee-herdsman:adapter:zStack:unpi:parser --> parsed 3 - 2 - 5 - 196 - [94,89,0] - 133 +0ms
  zigbee-herdsman:adapter:zStack:znp:AREQ <-- ZDO - srcRtgInd - {"dstaddr":22878,"relaycount":0,"relaylist":[]} +4ms
  zigbee-herdsman:adapter:zStack:unpi:parser --- parseNext [] +0ms
  serialport/stream _read reading { start: 756, toRead: 64780 } +0ms
  serialport/binding-abstract read +1ms
  serialport/bindings/unixRead Starting read +1ms
  serialport/bindings/unixRead waiting for readable because of code: EAGAIN +0ms
  serialport/bindings/poller Polling for "readable" +1ms
  serialport/bindings/poller received "readable" +110ms
  serialport/binding-abstract read +110ms
  serialport/bindings/unixRead Starting read +110ms
  serialport/bindings/unixRead Finished read { bytesRead: 17,
  buffer:
   <Buffer fe 0e 61 02 02 00 02 06 03 9b 15 34 01 02 00 00 00 00 d1 fe 03 61 08 00 01 55 3e fe 03 61 08 00 01 55 3e fe 06 61 08 00 04 00 08 00 00 63 fe 03 61 08 ... > } bytes +0ms
  serialport/stream binding.read finished { bytesRead: 17 } +111ms
  zigbee-herdsman:adapter:zStack:unpi:parser <-- [254,12,69,202,75,106,30,86,218,254,255,87,11,0,94,89,106] +112ms
  zigbee-herdsman:adapter:zStack:unpi:parser --- parseNext [254,12,69,202,75,106,30,86,218,254,255,87,11,0,94,89,106] +0ms
  zigbee-herdsman:adapter:zStack:unpi:parser --> parsed 12 - 2 - 5 - 202 - [75,106,30,86,218,254,255,87,11,0,94,89] - 106 +0ms
  zigbee-herdsman:adapter:zStack:znp:AREQ <-- ZDO - tcDeviceInd - {"nwkaddr":27211,"extaddr":"0x000b57fffeda561e","parentaddr":22878} +112ms
  zigbee-herdsman:controller:log Device '0x000b57fffeda561e' joined +3s
  zigbee-herdsman:adapter:zStack:unpi:parser --- parseNext [] +1ms
  zigbee-herdsman:controller:log Device '0x000b57fffeda561e' accepted by handler +1ms
  zigbee-herdsman:controller:log Interview '0x000b57fffeda561e' start +0ms
zigbee2mqtt:info  2019-11-23 12:13:31: Starting interview of 'lamp_overloop'
winston:file written true false
zigbee2mqtt:info  2019-11-23 12:13:31: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"pairing","message":"interview_started","meta":{"friendly_name":"lamp_overloop"}}'
winston:file written true false
  zigbee-herdsman:controller:device Interview - start device '0x000b57fffeda561e' +0ms
  zigbee-herdsman:adapter:zStack:znp:SREQ --> ZDO - nodeDescReq - {"dstaddr":27211,"nwkaddrofinterest":27211} +18s
  zigbee-herdsman:adapter:zStack:unpi:writer --> frame [254,4,37,2,75,106,75,106,35] +18s
  serialport/stream _write 9 bytes of data +5ms
  serialport/binding-abstract write 9 bytes +5ms
  serialport/bindings/unixWrite Starting write 9 bytes offset 0 bytesToWrite 9 +18s
  serialport/stream _read reading { start: 773, toRead: 64763 } +1ms
  serialport/binding-abstract read +1ms
winston:file logged 106367 info  2019-11-23 12:13:31: Starting interview of 'lamp_overloop'

winston:file logged 106540 info  2019-11-23 12:13:31: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"pairing","message":"interview_started","meta":{"friendly_name":"lamp_ove
rloop"}}'

  serialport/bindings/unixRead Starting read +6ms
  serialport/bindings/unixWrite write returned: wrote 9 bytes +1ms
  serialport/bindings/unixWrite Finished writing 9 bytes +0ms
  serialport/stream binding.write write finished +1ms
  serialport/bindings/unixRead Finished read { bytesRead: 17,
  buffer:
   <Buffer fe 0e 61 02 02 00 02 06 03 9b 15 34 01 02 00 00 00 00 d1 fe 03 61 08 00 01 55 3e fe 03 61 08 00 01 55 3e fe 06 61 08 00 04 00 08 00 00 63 fe 03 61 08 ... > } bytes +1ms
  serialport/stream binding.read finished { bytesRead: 17 } +0ms
  zigbee-herdsman:adapter:zStack:unpi:parser <-- [254,12,69,202,75,106,30,86,218,254,255,87,11,0,94,89,106] +5ms
  zigbee-herdsman:adapter:zStack:unpi:parser --- parseNext [254,12,69,202,75,106,30,86,218,254,255,87,11,0,94,89,106] +0ms
  zigbee-herdsman:adapter:zStack:unpi:parser --> parsed 12 - 2 - 5 - 202 - [75,106,30,86,218,254,255,87,11,0,94,89] - 106 +0ms
  zigbee-herdsman:adapter:zStack:znp:AREQ <-- ZDO - tcDeviceInd - {"nwkaddr":27211,"extaddr":"0x000b57fffeda561e","parentaddr":22878} +7ms
  zigbee-herdsman:controller:log Device '0x000b57fffeda561e' joined +6ms
  zigbee-herdsman:adapter:zStack:unpi:parser --- parseNext [] +1ms
  zigbee-herdsman:controller:log Device '0x000b57fffeda561e' accepted by handler +0ms
  zigbee-herdsman:controller:log Not interviewing '0x000b57fffeda561e', completed 'undefined', in progress 'true' +0ms
  serialport/stream _read reading { start: 790, toRead: 64746 } +1ms
  serialport/binding-abstract read +2ms
  serialport/bindings/unixRead Starting read +1ms
  serialport/bindings/unixRead waiting for readable because of code: EAGAIN +0ms
  serialport/bindings/poller Polling for "readable" +9ms
  serialport/bindings/poller received "readable" +10ms
  serialport/binding-abstract read +11ms
  serialport/bindings/unixRead Starting read +11ms
  serialport/bindings/unixRead Finished read { bytesRead: 6,
  buffer:
   <Buffer fe 0e 61 02 02 00 02 06 03 9b 15 34 01 02 00 00 00 00 d1 fe 03 61 08 00 01 55 3e fe 03 61 08 00 01 55 3e fe 06 61 08 00 04 00 08 00 00 63 fe 03 61 08 ... > } bytes +0ms
  serialport/stream binding.read finished { bytesRead: 6 } +12ms
  zigbee-herdsman:adapter:zStack:unpi:parser <-- [254,1,101,2,0,102] +12ms
  zigbee-herdsman:adapter:zStack:unpi:parser --- parseNext [254,1,101,2,0,102] +0ms
  zigbee-herdsman:adapter:zStack:unpi:parser --> parsed 1 - 3 - 5 - 2 - [0] - 102 +0ms
  zigbee-herdsman:adapter:zStack:znp:SRSP <-- ZDO - nodeDescReq - {"status":0} +18s
  zigbee-herdsman:adapter:zStack:unpi:parser --- parseNext [] +0ms
  serialport/stream _read reading { start: 796, toRead: 64740 } +0ms
  serialport/binding-abstract read +2ms
  serialport/bindings/unixRead Starting read +2ms
  serialport/bindings/unixRead waiting for readable because of code: EAGAIN +0ms
  serialport/bindings/poller Polling for "readable" +2ms
  serialport/bindings/poller received "readable" +6s
  serialport/binding-abstract read +6s
  serialport/bindings/unixRead Starting read +6s
  serialport/bindings/unixRead Finished read { bytesRead: 8,
  buffer:                                                                                                                                                                          [256/51876]
   <Buffer fe 0e 61 02 02 00 02 06 03 9b 15 34 01 02 00 00 00 00 d1 fe 03 61 08 00 01 55 3e fe 03 61 08 00 01 55 3e fe 06 61 08 00 04 00 08 00 00 63 fe 03 61 08 ... > } bytes +0ms
  serialport/stream binding.read finished { bytesRead: 8 } +6s
  zigbee-herdsman:adapter:zStack:unpi:parser <-- [254,3,69,196,94,89,0,133] +6s
  zigbee-herdsman:adapter:zStack:unpi:parser --- parseNext [254,3,69,196,94,89,0,133] +0ms
  zigbee-herdsman:adapter:zStack:unpi:parser --> parsed 3 - 2 - 5 - 196 - [94,89,0] - 133 +0ms
  zigbee-herdsman:adapter:zStack:znp:AREQ <-- ZDO - srcRtgInd - {"dstaddr":22878,"relaycount":0,"relaylist":[]} +6s
  zigbee-herdsman:adapter:zStack:unpi:parser --- parseNext [] +0ms
  serialport/stream _read reading { start: 804, toRead: 64732 } +0ms
  serialport/binding-abstract read +0ms
  serialport/bindings/unixRead Starting read +1ms
  serialport/bindings/unixRead waiting for readable because of code: EAGAIN +0ms
  serialport/bindings/poller Polling for "readable" +2ms
  serialport/bindings/poller received "readable" +3ms
  serialport/binding-abstract read +4ms
  serialport/bindings/unixRead Starting read +3ms
  serialport/bindings/unixRead Finished read { bytesRead: 8,
  buffer:
   <Buffer fe 0e 61 02 02 00 02 06 03 9b 15 34 01 02 00 00 00 00 d1 fe 03 61 08 00 01 55 3e fe 03 61 08 00 01 55 3e fe 06 61 08 00 04 00 08 00 00 63 fe 03 61 08 ... > } bytes +1ms
  serialport/stream binding.read finished { bytesRead: 8 } +5ms
  zigbee-herdsman:adapter:zStack:unpi:parser <-- [254,3,69,196,94,89,0,133] +5ms
  zigbee-herdsman:adapter:zStack:unpi:parser --- parseNext [254,3,69,196,94,89,0,133] +0ms
  zigbee-herdsman:adapter:zStack:unpi:parser --> parsed 3 - 2 - 5 - 196 - [94,89,0] - 133 +0ms
  zigbee-herdsman:adapter:zStack:znp:AREQ <-- ZDO - srcRtgInd - {"dstaddr":22878,"relaycount":0,"relaylist":[]} +5ms
  zigbee-herdsman:adapter:zStack:unpi:parser --- parseNext [] +0ms
  serialport/stream _read reading { start: 812, toRead: 64724 } +0ms
  serialport/binding-abstract read +1ms
  serialport/bindings/unixRead Starting read +0ms
  serialport/bindings/unixRead waiting for readable because of code: EAGAIN +1ms
  serialport/bindings/poller Polling for "readable" +2ms
  serialport/bindings/poller received "readable" +110ms
  serialport/binding-abstract read +111ms
  serialport/bindings/unixRead Starting read +110ms
  serialport/bindings/unixRead Finished read { bytesRead: 17,
  buffer:
   <Buffer fe 0e 61 02 02 00 02 06 03 9b 15 34 01 02 00 00 00 00 d1 fe 03 61 08 00 01 55 3e fe 03 61 08 00 01 55 3e fe 06 61 08 00 04 00 08 00 00 63 fe 03 61 08 ... > } bytes +1ms
  serialport/stream binding.read finished { bytesRead: 17 } +112ms
  zigbee-herdsman:adapter:zStack:unpi:parser <-- [254,12,69,202,75,106,30,86,218,254,255,87,11,0,94,89,106] +112ms
  zigbee-herdsman:adapter:zStack:unpi:parser --- parseNext [254,12,69,202,75,106,30,86,218,254,255,87,11,0,94,89,106] +0ms
  zigbee-herdsman:adapter:zStack:unpi:parser --> parsed 12 - 2 - 5 - 202 - [75,106,30,86,218,254,255,87,11,0,94,89] - 106 +0ms
  zigbee-herdsman:adapter:zStack:znp:AREQ <-- ZDO - tcDeviceInd - {"nwkaddr":27211,"extaddr":"0x000b57fffeda561e","parentaddr":22878} +112ms
  zigbee-herdsman:controller:log Device '0x000b57fffeda561e' joined +6s
  zigbee-herdsman:adapter:zStack:unpi:parser --- parseNext [] +0ms
  zigbee-herdsman:controller:log Device '0x000b57fffeda561e' accepted by handler +1ms
  zigbee-herdsman:controller:log Not interviewing '0x000b57fffeda561e', completed 'undefined', in progress 'true' +0ms
  serialport/stream _read reading { start: 829, toRead: 64707 } +1ms
  serialport/binding-abstract read +2ms
  serialport/bindings/unixRead Starting read +1ms
  serialport/bindings/unixRead waiting for readable because of code: EAGAIN +0ms
  serialport/bindings/poller Polling for "readable" +2ms
  serialport/bindings/poller received "readable" +4ms
  serialport/binding-abstract read +4ms
  serialport/bindings/unixRead Starting read +4ms
  serialport/bindings/unixRead Finished read { bytesRead: 17,
  buffer:
   <Buffer fe 0e 61 02 02 00 02 06 03 9b 15 34 01 02 00 00 00 00 d1 fe 03 61 08 00 01 55 3e fe 03 61 08 00 01 55 3e fe 06 61 08 00 04 00 08 00 00 63 fe 03 61 08 ... > } bytes +0ms
  serialport/stream binding.read finished { bytesRead: 17 } +4ms
  zigbee-herdsman:adapter:zStack:unpi:parser <-- [254,12,69,202,75,106,30,86,218,254,255,87,11,0,94,89,106] +6ms
  zigbee-herdsman:adapter:zStack:unpi:parser --- parseNext [254,12,69,202,75,106,30,86,218,254,255,87,11,0,94,89,106] +0ms
  zigbee-herdsman:adapter:zStack:unpi:parser --> parsed 12 - 2 - 5 - 202 - [75,106,30,86,218,254,255,87,11,0,94,89] - 106 +0ms
  zigbee-herdsman:adapter:zStack:znp:AREQ <-- ZDO - tcDeviceInd - {"nwkaddr":27211,"extaddr":"0x000b57fffeda561e","parentaddr":22878} +6ms
  zigbee-herdsman:controller:log Device '0x000b57fffeda561e' joined +5ms
  zigbee-herdsman:adapter:zStack:unpi:parser --- parseNext [] +0ms                                                                                                                 [194/51876]
  zigbee-herdsman:controller:log Device '0x000b57fffeda561e' accepted by handler +0ms
  zigbee-herdsman:controller:log Not interviewing '0x000b57fffeda561e', completed 'undefined', in progress 'true' +0ms
  serialport/stream _read reading { start: 846, toRead: 64690 } +1ms
  serialport/binding-abstract read +1ms
  serialport/bindings/unixRead Starting read +1ms
  serialport/bindings/unixRead waiting for readable because of code: EAGAIN +0ms
  serialport/bindings/poller Polling for "readable" +1ms
  serialport/bindings/poller received "readable" +58ms
  serialport/binding-abstract read +58ms
  serialport/bindings/unixRead Starting read +58ms
  serialport/bindings/unixRead Finished read { bytesRead: 18,
  buffer:
   <Buffer fe 0e 61 02 02 00 02 06 03 9b 15 34 01 02 00 00 00 00 d1 fe 03 61 08 00 01 55 3e fe 03 61 08 00 01 55 3e fe 06 61 08 00 04 00 08 00 00 63 fe 03 61 08 ... > } bytes +0ms
  serialport/stream binding.read finished { bytesRead: 18 } +58ms
  zigbee-herdsman:adapter:zStack:unpi:parser <-- [254,13,69,193,75,106,75,106,30,86,218,254,255,87,11,0,142,200] +59ms
  zigbee-herdsman:adapter:zStack:unpi:parser --- parseNext [254,13,69,193,75,106,75,106,30,86,218,254,255,87,11,0,142,200] +0ms
  zigbee-herdsman:adapter:zStack:unpi:parser --> parsed 13 - 2 - 5 - 193 - [75,106,75,106,30,86,218,254,255,87,11,0,142] - 200 +0ms
  zigbee-herdsman:adapter:zStack:znp:AREQ <-- ZDO - endDeviceAnnceInd - {"srcaddr":27211,"nwkaddr":27211,"ieeeaddr":"0x000b57fffeda561e","capabilities":142} +59ms
  zigbee-herdsman:controller:log Device announce '0x000b57fffeda561e' +59ms
zigbee2mqtt:debug 2019-11-23 12:13:37: Device 'lamp_overloop' announced itself
winston:file written true false
  zigbee-herdsman:adapter:zStack:unpi:parser --- parseNext [] +1ms
winston:file logged 106607 debug 2019-11-23 12:13:37: Device 'lamp_overloop' announced itself

  serialport/stream _read reading { start: 864, toRead: 64672 } +2ms
  serialport/binding-abstract read +2ms
  serialport/bindings/unixRead Starting read +2ms
  serialport/bindings/unixRead waiting for readable because of code: EAGAIN +0ms
  serialport/bindings/poller Polling for "readable" +2ms
  zigbee-herdsman:controller:device Interview - first node descriptor request failed for '0x000b57fffeda561e', retrying... +10s
  zigbee-herdsman:adapter:zStack:znp:SREQ --> ZDO - nodeDescReq - {"dstaddr":27211,"nwkaddrofinterest":27211} +10s
  zigbee-herdsman:adapter:zStack:unpi:writer --> frame [254,4,37,2,75,106,75,106,35] +10s
  serialport/stream _write 9 bytes of data +4s
  serialport/binding-abstract write 9 bytes +4s
  serialport/bindings/unixWrite Starting write 9 bytes offset 0 bytesToWrite 9 +10s
  serialport/bindings/unixWrite write returned: wrote 9 bytes +0ms
  serialport/bindings/unixWrite Finished writing 9 bytes +0ms
  serialport/stream binding.write write finished +0ms
  serialport/bindings/poller received "readable" +4s
  serialport/binding-abstract read +10ms
  serialport/bindings/unixRead Starting read +4s
  serialport/bindings/unixRead Finished read { bytesRead: 6,
  buffer:
   <Buffer fe 0e 61 02 02 00 02 06 03 9b 15 34 01 02 00 00 00 00 d1 fe 03 61 08 00 01 55 3e fe 03 61 08 00 01 55 3e fe 06 61 08 00 04 00 08 00 00 63 fe 03 61 08 ... > } bytes +0ms
  serialport/stream binding.read finished { bytesRead: 6 } +10ms
  zigbee-herdsman:adapter:zStack:unpi:parser <-- [254,1,101,2,0,102] +4s
  zigbee-herdsman:adapter:zStack:unpi:parser --- parseNext [254,1,101,2,0,102] +0ms
  zigbee-herdsman:adapter:zStack:unpi:parser --> parsed 1 - 3 - 5 - 2 - [0] - 102 +0ms
  zigbee-herdsman:adapter:zStack:znp:SRSP <-- ZDO - nodeDescReq - {"status":0} +10s
  zigbee-herdsman:adapter:zStack:unpi:parser --- parseNext [] +0ms
  serialport/stream _read reading { start: 870, toRead: 64666 } +1ms
  serialport/binding-abstract read +1ms
  serialport/bindings/unixRead Starting read +1ms
  serialport/bindings/unixRead waiting for readable because of code: EAGAIN +0ms
  serialport/bindings/poller Polling for "readable" +1ms
  zigbee-herdsman:controller:device Interview - failed for device '0x000b57fffeda561e' with error 'Error: AREQ - ZDO - nodeDescRsp after 10000ms
  zigbee-herdsman:controller:device     at Timeout.object.timer.setTimeout [as _onTimeout] (/srv/zigbee2mqtt/node_modules/zigbee-herdsman/dist/utils/waitress.js:44:24)
  zigbee-herdsman:controller:device     at ontimeout (timers.js:436:11)
  zigbee-herdsman:controller:device     at tryOnTimeout (timers.js:300:5)
  zigbee-herdsman:controller:device     at listOnTimeout (timers.js:263:5)
  zigbee-herdsman:controller:device     at Timer.processTimers (timers.js:223:10)' +10s
  zigbee-herdsman:controller:error Interview failed for '0x000b57fffeda561e with error 'Error: AREQ - ZDO - nodeDescRsp after 10000ms' +0ms
zigbee2mqtt:error 2019-11-23 12:13:51: Failed to interview 'lamp_overloop', device has not successfully been paired
winston:file written true false
zigbee2mqtt:info  2019-11-23 12:13:51: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"pairing","message":"interview_failed","meta":{"friendly_name":"lamp_overloop"}}'
winston:file written true false
winston:file logged 106711 error 2019-11-23 12:13:51: Failed to interview 'lamp_overloop', device has not successfully been paired

winston:file logged 106883 info  2019-11-23 12:13:51: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"pairing","message":"interview_failed","meta":{"friendly_name":"lamp_over
loop"}}'
syphernl picture syphernl on 23 Nov 2019

Getting exactly the same error messages with three Tradfri bulbs here, while a fourth paired without any issues. All had previously been connected as part of a Hassio install, using the same Zigbee dongle. Have tried the reset procedure suggested above, and it made no difference to the results

The paired one is an LED1545G12 (with white temperature control), and at least one of the others is the model without white temperature - I don't know if this could be affecting the process in some way?

mpettitt picture mpettitt on 23 Nov 2019

I think the problem depends on how the bulb is being reset, it seems to make a difference e.g. if the on/off's are shorter/longer. I hope I can soon solve https://github.com/Koenkk/zigbee2mqtt/issues/2396 for IKEA devices, this would provide a much easier and reliable reset procedure.

Koenkk picture Koenkk on 25 Nov 2019

I'm not convinced about the reset process being the problem here - the process which works reliably under 0.6.0 fails under 0.7.1, even with the same devices being used. I've also reset IKEA bulbs using a Hue Remote, and again, works for 0.6.0, fails for 0.7.1.

I could potentially see it being an issue with a specific firmware version of the bulbs, but I'm not sure how to verify what version they are on without digging out the hub.

mpettitt picture mpettitt on 26 Nov 2019
👍1

@mpettitt the only difference I can think of right now is that shepherd tries to query the node descriptor more times. zigbee-herdsman tries it twice, logic can be found here: https://github.com/Koenkk/zigbee-herdsman/blob/master/src/controller/model/device.ts#L321

Let me know if you are comfortable in changing this, otherwise please post your node_modules/zigbee-herdsman/dist/controller/model/device.js file.

Koenkk picture Koenkk on 26 Nov 2019

I've reverted to 1.6.0 for the moment, for domestic harmony reasons (e.g. wife getting annoyed with lights that were misbehaving or couldn't be controlled), so that file will be whatever was in the 1.6.0 Docker release - I've not changed it at all. (Obviously, I typoed with the version numbers here - all above should be 1.7.1 rather than 0.7.1...) From looking at changelogs, it may not even exist in that version!

I'm guessing that using the Hue remote reset method is equivalent to the Touchlink process? It seems more reliable than the on-off method, although not as convenient if you have high ceilings.

mpettitt picture mpettitt on 26 Nov 2019

@mpettitt yes it is the same as the hue dimmer switch reset method.

Koenkk picture Koenkk on 26 Nov 2019

Any news here? I tried everything, reset with on/offs, reset with Hue dimmer, nothing works. Still the same error in interview 😞 I''d be glad to send some logs or anything which could help 🙏

janmisar picture janmisar on 14 Dec 2019

I have the same problem, and after spending more than an hour with my bulb, i simply took the power, and went to bed.

I tried the tips, which are mentioned here, and multiple other places - but it's still an issue. I can't get it to pair successfully.

So, next step for me, will be to update all my IKEA bulbs on the IKEA Gateway. Hereafter, i'll update my ZigBee hardware, add a router (which should arrive, in a few days), and update my docker.

I don't think it will solve all my problems, however, hopefully it help out some of the issues. I would also like to give the "group"-function a try, which arn't an option with my current firmware (on the ZigBee hardware).

If i can help with logs or anything else, i would be happy to do that :-)

_... Cause.. After removing all IKEA bulbs from the Zigbee network, updating them with the IKEA Gateway, and trying to put them back in my main Zigbee-network, i really hope that it will work (o: Else, i'll be in big trouble..._

And oh, i'll also grap one of the IKEA switches, which hopefully will make it a bit easier..

exetico picture exetico on 15 Dec 2019

You can try pairing it with the latest zigbee2mqtt dev branch (it might fix the pairing issues as more attempts are done there).

Koenkk picture Koenkk on 15 Dec 2019
👍1

Thanks for the tip, @Koenkk ! I'll buy one of the buttons from IKEA, and give a single bulb a try. If the pairing goes smoothly, i'll fix the rest of them If not, i gues i need to rethink what to do (regarding the firmware update for the bulbs).

I have a good amount of bulbs, so i need to have at least some of them working. Softbuttons is mounted on top of the switches, so going manually, will be a pain :D

I'm still not quite sure about which firmware i should go with for the ZigBee USB-device, itself. If i should just use the lastest one, or what? However, i don't think it's a good idea to put that question here, now that the main issue/discussion is about the IKEA paring-process.

exetico picture exetico on 15 Dec 2019

You can try pairing it with the latest zigbee2mqtt dev branch (it might fix the pairing issues as more attempts are done there).

I installed update 1.8.0, which is based on latest dev branch afaik and I get still the same error 😞 The only difference is that it takes longer to fail. Before update it failed after few seconds, now it takes almost a minute - I guess it's caused by more trials as you described.
It's really frustrating... Can I help in any way?

janmisar picture janmisar on 16 Dec 2019

@janmisar it is really strange that in your case nothing works, even the touchlink factory reset. Did this bulb ever manage to pair successfully with zigbee2mqtt? Are any other zigbee network running or perhaps it could be interference? Did you connect your CC2531 through an usb extension cable?

Koenkk picture Koenkk on 17 Dec 2019
  1. It's brand new FLOALT panel and it has not been paired with anything yet.
  2. I have one led strip connected to Hue bridge (because of sync with philips ambilight tv) so I suppose it is other zigbee network.
  3. Yes, I have my CC2531 connected with USB extension but I have never had any problem with this. I paired everything smoothly few months ago even with ext cable 🤷‍♂

I will definitely try to turn off Hue bridge to avoid possible interference. And another possible problem could be that my CC2531 is pretty far away from floalt but again... my old floalt is even further and it worked anyway. Could this be a problem?

janmisar picture janmisar on 17 Dec 2019

OK, there's definitely something wrong with my floalt 😞 I also have another new one which I didn't even try to pair when first one didn't work... I tried it now and it paired in a second, just works like a charm 🧙‍♂️ The first floalt still without success, so I will try it with Hue or I will just return it to Ikea.

So at least from my point of view, issue is solved, thank you!

janmisar picture janmisar on 17 Dec 2019
👍1

_I just want to make a quick follow up._

My bulb which wouldn't do anything, is now paired again :+1:

I'm on the latest docker branch. But i've also updated the bulb itself.

Everything went smoothly, after two resets (i don't think it was close enough the first time).

Next step for me, is to:

  • Grap the rest of the IKEA bulbs
  • Update them with the IKEA Gateway
  • Pair them again

However, i'm also going to update the firmware on the zigbee-coordinator, itself. But i'm not sure if the public link is the best firmware to go with CC2531_DEFAULT_20190608.zip? Of if i should try out, something else than that? :-)

exetico picture exetico on 30 Dec 2019

OK, there's definitely something wrong with my floalt 😞 I also have another new one which I didn't even try to pair when first one didn't work... I tried it now and it paired in a second, just works like a charm 🧙‍♂️ The first floalt still without success, so I will try it with Hue or I will just return it to Ikea.

So at least from my point of view, issue is solved, thank you!

Before returning my floalt as broken I tried @Koenkk advice to turn off all other zigbee devices and it works - all my floalts are paired 🎉 Thanks again, I hope it will help to the others some time 🙌

janmisar picture janmisar on 30 Dec 2019

I had the same problem as mentioned and couldn't get the bulb (LED1545G12) to connect. Tried the method with slow on/off and connected to a ikea remote before connecting to zigbee2mqtt again but all didn't work.
The solution in the end was using the experimental feature touchlink reset as mentioned here: #2396 . The bulb reset in a matter of seconds and reconnected immediatly.

ikbenfrank picture ikbenfrank on 24 Jan 2020

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.

stale[bot] picture stale[bot] on 24 Mar 2020

For me power-cycle was the only option that worked :) Not sure if I have the latest firmware, but getting the stick out to re-flash it is not an option atm ;)

fss picture fss on 13 May 2020
Was this page helpful?
0 / 5 - 0 ratings

Related issues

andreasbrett picture andreasbrett  ·  3Comments
rm2kdev picture rm2kdev  ·  3Comments
jwilling picture jwilling  ·  4Comments
ophilips picture ophilips  ·  4Comments
pepp86 picture pepp86  ·  4Comments