You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
By default the card shows the forecast of the next 5 days - beginning with tomorrow.
I would like to begin with today. While I can already set the correct values if I begin with the “_0” values instead of “_1” in the config, the day names don’t reflect this.They start with FR (Friday) instead of today (Thursday).
IMO this is more elegant and space-saving than adding the same info above the forecast row. And predictions for more than 3 days in the future are inaccurate anyway.
Solution idea: allow config of a forecast start day (e.g. 0, 1, 2) and possible number of days so that the forecast shows e.g. today + 3 days or tomorrow + 4 days.
If you want to refactor a bit, you could think about removing the almost duplicate references to entity ids (.._0, .._1,...) and just have the user configure the prefix.
By default the card shows the forecast of the next 5 days - beginning with tomorrow.
I would like to begin with today. While I can already set the correct values if I begin with the “_0” values instead of “_1” in the config, the day names don’t reflect this.They start with FR (Friday) instead of today (Thursday).
IMO this is more elegant and space-saving than adding the same info above the forecast row. And predictions for more than 3 days in the future are inaccurate anyway.
Solution idea: allow config of a forecast start day (e.g. 0, 1, 2) and possible number of days so that the forecast shows e.g. today + 3 days or tomorrow + 4 days.
If you want to refactor a bit, you could think about removing the almost duplicate references to entity ids (.._0, .._1,...) and just have the user configure the prefix.
See here for the original forum post: https://community.home-assistant.io/t/custom-dark-sky-animated-weather-card/59816/1002
The text was updated successfully, but these errors were encountered: