nigeljohnson73 / gstation Goto Github PK

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'.

Move the logging out of the monitor and into the reader with ob_start() etc.

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.

Once the repository has been downloaded, do a self-install, use #3 to clear files we configure.

There is a bug in the compressed payload.

Currently hardcoded to the current latest board version, probably should read the board.txt file and do some deduction. Python training course required.

The graphs seem to have a gap where February 29th is. Remove this.

This is correct but was removed for testing, and to allow bug removal. Put it back.

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.

Need to implement this sensor.

Python implementation is here: https://pypi.org/project/mh-z19/

and another here: https://www.circuits.dk/testing-mh-z19-ndir-co2-sensor-module/

Look up the PhpSerial class in the include folder??

Here is some z19B data: https://revspace.nl/MH-Z19B

and the older Z19: https://revspace.nl/MHZ19

Remove lines between #gStation Start and #gStation end for example

INFO on page 1, Zone xxx etc. Use the press button as a press so that long hold will still shut the system down.

Create to a temporary file first, then unlink and rename

Like the gCam and then make it update from the backend server.

For graphs that have a lot of values, for example, the CPU graph, the y-axis is unreadable. do some capping on numbers of labels.

Investigate and stop it from happening.

Temps and humidities peak 45-70 days past the solstice so this is currently hardcoded to 60. Make it a parameter in the config file.

Need to make the sensor reading function barf if the age of the senor data is out of range.

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.

For the temp graphs for example, there appear to be more graph lines than there are numbers.

Prepend the station name to the message in case there are multiple setup.

I think these are just for making alerting working... Rework them cuz it's sucky.

This all happens in the tick() function in _App.php:1690

In the config, functionally sort out getting parameters and multi-array displays. Update index to show generated graphs.

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.

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.

So that caching will occur correctly, in the index.php file get the file time of the payload and add it correctly.

Something to do with the fact that paths are not sent through the ngrouter as it's not configured in apache.

Stick them in the database like the sensor data.

The calculation of whether it is supposed to be day or night only works when sunrise is before sunset on the day.

This all happens in the tick() function in _App.php:1671;

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.

https://www.raspberrypi.org/forums/viewtopic.php?t=80730#p1056163