Home

weewx-ultimate-push

A WeeWX driver for more than one weather station at once.

It started with hardware that pushes its readings instead of waiting to be polled. Six protocols share one port, an upload is recognised by what is in it, and roughly 900 raw field names are mapped.

It also runs the drivers WeeWX ships with. A Vantage on a serial port and an Ecowitt gateway on the network are one station in one database, rather than two WeeWX instances.

New here? Installation is twenty lines and ends with a working station.

The wiki is in three parts. Using it is for running a station. How it works is for understanding the machine behind it. Development is for changing it.

Using it

• Installation — install, point the hardware at it, start
• Hardware — every device that uploads, and what it takes to reach it
• Web interface — see what a station sends, and place a field without a restart
• Stations — setting one up, roles, and column ownership
• Several stations — growing the file, and saying which reading comes from which station
• Hosted hardware — a Vantage or a USB console beside the stations that upload
• Sensors this driver asks — a PurpleAir and anything else with a local API
• Database columns — which columns a station needs, and how to add them
• Configuration — every option, with worked examples
• Diagnostics — one command that answers most questions
• Troubleshooting — symptoms and what they mean
• Keeping strangers out — path, token, addresses, TLS
• Reporting a new sensor — exactly what to send

One page per protocol

Setting each kind up by hand, with everything that is only its own.

• Acurite
• Davis AirLink
• Ambient
• Ecowitt
• Ecowitt gateway API — the same hardware asked rather than pointed, with nothing set on the console
• Home Assistant — anything Home Assistant can read
• Lacrosse
• PurpleAir
• rtl_433 — cheap radio sensors, with an RTL-SDR stick
• Weatherflow
• Wunderground

One page per driver this machine can read

Generated from the drivers installed here, so they cannot describe a version nobody has.

• AcuRite
• CC3000
• FineOffsetUSB
• Simulator
• TE923
• Ultimeter
• Vantage
• WMR100
• WMR300
• WMR9x8
• WS1
• WS23xx
• WS28xx

How it works

• Protocols — what each protocol sends, and how they are told apart
• Field map — from raw field to database column
• Ecowitt sensors — every raw field the Ecowitt catalog knows, by sensor
• Unknown fields — what happens to a field the catalog misses
• Catalogs — where the field names come from, and who decided their places
• Architecture — the modules, and why they are cut this way

Development

• Contributing — what helps, and what a pull request needs
• Conventions — formatting, types, comments, documentation, commits
• Development — the source, the tests, the tools, releasing

Which page answers which question

Will it read my hardware?	Hardware for hardware that uploads, Hosted hardware for hardware on a cable
How do I set up my particular hardware?	its own page, under the two lists below
Nothing arrives	Troubleshooting
A sensor is missing from my reports	Troubleshooting, then Field map
A reading is out by a factor	Troubleshooting
Where does tf_ch1 go?	Field map, and Ecowitt sensors for the full list
The driver says it cannot place a field	Unknown fields, then Reporting a new sensor
I have a second console	Several stations
I have an air quality sensor	Sensors this driver asks
I have cheap 433 MHz sensors	rtl_433
My sensor is already in Home Assistant	Home Assistant
My station is on a cable, not the network	Hosted hardware
A reading vanishes at the archive interval	Database columns
This port is on the internet	Keeping strangers out