Koenkk / zigbee2mqtt

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

SNZB-02 fails to send temperature msTemperatureMeasurement failed (AREQ - ZDO - bindRsp after 10000ms) #8971

Closed tvrulesme closed 2 years ago

tvrulesme commented 3 years ago

Debug info

Zigbee2MQTT version: version 1.21.2 (commit #44922120) Adapter hardware: CC2531 Adapter firmware version: CC2531_DEFAULT_20201127

Supported device SNZB-02 pairs successfully but shows the following error when it attempts to broadcast a temperature reading Zigbee2MQTT:error 2021-10-03 10:23:10: Configure failed: Error: Bind 0x00124b0022cf704d/1 msTemperatureMeasurement from '0x00124b00193691c1/1' failed (AREQ - ZDO - bindRsp after 10000ms)

configuration.yaml:

homeassistant: false
permit_join: true
mqtt:
  base_topic: zigbee2mqtt
  server: mqtt://192.168.0.2
  user: mqtt_user
  password: Penguin1
serial:
  port: /dev/ttyACM0
devices:
  '0x00124b0022cf704d':
    friendly_name: '01-humidity'
    retain: true

logs:

Zigbee2MQTT:info  2021-10-03 10:12:49: Starting Zigbee2MQTT version 1.21.2 (commit #44922120)
Zigbee2MQTT:info  2021-10-03 10:12:49: Starting zigbee-herdsman (0.13.149)
Zigbee2MQTT:info  2021-10-03 10:12:58: zigbee-herdsman started (restored)
Zigbee2MQTT:info  2021-10-03 10:12:58: Coordinator firmware version: '{"meta":{"maintrel":3,"majorrel":2,"minorrel":6,"product":0,"revision":20201127,"transportrev":2},"type":"zStack12"}'
Zigbee2MQTT:info  2021-10-03 10:12:58: Currently 0 devices are joined:
.......

info  2021-10-03 10:18:39: Device '0x00124b0022cf704d' joined
info  2021-10-03 10:18:39: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0x00124b0022cf704d","ieee_address":"0x00124b0022cf704d"},"type":"device_joined"}'
info  2021-10-03 10:18:39: Starting interview of '0x00124b0022cf704d'
info  2021-10-03 10:18:39: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0x00124b0022cf704d","ieee_address":"0x00124b0022cf704d","status":"started"},"type":"device_interview"}'
info  2021-10-03 10:18:39: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":{"friendly_name":"0x00124b0022cf704d"},"type":"device_connected"}'
info  2021-10-03 10:18:39: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"interview_started","meta":{"friendly_name":"0x00124b0022cf704d"},"type":"pairing"}'
info  2021-10-03 10:18:40: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0x00124b0022cf704d","ieee_address":"0x00124b0022cf704d"},"type":"device_announce"}'
info  2021-10-03 10:18:40: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"announce","meta":{"friendly_name":"0x00124b0022cf704d"},"type":"device_announced"}'
info  2021-10-03 10:18:40: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":[],"type":"groups"}'
info  2021-10-03 10:18:40: MQTT publish: topic 'zigbee2mqtt/bridge/config/devices', payload '[{"dateCode":"20201127","friendly_name":"Coordinator","ieeeAddr":"0x00124b00193691c1","lastSeen":1633252720100,"networkAddress":0,"softwareBuildID":"zStack12","type":"Coordinator"},{"description":"-","friendly_name":"0x00124b0022cf704d","ieeeAddr":"0x00124b0022cf704d","lastSeen":1633252720050,"networkAddress":59037,"type":"Unknown","vendor":"-"}]'
info  2021-10-03 10:18:40: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":[{"dateCode":"20201127","friendly_name":"Coordinator","ieeeAddr":"0x00124b00193691c1","lastSeen":1633252720166,"networkAddress":0,"softwareBuildID":"zStack12","type":"Coordinator"},{"description":"-","friendly_name":"0x00124b0022cf704d","ieeeAddr":"0x00124b0022cf704d","lastSeen":1633252720050,"manufacturerID":0,"networkAddress":59037,"type":"EndDevice","vendor":"-"}],"type":"devices"}'
info  2021-10-03 10:18:45: Successfully interviewed '0x00124b0022cf704d', device has successfully been paired
info  2021-10-03 10:18:45: Device '0x00124b0022cf704d' is supported, identified as: SONOFF Temperature and humidity sensor (SNZB-02)
info  2021-10-03 10:18:45: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"definition":{"description":"Temperature and humidity sensor","exposes":[{"access":1,"description":"Remaining battery in %","name":"battery","property":"battery","type":"numeric","unit":"%","value_max":100,"value_min":0},{"access":1,"description":"Measured temperature value","name":"temperature","property":"temperature","type":"numeric","unit":"°C"},{"access":1,"description":"Measured relative humidity","name":"humidity","property":"humidity","type":"numeric","unit":"%"},{"access":1,"description":"Voltage of the battery in millivolts","name":"voltage","property":"voltage","type":"numeric","unit":"mV"},{"access":1,"description":"Link quality (signal strength)","name":"linkquality","property":"linkquality","type":"numeric","unit":"lqi","value_max":255,"value_min":0}],"model":"SNZB-02","supports_ota":false,"vendor":"SONOFF"},"friendly_name":"0x00124b0022cf704d","ieee_address":"0x00124b0022cf704d","status":"successful","supported":true},"type":"device_interview"}'
info  2021-10-03 10:18:45: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"interview_successful","meta":{"description":"Temperature and humidity sensor","friendly_name":"0x00124b0022cf704d","model":"SNZB-02","supported":true,"vendor":"SONOFF"},"type":"pairing"}'
info  2021-10-03 10:18:45: Changed device specific options of '0x00124b0022cf704d' ({"retain":true})

......

Zigbee2MQTT:info  2021-10-03 10:23:00: Device '01-humidity' joined
Zigbee2MQTT:info  2021-10-03 10:23:00: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"01-humidity","ieee_address":"0x00124b0022cf704d"},"type":"device_joined"}'
Zigbee2MQTT:info  2021-10-03 10:23:00: Configuring '01-humidity'
Zigbee2MQTT:info  2021-10-03 10:23:00: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":{"friendly_name":"01-humidity"},"type":"device_connected"}'
Zigbee2MQTT:info  2021-10-03 10:23:00: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"01-humidity","ieee_address":"0x00124b0022cf704d"},"type":"device_announce"}'
Zigbee2MQTT:info  2021-10-03 10:23:00: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"announce","meta":{"friendly_name":"01-humidity"},"type":"device_announced"}'
Zigbee2MQTT:info  2021-10-03 10:23:00: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":[],"type":"groups"}'
Zigbee2MQTT:info  2021-10-03 10:23:00: MQTT publish: topic 'zigbee2mqtt/bridge/config/devices', payload '[{"dateCode":"20201127","friendly_name":"Coordinator","ieeeAddr":"0x00124b00193691c1","lastSeen":1633252980641,"networkAddress":0,"softwareBuildID":"zStack12","type":"Coordinator"},{"dateCode":"20201026","description":"Temperature and humidity sensor","friendly_name":"01-humidity","hardwareVersion":1,"ieeeAddr":"0x00124b0022cf704d","lastSeen":1633252980584,"manufacturerID":0,"manufacturerName":"eWeLink","model":"SNZB-02","modelID":"TH01","networkAddress":35923,"powerSource":"Battery","type":"EndDevice","vendor":"SONOFF"}]'
Zigbee2MQTT:info  2021-10-03 10:23:00: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":[{"dateCode":"20201127","friendly_name":"Coordinator","ieeeAddr":"0x00124b00193691c1","lastSeen":1633252980659,"networkAddress":0,"softwareBuildID":"zStack12","type":"Coordinator"},{"dateCode":"20201026","description":"Temperature and humidity sensor","friendly_name":"01-humidity","hardwareVersion":1,"ieeeAddr":"0x00124b0022cf704d","lastSeen":1633252980584,"manufacturerID":0,"manufacturerName":"eWeLink","model":"SNZB-02","modelID":"TH01","networkAddress":35923,"powerSource":"Battery","type":"EndDevice","vendor":"SONOFF"}],"type":"devices"}'
Zigbee2MQTT:error 2021-10-03 10:23:10: Configure failed: Error: Bind 0x00124b0022cf704d/1 msTemperatureMeasurement from '0x00124b00193691c1/1' failed (AREQ - ZDO - bindRsp after 10000ms)
Zigbee2MQTT:info  2021-10-03 10:23:10: Successfully configured '01-humidity'
Zigbee2MQTT:info  2021-10-03 10:27:01: MQTT publish: topic 'zigbee2mqtt/bridge/state', payload 'offline'
qukla1000 commented 3 years ago

I have the same problem: https://github.com/Koenkk/zigbee2mqtt/issues/8979

yang360 commented 3 years ago

Same problem here as well.

sjorge commented 3 years ago

Make sure to force remove the failed pairing before trying again, I have the best success with removing the battery and putting it back in, instead of holding the button.

tvrulesme commented 3 years ago

Make sure to force remove the failed pairing before trying again, I have the best success with removing the battery and putting it back in, instead of holding the button.

Yes I have done this multiple times as well as deleting my database file and state files. Also tried with the dev branch with the same result

qukla1000 commented 3 years ago

Me too. I tired add three new sensors and the result was the same all the time. A tried add multiple times also with force removing. I also deleted datatbase and reinstall zigbe2mqtt. I tired reflash CC26X2R1 but it didn't help. Also tried change USB cable to another. I also added some tuya motion sensor - that works without any problem. The problem exists only with Sonoff SNZB-02.

sjorge commented 3 years ago

Are you pairing through a router or at the coordinator? I have a zzhp-lite prototype and all my pairings of my SNZB-02's were done through routers.

tvrulesme commented 3 years ago

Are you pairing through a router or at the coordinator? I have a zzhp-lite prototype and all my pairings of my SNZB-02's were done through routers.

Assuming through coordinator. Is zzhp-lite hardware?

tvrulesme commented 3 years ago

Are you pairing through a router or at the coordinator? I have a zzhp-lite prototype and all my pairings of my SNZB-02's were done through routers.

So my hardware is listed above it's pretty much the same as this: https://uk.rs-online.com/web/p/communication-wireless-development-tools/1977102/?cm_mmc=UK-PLA-DS3A-_-google-_-CSS_UK_EN_Raspberry_Pi_%26_Arduino_%26_Development_Tools_Whoop-_-Communication+%26+Wireless+Development+Tools_Whoop-_-1977102&matchtype=&pla-306759658968&gclid=CjwKCAjwzOqKBhAWEiwArQGwaEw5EcmHj-D38MUQm1z3uc8DZWEatV99cjjqob-V-9l6ZEpbq44ZjhoC4YAQAvD_BwE&gclsrc=aw.ds

sjorge commented 3 years ago

Assuming through coordinator. Is zzhp-lite hardware?

Yeah zzh-lite is a CC2652P based coordinator, can you try pairing through a router instead? Most of my bulbs are Trådfri bulbs and a few Hue/Innr so I don't think the manufacturer should matter.

tvrulesme commented 3 years ago

Assuming through coordinator. Is zzhp-lite hardware?

Yeah zzh-lite is a CC2652P based coordinator, can you try pairing through a router instead? Most of my bulbs are Trådfri bulbs and a few Hue/Innr so I don't think the manufacturer should matter.

OK now I am confused. So you mean take the SNZB-02 away from the CC2531 and try and use my wifi router?

qukla1000 commented 3 years ago

Are you pairing through a router or at the coordinator? I have a zzhp-lite prototype and all my pairings of my SNZB-02's were done through routers.

I have only coordinator in my network.

qukla1000 commented 3 years ago

Assuming through coordinator. Is zzhp-lite hardware?

Yeah zzh-lite is a CC2652P based coordinator, can you try pairing through a router instead? Most of my bulbs are Trådfri bulbs and a few Hue/Innr so I don't think the manufacturer should matter.

OK now I am confused. So you mean take the SNZB-02 away from the CC2531 and try and use my wifi router?

Not wifi router. Zigbee router - if you have.

tvrulesme commented 3 years ago

Assuming through coordinator. Is zzhp-lite hardware?

Yeah zzh-lite is a CC2652P based coordinator, can you try pairing through a router instead? Most of my bulbs are Trådfri bulbs and a few Hue/Innr so I don't think the manufacturer should matter.

OK now I am confused. So you mean take the SNZB-02 away from the CC2531 and try and use my wifi router?

Not wifi router. Zigbee router - if you have.

Ah no, I don't sorry

sjorge commented 3 years ago

OK now I am confused. So you mean take the SNZB-02 away from the CC2531 and try and use my wifi router?

Not wifi router. Zigbee router - if you have.

Yes, zigbee router... usually something that always has power like a bulb.

sjorge commented 3 years ago

I have only coordinator in my network.

Ah no, I don't sorry

Interesting, both of you don't have any routers in the network, I wonder if somehow due to this message don't get buffered as there are no routers to hold them.

@Koenkk unless I am mistaken that is how it usually works right, also why the IKEA blinds need the repeater or another router for the remote to be able to talk to the blinds... I wonder if that is an issue here too.

qukla1000 commented 3 years ago

I have only coordinator in my network.

Ah no, I don't sorry

Interesting, both of you don't have any routers in the network, I wonder if somehow due to this message don't get buffered as there are no routers to hold them.

@Koenkk unless I am mistaken that is how it usually works right, also why the IKEA blinds need the repeater or another router for the remote to be able to talk to the blinds... I wonder if that is an issue here too.

I also have other installation in other house. But zigbee2mqtt version is 1.18.1-1. There is also one coordinator, other sensors and few SNZB-02. It works without any problem. Joining and reporting states form sensors works seamlessly. It also works with CC26X2R1 bout i don't know with version of software.

tvrulesme commented 3 years ago

I have only coordinator in my network.

Ah no, I don't sorry

Interesting, both of you don't have any routers in the network, I wonder if somehow due to this message don't get buffered as there are no routers to hold them. @Koenkk unless I am mistaken that is how it usually works right, also why the IKEA blinds need the repeater or another router for the remote to be able to talk to the blinds... I wonder if that is an issue here too.

I also have other installation in other house. But zigbee2mqtt version is 1.18.1-1. There is also one coordinator, other sensors and few SNZB-02. It works without any problem. Joining and reporting states form sensors works seamlessly. It also works with CC26X2R1 bout i don't know with version of software.

Went through some old hardware boxes and found a switch which is acting as a router. So cleaned out database, added switch, added SNZB-02 and no error messages BUT I do not see any data in the logs either. How often does yours generally publish?

tvrulesme commented 3 years ago

Right, battery in and out and I am seeing data :)

Zigbee2MQTT:info 2021-10-04 13:42:11: MQTT published: topic 'zigbee2mqtt/humidity', payload '{"linkquality":89,"voltage":2900}' Zigbee2MQTT:info 2021-10-04 13:42:12: MQTT published: topic 'zigbee2mqtt/humidity', payload '{"battery":85,"linkquality":89,"voltage":2900}' Zigbee2MQTT:info 2021-10-04 13:42:12: Successfully configured 'humidity' Zigbee2MQTT:info 2021-10-04 13:42:17: MQTT published: topic 'zigbee2mqtt/humidity', payload '{"battery":85,"linkquality":89,"temperature":23.74,"voltage":2900}' Zigbee2MQTT:info 2021-10-04 13:42:17: MQTT published: topic 'zigbee2mqtt/humidity', payload '{"battery":85,"humidity":81.51,"linkquality":89,"temperature":23.74,"voltage":2900}' Zigbee2MQTT:info 2021-10-04 13:42:27: MQTT published: topic 'zigbee2mqtt/humidity', payload '{"battery":85,"humidity":75.94,"linkquality":89,"temperature":23.74,"voltage":2900}' Zigbee2MQTT:info 2021-10-04 13:42:37: MQTT published: topic 'zigbee2mqtt/humidity', payload '{"battery":85,"humidity":68.46,"linkquality":102,"temperature":23.74,"voltage":2900}' Zigbee2MQTT:info 2021-10-04 13:42:47: MQTT published: topic 'zigbee2mqtt/humidity', payload '{"battery":85,"humidity":64.67,"linkquality":92,"temperature":23.74,"voltage":2900}' Zigbee2MQTT:info 2021-10-04 13:42:58: MQTT published: topic 'zigbee2mqtt/humidity', payload '{"battery":85,"humidity":63.18,"linkquality":99,"temperature":23.74,"voltage":2900}'

qukla1000 commented 3 years ago

I have only coordinator in my network.

Ah no, I don't sorry

Interesting, both of you don't have any routers in the network, I wonder if somehow due to this message don't get buffered as there are no routers to hold them. @Koenkk unless I am mistaken that is how it usually works right, also why the IKEA blinds need the repeater or another router for the remote to be able to talk to the blinds... I wonder if that is an issue here too.

I also have other installation in other house. But zigbee2mqtt version is 1.18.1-1. There is also one coordinator, other sensors and few SNZB-02. It works without any problem. Joining and reporting states form sensors works seamlessly. It also works with CC26X2R1 bout i don't know with version of software.

Went through some old hardware boxes and found a switch which is acting as a router. So cleaned out database, added switch, added SNZB-02 and no error messages BUT I do not see any data in the logs either. How often does yours generally publish?

So it looks similar. I can add sonoff, it shows in zigbe2mqtt but sensor don't publish any status even after pushing button. Of course while i adding this sensor i have error like: sTemperatureMeasurement failed (AREQ - ZDO - bindRsp after 10000ms) Not always but most of the time.

sjorge commented 3 years ago

@tvrulesme certainly interesting, so a router in the mesh does seem to help. Mine don't immediately send data either, it goes something like this

  1. force remove device
  2. remove battery
  3. enable join via a bulb in the room with the sensor
  4. insert battery
  5. (check if the red led blinked, if not, hold the button until it does)
  6. wait for z2m to pair successfully
  7. (timeout error, back to 1.)

Then I think around ~15 min later it starts sending data, I think that might be some build in default when it first wakes up. Then it seems to follow whatever is configured in the reporting. Removing the battery and inserting it again once it is paired does seem to immediately have it publish battery and voltage, and the rest follow shortly after.

Edit: looking at the default reporting, it's probably ~30min as that is the first time it would forcefully be triggered unless there was a change in temp/humidity.

So it looks similar. I can add sonoff, it shows in zigbe2mqtt but sensor don't publish any status even after pushing button. Of course while i adding this sensor i have error like: sTemperatureMeasurement failed (AREQ - ZDO - bindRsp after 10000ms) Not always but most of the time.

I'm guessing it will never send temperature if msTemperatureMeasurement reporting setup gave a timeout. I think that's also the first one it tries, so it probably never got around to setting up the others either, not having any data would make sense then.

I never had luck manually configuring the reporting on these devices, but you could also try that.

image

This is what the default reporting looks like, probably need to remove battery, insert battery, setup reporting.

Koenkk commented 3 years ago

@tvrulesme if I understand correctly, the device works fine (temperature etc is updated), the only error here is the configure failing?

@sjorge if that is the case we can add a try/catch to the configure (to suppress this error) as it seems not all devices need this.

qukla1000 commented 3 years ago

@tvrulesme if I understand correctly, the device works fine (temperature etc is updated), the only error here is the configure failing?

@sjorge if that is the case we can add a try/catch to the configure (to suppress this error) as it seems not all devices need this.

@Koenkk For me device don't work but shows in zigbe2mqtt. Device don't raport their state. Error shows most of the time but not always. Pushing button on sensor don't update status. Device also isn't reporting its state after while.

tvrulesme commented 3 years ago

@tvrulesme if I understand correctly, the device works fine (temperature etc is updated), the only error here is the configure failing?

Yes this is correct @Koenkk, works with a router but not stand alone

Koenkk commented 3 years ago

@tvrulesme any chance you could provide a sniff when pairing via both router (working situation) and non-working situation (coordinator). https://www.zigbee2mqtt.io/how_tos/how_to_sniff_zigbee_traffic.html

tvrulesme commented 3 years ago

@tvrulesme any chance you could provide a sniff when pairing via both router (working situation) and non-working situation (coordinator). https://www.zigbee2mqtt.io/how_tos/how_to_sniff_zigbee_traffic.html

Yeah absolutely. Will get on it tomorrow

takthetank commented 3 years ago

I have the same problem with SNZB-02 sensors, while other devices work fine.

tvrulesme commented 3 years ago

@tvrulesme any chance you could provide a sniff when pairing via both router (working situation) and non-working situation (coordinator). https://www.zigbee2mqtt.io/how_tos/how_to_sniff_zigbee_traffic.html

Really sorry @Koenkk I got stuck at this point

pi@raspberrypi:~/flash_cc2531 $ /snap/bin/cc-tool.run -e -w sniffer_fw_cc2531.hex 
  CC Debugger device not found

This is on a raspberry pi. For the record I don't have a CC debugger.

tvrulesme commented 3 years ago

Brief update. Sadly the resolution above does not appear to be consistent. Tried a complete clean down removing all devices, adding the switch first followed by the SNZB-02 and again I see this error:

Zigbee2MQTT:error 2021-10-05 11:25:59: Configure failed: Error: Bind 0x00124b0022cf704d/1 msTemperatureMeasurement from '0x00124b00193691c1/242' failed (AREQ - ZDO - bindRsp after 10000ms) Zigbee2MQTT:info 2021-10-05 11:25:59: Successfully configured '0x00124b0022cf704d'

Please shout if there is anything useful I can send through

sjorge commented 3 years ago

You only enabled joining through the switch right?

tvrulesme commented 3 years ago

You only enabled joining through the switch right?

Sorry @sjorge how would I do that?

sjorge commented 3 years ago

Easiest is using the frontend and hitting the V icon next to Permit join (All) then selecting the switch:

image

That should prevent the sensor from trying to use the coordinator.

tvrulesme commented 3 years ago

That should prevent the sensor from trying to use the coordinator. Screenshot 2021-10-05 at 11 54 56 Only seeing Disable join. Is that right?

tvrulesme commented 3 years ago

Screenshot 2021-10-05 at 12 02 11 Lined to coordinator. So adding it to router before must have just been luck

sjorge commented 3 years ago

Might have been because joining was still enabled from before you selected the switch?

tvrulesme commented 3 years ago

@sjorge have tried everything I can think of and I can't get it to join the switch instead of composer.

tvrulesme commented 3 years ago

Ok, finally got it to join the router (by physically moving both a long way)

Screenshot 2021-10-05 at 13 35 01

But the error message persists

Zigbee2MQTT:error 2021-10-05 13:31:59: Configure failed: Error: Bind 0x00124b0022cf704d/1 msTemperatureMeasurement from '0x00124b00193691c1/1' failed (AREQ - ZDO - bindRsp after 10000ms)
Zigbee2MQTT:info  2021-10-05 13:31:59: Successfully configured '0x00124b0022cf704d'
Zigbee2MQTT:info  2021-10-05 13:32:07: Starting network scan (includeRoutes 'false')
Zigbee2MQTT:info  2021-10-05 13:32:09: Network scan finished
sjorge commented 3 years ago

😞 so the earlier successful attempt was just random then

tvrulesme commented 3 years ago

😞 so the earlier successful attempt was just random then

Unfortunately yes. So sorry to raise hopes

mgabetta commented 3 years ago

Same problem here with my new SNZB-02 (I'm trying to add two of them but same error for both), here's the log line:

Configure failed: Error: Bind 0x00124b0023adcfe3/1 msTemperatureMeasurement from '0x00124b0022813510/1' failed (AREQ - ZDO - bindRsp after 10000ms)

I have another SNZB-02 in my network (added months ago) and it works fine.

Koenkk commented 3 years ago

I've ordered the device to further debug this issue.

StandardTheory commented 3 years ago

I'm getting this exact same problem with a Sonoff SNZB-01. Device is picked up but fails to configure:

error 2021-10-06 21:37:02: Failed to configure '0x00124b0022665b19', attempt 1 (Error: Bind 0x00124b0022665b19/1 genOnOff from '0x00212effff0721b6/1' failed (waiting for response TIMEOUT) at DeconzAdapter.bind (/app/node_modules/zigbee-herdsman/src/adapter/deconz/adapter/deconzAdapter.ts:757:19) at Endpoint.bind (/app/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:500:13) at Object.bind (/app/node_modules/zigbee-herdsman-converters/lib/reporting.js:33:9) at Object.configure (/app/nodemodules/zigbee-herdsman-converters/devices/sonoff.js:76:13) at Configure.configure (/app/lib/extension/configure.ts:119:13) at Configure.onMQTTMessage (/app/lib/extension/configure.ts:60:21))

image

I'm using Home Assistant OS on a Pi4 with a Conbee II. If I disable the Zigbee2MQQT addon and fire up the ZHA integration without changing anything else the device pairs fine first time, reports all the states and fires events as expected so I don't think its a hardware issue.

I've flashed the Conbee to the latest firmware (0x26720700) ensured all software is up to date and tried all the suggestions above but can't get it to configure.

takthetank commented 3 years ago

Hi @Koenkk I managed to sniff through windows, please find attached the z2m and sniffing logs. SNZB-02_logs.zip

Please tell me if you need something more!

phobosdigg commented 3 years ago

The same problem with this sensor. The problem appeared after I changed the pan_id to 6755 in the zigbee2mqtt settings due to other problems. Up to this point, the sensors worked fine. What pan_id do you use in the settings zigbee2mqtt?

mgabetta commented 3 years ago

I think the problem is not due to pan_id itself, but to the fact that, after changing pan_id, the devices have to be re-paired: and here you are in the same situation of us.

takthetank commented 3 years ago

I haven't set or changed the pan_id!

grfernandes54 commented 3 years ago

I Tried to add 4 SNZB-02 and have the same problem, all sensors show N/A at the exposes

image

nickmcgill commented 3 years ago

I have just downloaded the latest-dev docker image, and I can now pair the SNZB-02, no errors appear to be logged, but, to get it to report correctly I need to reconfigure it. The reconfiguration must be done before renaming the device. I hope this is of some help.

maxbause commented 3 years ago

Hey guys, I had the same problem: The sensor was connected, but I couldn't get any data out of it.

I've found a sloppy fix, but it worked for me:

  1. Make sure that the sensor is still connected to the bridge
  2. Now open the back of the sensor and remove the button cell battery
  3. In your zigbee2mqtt web interface, force remove the sensor
  4. Take a piece of metal (I used a screwdriver tip) and short out the two battery contacts of the sensor (see attached file)
  5. Now put the battery back in and wait for the sensor to connect 5.1 Note: Don't press the button on the sensor, let it connect by itself

After that, all of my 5 sensors worked perfectly. IMG_8794

degreal commented 3 years ago

@maxbause I can confirm this method works great! I connected 15 sensors with this method. Previously it took about 2 hours retrying 10x per sensor before it connected.

sjorge commented 3 years ago

Given the sensor doesn't leave then doing a normal leave network and we have to use the force one... I wonder if some state stays on the device and that is why it immediately goes to sleep mid interview instead of staying awake for a while like during the initial pairing.