meteohub.de

Hello everyone,

short version for those who upload to Meteotemplate from the Weather Networks tab: nothing changes, and nothing needs to be touched on your Meteobridge. The longer story is below, because I think it is worth telling.

What happened to Meteotemplate

Meteotemplate, the weather website platform written by Jachym Brzezina, has not been maintained for some time and the original site went offline. That left a number of stations — including several Meteobridge users — uploading to a network that was effectively gone.

What I did about it

I acquired the meteotemplate.com domain, and the Meteotemplate-compatible endpoint now lives inside WS40, the WordPress plugin I develop. Jachym is aware of this and is happy with how it worked out; Boris kindly checked with him directly before I posted here.

What it means for you, in practice

• The Meteotemplate entry in Weather Networks keeps working as before.
• Same protocol, same parameters — Boris has confirmed he does not plan to change the upload protocol on the Meteobridge side.
• No settings to modify, no firmware update, nothing to reconfigure. If your station is uploading today, it keeps uploading tomorrow.

The only difference is where the data lands: instead of the old central Meteotemplate site, the endpoint now runs on your own WordPress installation, so the data stays on your own server.

If you were a Meteotemplate user

Your historical database is not lost. WS40 imports Meteotemplate's alldata and alldataExtra tables directly, with automatic unit conversion, so you can bring years of records across rather than starting from zero.

About the plugin

I will not repeat myself here — I introduced WS40 in this thread back in May. It is free on WordPress.org, with an optional paid tier, and it reads Meteobridge natively. That part is not the point of this post: the point is that the Meteotemplate network is in maintained hands again.

Thanks

To Jachym, for building something that a lot of us used for years, and for being gracious about the handover. And to Boris, both for confirming the protocol stays put and for suggesting I introduce myself here.

Happy to answer any questions — technical ones very much included. If something about the endpoint does not behave the way it used to, tell me and I will look into it.

Pasqualino De Marco
weatherstation40.live · cervignanometeo.org

Thank you Pasqualino! To make your "Weather Station 40" development based on Meteotemplate API a bit more visible, the Meteotemplate settings in Meteobridge are named "Meteotemplate / WS40" in most current Meteobridge release.

Hi,

I rather will still use the old meteotemplate though.

So just for to be certain: I use MB and MT, nothing will ever change?

For updates: I am already maintaining it myself with the use of Claude.
They can be find soon on a github page .

Alex

alexvanuxem wrote: Mon Aug 10, 2026 3:50 pm Hi,

I rather will still use the old meteotemplate though.

So just for to be certain: I use MB and MT, nothing will ever change?

For updates: I am already maintaining it myself with the use of Claude.
They can be find soon on a github page .

Alex

There are no plans to suspend any introduced upload mechanism. You are safe.

Re: Meteotemplate is maintained again — nothing changes for Meteobridge users

Boris, thank you for renaming the entry to "Meteotemplate / WS40" — I only noticed it when a user pointed it out. That was a generous thing to do, and it is appreciated.

Alex, sorry for the slow reply, and to answer you directly: nothing changes for you. Your Meteobridge keeps uploading exactly as it does today, to whatever endpoint you point it at. Boris already confirmed it from his side, and I will confirm it from mine: the parameters the network sends are not going away.

And genuinely — good on you for keeping the original Meteotemplate running. I took over the domain because the platform deserved not to disappear, not to become the only way to use it. If your GitHub version and my endpoint both speak the same protocol, that is a win for everyone who owns a station: two implementations, one network, no one locked in. If you ever hit a case where the two behave differently, tell me and I will align mine.

One thing on the horizon, since this thread is the right place for it.

There are sensors that Meteobridge measures today but the Meteotemplate protocol has no way to carry: extra temperature/humidity probes, CO₂, and particulate readings whose slot numbering is ambiguous enough that a receiver has to guess what PP1 actually means. I am putting together a v2 of the upload parameters to close those gaps.

Two commitments about it, so nobody has to wonder:

It is purely additive. Every v1 parameter stays valid forever. A station uploading today will still be uploading, unchanged, years from now. Nothing to reconfigure, ever.
The specification will be published openly, not buried in my plugin. Anyone implementing a Meteotemplate-compatible receiver — including your fork, Alex — can support it, and any uploader can send it.

Nothing is being asked of Meteobridge users at this stage. When the spec is ready I will post it here first, and if there is a sensor you want carried that the protocol currently drops, this is a good moment to say so — it is much easier to add a parameter before the spec is fixed than after.

Pasqualino