Closed purcell-lab closed 7 months ago
This is no longer a beta, all HA users that update to 2023.9 are recieving this message.
yep - there will be a flurry of us as we all update
https://github.com/bremor/bureau_of_meteorology/pull/190 seems to address this when I tested locally, am not sure if there's more to change however @bremor ?
It's a little bit bigger of a change to implement I suspect
https://developers.home-assistant.io/blog/2023/08/07/weather_entity_forecast_types
It seems like the WeatherDaily
and WeatherHourly
needs to get scrapped since the WeatherEntity doesn't need seperate entities for different forecast types. Is the solution to merge the two entities into one and define async_forecast_daily
and async_forecast_hourly
(I believe these can be same code from WeatherDaily.forecast
and WeatherHourly.forecast
?).
Hi folks. I've put up #193 to address this issue. It keeps things AS-IS for the moment but I think longer term need a discussion on unifying WeatherDaily
and WeatherHourly
and what that transition looks like as it will be a breaking change.
@evilmarty thanks for the work to fix this..
I have merged and created a pre-release v1.2.0. Please test and report any issues as well as any successes.
Installed the update - is there supposed to be a forecast imported now?
I thought in the past it had a 7 day forecast - but I can't seem to see that anymore?
Working for me. Thanks Simon and evilmarty.
The update fixed the notice, but now the hourly forecast is missing.. Any ideas?
I've lost hourly and daily forecasts. Can't seem to get them back despite deleting my sensors, redownloading via HACS and setting up sensors from scratch. Any tips appreciated
The code needs to be fixed to reenable the forecasts again. I can see how to do it but don't have time right now.
No urgency here ...
I tried the v1.2.0 pre-release, and it removed the HA warning but lost forecasts.
I reverted to v1.1.21, and forecasts resumed just fine. The HA warning is that the integration needs to be updated prior to HA 2024.3, so that's a full 5 months away yet.
For anybody who wants forecasts now, just use v1.1.21 of the BOM integration.
No urgency here ...
I tried the v1.2.0 pre-release, and it removed the HA warning but lost forecasts.
I reverted to v1.1.21, and forecasts resumed just fine. The HA warning is that the integration needs to be updated prior to HA 2024.3, so that's a full 5 months away yet.
For anybody who wants forecasts now, just use v1.1.21 of the BOM integration.
Thanks Tatham, did the trick. I didn't think I opted in for pre releases and blindly updated to get rid of the integration warning.
Looks like time is up, I had pinned to 1.1.21 of the BOM integration which has provided me forecasts.
Home Assistant 2024.4.b release seems to no longer present those forecasts ;-(
I don't think you need to pin to an old version any more; I'm not.
Try BOM integration 1.3.0 with 2024.4.
Everything is back in alignment.
Nice work, 1.3.0 has the BoM forecasts.
But no longer available as attributes ;-(
So I have to go from:
{{state_attr('weather.noosa_heads_hourly','forecast')}}
To something that calls a lot of services, stores those values somewhere so I can use them in an automation ;-(
https://community.home-assistant.io/t/petition-dont-delete-the-forecast-attribute/609298/240
That is not the integration developer's fault.
The core HA team have implemented this method for accessing forecasts for performance reasons.
Nice work on this integration.
I have just upgraded to HA 2023.9 beta and am receiving this error message.
HA 2023.9 is expected to be released on 6 September, at which point I would envisage you will get more users of your integration seeing this issue as it states the issue needs to be resolved before 2024.3.