Not really.I just came across remote GPIO using pigpio. Would this be a better way to control the system, the pi zero out in the greenhouse (or possibly a couple of picos) being controlled remotely over network by the more powerful RPi in the house with the display?
You probably want some local smarts in the greenhouse, and display and control in the house. Then, if the communication link is severed or the house unit crashes or goes offline the greenhouse will still look after itself.
There are probably two popular ways to do this:
Pi in greenhouse with web gui. Software on Pi controls greenhouse. Any device in network can query state/change things via web browser.
Microcontroller in greenhouse with some kind of interface (wifi, ethernet, serial). Pi in house interprets microcontroller data and presents nice web gui. Although, actually, a microcontroller can have a web gui these days.
There are other options, but basically you want to ensure that you can interact with the controller locally and remotely, so that you don't box yourself in.
Since we live in a distributed world you can put any feature anywhere, and link them together via the network. But it makes sense to have the bulk of the functions locally for safety and security. You might, for example, have an override in the greenhouse controller that always opens the windows if it gets too hot, or always closes them if it gets too cold, or always opens a valve for watering if things are too dry. Then it doesn't matter what happens in the house.
Whatever you do, the computational requirements for operating a greenhouse are miniscule.
Statistics: Posted by ame — Sat Jan 20, 2024 4:55 am