# ProWeatherLive Alternative: Get a Weather Site of Your Own

URL: https://pro-weather.com/blog/proweatherlive-alternative

> ProWeatherLive shows your station data in an app, but the page is theirs. Here is how to keep the same hardware and get a real website on your own domain.

**ProWeatherLive** is the cloud dashboard and mobile app bundled with Bresser and several Fine Offset weather stations. It works, it is free, and for checking your own conditions on a phone it is perfectly good. What it does not do is give you a website: your data lives in their app, on their layout, at their address. If that is the limit you have run into, you do not need new hardware. You need a different destination for the data you are already sending.

**Key takeaways:**

- ProWeatherLive is an app and cloud dashboard, not a website builder, so there is no custom domain, no branding and no page you control.
- Your station keeps working unchanged: most compatible hardware has a Customized upload that can post to a second destination at the same time.
- Stations with no custom-server field (many Bresser models) need weewx, Meteobridge or CumulusMX in between, which is a small piece of software, not a replacement station.
- A hosted weather site gives you your own domain, permanent history and the accessory sensors app dashboards usually bury.
- Nothing has to be switched off to try it: run both in parallel and compare.

*Not sure which category your station falls into? The [supported weather stations list](https://pro-weather.com/docs/supported-hardware) sorts them by brand and setup path.*

## What is ProWeatherLive, exactly?

**ProWeatherLive** is a cloud service with [iOS and Android apps](https://apps.apple.com/us/app/proweatherlive/id1528918101) that receives readings from a compatible personal weather station and shows current conditions, graphs and a local forecast. It ships with Bresser hardware in particular, and it appears in the compatible-device lists of other services such as [Weathercloud](https://weathercloud.net/en/compatible-devices/proweatherlive).

It is genuinely useful for what it is: a monitoring app. The forecast comes from a third-party provider, alerts are configurable, and the graphs cover the recent past.

The confusion worth clearing up is that it is a **dashboard**, not a site. There is no page you can hand to a neighbour that looks like yours, no address at your own domain, and no way to change what is displayed or in what order.

## What do you actually gain from your own site?

Four things, in the order owners tend to care about them.

**An address that is yours.** `weather.yourtown.com` instead of an app deep link. It is memorable, it is linkable, and it survives you changing services later, because you keep the domain.

**A permanent archive.** App dashboards keep a recent window. A site that archives independently keeps building history from the day you connect, which is what makes records, almanacs and year-on-year comparisons possible at all.

**Design you control.** Your logo, your colours, the panels you care about in the order you want them.

**The sensors nobody else shows.** If you have paid for a lightning detector, a CO2 module, soil probes or extra room sensors, a generic dashboard often reads only the headline values. Those readings are already in your upload payload and are simply being discarded.

## How do you keep the hardware and change the destination?

It depends on one thing: whether your station's firmware lets you type in a server address.

| Your hardware | Custom server field? | What to do |
|---|---|---|
| Ecowitt, Froggit, Sainlogic, Eurochron, Ambient Weather | Yes, "Customized" | Paste in a second upload URL. Five minutes, nothing else changes. |
| Bresser 5-in-1, 6-in-1, 7-in-1, ClearView | No | Relay through weewx, Meteobridge or CumulusMX |
| Vevor 7-in-1 | No | Relay through weewx, Meteobridge or CumulusMX |

### If your station has a Customized upload

Most Fine Offset hardware does, and this is the easy case. In WS View Plus (or awnet on Ambient Weather), open your device, then **Weather Services**, then **Customized**. Enable it, set the protocol to **Ecowitt**, and enter the server, path and port your new destination gives you.

That entry is separate from every other service on the device, so ProWeatherLive keeps receiving data exactly as before. You are adding a destination, not switching one. The step-by-step is in [how to put an Ecowitt weather station online](https://pro-weather.com/blog/how-to-put-ecowitt-weather-station-online).

### If your station has no custom-server field

Several Bresser models only offer a fixed list: Weather Underground, Weathercloud, AWEKAS. There is no field to type your own address into.

The fix is a small relay. Run [weewx](https://weewx.com/docs/), Meteobridge or CumulusMX on a Raspberry Pi or an always-on machine, let it read your station, and point its Wunderground-protocol upload at your new destination. It is more setup than the copy-paste route, but it is a one-time job and it also gives you a local archive as a side effect.

> **A trick worth avoiding.** You will find advice to redirect `rtupdate.wunderground.com` with Pi-hole or AdGuard so a locked-down station uploads somewhere else without a relay. It does work. It also silently breaks your real Weather Underground upload and affects every other device on your network that resolves that hostname. A relay is reversible and does not hijack anyone else's traffic.

## How does a hosted site compare with the app?

| | ProWeatherLive | A hosted weather site |
|---|---|---|
| Your own domain | No | Yes, with automatic SSL |
| Public page you control | No | Yes |
| Design and panel order | Fixed | Configurable |
| History | Recent window | Permanent, from day one |
| Accessory sensors | Headline values | Lightning, CO2, soil, extra channels |
| Mobile app | Yes | Mobile-first site, installable |
| Cost | Free | Subscription |
| Runs alongside the other | Yes | Yes |

The honest summary: if a free app on your phone is all you want, ProWeatherLive already does that and you should keep it. The case for a site is that you want something public, branded and permanent, and those are exactly the things an app dashboard is not trying to be.

## Do you have to give anything up?

No, and this is the part worth emphasising because it is the main hesitation. Adding a second upload destination does not remove the first. Your station carries on posting to ProWeatherLive, your app carries on working, and your existing data there is untouched.

That makes this cheap to evaluate. Point the Customized upload at a new destination, leave everything else alone, and compare the two for a fortnight. If you do not prefer the site, delete the Customized entry and you are exactly where you started.

## Common questions

**Is Pro Weather the same thing as ProWeatherLive?**

No, and the names genuinely do collide. **ProWeatherLive** is the Bresser-associated app and cloud dashboard described above. **Pro Weather** is a hosted service that turns a station into a website on your own domain. Different companies, different products. If you arrived here looking for the app, [its App Store page](https://apps.apple.com/us/app/proweatherlive/id1528918101) is what you want.

**Will this work with my Bresser 7-in-1?**

Yes, through a relay. The 7-in-1's firmware has no custom-server field, so weewx, Meteobridge or CumulusMX has to sit in between. Once that is running the station itself needs no further changes.

**Can I keep uploading to Weather Underground too?**

Yes. Community-network uploads are separate settings again, so a station can feed ProWeatherLive, Weather Underground and your own site at the same time. Contributing to the public networks is worth doing regardless.

**Does my lightning sensor come through?**

If your destination parses it. Lightning arrives in the upload as strike count, distance and time of the last strike, and plenty of services ignore those fields entirely. Pro Weather reads them and shows them on a Sensors tab, along with CO2 modules and extra room channels.

**What happens to my data if I stop paying?**

Your station never stopped uploading to the manufacturer cloud, so that side is unaffected. This is the practical argument for leaving the original destination enabled: it costs nothing and it means no single service holds your only copy.