ZigBee2MQTT randomly stops receiving from end device SNZB-02

[WombatHollow]

What happened?

z2M randomly stops receiving data from a SNZB-02 Sonoff Temperature and Humidity Sensors. If you stop then start z2M then the missing devices reappears. My Z2M network has 8 SNZB-02 but over the last 4 months, 3 devices stopped reporting at different times. They do return if I issue the following CLI commends

• `sudo systemctl stop zigbee2mqtt.service
• sudo systemctl start zigbee2mqtt.service`

The devices are still listed under 'Devices' in Z2M, and details look no different to working devices

Z2M is installed on a Raspi 3B also running Node-red

Z2M software and net is

Zigbee2MQTT version
2.1.1 commit: 1accb8b
Coordinator type
EmberZNet
Coordinator revision
7.4.4 [GA]
Coordinator IEEE Address
0x84b4dbfffeefcc9a
Frontend version
0.9.4
zigbee-herdsman-converters version
21.31.0
zigbee-herdsman version
3.2.5
Stats
Total 15

By device type

End devices: 13
Router: 2
By power source
Battery: 13
Mains (single phase): 2

By vendor

eWeLink: 11
SONOFF: 2
_TZE200_myd45weu: 1
_TZ3000_nkkl7uzv: 1

By model

TH01: 9
SWV: 2
SA-003-Zigbee: 1
TS0601: 1
TS0207: 1
WB01: 1

What did you expect to happen?

I expect data sent by devices that are paired to Z2M to be receive and sent out over MQTT

How to reproduce it (minimal and precise)

No response

Zigbee2MQTT version

2.11

Adapter firmware version

7.4.4 [GA]

Adapter

ITead Sonoff Zigbee 3.0 USB Dongle Plus model ZBDongle-E

Setup

Installed into a Raspi3B (no docker) running "Debian GNU/Linux 12 (bookworm)" that also runs Node-Red and Mosquito

Device database.db entry

No response

Debug log

No response

[mrmaximas]

@WombatHollow You are using an very old version of z2m. How about update it to 2.6.0?

[Nerivec]

Also these devices can be very picky about battery charge. They will often start misbehaving when battery drops below a certain level.

[WombatHollow]

@WombatHollow You are using an very old version of z2m. How about update it to 2.6.0?

Ok, I will install 2.6.0 and let it run for a few months, if I see none in 3 Months I will close the issue. (I saw 3 drop out over last 4 months as a baseline).

As for suggestion of battery, all are reporting high battery levels, and I did nothing to the end devices to restore connection, just restarted Z2M, but thanks for the heads up on a potential future issue.

[WombatHollow]

Update:
I Z2M v2.6.1 installed and already one SNZB-02, and a SNZB-01 have dropped off line. The original fix doesn't work, I was fooled by the report of data, but it is old data, and no fresh data is reported.
The fix remains as per Z2M documentation

• on z2M UI, remove the defective device
• enable Join, then press the pairing button (long press of 5 seconds
• Once joined, then reset the devices setting (like Name)

[WombatHollow]

Same problem as in closed issue #21141 @gcardy

[Nerivec]

I have a few snzb02 and 03 myself (live network), they never stopped reporting, except when battery is low (which tends to happen suddenly, i.e. don't trust the advertised battery level).
Could be something about a nearby router they don't like, or a poor link quality maybe?
I'd still advise you to change batteries, just in case (you can set the old ones aside for other devices that may not be so picky).
You can also try to do a clean join: 1. remove the device (do NOT force), 2. restart Z2M, 3. re-pair the device (do a long reset 25-30sec to put it in pairing mode). That will clear the cache, and the join will be like a brand new device.
You can also update your coordinator to latest 8.0.2: https://github.com/Nerivec/silabs-firmware-builder/releases/tag/v2024.6.2-update7

[ekain-fr]

Hello @Nerivec I see your recommendation above to update the coordinator to latest 8.0.2 firmware.

My Zigbee network with ~40 devices is currently running fine on Sonoff ZBDongle-E with 7.4.4 [GA] firmware, using EmberZNet.
I recently upgraded Z2M from version 2.4.0 to version 2.6.2 and everything is running fine so far.
I have 5 SNZB-02D devices that are correctly connected and reporting as expected.

In this situation, do you recommend me to update my coordinator firmware to 8.0.2?
Or should I remain on 7.4.4 since "if it ain't broke don't fix it"?

Thanks for your insights, and for your great job on Z2M.

[Nerivec]

@ekain-fr 8.0.2 and later have some nice benefits, especially for busy networks (spammy devices, heavy broadcasting, etc.). Most users have updated nowadays. Though, if your network is stable, you likely won't see much difference. Note that you can upgrade and downgrade at will between 7.4 and 8.x.

[github-actions]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days

[WombatHollow]

Final update.
I contacted Sonoff and they indicated that earlier batches of SNZB-02 and SNZB-01 have a bug. As I have bought these in two batches some are good, some bad. But line is now discontinued so I will have to go and look for new ZB devices for temperature and switch which is annoying as I have made timber backplates for this format (allows easy battery change as held to wall by magnet rather than adhesive :-(