I’ve fixed the bug in v0.6.1 hopefully.
1 Like
I’ve released v0.7.0.. In this version it’s now possible while adding a location to configure if you like to manually select a weather station, or automatically collect the closest observation for each weather sensor.
I plan to add a lot more observation sensors. The variables that are available are listed here under variables.
I don’t think all variables listed there are useful. But things like Past 10 min Solar Radiation, sunshine duration, dewpoint, wind gusts, air temperature at 10 cm, soil temperature or rainfall amount can all be very useful
3 Likes
I’ve released version 0.8.0.
This release adds separate sensor entities for all weather observations. This makes it easier to integrate them directly in automations. Furthermore, it now also fetches cloud ceiling, sunshine duration, solar radiation and soil temperature data from KNMI. These have also been added as sensor entities. Thanks also to @Hmmbob for his help.
I’ve left all precipitation (e.g. rain) observations out for now. Rain is obviously very local, and I’m afraid they may be confusing. People may not realise these are local observations, and might be confused when the station sensors says there was no rain while there was rain at their position.
What do you think?
3 Likes
First of all great work on this integration Paul !
I’m not 100% on the observations. If you leave out rain why not leave out radiation, temperature etc as these are likely related to the rain as well (local).
Having a local PWS basically I’m only interested in the forecasts and cloud coverage/ceiling, radiation as these are much harder to measure accurately. Therefore an option to choose which sensors to load would be appreciated to limit the number of them. Something the F1-sensor does as well from the configuration.
I am really happy with this app! Exactly what I need with a great source directly from KNMI. I agree tot not include rain as it is very local. The buienradar app is a great source for that.
You can easily turn off sensors you don’t need right?
I’ve added wind (speed, gusts and direction), precipitation chance and UV index to the daily forecast. See version 0.9.0.
While working on this I noticed I can also increase the forecast from 6 days to 14 days. This does take some extra fiddling around. Personally, I don’t use such long range forecast. Deterministic forecasts are not useful beyond a week in most cases, you need to look at the ensembles forecasts if anything. But would anyone else use that?
3 Likes
Paul, amazing work! Your work is now visible on my epaper in the living room. With forecast of 3 days. For me that is sufficient. 
Pictures or it didn’t happen 
Thanks for this nice integration.
One thing I couldn't get right: animated radar images on mobile.
On my desktop browser (Safari, Edge and Firefox) the radar images are playing fine.
But on the mobile app (iOS) and mobile browser (Safari) it is a static image and I couldn't get it to play.
I have tried the Picture-entity and Advanced Camera Card (formerly Frigate card) but both don't play on mobile.
Picture-entity:
show_state: false
show_name: true
camera_view: auto
fit_mode: contain
type: picture-entity
entity: camera.neerslagradar
camera_image: camera.neerslagradar
tap_action:
action: none
aspect_ratio: "1:1"
Advanced camera card:
type: custom:advanced-camera-card
cameras:
- camera_entity: camera.neerslagradar
live_provider: image
always_error_if_entity_unavailable: true
image:
refresh_seconds: 5.6
triggers:
occupancy: true
motion: true
view:
default: live
menu:
buttons:
iris:
enabled: false
camera_ui:
enabled: false
ptz_controls:
enabled: false
permanent: false
ptz_home:
enabled: false
style: none
performance:
features:
card_loading_indicator: false
card_loading_effects: false
animated_progress_indicator: false
dimensions:
aspect_ratio_mode: static
aspect_ratio: "1:1"
timeline:
show_recordings: false
live:
preload: true
controls:
ptz:
mode: "on"
type: buttons
orientation: horizontal
hide_type: false
hide_home: false
builtin: false
auto_play:
- visible
- selected
show_image_during_load: false
If I replace the camera with a real camera entity, it plays fine. But the image sequency won't play.
Someone can point me in the right direction? Thank you!
Hmm.. I can't replicate that issue with the single iOS device in our household (using the companion app). I'm using the picture entity card, and your config matches mine.
That said, I do see quite some weirdness with the animated GIF. Sometimes I only see it loop once or twice. Sometimes I also see it stuck on an image. Usually this happens on first load, and if I revisit the dashboard screen it's fixed. In general though, it's working good enough. On both browser, companion app, and kiosk tablet.
I'm not sure I can do anything about it. I'm generating the animated gif as output image to a Camera entity. This animated gif does not seem really like the intended way to use the Camera entity. I see it no where in the documentation. It's the same as the core buienradar integration is doing.
If anyone got a better idea to display the animated radar, I'm all ears. I'm however not really looking forward to client side JS solution
@PaulVanSchayck : Thank you for your efforts on this; it is looking very nice.
FYI:
However, when I attempted to register for the KNMI API earlier today, I found that the process has changed due to an excessive number of bots. As a result, I need to wait a few days before I can proceed...
2026-06-05: Due to excessive numbers of bots and AI agents registering, we've had to temporarily disable e-mailing from the developer portal. Effectively, this means that you can no longer sign-up for an account directly from the portal. You will also no longer receive an e-mail when you request an API key. Make sure you note down the key when it is displayed on-screen. For sign-up, read this FAQ for more information.
After sending an email KNMI will review the request and get back within 2 working days.
Yeah, I've seen the notice. It's unfortunate. Not much we can do about it, other than behaving ourselves when making using of a public service. It's a pity that AI has turned up the 'evilness' on the internet yet another notch. Food for thought.
1 Like
I finally found the problem. It has to do with an IOS system setting.
Go to Settings > Accessibility > Motion > Auto-Play Animated Images or in Dutch
Instellingen > Toegankelijkheid > Beweging > Speel afbeeldingen met animatie automatisch af
Turn this off and it won't play, turn on and the radar images are moving 
Hi,
I seem to recall that I had set Deelen weather station as the fixed station, but I now see the information below. How can I edit the used stations and/or is there a logic in the automatic selected stations based on weather?
In addition, I was wondering whether the weather warning code sensor displays the warning color per province (i.e. based on the selected weather station), whether the warning code is applied nationally for the entire country, or whether it is determined using a combination of data from multiple weather stations when issuing weather warning codes.
Nice that you got that fixed. I'll see if I can note that quirk down in the README somewhere.
Hmm.. if you've set a fixed station, it should only use data from that station. In automatic selection mode, it takes for each sensor the closest data it can find. Not all stations report all sensors. A sensor or a whole station can also be under maintenance. So that's why you will often see a combination of stations. I know that Deelen Airport is undergoing maintenance these days. So that would explain the switch you see. It's not based on weather.
The screenshot looks like it's using automatic mode. You can not change a location from manual to automatic after adding it initially. I haven't implemented the reconfiguration flow for that. You can open a GitHub issue for it, if you like. If you're sure you've selected manual mode, this could also be a bug.
You can always add a new location, and configure that. Maybe good to experiment with that, and see if you can understand what's happening.
The weather warnings are determined by the Region you've selected when adding the Location. They are not determined by either the location or the selected weather station. So you can have a location with Maastricht Airport as station and warnings from Groningen.
1 Like
If there is an option for more that a few days i would love to see that in the integration.
If the integration supports it you can tweak the visibility of the amount of days in you respective card, as all of them have an option to select the number of days.
You mean how many days are forecasted? Right now that's 6. The app API contains up to 14 days. So more is possible, but it requires different API calls which I haven't implemented yet.
I don't typically look at deterministic forecasts beyond 6 days anyway. The predictive value is pretty low for those. You're better of looking at ensemble forecasts such as this one.
Feel free to open an issue at GitHub, and I may add it in the future.
I've just released version 0.10.0. This is a pretty major release.
The release features several bug fixes and improvements. It should handle cases where KNMI data is not available better. It also improves using the API caches better, and make it less likely for the integration to start hammering the APIs.
Functionality wise, I've added a precipitation nowcast graph. Showing when to expect rain, and how much. For your location.
Home Assistant lacks a way to directly render the precipitation nowcast graph. The data for the graph is available in two ways:
- As service call
get_minute_forecastto theweather.weer_{location}_forecastentity.
- This has been pruned to only include data from now onwards.
- At a minute interval
- As
forecastattribute to thesensor.weer_{location}_precipitation_forecastedsensor.
- Use the HA Developer Tools to inspect the sensor
- This contains also data from the past
- At a 5 minute interval, as the API provides.
There are two good ways to render a graph from this.
- Using Weather Forecast Extended, which makes use of the get_minute_forecast service. Refer to the configuration of that card, how to setup the nowcast entities.
- Making use of ApexCharts Card and render the data from the sensor. This is an example configuration:
type: custom:apexcharts-card
experimental:
color_threshold: true
graph_span: 3h
span:
start: hour
offset: "-30m"
yaxis:
- max: ~10
now:
show: true
label: Now
series:
- entity: binary_sensor.weer_thuis_precipitation_forecasted
unit: mm/h
type: area
opacity: 0.3
stroke_width: 1
color: gray
color_threshold:
- value: 0
color: lightblue
- value: 1
color: blue
- value: 3
color: orange
- value: 7
color: red
data_generator: |
const data = entity.attributes.forecast || [];
return data.map(p => [
new Date(p.datetime).getTime(),
p.precipitation ?? 0
]);
Looking forward to seeing even better graphs being designed, and hearing what kind of automations you've made using this data.
Enjoy the release
4 Likes