Aqara temp sensor reports -100 degrees

[Ticker918]

Using Conbee 1 and Deconz V2_05_66, but the issue has also been there in previous versions.

Sometimes a couple of my Aqara temp/hum/press-sensors report -100°C but it is not even close to that temperature where it is located.

This is a picture from my Home Assistent history from one of the sensors that is reporting faulty values.

When using the Xiaomi gateway instead of Conbee and Deconz this is never an issue.

[bdickhaus]

I have also seen this. My application has a way to throw away values outside the norm, and that is what I have done. I thought it was a sensor problem, but I don't have the Xiaomi gateway to compare to.

[Smanar]

You are using too Home assistant @bdickhaus ?
Because I haven't this problem on my side but on another application.

[bdickhaus]

No, I use HomeSeer with the JowiHue plugin to interface with deCONZ and the Data History plugin to collect the data.

[Smanar]

"Data History plugin" ? it' a logger ? So you have perhaps logged the bad web socket return ?

[bdickhaus]

It is a plugin for HomeSeer. The JowiHue plugin collects the data using the deCONZ REST API and then the Data History plugin logs the data in a database on the HomeSeer system.

[Hypfer]

Can confirm.

This seems to be related to the battery level of the temperature sensor. The frequency of these false readings increases with the battery voltage drop.

[Smanar]

Yep, but if someone know how bad data looks, it will be possible to ignore bad data in API code, but without that ...
No-one have some log, at least the websocket return to check the bad data, to reconize them ?

[jo-me]

I have the same issue on deconz 2.05.69 with Firmware 26330500 on Conbee (1) connected to homeassistant 0.99.

I'm seeing this for 2 out of my 3 Aqara Temp Sensors but only for temperature values and not for humidity/pressure.

Xiaomi Temp Sensor also seem to work fine.

Could these be filtered out by deconz?

The spec says they have a temp range of -20 to 60 ° C (+ / - 0,3 ° C). So all values outside of this range should be discarded.

[Smanar]

Have you tried to change battery ? cf > https://www.domoticz.com/forum/viewtopic.php?f=68&t=29370

[NigelRook]

Confirmed that changing the battery works for one of my devices. That domoticz post suggests that the issue is present when using the official xiaomi gateway, which suggests the error is coming from the sensor itself rather than an deconz bug.

[ebaauw]

I'm seeing the same. As far as I can tell, the -100°C is reported by the Xioami special report; the regular attribute reports for the Measured Value of the Temperature Measurement cluster seem OK. The sensor reports 30.05V for the battery, which is still mapped to 100%. Apart from the odd temperature value, the sensor seems to function normally, sending both regular and the Xiaomi special attribute reports.

[ebaauw]

Damn, the -100°C is also reported by the regular attribute report for 0x0402/0x0000.

[alex3305]

I also had this issue (#1708) and for me the fix was very trivial, as my battery was just low. Also a given solution by @Smanar.

Although I think invalid reading handling can also be improved in deconz (for these sensors).

[jo-me]

@ebaauw 's fix should be in the latest version. I'm not seeing the -100° since I upgraded yesterday afternoon. Do you?

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[Mimiix]

It seems this issue is resolved or otherwise inactive. If it is not, please re-open!

[hille721]

It seems this issue is resolved or otherwise inactive. If it is not, please re-open!

Currently facing this issues with one of my Aqara sensors. Showing up since Tueasday, and now happens 2 to 3 times a day.
Conbee 2 with Firmware 26720700 and Phoscon v2.17.01

[Mimiix]

Hi there,

This is a very old issue.

Please check your battery (replace it) and update conbee firmware.

If that doesn't fix it, please open an topic on the forums :)