Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
They have a suggestions link on their forum. Have made the suggestion there? You will have to be a member to post there, but if you have Hydros it is a good idea to become a member there. I just add the readings directly into a excel spreadsheet. I do that for the 4 auto alkalinity test which also does a pH and salinity tests at that time and I also post those in the same spreadsheet. The other tests I do with Hanna testers once a week and also post them in excel. Here is a link https://forum.coralvuehydros.com/Landed here from a google search on how to export data from Hydros. Almost 4 years now and they still haven't implemented it. I know they use an mqtt backend (Amazon iot), so it's not like they have to implement a whole new backend or something.
I bought into into Hydros because they are supposed to be less "locked in" which is panning out to be a pile of unpleasant stuff. The only reason to keep people from accessing their data is if you have a plan, even a long term one to lock it behind a subscription.
Curious what leads anybody to consider a system that can’t function at all without registering their devices with their cloud service, and requiring regular connectivity to that cloud service, “less locked in”.I bought into into Hydros because they are supposed to be less "locked in"
First stop was there, it was search result number 1 "after google noise"They have a suggestions link on their forum. Have made the suggestion there? You will have to be a member to post there, but if you have Hydros it is a good idea to become a member there. I just add the readings directly into a excel spreadsheet. I do that for the 4 auto alkalinity test which also does a pH and salinity tests at that time and I also post those in the same spreadsheet. The other tests I do with Hanna testers once a week and also post them in excel. Here is a link https://forum.coralvuehydros.com/
Buying into promises of a future feature, not the first vendor's promises I have fallen for.Curious what leads anybody to consider a system that can’t function at all without registering their devices with their cloud service, and requiring regular connectivity to that cloud service, “less locked in”.
One of the reasons for the cloud is for easy access to the system when you are not local. Someone without the right computer skills would have a hard time setting up static IP addresses for all the controllers and port forwarding along with a ddns service. It is easier to build it into the controller firmware to talk to a cloud server and for any apps to also talk to the same cloud server. On my previous controller I had to setup a static ip address for the head unit and setup port forwarding for it and get a ddns service to be able to access the controller when I was not at home.Buying into promises of a future feature, not the first vendor's promises I have fallen for.
So my frustration everytime I have to wait 30 seconds or more just to see my pH/ORP/temp etc is more on me than them for falling for a "cloud first" and "cloud ONLY" vendor.
I believe I qualified my statement with "cloud first" and "cloud ONLY" vendor. Making your service work with cloud does not equal being unable to make it work with local. Cloud and local are not mutually exclusiveOne of the reasons for the cloud is for easy access to the system when you are not local. Someone without the right computer skills would have a hard time setting up static IP addresses for all the controllers and port forwarding along with a ddns service. It is easier to build it into the controller firmware to talk to a cloud server and for any apps to also talk to the same cloud server. On my previous controller I had to setup a static ip address for the head unit and setup port forwarding for it and get a ddns service to be able to access the controller when I was not at home.
That is spin. There is a difference between cloud required and cloud enabled.One of the reasons for the cloud is for easy access to the system when you are not local.
Nonsense. The very same basic architecture used now could have been leveraged as optional — in addition to a full featured local interface without a cloud requirement at all. Full Stop.Someone without the right computer skills would have a hard time setting up static IP addresses for all the controllers and port forwarding along with a ddns service.
I bought into into Hydros because they are supposed to be less "locked in" which is panning out to be a pile of unpleasant stuff. The only reason to keep people from accessing their data is if you have a plan, even a long term one to lock it behind a subscription.
You do realize the Launch does not come with the salinity probe either so you would have to get it extra also. Neither does the X10. The salinity probe is separate on all the controllers that have that port. The controller only cost between the standard X3 and X3-S is $10 more so that is not much difference. The Blenny is also one that has been ask for quite a bit and it will cost less than buying 2 Minnows.Nailed it. Coralvue DOES NOT CARE what their users want. Proof is how they keep releasing products nobody has asked for. A cheaper Salinity option was one of the only things people asked for and they finally did that. Although once you buy it and the probe it isn't much cheaper than a Launch.
You do realize the Launch does not come with the salinity probe either so you would have to get it extra also. Neither does the X10. The salinity probe is separate on all the controllers that have that port. The controller only cost between the standard X3 and X3-S is $10 more so that is not much difference. The Blenny is also one that has been ask for quite a bit and it will cost less than buying 2 Minnows.
I think the thought behind the X3-S is for someone to add the salinity capability to an existing Hydros system instead of someone just starting. The Launch is now the way to go just starting out if you want salinity readings with your system. They have been selling the Hydros for over 4 years so my guess is that they thought enough people would want one of these to add to their existing system to make it worthwhile to make. You can also use it as a add on for a mix station also. I don't use widgets and as far as checking things I just click on the app tile on my iPad to check on things. I am an electronics tech so hardware is more my thing than software. I built my first computer back in 1976. I would not even think of doing that now though but I was younger then. I remember taking it to work to show everyone and my boss said "Why are you spending all your time doing that. Those will never amount to anything". Boy was he wrong though. My current Hydros does everything my old controller was doing and a lot more so I cannot complain since I get more out if it than my old system. It did not have a app or widget. It did have built in web pages but now the only web app that will work with it is foxfire. I am not sure how much longer it will though.. As far as the cloud it is needed for some things but the controller will continue to do what it was setup to do without it. I was without internet for 5 days straight after an ice storm. I did get in using bluetooth to check on things and had no issues but I could still initiate modes and override outputs if needed. It does require the cloud server to change settings since the app uploads the changes you make to the cloud and the controllers download the changes from the cloud server at this time.I do realize that. But you get ALOT more control out of a Launch than just the X3S. More people want a data stream to have widgets and such before more controllers that aren't necessary. It is 2025 and we can't even have a phone widget and there still isn't a way to turn off logging in every single time.
You have never once said anything negative about Coralvue. Do you truly think they are perfect? Because they are far from it.
The source of this data is the sensors and controllers, the choice to make this reachable only from the cloud and only from their app was a design choice, so deliberate, not an accidental consequence.I think the thought behind the X3-S is for someone to add the salinity capability to an existing Hydros system instead of someone just starting. The Launch is now the way to go just starting out if you want salinity readings with your system. They have been selling the Hydros for over 4 years so my guess is that they thought enough people would want one of these to add to their existing system to make it worthwhile to make. You can also use it as a add on for a mix station also. I don't use widgets and as far as checking things I just click on the app tile on my iPad to check on things. I am an electronics tech so hardware is more my thing than software. I built my first computer back in 1976. I would not even think of doing that now though but I was younger then. I remember taking it to work to show everyone and my boss said "Why are you spending all your time doing that. Those will never amount to anything". Boy was he wrong though. My current Hydros does everything my old controller was doing and a lot more so I cannot complain since I get more out if it than my old system. It did not have a app or widget. It did have built in web pages but now the only web app that will work with it is foxfire. I am not sure how much longer it will though.. As far as the cloud it is needed for some things but the controller will continue to do what it was setup to do without it. I was without internet for 5 days straight after an ice storm. I did get in using bluetooth to check on things and had no issues but I could still initiate modes and override outputs if needed. It does require the cloud server to change settings since the app uploads the changes you make to the cloud and the controllers download the changes from the cloud server at this time.
I know nothing about Neptune or other vendors in this space. I do know that most have dashboards that leave more than a little to be desired
They already use a standard protocol (mqtt) to send data to their IoT backend. This would quite literally be an option of adding a "Configure local mqtt" or something hidden behind advanced menus if they so wished to keep people from accidentally "breaking" the app.This isn't an issue of on or off prem data retention but rather how the application is accessed and if they have API access.
Neptune chose to allow access via an API call on the local network. It is not allowed to the Fusion portal. One can use Excel and import that data which an example is given in their documentation. Chapter 10 I believe but don't hold me to that. If one wants to go beyond that some of us use telegraph to grab the data and store in a time stamp type DB such as Influx and then use Grafana for pretty presentation or sending notifications.
I cannot speak if GHL does or does not allow similar. I do not own one.
Putting on my devils advocate hat for a minute one has to ask if this is important and a priority. Do you really want them to spend developers time and money on this for little use or rather fix other things that everyone uses? My point is how many people actually want to export data? Any idea other than the one or two posts here?
Yo this awesome, I was working on something similar to get my datalogs off the apex before they get cleared (cron+influx+grafana). Is this open sourced by chance?Very true. I honestly just use it for data retention and then will select the dashboard I want to look in more detail. Trends.
Here is one of my development dashboards as I am currently looking to see how Grafana handles monitor of data and alert notifications. To be honest I do this to keep busy or putter around with and nothing that is on display 24 x 7.
Some do sudoku, I play with data. I've not tried your bacon recipe yet though but seriously considering it. Hope your day is well.
![]()