- Joined
- Jul 16, 2009
- Messages
- 9,436
- Reaction score
- 15,800
They all have their pros/cons
I am not a fan of the Neptune stuff - I (sadly) think that they spend time and money fiddling with the ( rather ugly and NON modular) artistic aspects that would be better spent on reliability and better materials and design. Their ecosystem feels clunky and random with physical properties that scream toy. The hard tie and almost 100% reliance on their "cloud" is a hard stop. Also not a fan of the group of companies and business direction over the last 5+ years.
I don't know a lot about Hydros, nice modular idea but too many overlapping products and models for me to spend more than 2 minutes trying to sort out the mess. I was not clear on what (if anything) had local control and does not rely on the "cloud". I
I went with GHL based on several factors. The build quality, modularity and feature set are favorable. The programming interface is decent and available from a local connection (not reliant on the internet) For those who think it is too complicated, it has to be that way to expose the underlying feature set and power. It is extremely flexible. I am not a fan of their semi-attached cloud service. The system does not rely on the cloud for programing or operation, but most of the relevant dashboard functions (reporting) are round-tripped through their cloud and not served from the controller itself. I think this is a rather poor design decision and their cloud is painfully slow, making the entire ecosystem frustrating from a "reporting" standpoint, even if the system itself is pretty rock solid.
I am not a fan of the Neptune stuff - I (sadly) think that they spend time and money fiddling with the ( rather ugly and NON modular) artistic aspects that would be better spent on reliability and better materials and design. Their ecosystem feels clunky and random with physical properties that scream toy. The hard tie and almost 100% reliance on their "cloud" is a hard stop. Also not a fan of the group of companies and business direction over the last 5+ years.
I don't know a lot about Hydros, nice modular idea but too many overlapping products and models for me to spend more than 2 minutes trying to sort out the mess. I was not clear on what (if anything) had local control and does not rely on the "cloud". I
I went with GHL based on several factors. The build quality, modularity and feature set are favorable. The programming interface is decent and available from a local connection (not reliant on the internet) For those who think it is too complicated, it has to be that way to expose the underlying feature set and power. It is extremely flexible. I am not a fan of their semi-attached cloud service. The system does not rely on the cloud for programing or operation, but most of the relevant dashboard functions (reporting) are round-tripped through their cloud and not served from the controller itself. I think this is a rather poor design decision and their cloud is painfully slow, making the entire ecosystem frustrating from a "reporting" standpoint, even if the system itself is pretty rock solid.
