- Turning lights on/off around the house, because I found cron to be a more reliable scheduling agent that the one built-into my Wave software when I first set it up.
- Testing network performance (ping times to various locations)
- Fetching a mail account and processing the messages for an automation I have setup for some things.
- Updating online weather services with data from my weather station.
- Kicking off data gathering/update jobs.
I moved some stuff out of cron into systemd and although it worked, it was over-complicated in an infuriating way.
I realize systemd is useful, but the implementation is like trying to navigate through a teenager's bedroom trying to find something.
So, I hear people doing this alot. However what exactly does this help with? Like, is the extra information really more useful than just the standard old TV weather forecast?
I do find it interesting to see the differences in temperature (and humidity, etc.) in the microclimate around my house compared to the city and greater metro area.
I also use the data to measure the performance of my home's HVAC system. Doing this _does_ require real-time local temperature and humidity data. But again, this is all for fun.
I just enjoy it.
Adafruit has a bunch of sensors that work over the i2c bus; they’ve included python code for accessing the data as well, which makes it easy to get started.
There are sensors out there for everything. Absolutely everything.
That is as good a reason as any!
I'm really benchmarking the system against itself, year on year, by comparing the weather outside vs. performance (output temperature of the HVAC unit, average temperature inside the house).
I'm not trying to find an objective efficiency rating so much as monitor performance over time to see if it's changing.
Whats your success with this? I am not referring so much to the Raspberry Pi part - but the actual ZWave protocol and whatever mesh network it creates. Is it reliable? Or do your lights flicker on and off randomly?
My experience is that it has all been rock solid. I’m using most GE branded in-wall light switches and they’ve been very reliable for me. Misc other brands for the other modules.
I’d recommend it.
Why 2 temperature sensors? Turns out the BME280 runs about 2°F hot, and the 18B20 is right on, so I end up using the 18B20 as my primary temp sensor.
Every minute a cronjob runs and the Pi takes readings from the sensors and stores them locally.
Then, I have another Pi that, every minute, reads those values and stores them in a long-term database (I have about 5 years of weather data at this point). The long-term database is running a custom Rails app I wrote to report on the data and show graphs, compare weather over years, etc.
In theory this could all live in a single Pi, but for various legacy reasons I ended up with a dedicated Pi for data processing, and a dedicated Pi for data gathering.
There's also some efficiencies from having everything on the same hardware platform.
But mostly it's just comfortable for me.
- Outdoor irrigation control via OpenSprinkler Pi: https://opensprinkler.com/product/opensprinkler-pi/
- Z-Wave home automation via ZWay: https://z-wave.me/products/razberry/
- 2 Custom HAVC thermostats using: https://github.com/jeffmcfadden/PiThermostat
- An NTP server with GPS attached for a time source.
- 2 for weather monitoring (one directly attached to sensors, one that aggregates the data from a few sources and provides reporting)
- A sort of centralized "workhorse" Pi that runs a lot of random cron jobs, etc.
- An Alexa gateway for home automation
- An NES emulator
- An infrared-remote source for turning on/off surround receiver, TV, etc.
- Monitoring of HVAC temperatures/performance
- An intranet server
Assuming I didn't forget anything.