Hi folks. I'm tinkering with a process that will require a reasonable number of hardware integration points (temp/pressure/current). I've had very encouraging results with using node red on a Raspberry Pi to orchestrate this process, but am quickly going to exceed the I/O capability of a single board. (I'm also running into an issue with 1-wire polling causing everything to pause, but I think that might just need to be moved to a separate flow or instance of node-red)
So now i'm thinking about how to partition this a bit and leave node red on the Pi to do high level monitoring and control. My initial thought is to use arduinos to interface with the hardware, then put them on a common bus of some form to communicate with the Pi running node red. But then I think about the fact that I might end up breaking a lot of hardware-specific nodes that expect to talk with the device over a gpio pin or i2c bus. I also think about managing all of the sketches being a possible pain point as well.
Another option would be to find a big hat that expands what the single Pi can do.sufficiently to meet my needs. This is an attractive option if it just overlays the new I/O capability with existing (elg GPIO pins 30-50 or whatever) but then i start thinking about resource contention on the Pi.
I'm going to experiment with the arduino idea this weekend, but would love to hear from people that have gone down this path. Conceptually think of the application like a fully automated brewing station with mashing/sparging/boiling/pumping/etc all done by node-red.