a yes, thanks.
how odd this has changed to something so incorrectā¦ what on earth is āNepaliāā¦other than Nepal, where we obviously are not, given the gps coordinates.
the full feedback changed though, because before we could filter on ānederlandsā and āfrancaisā.
Ive changed the template for now to:
Description: >
{% if states('sensor.weatherbit_weather_alerts')|int > 0 %}
{{state_attr('sensor.weatherbit_weather_alerts','alerts')
[0].description.split('ne-NL):')[1].split('English(en-GB):')[0]}}
{% else %} No alert
{% endif %}
This helped me, thankyou
I had assumed that the integration would pull the pollen count as entities, rather than having to request it through the API. Once I saw the link you had been struggling with, I realised what I had to do
I saw that in the release notes for 2021.6. I will need to check up on how this is implemented, but I assume it can be done. Could you please create an issue on Github, so I donāt forget?
I have a similar location issue that another user posted early on: my exact lat/lon is set in HA, but the Weatherbit integration sets a location that is several miles away. Your instructions indicated that other locations can be added, but there were no further instructions as to how this is to be accomplished. Iām a noob at this - can you elaborate what I need to modify to get one of the closer Weatherbit stations added to my integration?
Also, is ther a fix for the default 3 mi visibility issue?
Iāve been playing with several of the weather integrations and so far, Weatherbit seems to be more accurate for my (approximate) location than several of the others.
Hello DBB1
It is WeatherBit that picks the station closest to your Latitude/Longitude and it might just be that this is several miles away.
But I am in the process of completely rewriting the Integration and its WeatherBit communication module, so I will look in to this issue while doing that, to see if there is an option to ensure the closest possible station.
I expect a beta of the new Integration within a week.
Hoping someone can give me a little guidance on the subject issue I am seeing within my home assistant.
Below is the information from my logs. Can you all think of what could be causing this?
To my knowledge I havenāt changed anything with my setup. Could multiple home assistant restarts cause this?
File "/usr/local/lib/python3.9/site-packages/pyweatherbitdata/api.py", line 103, in update_sensors
File "/usr/local/lib/python3.9/site-packages/pyweatherbitdata/api.py", line 313, in _async_request
pyweatherbitdata.exceptions.InvalidApiKey: The API Key used is not valid. Try again with a new key.
2022-06-20 14:33:12 ERROR (MainThread) [custom_components.weatherbit] Unexpected error fetching weatherbit data: The API Key used is not valid. Try again with a new key.
File "/config/custom_components/weatherbit/__init__.py", line 117, in async_update_forecast
data: ForecastDescription = await weatherbitapi.update_forecast()
File "/usr/local/lib/python3.9/site-packages/pyweatherbitdata/api.py", line 196, in update_forecast
File "/usr/local/lib/python3.9/site-packages/pyweatherbitdata/api.py", line 313, in _async_request
pyweatherbitdata.exceptions.InvalidApiKey: The API Key used is not valid. Try again with a new key.
2022-06-20 14:33:13 ERROR (MainThread) [custom_components.weatherbit] Unexpected error fetching weatherbit data: The API Key used is not valid. Try again with a new key.
File "/config/custom_components/weatherbit/__init__.py", line 108, in async_update_data
data: ObservationDescription = await weatherbitapi.update_sensors()
File "/usr/local/lib/python3.9/site-packages/pyweatherbitdata/api.py", line 103, in update_sensors
File "/usr/local/lib/python3.9/site-packages/pyweatherbitdata/api.py", line 313, in _async_request
pyweatherbitdata.exceptions.InvalidApiKey: The API Key used is not valid. Try again with a new key.
Ahhh, I accidentally selected āFree Business Trialā which had a 30 day caveat rather than āFreeā when I signed up last month. Screenshot below for anyone accidentally doing the same thing as me in the future.
My Weatherbit integration was working normally for some time.
But yesterday I discovered that all entities had status unknown.
I since tried multiple times to remove the integration, restart HA, and re-add the integration.
This works every time but the integration only creates a device without any entities (see screenshot).
The logs show this error:
* Unable to prepare setup for platform weatherbit.weather: Platform not found (cannot import name 'ATTR_FORECAST_NATIVE_PRECIPITATION' from 'homeassistant.components.weather' (/usr/src/homeassistant/homeassistant/components/weather/__init__.py)).
* Unable to prepare setup for platform weatherbit.sensor: Platform not found (cannot import name 'ATTR_FORECAST_NATIVE_PRECIPITATION' from 'homeassistant.components.weather' (/usr/src/homeassistant/homeassistant/components/weather/__init__.py)).
Any ideas? Am I the only one? Is your integration still working as expected?
Hi Jƶrg,
Did you upgrade to 1.0.11? This version only works with Home Assistant 2022.7 and greater. I put that as a minimum version in HACS, but maybe you upgraded without using HACS.
Anyway, you can either downgrade to 1.0.10 again or wait until 2022.7 is released - I guess this Wednesday.