Same, but this thread.... yikes.
REDUNDANCIES
Using HYDROS as an example, we have a decentralized brain...a Collective as we call it, multiple brains working together as one cohesive unit.
These Controls are linked via the Command Bus Cable that is tug-proof, dust-proof, splash-proof, rather than a USB that could rust or get yanked, or a drop of water falls on it......
Using perhaps a HYDROS Control X4 and Control XP8 for example with a Heater, the X4 has the SENSE Ports, one of those being for TEMP Sensor. Meanwhile, the XP8 is handling the actual on/off of the heater controller via 120v controllable outlet.
ALWAYS use a heater controller!
Redundancy, what happens if that X4 and XP8 are disconnected by accident, what if the the temp sensor gets unplugged....what if HYDROS doesn't know what to do....you TELL it what it should do in the configuration.
For each output, there is the option for "If INPUT (Temp) or Dependency Unavailable...TURN ON or TURN OFF. If HYDROS doesn't know what it should do.
Let's continue using the Heater as an example...If HYDROS doesn't know what to do...TURN ON.
Therefore, now the Heater Controller (IceCap, InkBird, Helios, the dial on top of a glass heater, etc) is calling the shots, maintaining temperature.
HYDROS gets power from the wall source, HYDROS determines if the heater should be ON/OFF based on the temp...but if unknown, TURN ON. Therefore, the Heater Controller gets power and determines if the heating element should be on or off. Therefore, you have 2 layers of redundancy.
Let's go deeper into even more safety...the HYDROS Control XP8 has power monitoring on each outlet. We can set the power safe range for each output individually, lets say the heater is 300w, safe range we can set to 250w to 350w.
We need to ensure that when HYDROS turns the heater on, the heater controller is also attempting to turn on the heating element, we can ensure this by setting the Heater Controller to a degree higher than what the actual HYDROS goal is for temp. On a normal occurrence, it'll never get up to the heater controller temp as HYDROS would turn off the outlet at the tight HYDROS range. Now we have the extra layer of redundancy of power monitoring.
Further...HYDROS wants to keep the temp tight, perhaps less than a degree, but as we do so, we may be floating right around the turn on point or the turn off point...what we want to eliminate is that quick flipping ON/OFF/ON/OFF over and over again. Therefore, we can ENABLE ADVANCED settings and set our MIN On Time, which is how long the heater must remain on after coming on, and the MIN Off Time, which is the time the heater must be off before allowed to turn back on. With that we can eliminate rapid switching and save the lifetime of mechanical switches.
Further Further...what if one of those temps is higher than the other, or there's an issue with the temp sensor where its reading a temp, so its not unknown, but its not correct....well, add another temp sensor. In the standard HYDROS Heater Preset Family, if the 1st and 2nd temp sensor are greater than 2 degrees apart from each other...listen to the higher number, lets not cook the tank, plus fall back redundancy would fall to heater controller.
And we didn't even get to the part where you can then depend this on water level, flow, only while the return pump is on, and a LOT more. Just gotta set it up to act as you wish. It sounds difficult, but with HYDROS its all straightforward no coding, and if you need help, our support is just an email or call away.