IM6001-MPP01 devices seem to be reporting every minute, affecting battery life

[spry-salt]

What happened?

I have a bunch of IM6001-MPP01 devices.

Under the latest zigbee2mqtt Edge ([2.5.1-dev], commit [74e9357]) these devices seem to be reporting twice every minute.

In the Reporting tab I can reduce the frequency of reporting for Temperature and Battery measurements, but I can't change the frequency for acceleration or x, y or z axes because it reports UNSUPPORTED_ATTRIBUTE error for those.

What did you expect to happen?

I don't know what else I might be doing that could affect this, but the battery life is really awful for these devices at the moment (e.g. gone in days) whereas it was close to a year under previous versions.

How to reproduce it (minimal and precise)

No response

Zigbee2MQTT version

2.5.1-dev

Adapter firmware version

8.0.3 [GA]

Adapter

Sonoff ZBDongle-E, ember

Setup

Home Assistant OS on Proxmox VM
Linux core-ssh 6.12.35-haos #1 SMP PREEMPT_DYNAMIC Wed Jul. 9 14:17:59 UTC 2025 x86_64 Linux

Device database.db entry

No response

Debug log

[2025-07-15 08:45:26] �[34mdebug�[39m: z2m: Received Zigbee message from '0x286d97000114cf36', type 'attributeReport', cluster 'manuSpecificSamsungAccelerometer', data '{"acceleration":1,"x_axis":-445,"y_axis":-412,"z_axis":-635}' from endpoint 1 with groupID 0
[2025-07-15 08:45:28] �[34mdebug�[39m: z2m: Received Zigbee message from '0x286d97000114cf36', type 'attributeReport', cluster 'msTemperatureMeasurement', data '{"measuredValue":2617}' from endpoint 1 with groupID 0
[2025-07-15 08:45:36] �[34mdebug�[39m: z2m: Received Zigbee message from '0x286d97000114cf36', type 'attributeReport', cluster 'manuSpecificSamsungAccelerometer', data '{"x_axis":-166,"y_axis":-27,"z_axis":-1017}' from endpoint 1 with groupID 0
[2025-07-15 08:45:46] �[34mdebug�[39m: z2m: Received Zigbee message from '0x286d97000114cf36', type 'attributeReport', cluster 'manuSpecificSamsungAccelerometer', data '{"x_axis":-162,"y_axis":-40,"z_axis":-984}' from endpoint 1 with groupID 0
[2025-07-15 08:45:48] �[34mdebug�[39m: z2m: Received Zigbee message from '0x286d97000114cf36', type 'attributeReport', cluster 'manuSpecificSamsungAccelerometer', data '{"acceleration":0}' from endpoint 1 with groupID 0
[2025-07-15 08:46:46] �[34mdebug�[39m: z2m: Received Zigbee message from '0x286d97000114cf36', type 'attributeReport', cluster 'manuSpecificSamsungAccelerometer', data '{"x_axis":-162,"y_axis":-40,"z_axis":-984}' from endpoint 1 with groupID 0
[2025-07-15 08:46:49] �[34mdebug�[39m: z2m: Received Zigbee message from '0x286d97000114cf36', type 'attributeReport', cluster 'manuSpecificSamsungAccelerometer', data '{"acceleration":0}' from endpoint 1 with groupID 0
[2025-07-15 08:47:47] �[34mdebug�[39m: z2m: Received Zigbee message from '0x286d97000114cf36', type 'attributeReport', cluster 'manuSpecificSamsungAccelerometer', data '{"x_axis":-162,"y_axis":-40,"z_axis":-984}' from endpoint 1 with groupID 0
[2025-07-15 08:47:49] �[34mdebug�[39m: z2m: Received Zigbee message from '0x286d97000114cf36', type 'attributeReport', cluster 'manuSpecificSamsungAccelerometer', data '{"acceleration":0}' from endpoint 1 with groupID 0
[2025-07-15 08:48:46] �[34mdebug�[39m: z2m: Received Zigbee message from '0x286d97000114cf36', type 'attributeReport', cluster 'msTemperatureMeasurement', data '{"measuredValue":2490}' from endpoint 1 with groupID 0
[2025-07-15 08:48:47] �[34mdebug�[39m: z2m: Received Zigbee message from '0x286d97000114cf36', type 'attributeReport', cluster 'manuSpecificSamsungAccelerometer', data '{"x_axis":-162,"y_axis":-40,"z_axis":-984}' from endpoint 1 with groupID 0
[2025-07-15 08:48:50] �[34mdebug�[39m: z2m: Received Zigbee message from '0x286d97000114cf36', type 'attributeReport', cluster 'manuSpecificSamsungAccelerometer', data '{"acceleration":0}' from endpoint 1 with groupID 0
[2025-07-15 08:49:48] �[34mdebug�[39m: z2m: Received Zigbee message from '0x286d97000114cf36', type 'attributeReport', cluster 'manuSpecificSamsungAccelerometer', data '{"x_axis":-162,"y_axis":-40,"z_axis":-984}' from endpoint 1 with groupID 0
[2025-07-15 08:49:51] �[34mdebug�[39m: z2m: Received Zigbee message from '0x286d97000114cf36', type 'attributeReport', cluster 'manuSpecificSamsungAccelerometer', data '{"acceleration":0}' from endpoint 1 with groupID 0
[2025-07-15 08:50:49] �[34mdebug�[39m: z2m: Received Zigbee message from '0x286d97000114cf36', type 'attributeReport', cluster 'manuSpecificSamsungAccelerometer', data '{"x_axis":-162,"y_axis":-40,"z_axis":-984}' from endpoint 1 with groupID 0
[2025-07-15 08:50:51] �[34mdebug�[39m: z2m: Received Zigbee message from '0x286d97000114cf36', type 'attributeReport', cluster 'manuSpecificSamsungAccelerometer', data '{"acceleration":0}' from endpoint 1 with groupID 0
[2025-07-15 08:50:59] �[34mdebug�[39m: z2m: Received Zigbee message from '0x286d97000114cf36', type 'attributeReport', cluster 'msTemperatureMeasurement', data '{"measuredValue":2384}' from endpoint 1 with groupID 0
[2025-07-15 08:51:49] �[34mdebug�[39m: z2m: Received Zigbee message from '0x286d97000114cf36', type 'attributeReport', cluster 'manuSpecificSamsungAccelerometer', data '{"x_axis":-162,"y_axis":-40,"z_axis":-984}' from endpoint 1 with groupID 0
[2025-07-15 08:51:52] �[34mdebug�[39m: z2m: Received Zigbee message from '0x286d97000114cf36', type 'attributeReport', cluster 'manuSpecificSamsungAccelerometer', data '{"acceleration":0}' from endpoint 1 with groupID 0
[2025-07-15 08:52:36] �[34mdebug�[39m: z2m: Received Zigbee message from '0x286d97000114cf36', type 'attributeReport', cluster 'manuSpecificSamsungAccelerometer', data '{"acceleration":1,"x_axis":-137,"y_axis":152,"z_axis":-608}' from endpoint 1 with groupID 0
[2025-07-15 08:52:47] �[34mdebug�[39m: z2m: Received Zigbee message from '0x286d97000114cf36', type 'attributeReport', cluster 'manuSpecificSamsungAccelerometer', data '{"x_axis":-131,"y_axis":1,"z_axis":-990}' from endpoint 1 with groupID 0
[2025-07-15 08:52:54] �[34mdebug�[39m: z2m: Received Zigbee message from '0x286d97000114cf36', type 'attributeReport', cluster 'manuSpecificSamsungAccelerometer', data '{"acceleration":0}' from endpoint 1 with groupID 0
[2025-07-15 08:53:47] �[34mdebug�[39m: z2m: Received Zigbee message from '0x286d97000114cf36', type 'attributeReport', cluster 'manuSpecificSamsungAccelerometer', data '{"x_axis":-131,"y_axis":1,"z_axis":-990}' from endpoint 1 with groupID 0
[2025-07-15 08:53:54] �[34mdebug�[39m: z2m: Received Zigbee message from '0x286d97000114cf36', type 'attributeReport', cluster 'manuSpecificSamsungAccelerometer', data '{"acceleration":0}' from endpoint 1 with groupID 0
[2025-07-15 08:54:48] �[34mdebug�[39m: z2m: Received Zigbee message from '0x286d97000114cf36', type 'attributeReport', cluster 'manuSpecificSamsungAccelerometer', data '{"x_axis":-131,"y_axis":1,"z_axis":-990}' from endpoint 1 with groupID 0
[2025-07-15 08:54:55] �[34mdebug�[39m: z2m: Received Zigbee message from '0x286d97000114cf36', type 'attributeReport', cluster 'manuSpecificSamsungAccelerometer', data '{"acceleration":0}' from endpoint 1 with groupID 0
[2025-07-15 08:55:06] �[34mdebug�[39m: z2m: Received Zigbee message from '0x286d97000114cf36', type 'attributeReport', cluster 'manuSpecificSamsungAccelerometer', data '{"acceleration":1,"x_axis":-29,"y_axis":388,"z_axis":-890}' from endpoint 1 with groupID 0
[2025-07-15 08:55:16] �[34mdebug�[39m: z2m: Received Zigbee message from '0x286d97000114cf36', type 'attributeReport', cluster 'manuSpecificSamsungAccelerometer', data '{"x_axis":-112,"y_axis":-12,"z_axis":-995}' from endpoint 1 with groupID 0
[2025-07-15 08:55:22] �[34mdebug�[39m: z2m: Received Zigbee message from '0x286d97000114cf36', type 'attributeReport', cluster 'manuSpecificSamsungAccelerometer', data '{"acceleration":0}' from endpoint 1 with groupID 0
[2025-07-15 08:56:17] �[34mdebug�[39m: z2m: Received Zigbee message from '0x286d97000114cf36', type 'attributeReport', cluster 'manuSpecificSamsungAccelerometer', data '{"x_axis":-112,"y_axis":-12,"z_axis":-995}' from endpoint 1 with groupID 0
[2025-07-15 08:56:23] �[34mdebug�[39m: z2m: Received Zigbee message from '0x286d97000114cf36', type 'attributeReport', cluster 'manuSpecificSamsungAccelerometer', data '{"acceleration":0}' from endpoint 1 with groupID 0
[2025-07-15 08:57:17] �[34mdebug�[39m: z2m: Received Zigbee message from '0x286d97000114cf36', type 'attributeReport', cluster 'manuSpecificSamsungAccelerometer', data '{"x_axis":-112,"y_axis":-12,"z_axis":-995}' from endpoint 1 with groupID 0
[2025-07-15 08:57:23] �[34mdebug�[39m: z2m: Received Zigbee message from '0x286d97000114cf36', type 'attributeReport', cluster 'manuSpecificSamsungAccelerometer', data '{"acceleration":0}' from endpoint 1 with groupID 0
[2025-07-15 08:58:18] �[34mdebug�[39m: z2m: Received Zigbee message from '0x286d97000114cf36', type 'attributeReport', cluster 'manuSpecificSamsungAccelerometer', data '{"x_axis":-112,"y_axis":-12,"z_axis":-995}' from endpoint 1 with groupID 0
[2025-07-15 08:58:24] �[34mdebug�[39m: z2m: Received Zigbee message from '0x286d97000114cf36', type 'attributeReport', cluster 'manuSpecificSamsungAccelerometer', data '{"acceleration":0}' from endpoint 1 with groupID 0
[2025-07-15 08:59:19] �[34mdebug�[39m: z2m: Received Zigbee message from '0x286d97000114cf36', type 'attributeReport', cluster 'manuSpecificSamsungAccelerometer', data '{"x_axis":-112,"y_axis":-12,"z_axis":-995}' from endpoint 1 with groupID 0
[2025-07-15 08:59:25] �[34mdebug�[39m: z2m: Received Zigbee message from '0x286d97000114cf36', type 'attributeReport', cluster 'manuSpecificSamsungAccelerometer', data '{"acceleration":0}' from endpoint 1 with groupID 0
[2025-07-15 09:00:19] �[34mdebug�[39m: z2m: Received Zigbee message from '0x286d97000114cf36', type 'attributeReport', cluster 'manuSpecificSamsungAccelerometer', data '{"x_axis":-112,"y_axis":-12,"z_axis":-995}' from endpoint 1 with groupID 0
[2025-07-15 09:00:25] �[34mdebug�[39m: z2m: Received Zigbee message from '0x286d97000114cf36', type 'attributeReport', cluster 'manuSpecificSamsungAccelerometer', data '{"acceleration":0}' from endpoint 1 with groupID 0
[2025-07-15 09:01:20] �[34mdebug�[39m: z2m: Received Zigbee message from '0x286d97000114cf36', type 'attributeReport', cluster 'manuSpecificSamsungAccelerometer', data '{"x_axis":-112,"y_axis":-12,"z_axis":-995}' from endpoint 1 with groupID 0
[2025-07-15 09:01:26] �[34mdebug�[39m: z2m: Received Zigbee message from '0x286d97000114cf36', type 'attributeReport', cluster 'manuSpecificSamsungAccelerometer', data '{"acceleration":0}' from endpoint 1 with groupID 0
[2025-07-15 09:02:20] �[34mdebug�[39m: z2m: Received Zigbee message from '0x286d97000114cf36', type 'attributeReport', cluster 'manuSpecificSamsungAccelerometer', data '{"x_axis":-112,"y_axis":-12,"z_axis":-995}' from endpoint 1 with groupID 0
[2025-07-15 09:02:26] �[34mdebug�[39m: z2m: Received Zigbee message from '0x286d97000114cf36', type 'attributeReport', cluster 'manuSpecificSamsungAccelerometer', data '{"acceleration":0}' from endpoint 1 with groupID 0
[2025-07-15 09:03:21] �[34mdebug�[39m: z2m: Received Zigbee message from '0x286d97000114cf36', type 'attributeReport', cluster 'manuSpecificSamsungAccelerometer', data '{"x_axis":-112,"y_axis":-12,"z_axis":-995}' from endpoint 1 with groupID 0
[2025-07-15 09:03:27] �[34mdebug�[39m: z2m: Received Zigbee message from '0x286d97000114cf36', type 'attributeReport', cluster 'manuSpecificSamsungAccelerometer', data '{"acceleration":0}' from endpoint 1 with groupID 0
[2025-07-15 09:04:21] �[34mdebug�[39m: z2m: Received Zigbee message from '0x286d97000114cf36', type 'attributeReport', cluster 'manuSpecificSamsungAccelerometer', data '{"x_axis":-112,"y_axis":-12,"z_axis":-995}' from endpoint 1 with groupID 0
[2025-07-15 09:04:27] �[34mdebug�[39m: z2m: Received Zigbee message from '0x286d97000114cf36', type 'attributeReport', cluster 'manuSpecificSamsungAccelerometer', data '{"acceleration":0}' from endpoint 1 with groupID 0
[2025-07-15 09:05:22] �[34mdebug�[39m: z2m: Received Zigbee message from '0x286d97000114cf36', type 'attributeReport', cluster 'manuSpecificSamsungAccelerometer', data '{"x_axis":-112,"y_axis":-12,"z_axis":-995}' from endpoint 1 with groupID 0
[2025-07-15 09:05:28] �[34mdebug�[39m: z2m: Received Zigbee message from '0x286d97000114cf36', type 'attributeReport', cluster 'manuSpecificSamsungAccelerometer', data '{"acceleration":0}' from endpoint 1 with groupID 0
[2025-07-15 09:06:22] �[34mdebug�[39m: z2m: Received Zigbee message from '0x286d97000114cf36', type 'attributeReport', cluster 'manuSpecificSamsungAccelerometer', data '{"x_axis":-112,"y_axis":-12,"z_axis":-995}' from endpoint 1 with groupID 0
[2025-07-15 09:06:29] �[34mdebug�[39m: z2m: Received Zigbee message from '0x286d97000114cf36', type 'attributeReport', cluster 'manuSpecificSamsungAccelerometer', data '{"acceleration":0}' from endpoint 1 with groupID 0
[2025-07-15 09:07:23] �[34mdebug�[39m: z2m: Received Zigbee message from '0x286d97000114cf36', type 'attributeReport', cluster 'manuSpecificSamsungAccelerometer', data '{"x_axis":-112,"y_axis":-12,"z_axis":-995}' from endpoint 1 with groupID 0
[2025-07-15 09:07:29] �[34mdebug�[39m: z2m: Received Zigbee message from '0x286d97000114cf36', type 'attributeReport', cluster 'manuSpecificSamsungAccelerometer', data '{"acceleration":0}' from endpoint 1 with groupID 0
[2025-07-15 09:08:24] �[34mdebug�[39m: z2m: Received Zigbee message from '0x286d97000114cf36', type 'attributeReport', cluster 'manuSpecificSamsungAccelerometer', data '{"x_axis":-112,"y_axis":-12,"z_axis":-995}' from endpoint 1 with groupID 0
[2025-07-15 09:08:30] �[34mdebug�[39m: z2m: Received Zigbee message from '0x286d97000114cf36', type 'attributeReport', cluster 'manuSpecificSamsungAccelerometer', data '{"acceleration":0}' from endpoint 1 with groupID 0
[2025-07-15 09:09:24] �[34mdebug�[39m: z2m: Received Zigbee message from '0x286d97000114cf36', type 'attributeReport', cluster 'manuSpecificSamsungAccelerometer', data '{"x_axis":-112,"y_axis":-12,"z_axis":-995}' from endpoint 1 with groupID 0

[mlipscombe]

The problem is a result of this commit:

Koenkk/zigbee-herdsman-converters#8676

[Koenkk]

@natefelt Koenkk/zigbee-herdsman-converters#8676 seems to be causing some issues should we revert back to 1 hour?

[natefelt]

Seems you should. I stopped using this particular sensor after replacing my dryer.

[Koenkk]

@natefelt thanks!

Fixed! After updating make sure to re-configure the device via the reconfigure button on the frontend device page.

Changes will be available in the dev branch in a few hours from now and in the next release which is every 1st of the month.

[spry-salt]

A thousand thanks. I've reconfigured all the sensors and the network is so much quieter now. Fingers crossed the battery life returns to something normal.