Recurrence of issue from #287

[phurth]

Recurrence of issue from #287

[phurth]

I modified my NodeRed flow to delete the supported_features attribute and now it is working as expected. Thanks!

[pkissling]

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?

[phurth]

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.

[pkissling]

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

1. override supported_features:6 with supported_features: 0
2. omit the attribute entirely

this way, clock-weather-card will read the forecasts from the forecast attribute and will not try to subscribe to the weather service