[Solved] Temperature Graph broken because of incorrect -3000°C value

---

how can I fix this? And how can I prevent that this happens in the future?
It’s never that cold in my living room…

you can try to delete the value at the database.
maybe this tool will help : http://sqlitebrowser.org/
but be aware of jnot messing up with your database! first do a backup of the pimatic-database.sqlite!
tried it with my backup system, not the live one. seems to work but i don’t give any warranty (especially for your stored data ! use on your own risk)

Open your database in the sqlitebrowser, then

1. click on browse data
2. filter the values from lowest to highest
3. mark the line with the wrong value
4. click on “Delete Record”
5. Write changes to file.
6. Pray

But howto prevent is another story. Do you know if there was something happening at that time? System reboot or some service running at high cpu load and so on?
What hardware do you use to measure the temp?

thanks, I’ll remove it that way.
I don’t know what happened, high CPU load could be, also I’m restarting pimatic all the time because I add or change things. But it only happened once in several days. Also possible that the DHT22 sensor failed.

please let me know if the database correction worked.

If you know sql: The debian repositories also have a cli-tool called “sqlite3”.
But how mentioned by leader21, only use it with stopped pimatic and a copy of the database.

removing the values worked without problems, I was also able to remove some other flawed values.

good to hear!
well then i would say : successfully [solved] this issue

using the cli-tool isn’t that comfortable and you exactly need to know what you want to do.
i also tried that once, but i was unable to cope with a bigger database.
so nothing for database noobs like me

the only thing that remains is the question how to prevent.
i would say have an eye on that, when it happens and what the pi did that time, check system state and so on.

Good morning,

I also have some incorrect values in my database. The way with stopping pimatic and deleting the values worked but I think it should be possible to prevent writing unrealistic values.
Perhaps it is possible to define a range for example an indoor temperature sensor between 0°C and 40°C? Or for an DHT22 a max humididity of 100%?

Could it be possible?

So, happy X-Mas and so on

@hansmerkel yes could be fine that we could give a range of acceptable values.
You can also use my post here to delete some unwanted values http://forum.pimatic.org/topic/988/database-tips-part-2

@Yves911 Thanks for the tip. I tried but was a little to complicated for me. 😉
I used a plugin for Firefox, this was a little bit more comfortable.
But I am testing different sensors and setups and there are often incorrect values and I don’t want to purge it every time. 😁

I have the same issue with my vaillant roomtemperature. 1 - 3x the week I get wrong values over 1000°C or -100°C.
To avoid the ugly graph I use the pimatic-filter plugin.

  {
      "plugin": "filter"
    }

    {
      "class": "SimpleTruncatedMeanFilter",
      "id": "filter2-raum",
      "name": "Raum-f2",
      "size": 5,
      "output": {
        "name": "temperature",
        "label": "Raum",
        "expression": "$vaillant_raum_temp.vaillant_room_temp",
        "acronym": "T",
        "type": "number",
        "unit": "°C"
      }