If the friendly_name is “forecast 1”, “forecast 2” and so on, yes it did, however I triggered the automation manually. How long do you suggest me to wait for the automation? By the way Hassio just showed me an update to 0.63 which is being installed now.
So I have finally come back to this and it’s working nicely.
I created a group to put all the extra sensors into one group.
I then want to hide that group so it does not display but if I run the service group.set_visibility with the entity_id set to this group and visible: False it takes it out of the group display and throws the icons back up the top of the screen again.
I have all my sensors in a group and they all display on the one page - I don’t have multiple pages or tabs.
What do I need to do to hide all these sensors? I am using the weather.yaml I downloaded and also the python script to make friendly names.
Implementation of friendly_name_template for template sensor got released with 0.64
So instead of running a script it should now be possible to update the names like this.
forecast_1:
friendly_name_template: >
{%- set date = as_timestamp(now()) + (1 * 86400 ) -%}
{{ date | timestamp_custom("Tomorrow (%-m/%-d)") }}
...
forecast_2:
friendly_name_template: >
{%- set date = as_timestamp(now()) + (2 * 86400 ) -%}
{{ date | timestamp_custom("%A (%-m/%-d)") }}
...
note, to get the correct date/time offset you need to modify the 2 * 86400 calculation for each forecast sensor.
So to clarify… I can overwrite my current weather.yaml with your new one and delete the python script?
I still need the icons I downloaded. I remove the python script from configuration.yaml