Home Assistant release with the issue:
0.97.0
Last working Home Assistant release (if known):
0.96.5
Operating environment (Hass.io/Docker/Windows/etc.):
HassOS 3.4 on RaspBerry PI 3B+
Component/platform:
buienradar.sensor
https://www.home-assistant.io/components/sensor.buienradar/
Description of problem:
The sensor I want to monitor works as expected, but there are warnings shown in the log. Are they caused by the new json buienradar-api? Warning occurs every time Buienradar tries to retrieve data.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
- platform: buienradar
latitude: !secret location_latitude
longitude: !secret location_longitude
monitored_conditions:
- irradiance
Traceback (if applicable):
2019-08-08 07:19:11 WARNING (MainThread) [buienradar.buienradar_json] Data element with key='barometerfc' not loaded from br data!
2019-08-08 07:19:11 WARNING (MainThread) [buienradar.buienradar_json] Data element with key='barometerfcname' not loaded from br data!
2019-08-08 07:19:11 WARNING (MainThread) [buienradar.buienradar_json] Data element with key='barometerfcnamenl' not loaded from br data!
2019-08-08 07:19:11 WARNING (MainThread) [buienradar.buienradar_json] Data element with key='pressure' not loaded from br data!
Hey there @mjj4791, @ties, mind taking a look at this issue as its been labeled with a integration (buienradar) you are listed as a codeowner for? Thanks!
Rverm
These warnings are indeed caused by the buienradar component; when an update is requested the library will retrieve the json data from the closest station (either the location configured in home assistant or the location configured in the component). In your case, you seem to have configured the buienradar component with a specific location.
The warning you see here is that some data elements are missing from the retrieved data. We support a data element called _pressure_ (the others depend on pressure). As it seems, your selected station does not have a (air)pressure data-element in its json, thus causing the warning.
it seems there are several stations that do not have it:
Questions:
If you are just interested in not seeing this warning anymore:
logger:
default: warning
logs:
buienradar.buienradar: error
buienradar.buienradar_json: error
Hi mjj4791
The location i'm using is in your list: "Ell (6377)". The warning looks continous to me, I can't see a pattern in time / day / night.
I've added the logger configuration to hide the warning. It's no longer added to "home-assistant.log", but still on the "Developers Tools" page, tab "Info". Is this behavior expected?
Same problem here, using Stationname "Nieuw Beerta (6286)"
Also interested in how the logger works, only affects the .log file itself and indeed not the dev tools output.
Data element with key='visibility' not loaded from br data!
9:13 AM components/buienradar/sensor.py (WARNING) - message first occured at August 9, 2019, 5:47 PM and shows up 93 times
Data element with key='pressure' not loaded from br data!
9:13 AM components/buienradar/sensor.py (WARNING) - message first occured at August 9, 2019, 5:47 PM and shows up 93 times
Data element with key='barometerfcnamenl' not loaded from br data!
9:13 AM components/buienradar/sensor.py (WARNING) - message first occured at August 9, 2019, 5:47 PM and shows up 93 times
Data element with key='barometerfcname' not loaded from br data!
9:13 AM components/buienradar/sensor.py (WARNING) - message first occured at August 9, 2019, 5:47 PM and shows up 93 times
Data element with key='barometerfc' not loaded from br data!
9:13 AM components/buienradar/sensor.py (WARNING) - message first occured at August 9, 2019, 5:47 PM and shows up 93 times
So; the warning is correct; the data does not contain a airpressure element.
If you don't want the warning to show up, i would modify the logger config (for now).
Seeing that several stations do not have all elements (including airpressure, but others as well), i might change the buienradar library sometime to not output this as a warning, since this seems far more common than I anticipated....
I always understood that the dev tools also look at the logging in the logfile, so I also expected the warning to be gne after you reconfigure the logger and restart HA. If it doe snot, not sure how this works....
Did you try clicking on clear? do they remain even after that?
Doesn't work that way I noticed...
Already set this in my configuration.yaml:
logger:
default: critical
...but that results in only a 0KB home-assistant.log, not affecting the dev tools output
Thanks tho!
Few more warnings occured in the last days, nothing changed in the configuration except HA is now version 0.97.2.
Data element with key='rainlast24hour' not loaded from br data!
Data element with key='rainlasthour' not loaded from br data!
Data element with key='precipitation' not loaded from br data!
2019-08-29 14:41:43 WARNING (MainThread) [buienradar.buienradar_json] Data element with key='visibility' not loaded from br data!
2019-08-29 15:43:13 WARNING (MainThread) [buienradar.buienradar_json] Data element with key='barometerfc' not loaded from br data!
2019-08-29 15:43:13 WARNING (MainThread) [buienradar.buienradar_json] Data element with key='barometerfcname' not loaded from br data!
2019-08-29 15:43:13 WARNING (MainThread) [buienradar.buienradar_json] Data element with key='barometerfcnamenl' not loaded from br data!
2019-08-29 15:43:13 WARNING (MainThread) [buienradar.buienradar_json] Data element with key='pressure' not loaded from br data!
2019-08-29 15:43:14 WARNING (MainThread) [buienradar.buienradar_json] Data element with key='barometerfc' not loaded from br data!
2019-08-29 15:43:14 WARNING (MainThread) [buienradar.buienradar_json] Data element with key='barometerfcname' not loaded from br data!
2019-08-29 15:43:14 WARNING (MainThread) [buienradar.buienradar_json] Data element with key='barometerfcnamenl' not loaded from br data!
2019-08-29 15:43:14 WARNING (MainThread) [buienradar.buienradar_json] Data element with key='pressure' not loaded from br data!
2019-08-29 14:41:43 WARNING (MainThread) [buienradar.buienradar_json] Data element with key='visibility' not loaded from br data! 2019-08-29 15:43:13 WARNING (MainThread) [buienradar.buienradar_json] Data element with key='barometerfc' not loaded from br data! 2019-08-29 15:43:13 WARNING (MainThread) [buienradar.buienradar_json] Data element with key='barometerfcname' not loaded from br data! 2019-08-29 15:43:13 WARNING (MainThread) [buienradar.buienradar_json] Data element with key='barometerfcnamenl' not loaded from br data! 2019-08-29 15:43:13 WARNING (MainThread) [buienradar.buienradar_json] Data element with key='pressure' not loaded from br data! 2019-08-29 15:43:14 WARNING (MainThread) [buienradar.buienradar_json] Data element with key='barometerfc' not loaded from br data! 2019-08-29 15:43:14 WARNING (MainThread) [buienradar.buienradar_json] Data element with key='barometerfcname' not loaded from br data! 2019-08-29 15:43:14 WARNING (MainThread) [buienradar.buienradar_json] Data element with key='barometerfcnamenl' not loaded from br data! 2019-08-29 15:43:14 WARNING (MainThread) [buienradar.buienradar_json] Data element with key='pressure' not loaded from br data!
This does not appear to be consistently happening for that station. When this occurs, can you check whether the data is available on KNMI.nl on their observations page?
Dat is sometimes not reported by stations (for example: Houtribdijk and Ijmuiden are not reporting a temperature right now).
Marc, Ties
I am also seeing this behavior.
It seems that sometimes data elements are randomly missing from the json we
get from the buienradar API; even though they are usually there for that
station.
My station usually shows all elements i used for home assistant, but i
captured one occurrence in my HA logs with this warning and when i checked
the json, the element was actually not there....
What I will do is create an updated version of the buienradar library, to
remove the warning (will make it a debug message) and then provide an
update to the buienradar component to use the new library;
the missing dataelement will still not be updated (until it is back again
in the json), but at least there will not be a warning anymore....
On Thu, Aug 29, 2019 at 7:19 PM Ties de Kock notifications@github.com
wrote:
2019-08-29 14:41:43 WARNING (MainThread) [buienradar.buienradar_json] Data element with key='visibility' not loaded from br data!
2019-08-29 15:43:13 WARNING (MainThread) [buienradar.buienradar_json] Data element with key='barometerfc' not loaded from br data!
2019-08-29 15:43:13 WARNING (MainThread) [buienradar.buienradar_json] Data element with key='barometerfcname' not loaded from br data!
2019-08-29 15:43:13 WARNING (MainThread) [buienradar.buienradar_json] Data element with key='barometerfcnamenl' not loaded from br data!
2019-08-29 15:43:13 WARNING (MainThread) [buienradar.buienradar_json] Data element with key='pressure' not loaded from br data!
2019-08-29 15:43:14 WARNING (MainThread) [buienradar.buienradar_json] Data element with key='barometerfc' not loaded from br data!
2019-08-29 15:43:14 WARNING (MainThread) [buienradar.buienradar_json] Data element with key='barometerfcname' not loaded from br data!
2019-08-29 15:43:14 WARNING (MainThread) [buienradar.buienradar_json] Data element with key='barometerfcnamenl' not loaded from br data!
2019-08-29 15:43:14 WARNING (MainThread) [buienradar.buienradar_json] Data element with key='pressure' not loaded from br data!This does not appear to be consistently happening for that station. When
this occurs, can you check whether the data is available on KNMI.nl on
their observations page https://knmi.nl/nederland-nu/weer/waarnemingen?Dat is sometimes not reported by stations (for example: Houtribdijk and
Ijmuiden are not reporting a temperature right now).—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/home-assistant/home-assistant/issues/25767?email_source=notifications&email_token=AF36HR2ZZ6GSKV5VCKZBETLQHAAI5A5CNFSM4IKGPRQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5PGO7Y#issuecomment-526280575,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF36HRZPUYTUCXT7DIC5YDDQHAAI5ANCNFSM4IKGPRQQ
.
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
Please keep open, I see this still on 102.1:
Data element with key='irradiance' not loaded from br data!
I haven't set irradiance as a monitored condition for the sensor, because of the error since way back, and still the system errors out on this.
sensor:
- platform: buienradar
monitored_conditions:
- barometerfc
- barometerfcname
- condition
- conditioncode
- conditiondetailed
- conditionexact
- feeltemperature
- humidity
# - irradiance
- pressure
- groundtemperature
- precipitation
- precipitation_forecast_average
- precipitation_forecast_total
- stationname
- symbol
- temperature
- visibility
- windspeed
- windforce
- winddirection
- windazimuth
- windgust

my weather component configuration is as simple as can be:
weather:
- platform: buienradar
name: !secret buienradar_station
could it be this is trying to read irradiance while the station doesn't have it?
Still happening in 102.3. I use station 'IJmuiden' (see above), which has limited data in the data stream, which causes the log entries. For conditions not reported by IJmuiden I use Schiphol.
Same problem here, homeassistant 104.2.
Tue Jan 21 2020 17:18:04 GMT+0100 (Midden-Europese standaardtijd)
Data element with key='rainlast24hour' not loaded from br data!
configuration.yaml:
sensor:
- platform: buienradar
latitude: 52.92
longitude: 4.77
monitored_conditions:
- stationname
- symbol
- condition
- conditioncode
- conditiondetailed
- conditionexact
- humidity
- temperature
- groundtemperature
- windspeed
- windforce
- winddirection
- windazimuth
- pressure
- visibility
- windgust
- precipitation
- irradiance
- symbol_1d
- symbol_2d
- symbol_3d
- symbol_4d
- symbol_5d
- temperature_1d
- temperature_2d
- temperature_3d
- temperature_4d
- temperature_5d
- rainchance_1d
- rainchance_2d
- rainchance_3d
- rainchance_4d
- rainchance_5d
- sunchance_1d
- sunchance_2d
- sunchance_3d
- sunchance_4d
- sunchance_5d
- rain_1d
- rain_2d
- rain_3d
- rain_4d
- rain_5d
- precipitation_forecast_average
- precipitation_forecast_total
105.5: I also have a lot of warnings about conditions not being monitored. Here is my config:
- platform: buienradar
timeframe: 20
monitored_conditions:
- symbol
- conditiondetailed
- precipitation_forecast_average
- precipitation_forecast_total
- temperature_1d
- irradiance
Here is a part of a long list of warnings:
Data element with key='windazimuth' not loaded from br data!
Data element with key='winddirection' not loaded from br data!
Data element with key='windgust' not loaded from br data!
Same problem here. Using Ell weatherstation. Missing pressure and barometer values.
Hass version 0.106.4
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
Most helpful comment
Marc, Ties
I am also seeing this behavior.
It seems that sometimes data elements are randomly missing from the json we
get from the buienradar API; even though they are usually there for that
station.
My station usually shows all elements i used for home assistant, but i
captured one occurrence in my HA logs with this warning and when i checked
the json, the element was actually not there....
What I will do is create an updated version of the buienradar library, to
remove the warning (will make it a debug message) and then provide an
update to the buienradar component to use the new library;
the missing dataelement will still not be updated (until it is back again
in the json), but at least there will not be a warning anymore....
On Thu, Aug 29, 2019 at 7:19 PM Ties de Kock notifications@github.com
wrote: