SmartThings multipurpose sensor IM6001-MPP01 is reporting every few seconds

[Fabiancrg]

What happened

Sensor is sending data all the time, does not look like it's going to sleep so the battery is empty after a month.

What did you expect to happen

Sensor only send data when an event occurs and at regular interval (every 5, 10 or 30 minutes) for battery and temperature.

How to reproduce it (minimal and precise)

Just add the sensor, you will see a lot of messages in the log

Debug info

Zigbee2MQTT version: 1.19.1-dev commit: 2afd9ab
Adapter hardware: CC26X2R1
Adapter firmware version: 20200805

[asjmcguire]

I have this problem too, and I am unable to change any of the reporting times. With v1.20.0 any attempt to change the reporting intervals or even to disable them completely is met with an error message about a timeout.

Request 'zigbee2mqtt/bridge/request/device/configure_reporting' failed with error: 'Bind 0x286d970001134176/1 manuSpecificSamsungAccelerometer from '0x00212effff0741a6/1' failed (waiting for response TIMEOUT)'

[Koenkk]

@asjmcguire make sure to wakeup the device right before sending this command by clicking a button on it.

[Fabiancrg]

@asjmcguire did you succeed to configure your device(s) ?

[Fabiancrg]

@Koenkk I receive the following message for example when I am in debug mode:

juil. 22 15:00:32 NUC npm[300931]: Zigbee2MQTT:debug 2021-07-22 15:00:32: Received Zigbee message from 'IM6001', type 'attributeReport', cluster 'manuSpecificSamsungAccelerometer', data '{"acceleration":0}' from endpoint 1 with groupID 0

But when I try to change the reporting interval values by publishing

{"id":"0x286d97000106d50f/1","cluster":"manuSpecificSamsungAccelerometer","attribute":"acceleration","minimum_report_interval":300,"maximum_report_interval":3600,"reportable_change":5}

to zigbee2mqtt/bridge/request/device/configure_reporting, I get this error:

juil. 22 15:00:43 NUC npm[300931]: Zigbee2MQTT:debug 2021-07-22 15:00:43: Received MQTT message on 'zigbee2mqtt/bridge/request/device/configure_reporting' with data '{"id":"0x286d97000106d50f/1","cluster":"manuSpecificSamsungAccelerometer","attribute":"acceleration","minimum_report_interval":300,"maximum_report_interval":3600,"reportable_change":5}' juil. 22 15:00:44 NUC npm[300931]: Zigbee2MQTT:error 2021-07-22 15:00:44: Request 'zigbee2mqtt/bridge/request/device/configure_reporting' failed with error: 'ConfigureReporting 0x286d97000106d50f/1 manuSpecificSamsungAccelerometer([{"attribute":"acceleration","minimumReportInterval":300,"maximumReportInterval":3600,"reportableChange":5}], {"sendWhenActive":false,"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":4362,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Status 'UNSUPPORTED_ATTRIBUTE')' juil. 22 15:00:44 NUC npm[300931]: Zigbee2MQTT:info 2021-07-22 15:00:44: MQTT publish: topic 'zigbee2mqtt/bridge/response/device/configure_reporting', payload '{"data":{},"error":"ConfigureReporting 0x286d97000106d50f/1 manuSpecificSamsungAccelerometer([{\"attribute\":\"acceleration\",\"minimumReportInterval\":300,\"maximumReportInterval\":3600,\"reportableChange\":5}], {\"sendWhenActive\":false,\"timeout\":10000,\"disableResponse\":false,\"disableRecovery\":false,\"disableDefaultResponse\":true,\"direction\":0,\"srcEndpoint\":null,\"reservedBits\":0,\"manufacturerCode\":4362,\"transactionSequenceNumber\":null,\"writeUndiv\":false}) failed (Status 'UNSUPPORTED_ATTRIBUTE')","status":"error"}'

Is there omething wrong in the command I am using ?

[asjmcguire]

@Fabiancrg nope, the only value I am successfully able to change is the Temperature Reporting time. Anything to do with "manuSpecificSamsungAccelerometer" comes back with an error message - either a time out, or unsupported attribute.

[Fabiancrg]

Indeed, I did the same with the temperature and it worked:

Published this:
{"id":"0x286d97000106d50f/1","cluster":"msTemperatureMeasurement","attribute":"measuredValue","minimum_report_interval":300,"maximum_report_interval":3600,"reportable_change":5}

and got this:

juil. 22 15:40:11 NUC npm[300931]: Zigbee2MQTT:debug 2021-07-22 15:40:11: Received MQTT message on 'zigbee2mqtt/bridge/request/device/configure_reporting' with data '{"id":"0x286d97000106d50f/1","cluster":"msTemperatureMeasurement","attribute":"measuredValue","minimum_report_interval":300,"maximum_report_interval":3600,"reportable_change":5}' juil. 22 15:40:15 NUC npm[300931]: Zigbee2MQTT:info 2021-07-22 15:40:15: Configured reporting for '0x286d97000106d50f/1', 'msTemperatureMeasurement.measuredValue' juil. 22 15:40:15 NUC npm[300931]: Zigbee2MQTT:info 2021-07-22 15:40:15: MQTT publish: topic 'zigbee2mqtt/bridge/response/device/configure_reporting', payload '{"data":{"attribute":"measuredValue","cluster":"msTemperatureMeasurement","id":"0x286d97000106d50f/1","maximum_report_interval":3600,"minimum_report_interval":300,"reportable_change":5},"status":"ok"}'

[Koenkk]

I've increased the reporting interval now. Try updating to the latest-dev, wakeup the device and right after that click the configure button in the frontend (yellow refresh icon).

Changes will be available in the dev branch in a few hours from now. (https://www.zigbee2mqtt.io/how_tos/how-to-switch-to-dev-branch.html)

[Fabiancrg]

@Koenkk it's working now with this new dev release.
Thank you for your help !

[asjmcguire]

For me - one of mine is fixed: the max reporting time has been increased to 3600 and the min change has been increased to 5. The other one though is still sitting at a max reporting interval of 60 and a min change of 1. I did not reconfigure the one that has fixed itself, and the one that is not fixed I did try to press the yellow refresh button and wake the device up (both by opening and closing the door, and when that failed - by pressing the recessed button every second).

[Fabiancrg]

I have 3 sensors and 2 of them were fixed after the upgrade+restart; the last one was still working but was reporting only if the door was open or closed.
The last one was fixed by removing the battery and reinserting it, just after that I pressed the reconfigure button from the Z2M frontend.

[dcyonce]

This still seems to be an issue.
These sensors still report every 10 seconds with NO changes.

Zigbee2MQTT:info 2022-05-28 21:24:20: MQTT publish: topic 'zigbee2mqtt/Dirty Sensor', payload '{"battery":93,"battery_low":null,"contact":null,"last_seen":"2022-05-29T02:24:20.766Z","linkquality":135,"moving":false,"tamper":null,"temperature":29.22,"voltage":2600,"x_axis":-973,"y_axis":20,"z_axis":-28}'
Zigbee2MQTT:info 2022-05-28 21:24:30: MQTT publish: topic 'zigbee2mqtt/Dirty Sensor', payload '{"battery":93,"battery_low":null,"contact":null,"last_seen":"2022-05-29T02:24:30.768Z","linkquality":147,"moving":false,"tamper":null,"temperature":29.22,"voltage":2600,"x_axis":-973,"y_axis":20,"z_axis":-28}'
Zigbee2MQTT:info 2022-05-28 21:24:54: MQTT publish: topic 'zigbee2mqtt/Dirty Sensor', payload '{"battery":93,"battery_low":null,"contact":null,"last_seen":"2022-05-29T02:24:54.395Z","linkquality":129,"moving":false,"tamper":null,"temperature":28.21,"voltage":2600,"x_axis":-973,"y_axis":20,"z_axis":-28}'
Zigbee2MQTT:info 2022-05-28 21:25:20: MQTT publish: topic 'zigbee2mqtt/Dirty Sensor', payload '{"battery":93,"battery_low":null,"contact":null,"last_seen":"2022-05-29T02:25:20.814Z","linkquality":153,"moving":false,"tamper":null,"temperature":28.21,"voltage":2600,"x_axis":-973,"y_axis":20,"z_axis":-28}'

[asjmcguire]

@dcyonce remove the sensor and then readd it, that's how I fixed mine.