Open ksmolder opened 1 year ago
Tried to dig a bit deeper into the issue by creating an entity weather.openweathermap
for the daily forecasts and one named weather.openweathermap_hourly
for the hourly forecasts. Assumed that pointing v-weather-card to the one without the _hourly
suffix would make the card behave as intended when hourly_forecast
is enabled. Didn't do the trick however... So, not sure if the above assessment makes any sense...
Checklist:
Release with the issue:
Last working release (if known):
Browser and Operating System:
Description of problem:
Context
entity.openweathermap
. The second one fetches daily forecasts and is known asentity.openweathermap_daily
.sensor.openweathermap_cloud_coverage
. The same sensor associated with the daily forecasts is namedsensor.openweathermap_cloud_coverage_daily
Issue
Here, everything works as expected. v-weather-card correctly takes the date from the
weather.openweathermap_daily
entity.Here, things are broken as the card is simply not displayed (note that I'm using the correct entity for hourly forecasts). If I set
hourly_forecast
tofalse
without changing anything else, the card is rendered. It is however not using the time as a reference for each of the forecasts, but repeats the day names:Additional information: Looking at the code, I suspect line 321 in card.ts to be the source of the issue. It seems when
hourly_forecast
is enabled, the suffix_hourly
is appended to the entity's name. In reality, this entity does not need to have that name. You just need to know you configured an entity to fetch hourly predictions. SO my guess is that you don't need to append anything to the entity's name. A user just need to make sure that the correct entity is used when suggesting it provides hourly forecasts.