Rain radar in SmartThings: is it raining at home, how hard, when does it start and how long does it last, two hours ahead. In the Netherlands and Belgium from Buienradar (radar, 5 minute steps), everywhere else from Open-Meteo (15 minute steps, no account needed). Through the small Stoeckie Bridge (Windows or Docker) and its Edge driver.
What you get
A Buienradar device with the setting Show:
Detail (default): rain detected or not, intensity (none, possible, light, moderate, heavy, violent), rain now in mm/h, rain starts in (minutes), rain lasts (minutes) and a short summary
Rain or dry only: just the rain sensor
Location by Dutch postcode and house number (PDOK), by any address worldwide (OpenStreetMap), or by latitude, longitude. Looked up once
Source: Auto (Buienradar in NL/BE, Open-Meteo elsewhere), Buienradar or Open-Meteo
Summary in English (the app does not translate device texts)
Radius in meters (0 to 25000): rain anywhere within it counts. With a radius the bridge also reads up to 16 points around the address and takes the heaviest rain per 5 minutes
Rain from (mm/h): adjustable, default 0.1
Dew point now and Dew point max (forecast): the outdoor dew point now and the highest in the next 48 hours (6 to 72 adjustable), from the Open-Meteo hourly forecast, refreshed every hour. For routines that look ahead, e.g. keep a crawl space dryer on when humid air is coming (see post 8)
All settings are on the Buienradar device in the SmartThings app
Everything works in routines, e.g. rain starts in less than 15 minutes > close the windows, rain detected > notification, rain lasts more than 30 minutes > blinds down
Settings of the Stoeckie Bridge device: switch on Rain radar. A Buienradar / Rain radar device appears
Settings of that device: postcode and house number (NL), an address or latitude, longitude, radius in meters, rain from (mm/h), source, what to show and the dew point look ahead. The bridge setup page has the same fields
Developer notes
Rain counts from 0.1 mm/h. “Rain starts in” is 999 when no rain is expected in the next two hours
Uses the standard capabilities rainSensor and precipitationSensor plus a custom capability for mm/h and the minutes
Offline notification: SmartThings has no routine trigger for “device offline”, so the Stoeckie Bridge device has a Connection status (Connected or Offline). Make a routine: if Stoeckie Bridge > Connection is Offline, send a notification to members. Short drops are ignored, it only turns Offline after 2 minutes down. Each drop is shown afterwards as Last drop (time, duration, reason).
If you made the Offline routine (Stoeckie Bridge (rain radar) device, Connection is Offline, send notification), duplicate it in the app and change the condition to Connection is Connected, with a text like “Stoeckie Bridge (rain radar) is back online”. Then you know the problem is over without opening the app. The device also shows Last drop (when, how long, why).
Nothing changed in the rain logic. What is new: the setup page (location, radius, interval) is in English, and Docker users can reach it from a regular browser on their Docker machine at http://localhost:8787/setup, with or without host networking. For setup from a different computer, list its IP in STBRIDGE_SETUP_ALLOW and open https on port 8443 (README section 1b).
Update with git pull plus docker compose up -d --build, or copy the files and run install.bat on Windows; settings stay.
Update (bridge 2026-11-06e): summary always in English
The short rain summary on the device was Dutch in the Netherlands and Belgium and English elsewhere. Device texts are not translated by the SmartThings app, so it is now English for everyone, for example “Rain in 20 min, for 15 min, up to 1.2 mm/h”. Nothing else changed; routines on rain now, starts in and lasts work as before.
Fix (driver 2026-11-06f): location settings could get lost
The postcode, address or coordinates you set on the rain radar device were only sent to the bridge at the moment you changed them. If the bridge was restarting or unreachable right then, it kept using no location (the setup page then shows “no location, radius 0 m”). The driver now sends them again every time it starts, so they always end up on the bridge. Nothing to do: the driver updates on the hub by itself. Check the setup page after the update; it should show your place again.
Small heads up for anyone running the bridge: version 2026-11-07a switches to Python 3.14 for security updates on Windows. The rain radar itself is unchanged. To update: Windows, run install.bat once more; Docker, git pull and docker compose up -d --build (the image is now python:3.14-slim).
New (bridge 2026-11-07e, driver 2026-11-07b): dew point forecast on the rain radar device
The rain radar device now has two extra values you can use as routine conditions:
Dew point now: outdoor dew point in °C.
Dew point max (forecast): the highest outdoor dew point in the next 48 hours. The look ahead is a setting on the device (Dew point forecast (hours), 6 to 72).
Both come from the Open-Meteo hourly forecast (in the Netherlands the KNMI model) for the same location as the rain radar, refreshed every hour. Buienradar’s free feed only has humidity as a station measurement, not as a forecast, so this part always uses Open-Meteo. If that fetch fails the rain radar keeps working.
Why: I use it for a dryer in a crawl space that should switch at most once a day (it runs on for 10 minutes after switching off). At 14:00 it turns on when the crawl space humidity is 85% or more, or when Dew point max is 11 °C or more (humid air on its way). It turns off when the humidity is 80% or less and Dew point max is 8 °C or less, because then ventilation dries the crawl space by itself.
Update driver 2026-11-08b: no Offline notification for a short network outage
New setting Offline after (minutes), default 5. Connection only turns Offline after that many minutes without contact. Before it was 2 minutes, so a router or network update at night (a few minutes without network) gave an Offline notification even though nothing was wrong. A real outage still gives one. The setting is on the Stoeckie Bridge device.
Also: English and Dutch labels for the rain forecast (Rain now, Rain starts in, Rain lasts, Forecast) now follow the phone language, also in routines.
Bridge 2026-11-08a, driver 2026-11-08c: wind on the rain radar device
New component Wind on the Buienradar / Rain radar device: wind speed, gusts (km/h, at 10 m) and wind direction now, from Open-Meteo, every 15 minutes. Works everywhere, also outside the Benelux.
Usable in routines, for example: only open roof windows when the wind speed is 80 km/h or less.
The device switches to the new profile by itself after the driver update.
The dew point values are the part I’d actually use. Running a crawl space fan on a timer never accounts for humid air arriving later, so having Dew point max as a condition makes more sense than raw humidity alone. One question on the Offline after setting: does the timer reset on any received update from the bridge, or only on a full refresh? Curious whether a quiet period with no changed values could still trip it. The wind component on the rain radar device is a nice addition too, especially for the roof window routine.
@lucasdavis Thanks. The Offline timer is about reaching the bridge, not about changed values. The driver polls the bridge (every 10 to 60 s, depending on the source); every poll that gets an answer counts as connected, also when nothing changed. Only when polls fail does the timer start, and the first successful poll stops it again. So a quiet period without changes never trips it. After a drop that lasted longer than the setting you get Offline, and once it is back the device shows the drop under Last drop (time, duration and reason).
The values of a source itself (for example Buienradar or Open-Meteo not answering) do not count as offline: the bridge keeps the last good values for a while (dew point up to 3 hours, wind up to 1 hour) and when the rain radar itself cannot be updated, only the Buienradar device goes offline, not the bridge.
@lucasdavis On the dew point part: yes, that is exactly why I added it. A few things that help in practice:
Dew point now is the outdoor dew point at this moment, Dew point max (forecast) the highest one in the next hours. The look-ahead is a setting on the device (Dew point forecast (hours), 6 to 72, default 48).
For a crawl space fan the useful test is outdoor dew point against the crawl space temperature: only ventilate when Dew point now is a few degrees below the crawl space temperature. When the outdoor dew point is at or above it, outside air brings moisture in and it condenses on the cold surfaces, so a timer can make it worse.
Routines cannot calculate a dew point themselves, so compare the two temperatures directly, for example: fan on when crawl space humidity is above 75% andDew point now is at least 2 °C below the crawl space temperature; fan off when that gap is gone.
Dew point max is handy for things you can only switch rarely. Here a dehumidifier in the crawl space is switched at most once a day (14:00): on at 85% humidity or when Dew point max is 11 °C or more (humid air on its way), off at 80% or less andDew point max 8 °C or less.
The values come from Open-Meteo (hourly, in the Netherlands the KNMI model), the same location as the rain radar.
Warning, bridge 2026-11-09d: the LAN API of the bridge is now closed until a SmartThings hub is paired. Before, an unpaired bridge served your devices and commands to anyone on your LAN. If your setup page already says “SmartThings hub paired”, nothing changes for you. If not: after updating, your devices stop updating in SmartThings until you open the setup page, press Pair, wait until your hub shows up with its IP address and press Allow. Use driver 2026-11-02b or newer.
Fixed: Only changed values go to the hub. The driver sent every value of every device again on every poll (every 10 s), about 6 events a second for one bridge. The hub then drops events of a device and the app keeps a stale value. Now a value is only sent when it changes, and after every driver start all values are sent once so the app catches up.
Bridge security:
Pairing needs Allow: the token only goes to the hub address you allow on the setup page (before, the first device on the LAN that asked within the 5 minutes got it). The setup page shows the paired hub’s address.
Docker: with port mapping (Docker Desktop, rootless Docker, many NAS) every computer on the LAN can arrive from the Docker gateway address, which the setup page trusted. A browser from that address now first enters the setup key from docker logs stoeckie-bridge or data/setup-key.txt.
No plain http fallback: if the https certificate cannot be made, the setup page only opens on the bridge pc itself.
Samsung TV: the TV’s certificate is remembered; the TV token is not sent to another certificate.
A signed request seen on the LAN could be replayed by changing the letter case of the signature, and with the AEG dryer set up a token refresh could undo the hub pairing. Fixed in 2026-11-09c.
Errors in the log no longer contain a Samsung TV token; the rain radar address is no longer logged.
The setup page shows the bridge version.
Update: driver via the channel; bridge with git pull and docker compose up -d --build, or copy the new stoeckie_bridge.py and run install.bat (Windows). Details in the README.
Fixed: routines no longer run again after a driver update or hub reboot. After a start the driver sent the first value of every attribute as a forced event (state_change), so routines and notifications on these devices ran again on every update. Now it first compares with what SmartThings already shows and only sends what differs.
Air conditioners (Fujitsu): Swing per direction and Off in the mode list, see the Fujitsu topic. The hub picks up the new Off and Swing values within about 12 to 14 hours (it keeps its own copy of the capability definitions, per SmartThings staff).
Update: driver via the channel; the bridge itself did not change.
Update: bridge 2026-11-09i, driver 2026-11-09j: Tuya (Smart Life) devices, local
Thermostats and heaters from the Smart Life / Tuya Smart app, controlled on the LAN. A Tuya IoT Platform project (free) with your app account linked is used once to fetch the local keys and data points; after that everything is local and you can unlink the project. Keys stay in config.json and are never shown or logged.
The bridge finds the devices itself (UDP broadcast, protocol 3.3 to 3.5). Tested here with a floor heating thermostat (category wk: on/off, set temperature, room and floor temperature, mode smart/hold/holiday, child lock, heating state) and two infrared panels (category qn: on/off, set and room temperature, child lock).
The setup page lists each device with its data points, so a device whose cloud mapping misses something can be fixed with a small dps entry in config.json (see README, Tuya).
Windows install: the installer opens UDP 6666, 6667 and 7000 for the own network only (Tuya discovery).
Update: driver via the channel; bridge with git pull and docker compose up -d --build, or the new stoeckie_bridge.py and install.bat (Windows).
Removing a Tuya device in the Smart Life app resets it. After pairing it again it can get a new Tuya id, which would make a new SmartThings device and break your routines.
Now you can add "st_key": "<old id>" to its entry in the manual devices list in config.json (with the new id). SmartThings keeps the existing device with its name, room and routines. Settings in the manual list (dps, ip, st_key) also survive a new fetch from the Tuya cloud.
Tip: after setup you can block internet for the Tuya devices in your router; local control keeps working.