Closed kaizersoje closed 3 months ago
First - Yes I know. It's because the lovelace card still uses the forecast attribute and I wasn't able to figure out how I can call the service from the card. Quickly checking other weather integrations like OpenWeatherMap and Deutscher Wetterdienst all have the attribute still enabled. Did you find any example of a proper lovelace card using the new service?
Second, uups - I always forget to update the version in the one or the other place. Will correct it, thanks.
I noticed that after upgrading to v0.23.2, the weather attribute still contains the forecast attribute. I am not sure if the weather entity should contain the forecast attribute, unless I am mistaken.
I also noticed the
manifest.json
file shows the version as0.23.1