Originally designed to control the heat and light for a germination and grow station for my succulents mimicing the seasonal conditions anywhere in the world. The upside is that it will also control a full sized grow installation, hydroponics station and even a reptile vivarium.
This will be useful if we are looking at how often a sensor is causing a trigger to fire - a heater for example. Stick them in the database like the sensors.
In the trigger graphs, the SQL call stops out the trigger number and decides by 4 to determine how high to show the graph. It should divide by the number of lines that are displayed on the graph.
Host them on Google Drive in the gStationImages folder, then right-click and 'Get Sharable Link'. Then just paste and change 'open' in the URL to 'uc'.
When booting down the Pi you're never quite sure when it's safe to pull the power. You can readdress the heartbeat green activity LED on the board to a GPIO, and then change its value to be permanently on at run-time. Should probably change the status back to heartbeat on INIT change rather than button press so it will handle the shutdown command correctly as well.
Done with some fancy GPIO overlay management... urgh and the OLED python monitor.
Currently hardcoded to the current latest board version, probably should read the board.txt file and do some deduction. Python training course required.
IN the oled_monitor.sh file there is a test to determine if the new OLED is being used or not. Investigatge why the i2detect call comes back with 0x41 or 0x49... possibly should just come back with something.
DHT22/11 especially can be pootling along quite nicely at 20 degrees, and then suddenly throw out a -7 degrees and the CRC worked. I should probably check for these and ignore them and use the last value I got.
Change these to be Zero, but actually use real HIGH/LOW values that indicate triggeredness rather than the actual values sent to the pins. This is because if you're using an inverted sensor it will be triggered, but will say zero.