I've done more work on my grow environment automation/monitoring system.
My basement is a consistently stable 52F, and 75% RH. Flower exhaust stays on low when the light is off. Veg tent light is 24/0. When temp gets above 77F in veg, it enables the exhaust fan until the temp goes back below 76F. The hot air is blown into the flower tent to keep the temp up above 56F.
When the flower lamp is on, the exhaust turns on at 78F, and turns off at 76F, keeping the temp stable at ~77F. I have a little fan running constantly exhausting just a slight amount of air in order to keep a minimum of negative airflow in the flower tent.
Although I have the dehumidifier code tested, I haven't implemented it into this prototype as of yet. Probably tomorrow. For now, it's just the fans that are automated.
Here's the main dashboard of all of the important pieces. Note the "Shroom" widgets. That's a new mushroom cabinet I built... my wife wants to do micro-dosing. I haven't yet added in my main production flower tent yet... the one being tested is my experiment flower tent, where I do breeding and such. If something goes horribly wrong, it's not that big of a deal:
Dashboard for my basement security:
Here's the dashboard for the important bits of the shroom cab:
I've added in some basic emergency alerting as well. So far, all I've added in is if one of the readings from a hygrometer is out of whack, it adds to the issue count of the specific element, and sends me an email and a text. Also, if there's a reading error, it enables the fan for the respective tent as an emergency measure to protect against a runaway heat situation:
Because everything is logged and can be visualized by graph over short or long periods, it makes it trivially easy to test out changes for efficiency and stability purposes and get immediate and long-term information on what works, and what doesn't. The data is also downloadable in a format that allows for programmatic analyzation and inspection.
One last thing to note... all of the automation is done locally on the microcontroller, and the Internet is not required for any operation. The only role the Internet plays is allowing the storage and visualization of data.
My basement is a consistently stable 52F, and 75% RH. Flower exhaust stays on low when the light is off. Veg tent light is 24/0. When temp gets above 77F in veg, it enables the exhaust fan until the temp goes back below 76F. The hot air is blown into the flower tent to keep the temp up above 56F.
When the flower lamp is on, the exhaust turns on at 78F, and turns off at 76F, keeping the temp stable at ~77F. I have a little fan running constantly exhausting just a slight amount of air in order to keep a minimum of negative airflow in the flower tent.
Although I have the dehumidifier code tested, I haven't implemented it into this prototype as of yet. Probably tomorrow. For now, it's just the fans that are automated.
Here's the main dashboard of all of the important pieces. Note the "Shroom" widgets. That's a new mushroom cabinet I built... my wife wants to do micro-dosing. I haven't yet added in my main production flower tent yet... the one being tested is my experiment flower tent, where I do breeding and such. If something goes horribly wrong, it's not that big of a deal:
Dashboard for my basement security:
Here's the dashboard for the important bits of the shroom cab:
I've added in some basic emergency alerting as well. So far, all I've added in is if one of the readings from a hygrometer is out of whack, it adds to the issue count of the specific element, and sends me an email and a text. Also, if there's a reading error, it enables the fan for the respective tent as an emergency measure to protect against a runaway heat situation:
Because everything is logged and can be visualized by graph over short or long periods, it makes it trivially easy to test out changes for efficiency and stability purposes and get immediate and long-term information on what works, and what doesn't. The data is also downloadable in a format that allows for programmatic analyzation and inspection.
One last thing to note... all of the automation is done locally on the microcontroller, and the Internet is not required for any operation. The only role the Internet plays is allowing the storage and visualization of data.
Attachments
-
44.1 KB Views: 8
Last edited: