Several LYWSD03MMC stop reporting measurements

[fred777]

Yesterday I flashed 3 LYWSD03MMC one after the other from ATC BLE to Zigbee firmware 0x01233001 with TelinkMiFlasher.html. Integration into ZHA worked like a charm, until the morning.

The displays keep updating, but the temperatures and humidity being received by Homeassistant 2024.11.1 via ZHA are stuck since around 6am for all 3 devices and measurements are reported to have updated 6h ago.

Reboot of HA didn't help.

Reconfiguring the devices fails too.

My coordinator is a SONOFF ZBDongle-E 3.0 Plus (EFR32MG21 + CH9102F/CP2102N) with firmware 7.4.3.0

What brought the devices back is a reset via battery removal:

In the log it can bee seen that "a checkin event was fired" occurred every hour until 6am where it stopped. It re-appeared right after device reset.

I hope someone can help me here - I don't want to reset the thermometers every morning 🙈

[pvvx]

Reconfiguring the devices fails too.

Bindung - Not required
Reporting - ok

---

I hope someone can help me here - I don't want to reset the thermometers every morning

The device has nothing to do with it

When you turn the battery off and on, your Zigbee coordinator completely refreshed the "binding" and "reports".

First, check the connection quality with the device. The signal level depends on the orientation of the thermometer and receiver.
And also interference in the radio air...

Some coordinators lose everything when power is reset or rebooted...

1. To avoid devices dropping out of the Zigbee network, a standalone (constantly working) router is required.
2. Some coordinators and/or routers do not work with long communication intervals for end devices.

---

In the entire history of alternative firmware and work with HA in ZHA, I have not had a single dropout from any device. Only an experiment to turn off all routers and the Zigbee network coordinator for several days led to the loss of many Zigbee devices, not only with alternative firmware. With the Zigbee standalone router turned on, but the coordinator turned off, there was not a single dropout for a year, except for 2 Xiaomi LUMI.weather sensor failures.

My coordinator is a SONOFF ZBDongle-E 3.0 Plus (EFR32MG21 + CH9102F/CP2102N) with firmware 7.4.3.0

For ZHA, patches are always used: #6
ZHA does not adhere to Zigbee 3.0.

The HA system is powered by a power supply with a backup battery.

[fred777]

Thank you for the explanations!

I'm also convinced now that it's not device-related because I did not reset all devices but after an update of Homeassistant from 2024.11.1 to 2024.11.2 + reboot, measurements started to be reported for all devices again.

But I would rule out poor signal strength and power issues:

One thermometer is sitting only 50cm away from the coordinator, the others are like 2..5m away with thin walls in between and routers nearby in the same room.

HA is running on an UPS-backed thin client - no reboots or power failures, same for the coordinator (attached to HA computer via USB) and all routers (AC-powered Tadfri LED drivers).

Applying the ZHA patch seems to be affect only measurement resolution - or is there something else that I have missed? It's is not so straight-forward in my case as I'm running the official docker image of homeassistant. Seems like related python modules are being shipped pre-compiled only, no source code. Will try to find a way.

[fred777]

Side-note: This might be related and the fix was included in 2024.11.2: home-assistant/core#130259 (comment)

[pvvx]

Applying the ZHA patch seems to be affect only measurement resolution - or is there something else that I have missed?

When changing the "report" parameters, the thermometer transmits readings more often.

---

It is impossible to use PollControl in the device, since ZHA applies settings not according to the algorithm described in Zigbee 3.0, but according to its own constants. It sets parameters not from the range of parameters issued by the device, but its own. ZHA sets up the device to communicate every 6 seconds, which drains the battery significantly.

As a result, the PollControl cluster and PollControl management in the device had to be removed.

Due to a lot of such and other problems in ZHA and Z2M, it is impossible to make a device with a normal implementation of Zigbee 3.0.

[fred777]

Meanwhile I migrated from ZHA to Z2M. It appears to be much more stable.

But still I had one of the thermometers not report measurement values properly. Temperature was fine, humidity was stuck at a fixed value for hours.

A couple of resets and re-pairings (against a router in 1m proximity, LQI 168) later it now works. Who know's what went wrong 🤷‍♂️