ambient2mqtt
purpleair2mqtt
| ambient2mqtt | purpleair2mqtt | |
|---|---|---|
| 1 | 2 | |
| 4 | 3 | |
| - | - | |
| 10.0 | 2.9 | |
| over 1 year ago | 12 months ago | |
| Go | Go | |
| MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
ambient2mqtt
-
Monitoring My Weather at Home
One of the most unexpected and wonderful things about my Ambient Weather station is that within its settings app, you can configure an additional URL for it to send periodic pings to. In my case, I whipped up ambient2mqtt[0] as a way to capture the output of the weather station locally and do what I want with it - in this case, post the data to MQTT and InfluxDB.
A few years after that I also purchased a Purple Air PM2.5 monitor. I was pleasantly surprised that this device exposes a local REST interface for polling the data. Naturally, I wrote purpleair2mqtt[1] to pull the data from that and post to MQTT and InfluxDB.
Together these two applications and pieces of hardware give me a great view of the weather conditions. And like the author of the article, I found that other weather information tended to be off significantly. Doubly true as I live next to a lake in a rural-ish part of New England which is about 500ft higher than the city and airport where our weather data comes from. Over the last couple of years I've been pleased to see that my data has become the defacto source for weather data in my town (I publish it to numerous sources) and that the PM2.5 information gets brought into lots of reports, including the EPA's AirNow system - which is great, because it doesn't look like there's another PM2.5 monitor within 20 miles of me.
[0]: https://github.com/pridkett/ambient2mqtt
purpleair2mqtt
-
The Hidden Cost of Air Quality Monitors
They may be referring to the changes to PurpleAir API [0] that introduces paid requests that you can rip through quickly when doing large scale analysis.
In the United States, AirNow.gov includes most PurpleAir sensors, although they are annotated differently than “higher quality” sensors (I was going to say than government sensors, but here in Connecticut, the state has a number of PurpleAir monitors deployed and rapidly deployed more when stuff got bad due to Canadian wildfires a few weeks ago).
Fortunately, for local users, you can hit your own sensor and grab the data however often you want. I even wrote a tool to help out and drop it into influxdb and post it to MQTT[1]. They still support local fetching of data. However, many default integrations from tools like Home Assistant could be affected as they use the cloud integration.
[0] https://community.purpleair.com/t/api-pricing/4523
[1] https://github.com/pridkett/purpleair2mqtt
- Monitoring My Weather at Home
What are some alternatives?
rtldavis - An rtl-sdr receiver for Davis Instruments weather stations.
rtl_433 - Program to decode radio transmissions from devices on the ISM bands (and other frequencies)
openaq.org - The OpenAQ website
community-airmonitor - Miller Beach / NWI air quality monitor using PurpleAir PM sensor, tracking PM2.5, PM10, weather, traffic congestion, trains in "The Region", etc. built in node.js/express.js, updated every 15 minutes.