Hi All, I've been reading the forums for a while, this is my first post and first thread.
With the release of the Raspberry pi Zero ($5USD); the raspberry pi is an increasingly appealing option for those wishing to automate their growing space while keeping costs low. I have looked at other projects for automation of this nature on the pi and other platforms, however I found that none of them quite fit what I had in mind for an ideal system.
I am not an amazing programmer, I am extremely inexperienced in the field of growing; I do however, have a great background in electronics, computing, and random tinkering.
The pi consumes a very small amount of power, and doesn't output a significant amount of heat. It is highly configurable, and extremely stable when the OS isn't messed with. With proper wiring, the pi can handle upwards of 256 sensors and relays; even more with some extra wiring. This allows for massive expansion if needed. When the system is not being taxed by heavy code and large bulky programs, the pi should have no problem keeping up with all of the sensor data and logic we can feed to it.
GHpi is being written entirely in bash, it is not CPU architecture dependent and thus should run without issue on any other platforms that are running Linux. The limitation being input output for relays and sensors. (More on this when a public release happens)
So today, I would like to present a preview and preliminary description of the first revision of my latest project, GHpi.
Features both existing and planned:
Alarms, Smoke, Flood, and Climate (entry/motion sensors planned)
Scheduling Groups, full control of Lighting, Nutrients, Water, Climate, and more.
Automatic Cycle Change, schedule your move from veg to fruit
CSV Data Export, easy graphing and analysis of your grows.
Fully configurable, use what you want, not forced to use what you don't want.
The main focus of this project is stability with the secondary objective being ease of use. I am still investigating which input method will be most the intuitive and easy.
The user interface is reminiscent of a terminal window from long ago. There are no current plans to significantly change the interface. It is totally up to the end user if they want to connect it to the internet or not - SSH works great to view the interface and is relatively secure when using 2048-bit RSA keys.
In an effort for better performance and thus higher stability, SQL is not being used.(I'm not saying SQL isn't stable, but the pi has limited computing power) Instead, data logged is exported into CSV files for later viewing. CSV makes it very easy to generate graphs and other reports. You can even view sweet ASC-II art graphs from within the interface, however, I'm still working on scrolling in the graphs.
Compatibility with a wide range of relays has already been achieved; I also have multiple popular sensors from different vendors on the way. Sadly there is a very wide range of sensors so I will not be able to support compatibility for each and every one. This may change over time as newer and less expensive sensor options become available or as I begin to realize that all of the sensors use the same bare metal parts lol.
Once a public version is released, I will include along with it a list of budget-oriented confirmed working, hardware, relays, sensors, and wiring diagrams. My goal is to have the least expensive, fully automated system while maintaining stability, reliability and usability.
Questions/Comments/Suggestions/Features are greatly appreciated.
With the release of the Raspberry pi Zero ($5USD); the raspberry pi is an increasingly appealing option for those wishing to automate their growing space while keeping costs low. I have looked at other projects for automation of this nature on the pi and other platforms, however I found that none of them quite fit what I had in mind for an ideal system.
I am not an amazing programmer, I am extremely inexperienced in the field of growing; I do however, have a great background in electronics, computing, and random tinkering.
The pi consumes a very small amount of power, and doesn't output a significant amount of heat. It is highly configurable, and extremely stable when the OS isn't messed with. With proper wiring, the pi can handle upwards of 256 sensors and relays; even more with some extra wiring. This allows for massive expansion if needed. When the system is not being taxed by heavy code and large bulky programs, the pi should have no problem keeping up with all of the sensor data and logic we can feed to it.
GHpi is being written entirely in bash, it is not CPU architecture dependent and thus should run without issue on any other platforms that are running Linux. The limitation being input output for relays and sensors. (More on this when a public release happens)
So today, I would like to present a preview and preliminary description of the first revision of my latest project, GHpi.
Features both existing and planned:
Alarms, Smoke, Flood, and Climate (entry/motion sensors planned)
Scheduling Groups, full control of Lighting, Nutrients, Water, Climate, and more.
Automatic Cycle Change, schedule your move from veg to fruit
CSV Data Export, easy graphing and analysis of your grows.
Fully configurable, use what you want, not forced to use what you don't want.
The main focus of this project is stability with the secondary objective being ease of use. I am still investigating which input method will be most the intuitive and easy.
The user interface is reminiscent of a terminal window from long ago. There are no current plans to significantly change the interface. It is totally up to the end user if they want to connect it to the internet or not - SSH works great to view the interface and is relatively secure when using 2048-bit RSA keys.
In an effort for better performance and thus higher stability, SQL is not being used.(I'm not saying SQL isn't stable, but the pi has limited computing power) Instead, data logged is exported into CSV files for later viewing. CSV makes it very easy to generate graphs and other reports. You can even view sweet ASC-II art graphs from within the interface, however, I'm still working on scrolling in the graphs.
Compatibility with a wide range of relays has already been achieved; I also have multiple popular sensors from different vendors on the way. Sadly there is a very wide range of sensors so I will not be able to support compatibility for each and every one. This may change over time as newer and less expensive sensor options become available or as I begin to realize that all of the sensors use the same bare metal parts lol.
Once a public version is released, I will include along with it a list of budget-oriented confirmed working, hardware, relays, sensors, and wiring diagrams. My goal is to have the least expensive, fully automated system while maintaining stability, reliability and usability.
Questions/Comments/Suggestions/Features are greatly appreciated.