Closed kaizersoje closed 9 months ago
Crap. First thing found and resolved in the code. I forget to test for the availability of item [1] before accessing it. Currently evaluating why it is missing. I'm continuously testing with five different locations and they all work fine in regards the forecast. But a 6th test location in Chile fails with the same error. Out of curiosity, my I ask for your location?
Found it. I will draft a new release tomorrow.
Until then change the dependency to pyastroweatherio
in manifest.json
to
"requirements": [ "pyastroweatherio==0.42.4" ],
Crap. First thing found and resolved in the code. I forget to test for the availability of item [1] before accessing it. Currently evaluating why it is missing. I'm continuously testing with five different locations and they all work fine in regards the forecast. But a 6th test location in Chile fails with the same error. Out of curiosity, my I ask for your location?
I am located in Melbourne, Australia
Found it. I will draft a new release tomorrow. Until then change the dependency to
pyastroweatherio
inmanifest.json
to
"requirements": [ "pyastroweatherio==0.42.4" ],
This fixed the issue.
Calculating all these moving objects for any global location, time, and timezone sometimes screws my head ;-). Thank you for testing. Will create a release then.
After upgrading to v0.42.0, the following entities are not getting set up -
sensor.astroweather_deepsky_forecast_tomorrow
sensor.astroweather_deepsky_forecast_tomorrow_plain
weather.astroweather_home
This is what I can see in the logs.