How to Make a Weather Website from a Meteobridge (2026 Guide)
To turn a Meteobridge into a public weather website, add one HTTP push event on its Services tab that sends your readings every 60 seconds to a hosted site. The Meteobridge keeps doing everything else it already does. With Pro Weather that is one URL copied from your dashboard: the site gets live conditions, charts, records and a permanent archive, on a free subdomain or your own domain. It costs €5,99 a month or €39 a year per site, excluding VAT, after a 14-day trial that asks for no card.
You can see the result before you start: meteobridge.pro-weather.com is a live site fed by a Meteobridge in exactly this way.
Why use a Meteobridge for a weather website?
A Meteobridge is a small always-on logger that reads your station and republishes the data. Its published feature list covers a long list of station brands and a set of weather networks it can upload to, plus push services that send data to your own server over HTTP, HTTPS, FTP or MySQL.
That last part is what makes it a good website source. Stations whose own firmware has no custom-server field, older Davis consoles with a data logger, or a mix of sensors from different brands can all be read by one Meteobridge and pushed to one place. It is the same job weewx or CumulusMX does on a Raspberry Pi or a PC, without the computer to maintain.
What are the options?
There are three realistic routes from a Meteobridge to a website:
| Route | What you get | What it costs you |
|---|---|---|
| Weather networks (Weather Underground, AWEKAS, WOW) | A station page on their site, next to thousands of others | Free, but the layout and address are theirs |
| Your own server | Anything you build: FTP a template, run a PHP site, write to MySQL | A web host, the site software, and keeping both running |
| A hosted weather website | A site of your own with charts, records and history, nothing to run | A subscription |
The first route is worth keeping regardless: it is free and feeds the community networks. Most people who search for this want the page to be theirs, on their own address and their own layout, without running a server. That is the third route, and it is the rest of this guide.
How do you connect a Meteobridge to Pro Weather?
Four steps, about ten minutes.
1. Create the site and turn on uploads
Sign up, create a site, and on Setup → Connection → Local hardware choose Enable uploads. The Upload URL card shows your personal URL, and a ready-made Meteobridge template with your key already in it.
2. Add an HTTP event on the Meteobridge
On the Meteobridge web interface, open the Services tab and, under Definition of Events, add an HTTP event with an interval of 60 seconds. Paste the URL from your dashboard on one line. It looks like this, with your own key where the f3a91c… is:
https://pro-weather.com/api/ingest/f3a91c…?tempf=[th0temp-act=F.1:--]&humidity=[th0hum-act.0:--]&dewptf=[th0dew-act=F.1:--]&windspeedmph=[wind0wind-act=mph.1:--]&windgustmph=[wind0wind-max10=mph.1:--]&winddir=[wind0dir-act.0:--]&baromin=[thb0seapress-act=inHg.2:--]&rainin=[rain0total-sum1h=in.3:--]&dailyrainin=[rain0total-sumday=in.3:--]&rainratein=[rain0rate-act=in.3:--]&solarradiation=[sol0rad-act.0:--]&UV=[uv0index-act.1:--]&indoortempf=[thb0temp-act=F.1:--]&indoorhumidity=[thb0hum-act.0:--]&AqPM2.5=[air1pm-act.1:--]&AqPM10=[air0pm-act.1:--]&pm1=[air2pm-act.1:--]Each [...] is a Meteobridge template variable: the sensor (th0 is the outdoor thermo-hygrometer), the value (temp), the selector (act for the current reading), an optional unit converter (=F), the decimals (.1) and a fallback (:--). Meteobridge's template reference lists every sensor and selector if you want to add more.
3. Set the success string
Set the event's success string to success. That is what the upload URL answers when a reading was accepted, so Meteobridge can show you a green result next to the event instead of guessing.
4. Watch the data arrive
Within a minute your site gains a new station. Give it a name, a time zone and coordinates on the same Connection page, pick a look, and publish.
What goes wrong most often?
Pasting the bare URL. Meteobridge sends the URL exactly as written. Without the ?tempf=[...] part there are no readings in the request, and the upload is rejected. Copy the whole template from the dashboard.
Two decimals on rain. An old template with in.2 rounds rain to hundredths of an inch. A Davis gauge tips in 0.2 mm steps, which is 0.00787 inches, so small totals lose a tip each time. The current template uses in.3. If you set this up a while ago, re-copy it.
Air quality on the wrong channel. The last three fields assume a Davis AirLink, which Meteobridge numbers air0pm for PM10, air1pm for PM2.5 and air2pm for PM1. Other sensors number differently: an Ecowitt WH46 lands on air4pm to air6pm. Check the Live Data tab on the Meteobridge and adjust the numbers.
A sensor you do not have. Nothing to fix. A missing sensor posts -- and is ignored, so the same template works on a basic station and a fully loaded one.
What does the website show?
Everything the Meteobridge sends that the site recognises: temperature, humidity and dew point, wind and gusts, pressure, rain totals and rate, solar radiation and UV, indoor readings and particulates. From those it derives the rest, including feels-like temperatures, daily extremes, records, a climate report and the almanac.
The archive is kept independently, one reading about every four minutes, so the history does not depend on the Meteobridge's own storage or on any weather network staying online. The supported readings table lists every field.
Common questions
Do I need a Meteobridge PRO, or does a NANO SD work?
Any Meteobridge that offers HTTP push events on its Services tab works. The upload is one HTTPS request a minute, which every model handles.
Will this stop my Weather Underground upload?
No. The HTTP event is independent of the weather networks you already publish to. Everything keeps running side by side.
Can I use my own domain?
Yes. Add a CNAME record for a domain you own and the site moves there, with SSL issued and renewed automatically. See using your own domain.
What if my station is a Davis with WeatherLink Live?
Then you have a choice. Pro Weather can read a Davis station directly through a free WeatherLink API key, with no Meteobridge involved, and imports past readings on the WeatherLink plans that allow it. The Meteobridge route suits a Davis without WeatherLink, or a mixed setup the Meteobridge already reads.
How does this compare with running weewx or CumulusMX?
All three can relay to the same upload URL. The difference is what you maintain: weewx and CumulusMX run on a computer you keep patched and powered, while a Meteobridge is an appliance. The full setup notes for all three are in the help center, and Pro Weather vs weewx covers the trade-off in more depth.