Core: Buienradar sensor not picking up the correct location/station.

[Zendio]

The problem

Buienradar sensor is suddenly picking the wrong location. It used to pick the closest to my home, which is Gilze Rijen, but now only returns Arcen. I've tried setting lat/lon manually in the sensor configuration to my home in a first attempt to fix it, and then tried setting it to Gilze Rijen (the location in the XML feed 51.94, 5.56) but both eventually load the data from Arcen. It only stopped working for me since the last update to 0.108.5 and I notice it takes quite a bit longer for it to find a weather station after restarting HA.

Environment

• Home Assistant Core release with the issue: 0.108.5
• Last working Home Assistant Core release (if known): 0.107
• Operating environment (Home Assistant/Supervised/Docker/venv): Home Assistant (Hassio) on RPI3
• Integration causing this issue: sensor.buienradar
• Link to integration documentation on our website: https://www.home-assistant.io/integrations/sensor.buienradar/

Problem-relevant configuration.yaml

• platform: buienradar
  monitored_conditions:
  
  
  
  • stationname
  
  
  • barometerfc
  
  
  • barometerfcname
  
  
  • conditioncode
  
  
  • condition
  
  
  • conditiondetailed
  
  
  • conditionexact
  
  
  • symbol
  
  
  • feeltemperature
  
  
  • humidity
  
  
  • temperature
  
  
  • groundtemperature
  
  
  • windspeed
  
  
  • windforce
  
  
  • winddirection
  
  
  • windazimuth
  
  
  • pressure
  
  
  • visibility
  
  
  • windgust
  
  
  • precipitation
  
  
  • irradiance
  
  
  • precipitation_forecast_average
  
  
  • precipitation_forecast_total
  
  
  • rainlast24hour
  
  
  • rainlasthour
  
  

Traceback/Error logs

No error logs

Additional information

[Zendio]

The buienradar XML file is stuck on 04/15/2020 23:20:00 and might trip up the sensor. I do however receive updates from the Arcen station with a correct timestamp in the sensor info.

[probot-home-assistant[bot]]

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!

[Heronimonimo]

It seems that their XML feed is indeed stuck. Already notified them on Twitter about this issue: https://twitter.com/HGPPeters/status/1250796517851631617

Fortunately it seems that their JSON feed still works. Might it be an idea to switch to their JSON feed as a source: https://data.buienradar.nl/2.0/feed/json

[Zendio]

It seems that their XML feed is indeed stuck. Already notified them on Twitter about this issue: https://twitter.com/HGPPeters/status/1250796517851631617

Fortunately it seems that their JSON feed still works. Might it be an idea to switch to their JSON feed as a source: https://data.buienradar.nl/2.0/feed/json

I'm not exactly sure where the sensor gets it's data from but just looking at the JSON feed you posted, I noticed that every single location has a lat/lon of 0.0. That might be the issue.

[Heronimonimo]

Sharp, did not notice that. Than I think the JSON location data might be the cullprit why it defaults to Arcen. Just tweeted this problem also to them: https://twitter.com/HGPPeters/status/1251078673765195778

[mrh3nk]

I closed the other issue, did not see this thread. Probably because it was closed before.

[Heronimonimo]

Just got a reply that Buienradar is looking at the issue: https://twitter.com/BuienRadarNL/status/1251125909622599686

[Zendio]

Just got a reply that Buienradar is looking at the issue: https://twitter.com/BuienRadarNL/status/1251125909622599686

And it's fixed!

[mrh3nk]

Hooray!