austinmeier / old_growberry_pi Goto Github PK

ExtractionError: Can't extract file(s) to egg cache

The following error occurred while trying to extract file(s) to the Python egg
cache:

[Errno 13] Permission denied: '/root/.python-eggs'

The Python egg cache directory is currently set to:

/root/.python-eggs

Perhaps your account does not have write access to this directory? You can
change the cache directory by setting the PYTHON_EGG_CACHE environment
variable to point to an accessible directory.

only happens on non-pi users (nimrod from growberry-webserver)

Something is wrong with the logging handler. Not catching the pins.py logger.

No handlers could be found for logger "pins"

is printed to the console after manually starting growberry with python growberry

Won't be necessary in the long run, but I want it to look nice.

Need this to run at boot up, in case of power loss.

After reboots, the images are taken too quickly, and the lights are not on all the way, so the image appears dim.

Just add a delay upon bootup. Might tie in with the other issue that detects power outages.

There are too many errors for that specific log.

[WARNING] __main__ 2018-08-03 02:20:15,647 one of the sensors could not be read, defaults used.
[ERROR] pins 2018-08-03 02:21:24,072 internal-DHT22 sensor could not be reached after 3 attempts.  Make sure sensor is connected to GPIO 15

Long term: Need a way to keep track of the number of successful reads/errors. Maybe a percentage? Also implement option B below.

Short term: A. Make the logs longer, B. change the error code to lower than ERROR/WARNING, and change the logging level. C. increase the number of attempts on the sensor read.

Recommend: option C and A for now. Follow up with the long term option. That is... unless IC2 sensors are used in the future.

cron job should dump data to computer on the network, maybe on Google Drive, so I can see it anywhere

an internal humidity sensor went out, and was just reading 1% constantly. This was below the set threshold, so the fans never came on when the lights were off. Mold happened.

I suggest some sort of set number of readings, maybe a list that holds 24 previous readings. And if the number doesn't change for X readings, put the bucket into "alarm:True"

Growberry_web will have to signal the error somehow. I'm thinking coloring the grow's outline.

can we use this to look at the pictures?

The device just runs when the pi is on. So it needs a standby mode while nothing is growing.

you only get a few minutes of free weaved connection, so maybe just have it open the connection, dump the last hour of data?

When the sunrise is late, and the length of the day spans midnight, the times in the morning are not correctly registered.

Check logs to see if the length of sun.sinktemps is getting insanely long.

in the capture_data() function, the sinktemps are pulled, but never reset back to an empty list.

Should be easy to fix: just add -

sun.sinktemps = []

after data is captured.

If you activate the water pump in the interactive mode, and quit. It will leave the water pump on until the next pump cycle. Not ideal.

Would suggest that it checks the status of the water pump, before firing off the watering() function.

When a plant is done, there needs to be a way to dry the plant. Just vacuum out the water, and have lights off, but humidity control intact.

This can come from the “status” or “is active” setting. If the grow is in “drying” mode.

Some function to turn on the light for 30 seconds for taking an image, and collecting data. These images would be great.

should cleanup all GPIO pins upon 'ctr+c' or reboot
need to prevent lights from flashing during the night cycle.

pins are cleaned properly if program is killed using ctl +c or supervisorctl stop growberry_pi but when ran from the command line, and the ssh connection is terminated, the program stops running, and the lights stay on, while the fans turn off (fans power pin was on, but the pwm pin must have been off.)

This might be fixable with a pull up/pull down resistor on the pwm pin.

Also use signal module to install my own signal handler for SIGTERM (you would have it raise an exception, similar to KeyboardInterrupt).
https://docs.python.org/2/library/signal.html?highlight=signal#module-signal