Skip to content

Latest commit

 

History

History
77 lines (60 loc) · 3.22 KB

README.md

File metadata and controls

77 lines (60 loc) · 3.22 KB
Raw

Tempest Weatherflow Plugin for Telegraf

This application connects the Weatherflow Tempest weather station with Telegraf, the open-source agent that is a companion to the InfluxDB time series database. This plugin listens to the Tempest UDP v143 format messages broadcast to the local network to which the weatherflow hub is connected. It does not connect back to the Weatherflow cloud API (it is all local).

Telegraf is fairly general-purpose and telegraf can route data other places than just influxdb. It can route data to a few other time series databases, and also to other destinations such as an MQTT endpoint. There are a lot of Telegraf Plugins available that do different things.

This 'plugin' is an external program that writes data in the Influx Line Protocol format suitable for writing to telegraph using the inputs.execd plugin. It takes no parameters, and starts listening on the local network for UDP broadcasts to port 50222. To use it, create a telegraf input configuration like this:

[[inputs.execd]]
 command = [ "tempest_udp" ]

That's pretty much all you have to do, but if that's all you have the data won't go anywhere. A more complete example is:

[[outputs.influxdb_v2]]
  urls = ["http://127.0.0.1:8086"]
  bucket = "power"
  organization = "your_org"
  token = "your_influx_token"

[[inputs.execd]]
  ## Commands array
  command = [ "telegraf-tempest" ]

Currently this writes the following measurements:

  • wind - rapid wind observation
  • observation - general weather information (temperature, pressure, humidity, etc)
  • hub_status - periodic messages coming from the hub telling you it is alive. There is an RSSI in this message and they don't document what it means, but it may be the RSSI the Hub is reporting for whatever Wi-Fi network it is conneted to
  • device_status - info about the remote device, including two RSSIs which are also undocumented, but it's likely that one of them is tempest-to-hub and the other is hub-to-tempest

Logging

Optionally you can set a "--log" parameter which can be either a file path, "stderr", or "stdout". The default is stderr.

If you choose to write to standard output, all log message lines will be prepended with a # to make them look like influx line protocol comments.

Log rotation is included, with fixed parameters:

  • Logs rotate when the size exceeds 10 megabytes
  • Up to 10 previous logs are kept (gzipped)
  • Log files older than 30 days are purged

Future Improvements

  • Make the individual measurement names be configurable
  • Make logging a little more configurable, maybe through a -debug or -quiet flag
  • Add lightning strike observation (have yet to see it happen, though, so it's not there yet)
  • If you need/want something else, write an issue and I'll see what I can do

Author

Christopher Piggott