Currently, the load is preconfigured via a CSV file. This requires constant attention to adjust it to the given circumstances in your house. I bet last January will be different then this January.
I propose to add a configuration of another possible source for the consumption: a generic url endpoint.
We propose the usage the following parameters:
- weekday (0-6) Monday is 0
- weekday2 (0-1-7) Sunday is 0 & 7
- month
- hour_abs , 0-23 hour
- hour_rel , 0 current hour ; 1 next hour
And a url config like:
- url_template: "http://.../{weekday}/{hour_abs}
- return: single-value
The template is parsed and the expected return of the url is a single value response like 350 , which corresponds to 350w usage for the requested hour.
This offers the possibility to experienced users for a running consumption calculation, based on their wishes.
In my case, I would calculate the value off the influxdb values provided by evcc, which is excluding my wallbox.
Currently, the load is preconfigured via a CSV file. This requires constant attention to adjust it to the given circumstances in your house. I bet last January will be different then this January.
I propose to add a configuration of another possible source for the consumption: a generic url endpoint.
We propose the usage the following parameters:
And a url config like:
The template is parsed and the expected return of the url is a single value response like 350 , which corresponds to 350w usage for the requested hour.
This offers the possibility to experienced users for a running consumption calculation, based on their wishes.
In my case, I would calculate the value off the influxdb values provided by evcc, which is excluding my wallbox.