-
Notifications
You must be signed in to change notification settings - Fork 0
Protocol Acurite
Setting up Acurite hardware by hand, in weewx.conf.
Generated by tools/build_protocols.py. What each protocol needs is written in that
tool; what it is called and what goes into the console comes from the code. Do not edit
by hand.
There is a web interface for all of this. It is on by default, and the driver prints its address when WeeWX starts:
INFO user.ultimatepush.driver: The web interface is at http://1.2.3.4:8080/?token=abcdefg12345Everything on this page can be done there instead, and one thing is much easier: deciding which reading goes into which database column. See Web interface.
smartHUB and Access bridges, with a 5-in-1, towers, Pro sensors and the 899 rain gauge
In protocols = auto
|
yes |
| Named by | its id
|
| Can be set up before it uploads | No, it is adopted |
[Station]
station_type = UltimatePush
[UltimatePush]
driver = user.ultimatepush.driver
port = 8000
[[stations]]
[[[garden]]]
id = 246F28AABBCCThe identity is the hardware's own and cannot be chosen, so this line cannot be written until the station has uploaded once. The log prints it the first time, ready to copy, and until then the station shows in the web interface as one waiting to be let in.
A bridge cannot be told where to post. It goes to Chaney's servers, over plain HTTP on port 80, and there is no setting for it.
So hubapi.myacurite.com has to resolve to 1.2.3.4 on your network. With dnsmasq:
address=/hubapi.myacurite.com/1.2.3.4
Most routers can do the same under a name like 'local DNS'. A hosts file on this machine will not do: the entry has to be seen by the bridge.
It posts to port 80, so redirect that rather than running WeeWX as root:
iptables -t nat -A PREROUTING -p tcp --dport 80 -j REDIRECT --to-port 8000
Once it is pointed here it no longer reaches Chaney, so the app and the website stop showing the station.
None. Everything that applies to this protocol applies to all of them, and is in Configuration.
The bridge cannot be told where to post. It goes to Chaney's servers over plain HTTP on port 80, and there is no setting for it, so the only way to reach it is to answer for that name on your own network.
Once it is pointed here it no longer reaches Chaney, so the Acurite app and website stop showing the station. That is the trade, and it is not reversible without undoing the DNS entry.
Redirect port 80 rather than running WeeWX as root.
The bridge still reaches Chaney: the DNS entry is not being seen by the bridge. A hosts file on the WeeWX machine does not help; the entry has to be served by whatever the bridge uses for DNS, which is usually the router.
tcpdump -i any -n port 80 on the WeeWX machine shows whether anything is arriving at
all.
This is one station among however many others. Which of them fills outTemp, and where
the rest of their readings go, is in Several stations.
- Installation
- Hardware
- Web interface
- Stations
- Several stations
- Hosted hardware
- Sensors this driver asks
- Database columns
- Configuration
- Diagnostics
- Troubleshooting
- Keeping strangers out
- Reporting a new sensor
- Acurite
- Davis AirLink
- Ambient
- Ecowitt
- Ecowitt gateway API
- Ambient Weather (ambientweather.net)
- Home Assistant
- Lacrosse
- PurpleAir
- rtl_433
- Weatherflow
- Wunderground