Does the #Buienradar intergration for #HomeAssistant work for you?

I'm getting Unable to parse data from Buienradar. (Msg: Unable to parse content as json.) error in the logs.

Well... No wonder. API endpoint at https://data.buienradar.nl/2.0/feed/json return an application/json with just Buienradar.Weather.Models.JsonFeed inside.

The API endpoint seems to be working. But the integration still doesn't work.

2026-06-11 12:04:39.077 WARNING (MainThread) [buienradar.buienradar_json] Missing section in Buienradar xmldata (stationmeasurements).Can happen 00:00-01:00 CE(S)T
2026-06-11 12:04:39.078 DEBUG (MainThread) [buienradar.buienradar_json] Extracted weather-data: None
2026-06-11 12:04:39.078 DEBUG (MainThread) [homeassistant.components.buienradar.util] Buienradar parsed data: {'success': False, 'msg': 'No location selected.', 'data': None}
2026-06-11 12:04:39.078 WARNING (MainThread) [homeassistant.components.buienradar.util] Unable to parse data from Buienradar. (Msg: No location selected.)
2026-06-11 12:04:39.079 DEBUG (MainThread) [homeassistant.components.buienradar.util] Scheduling next update in 2 minutes

Shall I submit the bug to HA?

#HomeAssistant #Buienradar

@agturcz have you configured your location in HA? I think it's optional during initial setup. Assuming this integration reads the location data from there rather than having its own configuration. Have you checked if there's a configuration option in the integration's menu?

@anyia

have you configured your location in HA?

Yes.

if there's a configuration option in the integration's menu?

Not in the configuration for already configured sensor. But when you create a new sensor, it asks for the location, proposing home location as default.

BTW, it has worked two days ago.

@agturcz oh, if it used to work, then I have zero to contribute

@anyia I suspect any of following.

  • Buienradar did some backward incompatible change in the data format, which might be a bug or a feature.
  • The recent HA update has broken something.
  • I bet on 1, as they were messing with the API, breaking the endpoint for a day.
    2 is just the change I've made meantime. So I cannot exclude it, but it's highly unlikely.

    If the situation won't resolve on its own till tomorrow afternoon, I'll report a bug. Or try to investigate it further. Fortunately, that aspect is not critical to me.