Samsung Multipurpose Sensor 2018 reports two different battery values

🛎️ Get Help
1

Some of my Samsung SmartThings Multipurpose Sensors, 2018 versions, are reporting the battery status twice, with two different amounts.

The device events show the sensor reporting the battery level as 66% and 93%.

The logs with debug on show:

[dev:171](http://10.0.0.67/logs#dev171)2018-12-04 10:11:06.610 am [debug](http://10.0.0.67/device/edit/171)parse: listResult [[name:battery, value:93, descriptionText:Front door bell battery is 93%]]

[dev:171](http://10.0.0.67/logs#dev171)2018-12-04 10:11:06.607 am [debug](http://10.0.0.67/device/edit/171)parse: listResult [[name:temperature, value:22.94, descriptionText:Front door bell temperature is 22.94°C, unit:°C]]

[dev:171](http://10.0.0.67/logs#dev171)2018-12-04 10:11:06.604 am [debug](http://10.0.0.67/device/edit/171)parseReportAttributeMessage: Temp resultMap: [name:temperature, value:22.94, descriptionText:Front door bell temperature is 22.94°C, unit:°C]

[dev:171](http://10.0.0.67/logs#dev171)2018-12-04 10:11:06.599 am [info](http://10.0.0.67/device/edit/171)Front door bell battery is 93%

[dev:171](http://10.0.0.67/logs#dev171)2018-12-04 10:11:06.597 am [debug](http://10.0.0.67/device/edit/171)zigbee.parseDescriptionAsMap-read attr: [raw:BAFD0100010A210020BA, dni:BAFD, endpoint:01, cluster:0001, size:0A, attrId:0021, encoding:20, value:BA, clusterInt:1, attrInt:33]

[dev:171](http://10.0.0.67/logs#dev171)2018-12-04 10:11:06.593 am [info](http://10.0.0.67/device/edit/171)Front door bell temperature is 22.94°C

[dev:171](http://10.0.0.67/logs#dev171)2018-12-04 10:11:06.590 am [debug](http://10.0.0.67/device/edit/171)parse: listResult [[name:battery, value:66, descriptionText:Front door bell battery is 66%]]

[dev:171](http://10.0.0.67/logs#dev171)2018-12-04 10:11:06.587 am [info](http://10.0.0.67/device/edit/171)Front door bell battery is 66%

[dev:171](http://10.0.0.67/logs#dev171)2018-12-04 10:11:06.584 am [debug](http://10.0.0.67/device/edit/171)parse: read attr - raw: BAFD0100010A210020BA, dni: BAFD, endpoint: 01, cluster: 0001, size: 0A, attrId: 0021, encoding: 20, value: BA

[dev:171](http://10.0.0.67/logs#dev171)2018-12-04 10:11:06.580 am [debug](http://10.0.0.67/device/edit/171)zigbee.parseDescriptionAsMap-read attr: [raw:BAFD0100010A2000201B, dni:BAFD, endpoint:01, cluster:0001, size:0A, attrId:0020, encoding:20, value:1B, clusterInt:1, attrInt:32]

[dev:171](http://10.0.0.67/logs#dev171)2018-12-04 10:11:06.577 am [debug](http://10.0.0.67/device/edit/171)parse: read attr - raw: BAFD0100010A2000201B, dni: BAFD, endpoint: 01, cluster: 0001, size: 0A, attrId: 0020, encoding: 20, value: 1B

[dev:171](http://10.0.0.67/logs#dev171)2018-12-04 10:11:06.572 am [debug](http://10.0.0.67/device/edit/171)zigbee.parseDescriptionAsMap-read attr: [raw:BAFD0104020C000029F508, dni:BAFD, endpoint:01, cluster:0402, size:0C, attrId:0000, encoding:29, value:08F5, clusterInt:1026, attrInt:0]

[dev:171](http://10.0.0.67/logs#dev171)2018-12-04 10:11:06.546 am [debug](http://10.0.0.67/device/edit/171)parse: read attr - raw: BAFD0104020C000029F508, dni: BAFD, endpoint: 01, cluster: 0402, size: 0C, attrId: 0000, encoding: 29, value: 08F5

Any ideas why I'm getting two different battery values?

Ignore the fact the device is named front door bell, as this contact sensor is in my annunciator panel, next to the electro-magnet for the front door bell pull.

2

One is percent, the other is voltage converted to percent.
Normally a device produces one or the other but not both.
Which driver are you using with this?

3

The "Generic Zigbee Contact Sensor"

4

@mike.maxwell This behaviour is fixed now with the latest firmware. Thanks!

Another thing I was wondering is if there is a way to set the update frequency for things like temperature on these sort of devices? Or switch the temperature reporting off completely for sensors where I'm only really using it as a contact sensor.

5

It's zigbee, so yes it can be changed, however implementing an interface for this in the drivers is pretty time consuming, and whilst on my todo list someplace, its currently not near the top unfortunately...

6

Thanks, at least I know it's not some settings page I've overlooked :slight_smile:

I can wait, the main reason I was thinking about it is that I thought it would be better for battery life on those sensors where I dont need it.

1 Like