Aqara WSDCGQ11LM
deCONZ 2.32.5
Reading values from PWA API with Zabbix.
If I restart deCONZ [because of issues with Home Assistant, see other threads], the temperatures jump around implausibly:
Every temperature has suddenly jumped. The pressure and humidity behave the same.
Is this likely to be a deCONZ issue, or is it the sensors?
Odder still, in the PWA, Kitchen is showing as 14°C, which is higher than expected from the above trend, but Updated is from 6 days ago? Doesn’t make sense.
You need a new battery.
On all of them?
Aqara/Xiaomi device make report every hours maximum, so 6 days without report generaly mean battery issue.
I don’t think it’s a connexion issue else the device will be grayed and marked as unreachable.
But yes the jump is strange ^^.
Devices can take 1 hours before making their first real report (if temperature don’t move), idk what is the defaut value at start. But it’s strange you have all sensors starting to send report at exaclty same time, around 21h20, for me it’s not real reports.
Perhaps it’s not clear, but it’s nonsense, it was definitely reporting data because I am polling it from deCONZ API with Zabbix, this is in the graph.
But the value is changing during thoses 6 days ?
Polling the API don’t give actual temperature value, it just give more recent report value, if the temperature don’t move enougt the device just don’t make report, if you poll the API or not.
Even if the device disconnect, you can poll the API and have values.
Yes - I have a trigger in Zabbix that fires if value has not changed for 4h, this alerts me when sensor has dropped off. The “reachable” value in API takes a lot longer to change, hence using this trigger.
So issue is that deCONZ is returning some remembered value from some time in the past after a service restart, which happens to not be the most recent value before it went offline. Then sensor reconnects and things return to normal.
Yes exactly, I have another user whith the same issue (he don’t make poll, but ask for value at start), probably nothing to see, but you are using docker or classic OS ?
On my side I m using websocket, so I have only new value.
And looking your graph, the green line go to 23°C at restart, long time you haven’t this value, IDK why deconz have stored this one.
Here you have save databse delay
#define DB_HUGE_SAVE_DELAY (60 * 60 * 1000) // 60 minutes
#define DB_LONG_SAVE_DELAY (15 * 60 * 1000) // 15 minutes
#define DB_SHORT_SAVE_DELAY (1 * 60 * 1000) // 1 minute
#define DB_FAST_SAVE_DELAY (1 * 1000) // 1 second
But I have another question, if value are changing, why the last updated date is 6 days …
Can you share the complete device json ?
Had to restart deCONZ because it crashed when Home Assistant was restarted and again there is a spike in values:
If this is some “cached” value then it is from some time last year, my office has not been 22°C for at least 6 months.
And if I m right it’s exaclty same valued after the crash than on your previous capture (the first post) ?
Have you tried to take a look on the database ?
And if you close and re-open deconz, not a crash, same result ?
Ah, well spotted.
It looks like a simple restart of deCONZ does not cause this behaviour. I am going to try leaving it closed for a while longer and see what it does.
I will also have a poke about in the database.
