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

tvrulesme · 2021-10-03T09:53:53Z

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'

The text was updated successfully, but these errors were encountered:

qukla1000 · 2021-10-03T14:25:13Z

I have the same problem: #8979

yang360 · 2021-10-04T02:40:01Z

Same problem here as well.

sjorge · 2021-10-04T11:21:02Z

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 · 2021-10-04T11:24:49Z

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 · 2021-10-04T11:46:55Z

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 · 2021-10-04T11:50:22Z

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 · 2021-10-04T11:52:06Z

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 · 2021-10-04T11:55:02Z

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 · 2021-10-04T12:01:42Z

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 · 2021-10-04T12:08:26Z

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 · 2021-10-04T12:09:36Z

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 · 2021-10-04T12:11:26Z

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 · 2021-10-04T12:17:59Z

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 · 2021-10-04T12:18:12Z

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 · 2021-10-04T12:20:15Z

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 · 2021-10-04T12:28:29Z

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 · 2021-10-04T12:38:08Z

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 · 2021-10-04T12:43:19Z

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 · 2021-10-04T12:44:15Z

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 · 2021-10-04T13:14:51Z

@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

force remove device
remove battery
enable join via a bulb in the room with the sensor
insert battery
(check if the red led blinked, if not, hold the button until it does)
wait for z2m to pair successfully
(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.

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

Koenkk · 2021-10-04T15:25:58Z

@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 · 2021-10-04T15:59:28Z

@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 · 2021-10-04T16:10:16Z

@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 · 2021-10-04T19:27:03Z

@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 · 2021-10-04T19:43:49Z

@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 · 2021-10-04T20:17:13Z

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

tvrulesme · 2021-10-05T06:47:00Z

@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 · 2021-10-05T10:37:27Z

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 · 2021-10-05T10:46:23Z

You only enabled joining through the switch right?

jjromannet · 2022-02-15T21:38:33Z

I hit this issue few days ago when tried to setup 3 of my SNZB-02 devices (all purchased as a single order from single supplier). I only had coordinator in my network which is USB stick CC2531.
I read all comments in both issues here but nothing helped - SNZB-02s were only reporting battery level at pairing time and never actually actively send any message to coordinator. I tried hitting reconfigure along with pressing button at various frequencies, force remove devices and add them back, remove battery etc. For this purpose i was using device A & B, device C was only paired once and I did not touch it.

From reading some comments here I concluded that people have more luck if there is router in the network. My another suspicion was that newer firmware (20201026) on SNZB-02 that i have is somehow incompatible. I purchased 2ch tuya switch device that is also acting as router and I gave it another go today.
Today i had a bit more luck (it may be coincidence or indeed adding router to the network helped). Yet device A is not even reporting battery level right now and appears broken in the frontend - my working assumption is that I drain its batter during my tries last week. Device B started to report temperature and battery level (no humidity) only after i successfully reconfigured and set maximum reporting value for temperature to 60 (required frequent button presses).
Device C - that i never tried to reconfigure before (only paired) - Today i only pressed reconfigure with default values T=> min: 5, max: 1800, H => min: 10, max 3600 - then it started to report both T&H

Another issue (not sure if related) is that "Last Seen" is always set to N/A even thought 2 out of 3 devices actually sending data to coordinator.

My set up it to run standalone (without HA) zigbee2mqtt as a docker container with following versions:

Starting Zigbee2MQTT version 1.23.0 (commit #6ea61ba)
Starting zigbee-herdsman (0.14.10)
Coordinator firmware version: '{"meta":{"maintrel":3,"majorrel":2,"minorrel":6,"product":0,"revision":20201127,"transportrev":2},"type":"zStack12"}'

SNZB-02 firmware versions: 20201026
Linux kernel: 5.13.19-4

Attaching extracts from DB for all three devices db-extract.zip

I need to park the project for next two weeks. My next steps:

Test battery and order replacement
Test version 1.21.1
Try to understand what is interview and somehow force two remaining devices to complete it

ndevenish · 2022-02-15T22:04:19Z

Try to understand what is interview and somehow force two remaining devices to complete it

Assuming that it’s not an easily traceable software issue, what would be required to properly diagnose this on the hardware side - sniffing the general packets was mentioned earlier, is that what would be definitive? (Which would presumably require buying a second coordinator and custom flashing)

linker3000 · 2022-02-26T11:27:25Z

I've also downgraded to 1.21.1 and the SNZB-02 has been working solid for a week now.

danieldid · 2022-02-26T15:04:46Z

I'm facing exactly the same issue with 1.21.1 through 1.23.

The error thrown in the logs:
Configure failed: Error: Bind 0x00124b00245ce94c/1 msTemperatureMeasurement from '0x00212effff07710a/1' failed (waiting for response TIMEOUT)

I have two Sonoff SNZB-02 from the same delivery. One is working like a charm. The other one is always having trouble after a couple of days. Usually removing and pairing helped out so far. Unfortunately this doesn't work anymore.

My setup:

zigbee2mqtt@1.23
conbee@0x26660700

I'm running everything in docker on a raspberry pi.

jjromannet · 2022-02-27T16:33:05Z

I downgraded to 1.21.1 and all of my SNZB-02s work now (even without router in the network). At first when i only changed version of image in docker-compose to koenkk/zigbee2mqtt:1.21.1 and restarted with forced build it still was not working.
I deleted all files apart from docker-compose and executed:

docker compose down --remove-orphans
docker compose rm
docker compose up -d

After this I paired all devices again without any issue.

One of the differences i see is that in version 1.21.1 default accuracy for all reading is set to 2 decimal places while in most recent version it was set to no precision point. I wonder whether precision set to 0 may cause SNZB-02 to misbehave.

This would explain why devices were not working after image downgrade - without repairing (during pairing new configuration is send). I will test this hypothesis after i am happy with result of 1.21.1 testing.

@danieldid

zigbee2mqtt@1.23

Can you confirm if your SNZB-02 does not work when you set up version 1.21.1 from scratch?

danieldid · 2022-02-28T11:01:35Z

@jjromannet I can confirm this works with 1.21.1

By the way your temps are pretty hot (no offense! :-)) I'd like to have it cool

As with 1.23 the interview doesn't work and no temp and humidity is delivered

The difference (didn't check the changelogs!) between 1.21.1 and 1.23 is that you can't set the precission of the sensors under Settings (spezifisch) [german].

This is under 1.23

This is under 1.21.1

I'll have a look on this for a couple of days and will be reporting.

danieldid · 2022-03-02T20:45:04Z

Update after 2 days: Everything's running normal.

So it seems that downgrading was the solution or in other words in 1.23 something changed. I guess your thesis is correct @jjromannet. Must've been something with the accuracy. At least this is the only liable difference I can see.

BTW: I'm fairly new to docker and --remove-orphans did only work when using docker-compose up -d --remove-orphans. Should have read the flag first :-/ did reset some things (my complete influxdb datas were dropped).

DarkPako84 · 2022-03-09T20:45:46Z

I have SONOFF SNZB-02 and the @maxbause solution didn't work for me. What I did is:

Enable joining new devices in z2m

Press and hold paring button on Sonoff device

Wait until z2m shows error with configuration

Go to Device section and click yellow reconfigure button next to the Sonoff device

Then device starts reporting data finally.

Finally i have find a great solution!
Thanks!

danieldid · 2022-03-14T21:12:26Z

Post update - with 1.21.1 there's still no problem. Things are running normal.

jjromannet · 2022-03-15T20:58:56Z

@danieldid what do you mean by this? Did you setup your SNZB-02 with 1.21.1 and later upgraded zigbee2mqtt to more recent version - with SNZB-02 devices already paired?

danieldid · 2022-03-15T21:39:05Z

@jjromannet I set up everything with 1.21.1 in a docker environment. Then updated the image to the latest (back then) version 1.23. The problems mentioned here started with that version. I downgraded the docker image to 1.21.1 and started it with docker-compose up -d —remove-orphans (like mentioned previously).

Since then everything works seamlessly.

Can anyone confirm that with the latest version 1.24 this is working properly?

linker3000 · 2022-03-15T21:53:49Z

No 1.24 does not work. I upgraded to 1.21.2 and the sensor still worked, but it stopped after a server reboot. I wanted 1.21.2 for Sonoff mains switch support and I had to revert to 1.21.1 then upgrade to 1.21.2 again.

…

On Tue, 15 Mar 2022, 21:39 Daniel Didusch, ***@***.***> wrote: @jjromannet <https://github.com/jjromannet> I set up everything with 1.21.1 in a docker environment. Then updated the image to the latest (back then) version 1.23. The problems mentioned here started with that version. I downgraded the docker image to 1.21.1 and started it with docker-compose up -d —remove-orphans (like mentioned previously). Since then everything works seamlessly. Can anyone confirm that with the latest version 1.24 this is working properly? — Reply to this email directly, view it on GitHub <#8971 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEUHQXZ4JY7PLERKTB6XAM3VAD7QPANCNFSM5FHNI4WA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you commented.Message ID: ***@***.***>

dsduarte · 2022-03-17T23:21:40Z

I had this problem again...
I removed all my SNZB-02's and started Z2M with the key "avalability = false" on config.yaml and paired again and it was ok!
I removed all my SNZB-02's again and started Z2M with "avalability = true" and paired again. Same error.
Than, at last I removed all my SNZB-02's and started Z2M with "avalability = false" and paired again and it was ok!

I think we can declare "avalability = false" on devices.yaml only for the SNZB-02's.

jjromannet · 2022-03-28T20:59:17Z

I think i will join "give up on SNZB-02" camp. After playing with initial three devices (out of which I though i bricked two) I bought another 2 (so 5 devices in total here). Two new ones join the network without any issues with software version 1.21.1 (no luck with newer versions). After a week one of them stopped reporting any data - by pure guess i bought new CR2450 quality batteries - with their help all of devices (including ones I initially though were broken) started to work properly. Only info I was able to find about original batteries shipped with SNZB-02 device ("Newsun" brand here) are three opinion on popular online store each for 1 star out of 5 - complaining battery dies after a week.

Hint1: If you have any issues - start with new batteries - buy branded ones.

Unfortunately even with new batteries indicators are randomly dying.

PS: I just realized that reading of the sensor is also off. One of them is showing me 25.9 which is simply not possible (actual temp in this room is 22)

matbech · 2022-03-30T08:39:55Z

I'm seeing the same issue (error in log, no data is reported from device) using Zigbee2MQTT version 1.24.0, version 1.22.1 and with the dev branch as the original poster.

Also reconfigure (zigbee2mqtt/bridge/request/device/configure) does not solve my problem. The same error is reported:

info  2022-03-30 08:35:35: Starting Zigbee2MQTT version 1.24.0 (commit #7a2ddf24)
info  2022-03-30 08:35:35: Starting zigbee-herdsman (0.14.20)
info  2022-03-30 08:35:36: zigbee-herdsman started (resumed)
...
info  2022-03-30 08:37:14: Configuring '0x00124b002512211d'
error 2022-03-30 08:37:24: Configure failed: Error: Bind 0x00124b002512211d/1 msTemperatureMeasurement from '0x00124b0022812a65/1' failed (AREQ - ZDO - bindRsp after 10000ms)
info  2022-03-30 08:37:24: Successfully configured '0x00124b002512211d'
info  2022-03-30 08:37:24: MQTT publish: topic 'zigbee2mqtt/bridge/response/device/configure', payload '{"data":{"id":"0x00124b002512211d"},"status":"ok"}'

Update: I can confirm that version 1.21.1 works. No error is reported and the device is reporting data.

@Koenkk Do you think you could take a look at this regression?

Koenkk · 2022-03-30T15:13:24Z

@matbech seem to be a duplicate of #10973 (comment) , already fixed in the dev branch (make sure to repair the device after upgrading). (https://www.zigbee2mqtt.io/advanced/more/switch-to-dev-branch.html)

danieldid · 2022-04-10T15:38:32Z

I can confirm what @Koenkk said - this is fixed at least in latest dev branch. After reconfiguring all of my devices this works like a charm. This shall be closed though.

@matbech and @jjromannet did you tried it with 1.26 (latest) or dev branch?

linker3000 · 2022-04-10T16:13:56Z

I've been running 1.25.0 for about a week and this version seems to have fixed disconnect issues with both my SNZB-02 temperature sensors and Sonoff S26R2ZB smart plugs. Nigel

…

On Sun, 10 Apr 2022, 16:38 Daniel Didusch, ***@***.***> wrote: I can confirm what @Koenkk <https://github.com/Koenkk> said - this is fixed at least in latest dev branch. After reconfiguring all of my devices this works like a charm. This shall be closed though. @matbech <https://github.com/matbech> and @jjromannet <https://github.com/jjromannet> did you tried it with 1.26 (latest) or dev branch? — Reply to this email directly, view it on GitHub <#8971 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEUHQX7IF6KHLWQNKQKY6T3VELYYNANCNFSM5FHNI4WA> . You are receiving this because you commented.Message ID: ***@***.***>

ndevenish · 2022-04-17T17:52:08Z

I've updated to 1.25.0 and it seems to be working fine. I needed to re-pair, reconfiguration failed, but the re-pair worked first time and running smoothly since then.

This also fixed the issues I had (on 1.21.0) with an Ikea Tradfri button, so pleased all around.

Koenkk · 2022-04-17T18:11:59Z

Thanks for confirming all, time to close this.

Notes based on Koenkk/zigbee2mqtt#8971 (comment) and Koenkk/zigbee2mqtt#11273 (comment)

* Add troubleshoot instructions for SONOFF SNZB-02 Notes based on Koenkk/zigbee2mqtt#8971 (comment) and Koenkk/zigbee2mqtt#11273 (comment) * incorporate review comment

MarcoGT · 2023-04-16T11:51:56Z

With 1.30.1 not working

dsduarte · 2023-04-16T23:58:20Z

With 1.30.1 not working

I got 1.30.3 and my SNZB-02 devices were getting offline and stop reporting every day...
Yesterday I forced removed them and then added again e now they are working well.

miekrr · 2023-07-27T14:21:36Z

Same, not working on the latest docker image. Following instructions Koenkk/zigbee2mqtt.io@fd2285c fixes temporary.

Next server reboot usually at least one sensor is left out and doesn't report anything.

mnn · 2023-08-10T17:31:51Z

I am on 1.32.2 (I think current latest?) and even the "temporary fix" doesn't work for me. It takes long just to start pairing (5-10 minutes), it has to be almost touching the antenna otherwise there's not a chance of even getting this "far". Then usually paring fails. And even when it doesn't fail, it doesn't setup reporting, so I never hear from the device again... Tried it two times, it took total half an hour and without any result 😩.

tvrulesme added the problem Something isn't working label Oct 3, 2021

Koenkk closed this as completed Apr 17, 2022

eloo mentioned this issue Apr 18, 2022

Sonoff SNZB-02 no data #11273

Closed

lazou added a commit to lazou/zigbee2mqtt.io that referenced this issue Jul 14, 2022

Add troubleshoot instructions for SONOFF SNZB-02

661a392

Notes based on Koenkk/zigbee2mqtt#8971 (comment) and Koenkk/zigbee2mqtt#11273 (comment)

lazou mentioned this issue Jul 14, 2022

Add troubleshoot instructions for SONOFF SNZB-02 Koenkk/zigbee2mqtt.io#1480

Merged

burmistrzak mentioned this issue May 28, 2024

Convert Sonoff SNZB-02D & SNZB-02P to modernExtend Koenkk/zigbee-herdsman-converters#7572

Merged

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

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

Comments

tvrulesme commented Oct 3, 2021

Debug info

qukla1000 commented Oct 3, 2021

yang360 commented Oct 4, 2021

sjorge commented Oct 4, 2021

tvrulesme commented Oct 4, 2021

qukla1000 commented Oct 4, 2021

sjorge commented Oct 4, 2021

tvrulesme commented Oct 4, 2021

tvrulesme commented Oct 4, 2021

sjorge commented Oct 4, 2021

tvrulesme commented Oct 4, 2021

qukla1000 commented Oct 4, 2021

qukla1000 commented Oct 4, 2021

tvrulesme commented Oct 4, 2021

sjorge commented Oct 4, 2021

sjorge commented Oct 4, 2021

qukla1000 commented Oct 4, 2021

tvrulesme commented Oct 4, 2021

tvrulesme commented Oct 4, 2021

qukla1000 commented Oct 4, 2021

sjorge commented Oct 4, 2021 • edited Loading

Koenkk commented Oct 4, 2021

qukla1000 commented Oct 4, 2021 • edited Loading

tvrulesme commented Oct 4, 2021

Koenkk commented Oct 4, 2021

tvrulesme commented Oct 4, 2021

takthetank commented Oct 4, 2021

tvrulesme commented Oct 5, 2021 • edited Loading

tvrulesme commented Oct 5, 2021

sjorge commented Oct 5, 2021

jjromannet commented Feb 15, 2022 • edited Loading

ndevenish commented Feb 15, 2022

linker3000 commented Feb 26, 2022

danieldid commented Feb 26, 2022

jjromannet commented Feb 27, 2022 • edited Loading

danieldid commented Feb 28, 2022

danieldid commented Mar 2, 2022

DarkPako84 commented Mar 9, 2022

danieldid commented Mar 14, 2022

jjromannet commented Mar 15, 2022

danieldid commented Mar 15, 2022

linker3000 commented Mar 15, 2022 via email

dsduarte commented Mar 17, 2022

jjromannet commented Mar 28, 2022 • edited Loading

matbech commented Mar 30, 2022 • edited Loading

Koenkk commented Mar 30, 2022

danieldid commented Apr 10, 2022

linker3000 commented Apr 10, 2022 via email

ndevenish commented Apr 17, 2022

Koenkk commented Apr 17, 2022

MarcoGT commented Apr 16, 2023

dsduarte commented Apr 16, 2023

miekrr commented Jul 27, 2023

mnn commented Aug 10, 2023

sjorge commented Oct 4, 2021 •

edited

Loading

qukla1000 commented Oct 4, 2021 •

edited

Loading

tvrulesme commented Oct 5, 2021 •

edited

Loading

jjromannet commented Feb 15, 2022 •

edited

Loading

jjromannet commented Feb 27, 2022 •

edited

Loading

jjromannet commented Mar 28, 2022 •

edited

Loading

matbech commented Mar 30, 2022 •

edited

Loading