mirror of
https://github.com/OpenEPaperLink/OpenEPaperLink.git
synced 2026-03-21 00:04:28 +01:00
[GH-ISSUE #312] Buienradar seems broken/has wrong text #1286
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @marcovannoord on GitHub (May 6, 2024).
Original GitHub issue: https://github.com/OpenEPaperLink/OpenEPaperLink/issues/312
Describe the bug
It seems that for about a week or so, the buienradar image generation seems to produce a wrong image. The graph keeps indicating no rain expected and there is some extra text at the bottom that i can't fully make sense of.
I tried this for different locations in the Netherlands, using a M2 2.9" display.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots

Additional context
Add any other context about the problem here.
@nlimper commented on GitHub (May 6, 2024):
‘Nederland’ is a place name in the USA. Please try with a valid Dutch city name.
other than that, sometimes the Buienradar API is broken for a few days. That’s out of our control.
@PieterBoeren commented on GitHub (May 8, 2024):
I have exact the same issue, with a normal Dutch location (Hooglanderveen), it's broken for over a week now (it did work when it was raining last week). It looks exactly like the screenshot above.
@marcovannoord commented on GitHub (May 8, 2024):
To add on this: in my screenshot i used Nederland, the place in Overijssel to not give away my location, but it also has the same issue with other places like Utrecht.
@kvandt commented on GitHub (May 10, 2024):
Same here for Soesterberg. Probably buienradar changed something in their data, since i did not change the firmware on my AP...
@nlimper commented on GitHub (May 11, 2024):
Buienradar made a change to their API. :-(
Fixed!
73db8d52a8@kvandt commented on GitHub (May 12, 2024):
Just compiled a new bin file with this fix. Works great again.