rluckom / bucket-brain Goto Github PK

The front end should be able to show you anything sensors have picked up (including images), as well as modify data in the db to be used for scheduling.

Writing a bunch of images to the microsd card is probably not a great idea. Instead, maybe use a thumb drive for writes that happen frequently. In the extreme, there'd even be two DBs; one for 'life support' scheduling tasks that gets written to rarely, and another for monitoring that gets written all the time. also move the logs to a thumb drive?

If the lights are on a 12 hour / 12 hour duty cycle, I should be able to add a camera task that turns off the lights when it's taking a picture so as not to have the image washed out.

keeping everything in utils is dumb

Pump and light processes should use the db, not hardcoded values, to decide when to go on / off. Need state awareness and polling the db, so if I tell the lights to go off and stay off for a week, then make an update telling them to go to a 5minute on, 5minute off duty cycle, they can switch immediately rather than only checking at the end of the week.

Need a config file so that e.g. path names in start scripts aren't hard coded.

The purple grow lights are pretty uncomfortable to be around long-term. To make these easier to install in lightly-trafficked areas, it would be nice to use a motion sensor to detect when people are around and turn off the lights for 5-10 minutes from the last detected movement. The process responsible for the lights (which may be the process responsible for all gpio stuff) should get input from the motion sensor--they should not share control of the GPIO pin.