Zigbee2MQTT Reporting time about z03mmc

[fryc88]

Mine doesn't seem to be accepting reporting time changes, temp, humidity and battery are reporting after bang on every 5 minutes, which is draining battery quite a lot i guess - got 78% left from brand new battery, all flashed at saturday so it's 5th day of using it today. I only flashed one of my whole lot of these termometers to see battery drain, but that doesn't look well. With stock BT firmware they lasted 9-12 months each, with custom ATC they were about 4-5 months...
I've got 1.0.4 firmware now, trying to do OTA to 1.0.5 but they don't mention any battery/reporting changes

[wimpie007]

my 2 devices report every minute spot on.
killing battery.😥
1.0.5

[pvvx]

The current version 1.0.5 after "bind clasters" passes all values every 10 seconds.
Changing the parameters of the "report" (times) does not work.

Log Zigbee2BLE (custom ver Zigbee-direct, down with the monster "zigbee2mqtt" :) ):

I	07:05:17.844	Notification received from 00010203-0405-0607-0809-0a0b0c0d2b12, value: (0x) 81-04-BB-70-01-01-B6-04-05-01-00-00-21-10-AE
A	07:05:17.844	"(0x) 81-04-BB-70-01-01-B6-04-05-01-00-00-21-10-AE" received
I	07:05:17.844	Notification received from 00010203-0405-0607-0809-0a0b0c0d2b12, value: (0x) 81-04-BB-70-01-01-B7-04-02-01-00-00-29-08-C9
A	07:05:17.844	"(0x) 81-04-BB-70-01-01-B7-04-02-01-00-00-29-08-C9" received
I	07:05:27.980	Notification received from 00010203-0405-0607-0809-0a0b0c0d2b12, value: (0x) 81-04-BB-70-01-01-B8-04-05-01-00-00-21-10-A8
A	07:05:27.980	"(0x) 81-04-BB-70-01-01-B8-04-05-01-00-00-21-10-A8" received
I	07:05:27.981	Notification received from 00010203-0405-0607-0809-0a0b0c0d2b12, value: (0x) 81-04-BB-70-01-01-B9-04-02-01-00-00-29-08-D5
A	07:05:27.981	"(0x) 81-04-BB-70-01-01-B9-04-02-01-00-00-29-08-D5" received
I	07:05:38.116	Notification received from 00010203-0405-0607-0809-0a0b0c0d2b12, value: (0x) 81-04-BB-70-01-01-BA-04-05-01-00-00-21-10-AA
A	07:05:38.116	"(0x) 81-04-BB-70-01-01-BA-04-05-01-00-00-21-10-AA" received
I	07:05:38.117	Notification received from 00010203-0405-0607-0809-0a0b0c0d2b12, value: (0x) 81-04-BB-70-01-01-BB-04-02-01-00-00-29-08-D2
A	07:05:38.117	"(0x) 81-04-BB-70-01-01-BB-04-02-01-00-00-29-08-D2" received
I	07:05:47.125	Notification received from 00010203-0405-0607-0809-0a0b0c0d2b12, value: (0x) 81-04-BB-70-01-01-BC-04-05-01-00-00-21-10-A8
A	07:05:47.125	"(0x) 81-04-BB-70-01-01-BC-04-05-01-00-00-21-10-A8" received
I	07:05:47.125	Notification received from 00010203-0405-0607-0809-0a0b0c0d2b12, value: (0x) 81-04-BB-70-01-01-BD-04-02-01-00-00-29-08-D9
A	07:05:47.125	"(0x) 81-04-BB-70-01-01-BD-04-02-01-00-00-29-08-D9" received

[wimpie007]

mmm, how can we lower the report frequency?
only with an other firmware?

[pvvx]

Do not “link clusters” 0x402, 0x405,.., but request these attributes using any timer.

PS: What is the point of a thermometer that transmits readings below once every ten seconds?
My slightly adapted version of z03mmc consumes approximately 54..58 µA when all reporting every 10 seconds.
If this does not suit you, then use BLE - With the correct settings and a 10 sec report, consumption is less than 14 µA on typical transmission and less than 20 µA with BLE Long Range (~1 km).

[wimpie007]

zigbee thermometers only transmit when values are changed, and never very fast like 10 seconds.
I dont need to have such a detailed reports. once every x minutes is fine with me.
the reason to use zigbee? range is superieur because i have zigbee devices everywhere. (BLE requires extra devices...)

[pvvx]

To change the display, it is also required to wake up all the chips in the thermometer, which does not allow for low consumption in the Zigbee version. And the Zigbee protocol itself requires significantly more consumption compared to BLE. And it doesn't matter which chip is used.
Similarly with server resources. Zigbee2mqtt is a monster compared to the usual built-in integration 'blotooth' in Home Assistant

zigbee thermometers only transmit when values are changed,

This entails a decrease in the accuracy of the readings due to the hysteresis being set

Zigbee vs BLE:

[devbis]

Fixed applying of received reporting values in https://github.com/devbis/z03mmc/releases/tag/1.0.6.