Osprey72 wrote: ↑
Tue Jun 19, 2018 2:29 am
Ok, trying not to sound or come off brass, but I'm building a greenhouse, as stated in my original post (see the experimental sentence at the end).
As written, that came off as more of an aside than central to your listed requirements.
Now, if I must,
You must. Nobody here is a mind reader. You have a complex project ahead of you, and if you expect to get any useful help you need to adopt a more empathetic attitude.
This is why I am thinking of choosing the Pi Zero Wireless so that I only have to run as little wiring as needed.
noted, you're almost certainly going to have to run wiring for power. If you have other thoughts on the matter, you need to clue us in. We have no idea what already exists in your greenhouse (wired or
wireless), or what the layout might be.
As for computing demands, that is the question I am posing.
You haven't posed any such questions. You have sensors, yes. You want to gather the readings (with some yet-unknown requirements), sure. But you've said nothing
about what you're actually going to do with that data.
As for topology/architecture...I cannot say that there will be a given setup. It will all depend on the crop I am growing and the needs of that crop. Racks will have to be moved around possibly. This is why I am trying to go wireless. I know I am constrained a bit with some power plugs. Those units can be managed from the ceiling or dedicated racks that don't move. It's a "semi-fluid environment"...things can change...best way to describe it.
Then you need to understand that that fluidity also makes it difficult to give you any one simple answer that actually solves all your problems. It's quite possible you can wire dozens of sensors into one 0W, but also entirely possible that it only makes sense to wire just one sensor into another one. If this is something that's going to change a lot, it might make sense to go with a 0WH, but that comes with a corresponding price increase and a bit of additional complexity when it comes to the hardware/software configuration.
It may make more sense to use some kind of microcontroller with built in WiFi and MQTT support.
Why? can't the Pi handle this? Should I scrap this idea and just build my own microcontroller instead? Why reinvent the wheel when I can just add rubber? I've read so much hype that the Pi and Arduino are so bad A** and now there is doubt being cast? Clarification please...
The concept of overkill is what you're missing. The 0W is a tiny computer, but you have yet to describe anything that requires any significant computing needs that benefit from being local to the sensors. A microcontroller is more likely to be able to collect data and/or transmit it to a server for processing, all while sipping so little power that it could be run off a battery. While there could be some benefit from using the RPi platform for everything, nothing you're describing leads me to believe that such an architecture benefits you in any way. So, yes, "scrap" the notion that you don't want any microcontrollers, because a lot of what you have described seems to be screaming for something less complex than even a 0W.