Recent content by HaulinAshe

No, the only schedules I attempted to share were the two feed period schedules where the pattern was Constant and the Value 0%. Outside of those two periods, the Sicce device had its own three schedules that were also Constant with a Value in the 50s. I was very careful not to send many changes...

The revised setup has run error-free long enough for me to say it works. The problem was including a Sicce 3rd Party Device in the same schedule as the Icecap GYREs instead of having a separate schedule dedicated to the Sicce. I doubt brands have anything to do with the problem I experienced...

I don't manually trigger Feed modes. I use independently timed autofeeders and schedule GYREs (driven by WAVE-LE) along with a Sicce SDC-9 Return Pump (powered by Hydros WiFi Outlet) to shutdown to 0% for 30-minute feeding periods. Note: I do not shut off the AC power to the Sicce controller...

Isolating the Sicce pump with it's own set of schedules appears to be working fine. Sharing a schedule(s) with two GYREs and with the Sicce as a third output device is what produced erroneous data/errors.

I did submit a support ticket. However, I'm not willing to continue operating my system with an unreliable return pump setup. So I deleted everything Sicce related and went back to the old setup. Since then I did have one hunch that it may have had something to do with using the two...

No, I am not running anything more than constant flow with two feed mode changes each day. The pump speed changes worked great and always matched between Hydros Schedule settings and Sicce ContrAll (within the 5% window). But the reported Water Temp value would arbitrarily go to zero(0) which...

I setup the Sicce SDC 9 return pump using the new 3rd Party Device Support feature and quickly experienced problems. Despite several days of reviewing and revising setups, I found the communications between Hydros and Sicce to be unreliable and often resulted in what appeared to be erroneous...

I could do that on my bigger collective system using a scheduled 0-10v output tied back to a 0-10v input. But on the smaller system that doesn't have any 0-10v I'm SOL.

Thanks @Danny , using the Depends On in conjunction with Minimum Off Time does work. I'm triggering off one of the GYRE pumps because they are on a schedule, and I have more than one feed cycle each day. The "ultimate fix" would be the ability to setup a Feed Mode and then schedule the mode...

Unless I've totally missed how to accomplish this, I've found no way to create a true startup delay time for Generic, Constant, Combiner etc. I'm not talking about setting a Minimum OFF Time, that's not the same. For example... ATO Pump driven by DRIVE Port Three(3) water level sensors used to...

My apologies for the typo. I meant to say that one of my Hydros systems doesn't have a WAVE controller installed, and did not mean to imply that Hydros doesn't make a WAVE controller. The system I'm discussing is run by a X3 with two Power-4.

The problem I ran into on this system is it does not have a WAVE controller and therefore the option to configure a Flow Pump type output is not available in Hydros. I worked around it by creating a separate Generic (dummy) output for each feed cycle (my feeders are autonomous), then...

I would like to have the ability to schedule a MODE change, say from Normal to Feed mode and back. This would be extremely useful for managing non-Hydros devices such as AC powered flow pumps connected to Hydros WiFi outlets and shutting them off during automated feeding cycles. It would...

@Carlos It's been over a year now, any update?

One of the handiest features for setup/changes/documentation on a collective is the Devices menu option. Then just click on the device name and you get a screen that shows every port and it's assignment (or Unused). Sure wish a single device system had the same menu option. The STATUS display...