the purpose of this is to roughly right determine the daily average power peaks per month as defined by Ellevio in Sweden here:
https://www.ellevio.se/abonnemang/ny-prismodell-baserad-pa-effekt/
and to ultimately use this for load shedding / balancing / planning by being able to set a maximum allowed power each hour (based on the usage peaks and prices) to keep the peaks and prices lower.

After a few days, the data collection is all now seemingly working pretty well (except step 7 which i just fixed). I could use some advice / tips / ideas to improve it!
graphically in apex charts it is looking like this for checking/debug:

yeah, a lot of data, it is taking me 7 steps (8 maybe in the end?). what is nice with Apex has been to be able to turn off everything and then go step by step through it to gain an understanding and see it is working. It has recovered well with various hiccups but I have NOT checked this vs Ellevio in detail but I suspect it will not be 100% as the import data I have is not 100%, again the idea is to get roughly right.
if you want to try have a look, see below install and process to understand

help, advice, tips, improvements?

I am guessing as I am not so great at yaml that there are some improvements to be made here, some things I have identified

1. time shifts - but maybe someone better at templating can help (?) with some ideas how to avoid the time shifts that grow till end of month where the final value will be on the 2nd each month (as the last peak of the day is not ready until the 1s and all values are for the previous hour). Sequencing of the triggers would be nice I think but as the code is a trigger depends on the previous value with actions and well, I don’t know how to do that.
2. sensor names - maybe i should have named the sensors better as well. eg… it is not the hourly average now it is the hourly average of the last hour … but if time shifts are fixed then they are maybe ok?
3. the initialization of 7 is annoying as well … i looked at doing it with a input text instead but went back to this and well … maybe it was better with an input_text as it can be at least initialized
4. package / blueprint? looked at blueprint but i don’t think they accept trigger sensors
5. more?

install

1 post - 1 participant

Read full topic