I disagree on the value of the tasks. They are a bandaid on a ancient foundation that is far out of date. Do they work? Most yes. However when thing don’t work together, I.e. set a V/O for maintenance and say, turn the heaters and skimmer off when it on.
Good luck with “fixing” any of it when it doesn’t work.
in the world we live in today, there’s no reason to have a product that requires line by line coding with limited functionality and requires every line of code be in the proper order or things simply don’t work.
Here’s another example of how dated the Apex is.
Setting up my Klir filter on my Hydros I set an alarm to alert me if the filter didn’t roll in 24 hours on the days it was programmed to roll. I set a second alarm to alert me if it rolled longer than it is programmed to roll.
The first alarm took 2-3 minutes on Hydros. It’s not even possible on Apex. Ok, it kinda is, but it’s a lot of long convoluted programming with room for many errors.
The alarm can’t be done either, at least not directly. There is a convoluted work around. With Hydros it was a few seconds to set it up.
The difference. Hydros is a modern more or less WYDIWYG, or at least point and click interface. It’s far more robust and can do many things Apex isn’t capable off. Apex on the other hand is 1980’s (being generous) technology with a bunch of bandaids to try and keep it working.
I get it. Neptune wants to have their own ecosystem. I mean they frequently compare themselves to Apple. That not too smart, it like comparing a 1902 Volkswagen to a 2021 BMW. Add to that you can’t build a ecosystem on cheap Chinese junk or by stealing other companies IP. Especially in a micro industry.
Hopefully BRS puts better management in place and spends money and time addressing core products at Neptune.