andreasd

thanks for the quick response! i think it's just important to not limit this awesome extension by the price sources. so providing a generic price source that can either be...

is there anything i could do to help adding support for a broader range of price data sources? it seems like a defined structure for a sensor and then using...

hi! thanks for the quick response. yes, I'm confident that I can construct such a sensor. I'm not entirely sure about the price_today and price_tomorrow attributes. the epex spot integration...

``` - sensor: - name: "epex_spot_transformed" state: > {{ states('sensor.epex_spot_data_net_price') | float }} attributes: prices_today: > {%- set hours_list = (state_attr('sensor.epex_spot_data_net_price', 'data') | sort(attribute='start_time',reverse=false)) %} {%- set today = namespace(items=[])...

@andreas-berg i have no play in ha_epex_spot and think a better approach for this integration would be to offer a standardized interface to read in price data, like in the...

having the same issue on my raspi (libreelec).

thanks for taking time to work on this! my template sensor was a quick proof of concept that it is possible to integrate different sources via templating to a format...

i'll take a look and will adapt the template sensor to fit this description! thank you!

i have modified the template sensor and it should now fit the format. * renamed attribute to "time" * fixed error where the today/tomorrow split used UTC instead of local...

i'll take a close look next week when I'm back home! thank you!