Closed phurth closed 7 months ago
hi @phurth, can you please elaborate on your following statement:
in this case, the weather entity is set via the HA API
what do you mean by that? can you clarify?
Yes, sorry. I have a NodeRed flow set up that allows me to switch between predefined locations (and the related weather forecast). To do this, I have a weather entity set up in configuration.yaml which gets set via the HA API in NodeRed. The flow simply sets the custom location attributes from the JSON payload of the appropriate NWS entity attributes.
Using this weather entity allows me to set the front end up such that it updates automatically if the location is changed by the flow.
With the above, in version 2.1.3 of the card, the forecast displayed as expected. In subsequent versions, it does not.
Thanks in advance, and let me know if you need for specific details.
okay i see, thanks for the explanation.
the weather entity you are emulating exposes supported_features: 6
. this indicates, that the weather entity does support the new weather.get_forecast
service (https://www.home-assistant.io/integrations/weather/#service-weatherget_forecast). consequently clock-weather-card tries to subscribe to weather updates (which will fail - hence the forecast is not rendered properly).
please try to either
supported_features:6
with supported_features: 0
this way, clock-weather-card will read the forecasts from the forecast
attribute and will not try to subscribe to the weather service
I modified my NodeRed flow to delete the supported_features attribute and now it is working as expected. Thanks!
I am seeing the same issue as closed bug #287 except this happens in the following situation:
In a separate Home Assistant install I am still getting the same error and the forecast is not rendering after updating to 2.1.8. In this case, the weather entity is set via the HA API, but is otherwise the same NWS weather object. This also worked just fine on 2.1.3. Below I'm including the attributes first from weather.kimt_daynight, then from weather.custom_location which is set to the value of the first via the API. They should be identical, but when using weather.custom_location in the clock weather card no longer displays the forecast days.