waltervl wrote: ↑Monday 05 June 2023 9:09
Why do you need them as current data?
Hello,
I think I experienced the same kind of issue: Only data for such sensors (global home power in my case, from a Qubino Smart-Meter at the head of my fuse panel, sending I/V/W/CosPhy to Domoticz on a few % change in my case) that makes it's way to DB (thus graphs) are sampled every 5mn. That may (rarely!) or may not (99.66%, considering the lucky second over 300s=5mn?) be a min/max for the 5mn sampling period.
=> Had to build a virtual sensor that gets fed by a Lua script that records true max (only for W) in my case, on a 10mn period (>5 mn Domoticz slices, to avoid loosing some samples). This allowed me to notice my true instant power maxes were almost every day/weeks several kW higher than expected from Domoticz graphs, so I was at risk of power cuts on exceeding my provider max allowed instant power drain!
So this 5mn sampling makes current data mostly false, even if I understand that this was probably done to avoid too much DB grow if recording true min/max as a core function for every sensor in the 5mn slices on top of current sample value.
Maybe another (slave) sensor type could be attached to an existing one with the option to record true slices min/max only for data that makes sense (in my case, I just choose to record true max & only for W, skipping I/V/CosPhy) and on a configurable time slice (than may exceed 5mn): This would be user decision to target records+periodicity to avoid DB size increase too much.
This would also not disturb current sensors use-cases...
Another addition I'm doing in script in the same way (somehow integrating every device samples over last_update time slices, as device last_update is luckily still updated even if data is not recorded by default, allowing to script this as a Lua device script that does not offer data persistence between calls) is calculating/recording (approx) power average values, on a 10mn time frame as well in another power average virtual sensor. Some devices are able to compute/record true averages over a configurable period but that's not the case for mine...
=> Such slave sensor introduction able to record, on user selection, min/max/average over a configurable period would be a nice Domoticz core addition, even if this can currently be scripted as Domoticz is quite flexible/well designed on this.
EDIT: Average addition would probably help a lot users in countries/regions that now have power contracts taking into account the day max average consumption over a quarter for billing! Monitoring averages over a sub-period (10mn?) would allow them to trigger targeted heavy consumer stop (for next 5mn?) to smooth their daily quarter power peaks thus keep lower electricity prices.
