03MMC: v0.1.2.3: reported temperature values ​​are lagging behind the display

[rpallai]

After updating to Z03MMC_v0123.bin, I noticed that the display and the reported temperature values differ consistently. The former updates correctly, while the latter follows with significant delays. Interestingly, this does not apply to the RH value, which always updates instantly over Zigbee when the display changes. Reverting back to v0.1.2.2, I do not experience this issue, and the value reported over Zigbee always matches the value shown on the display.

[rpallai]

Before 10:45, v0.1.2.3 was running, and after that, I downgraded to v0.1.2.2. Nothing else changed. I didn’t modify the configurations after flashing. (bottom chart is RH)

[pvvx]

It was your Zigbee coordinator who did not set report settings. And the second time, after reflashing, the agreement was made.

+ REPORT_CONFIG

+ measurement-interval

[rpallai]

@pvvx Thanks for your reply. I have an idea of what happened. When I first flashed the firmware, I was running an out-of-date Z2M that didn’t support -z suffix in device names, so I believe it didn’t configure the device’s report settings. Later, I upgraded Z2M to the latest version, but I didn’t re-pair the device to the network, so it remained unconfigured. When I flashed it second time, the updated Z2M (which supported the firmware) was already running, allowing it to properly configure the report settings, and everything worked as expected.

What do you think, could this have been the case?