Graph Smoothing

Moderator: leecollings

Post Reply
Zith
Posts: 3
Joined: Thursday 11 February 2016 12:05
Target OS: Raspberry Pi / ODroid
Domoticz version:
Contact:

Graph Smoothing

Post by Zith »

Thanks to this great forum and the awesome dwellers within I was able to relatively easilly setup my own system at home, consisting of a 1wire temperature newtork and a SBFspot-based Solar Inverter reader.

Now, as I hinted, this works fine - apart from a cosmetic point regarding the "Generated Last 24 Hours" graph.
Is there a way to disable the "smoothing" that takes place when the graph is generated?
Since no measurements are dune during nighttime, Domoticz creates a smooth curve between the last registered points, which looks odd.
sbfspot curves.png
sbfspot curves.png (319.05 KiB) Viewed 1970 times
I put a workaround in place today, by forcing measurements even during the night, but ideally I would simply like the curve to treat null/missing values as zero.

Thanks!
crew_one
Posts: 2
Joined: Wednesday 14 January 2015 13:05
Target OS: Raspberry Pi / ODroid
Domoticz version:
Contact:

Re: Graph Smoothing

Post by crew_one »

In fact, a bar graph would make much more sense...
User avatar
bbqkees
Posts: 407
Joined: Sunday 17 August 2014 21:01
Target OS: Linux
Domoticz version: 4.1x
Location: The Netherlands
Contact:

Re: Graph Smoothing

Post by bbqkees »

crew_one wrote:In fact, a bar graph would make much more sense...
Well a bar graph would make sense for energy (kWh) but not for power (kW).
Bosch / Nefit / Buderus / Junkers / Worcester / Sieger EMS bus Wi-Fi MQTT Gateway and interface boards: https://bbqkees-electronics.nl/
crew_one
Posts: 2
Joined: Wednesday 14 January 2015 13:05
Target OS: Raspberry Pi / ODroid
Domoticz version:
Contact:

Re: Graph Smoothing

Post by crew_one »

Indeed.

I was in fact referring to graphs per month / year.
User avatar
gizmocuz
Posts: 2350
Joined: Thursday 11 July 2013 18:59
Target OS: Raspberry Pi / ODroid
Domoticz version: beta
Location: Top of the world
Contact:

Re: Graph Smoothing

Post by gizmocuz »

i think this happens because there is no short-log value stored when it did not receive any update

there are two solutions:
#1
- in the sbfspot class when there is no new data, send 0 as usage with the last counter

#2
fix it in the general function that adds a shortlog value

void CSQLHelper::UpdateMeter()
//do not include sensors that have no reading within an hour

void CSQLHelper::UpdateMultiMeter()
//do not include sensors that have no reading within an hour

could you try (for the test), go to the settings/other, for sensor timeout (default 60), set this to 1440 (1 day),
this might solve this problem because #2 is using this value
Quality outlives Quantity!
Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest