Adventures in GHL'ing.

[JoeinLA]

I’m not sure if this is just a rant thread, but I wanted to detail my experiences with the GHL Connect software in case anyone is considering getting a GHL Profilux 4. I am using this (or at least trying to) on an iPad Pro, via the GHL Connect App, on an Eero Pro mesh network and have 1 gig internet service. TLDL: the headache you'll get from reading this post will give you a sense of the headache you'll get from this software.

1. When you first boot up the app on your home network, you’ll need to log in to your, or create a new, GHL account
2. You then select “Add Device”, and choose the Profilux new device icon. Note, this is the first of two Profilux devices you’ll need, and this first Profilux represents the Profilux via direct access through its internal hotspot.
3. Then, you have to disconnect from your home wi-fi network and connect to the Profilux’s own internal access point (it’ll be the “GHL[xyz]” when you search for new wi-fi hotspots). The default password is “Starfish”. This is all straightforward in the app itself.
   1. This was my first problem – once on the GHL Access Point, I kept getting a connection failed over and over. This led me to spending 30-45 minutes watching various youtubes trying to figure out if I had done anything wrong or missed a step.
   2. I believe the problem was with the VPN that comes with the Eero security software. Whenever I’m having a problem connecting to the Profilux access point / hot spot (more on this later), it seems to fix itself when I force the VPN off.
      1. Forcing the VPN off is a bit tricky since it seems to want to restart itself a couple of times before it realizes that you want it to stay off.
4. Once you’ve connected to the GHL via its Access Point, you then enter your home wi-fi network log in information.
   1. *at this point*, please go to the System tab and write down your Profilux “myGHL ID” – you will need to this to access the Profilux via web interface (see below).
5. The Profilux then creates a separate hotspot which has a “Profilux” name on it (and you can then change the name it whatever you want).
   1. The “GHL[xyz]” Access Point no longer shows up, but there’s now the “Profilux[xyz]” hotspot. It’s not clear to my why this is now a “Profilux[xyz]” hotspot where before it was the “GHL[xyz]” Access Point – not sure if that’s semantics or a security issue, or whatever, but there you go.
   2. One question that I haven’t yet figured out is whether you should go with Auto IP or Manual IP. I went with Auto IP because that seemed easiest (I mean, who doesn’t choose “Auto” for stuff like this). Not sure if that’s a source of the problems I’m facing now.
6. Once you’ve created the Profilux hotspot, you then need to add a SECOND Profilux device, which I understand is supposed to handle the connection via your home wi-fi network.
   1. Here is the point where I’m stuck: when I try accessing this via my home network, it always says connect failed. I can access this second Profilux when connected directly to the direct Profilux Hotspot.
      1. I do have the IP assigned to the Profilux via the Eero network. My current theory is that perhaps I don’t have the right port. By default, the port in the GHLConnect App is set to “80” – I need to figure out how to find the actual port assigned to the Profilux via the Eero network.
7. Going forward, note that if you want to connect via the direct Profilux hotspot, you have to FIRST connect to you home network and open the GHLConnect because this seems to be the only way to connect to you GHL account. FROM THERE, you have to switch to the direct Profilux hotspot without closing the GHL App, otherwise you lose the log in information from your GHL account.
   1. It seems like I have to keep the Eero VPN turned off any time I access the GHL App. This can get frustrating because the Eero VPN seems to want to turn itself on automatically (and even after you’ve turned it off) and repeats that when you switch networks (between your home network and the direct Profilux hot spot). It does feel like a bit of whack-a-mole.
8. Currently, I continue to be unable to access the Profilux via my home network. My current attempt at a solution will be to:
   1. See if the port numbering is wrong and whether that fixes anything
   2. Try to see if I can fix this by direct USB connect to my laptop and setting it up that way.
9. I did try accessing the Profilux via the website, but:
   1. First it asks for your myGHL ID (see step 4(a) above).
   2. I’m currently stuck here, because it says that it couldn’t find my Profilux and to confirm that (1) the Profilux is online and (2) that the firmware is 6718 or above.
      1. *NOTE* that the referenced firmware is the “Wi-Fi” specific firmware. On the system page where your myGHL ID is displayed, it will have a DIFFERENT firmware number. You have to go to the Network tab to get the firmware version for your “Wi-Fi” module.
         1. The fact that there are (a) different firmware “modules”, (b) that they’re displayed in completely different sections, and that (c) the information you need to do this is in two different sections, and that it’s entirely unintuitive that (a), (b), and (c) are even things that you have to figure out on your own, is just one example of what I hope this entire long post demonstrates – this software is terrible, unintuitive, and frustrating beyond imaging.

All of the above has cost me hours and hours of frustration and headaches. And I'm still unable to access the Profilux via my home network. I will update this post as further discoveries are made.

 

[JoeinLA]

oops delete

 

[JoeinLA]

Alright. sitting here in front of my open cabinet with a usb cable connected from my laptop to the GHL.

I've spent the last 2.5 hours on a lovely Sunday afternoon (1) monkeying around with the ipad, changing DNS settings, subnet masks, IP addresses, default gateways, switching back and forth between my home network and the Profilux access point, saving, being logged out, logging back in, re-saving, repeat, etc., etc., and (2) trying to get the GHL software to connect via USB, monkeying around with device manager, driver installations, com ports, uninstalling, reinstalling etc., etc.

This is some serious level of craziness. My last hope is trying to connect with GHL customer support directly. Hopefully they can figure it out.

Otherwise, I'm going to return all my GHL accessories, buy the cheapest android device and keep it as a dedicated device ala user "mywifeisgunnakillme". And then buy an Apex or a Hydros.

I would not recommend that anyone to buy this thing unless you can first confirm that it works with your network/system/settings.

 

[JoeinLA]

OK at 10:45 PM I am FINALLY able to connect through my home network - the final price of the puzzle was that the profilux’s default IP address was 192.168.4.1 which was also the same as my Eero router. Once I changed that (I used 192.168.0.1) in both the network setting (when connected to the ProfIlux via the ProfIlux hotspot) and also the device setting (on the list of devices menu for the GHL Connect app), I was able to connect to the “2nd” ProfIlux Device that‘a for the network connection.

heh. Serious hoops.

‘now to get It connected via web interface and then how to use this thing

 

[Mywifeisgunnakillme]

I’m not sure if this is just a rant thread, but I wanted to detail my experiences with the GHL Connect software in case anyone is considering getting a GHL Profilux 4. I am using this (or at least trying to) on an iPad Pro, via the GHL Connect App, on an Eero Pro mesh network and have 1 gig internet service. TLDL: the headache you'll get from reading this post will give you a sense of the headache you'll get from this software.

1. When you first boot up the app on your home network, you’ll need to log in to your, or create a new, GHL account
2. You then select “Add Device”, and choose the Profilux new device icon. Note, this is the first of two Profilux devices you’ll need, and this first Profilux represents the Profilux via direct access through its internal hotspot.
3. Then, you have to disconnect from your home wi-fi network and connect to the Profilux’s own internal access point (it’ll be the “GHL[xyz]” when you search for new wi-fi hotspots). The default password is “Starfish”. This is all straightforward in the app itself.
   1. This was my first problem – once on the GHL Access Point, I kept getting a connection failed over and over. This led me to spending 30-45 minutes watching various youtubes trying to figure out if I had done anything wrong or missed a step.
   2. I believe the problem was with the VPN that comes with the Eero security software. Whenever I’m having a problem connecting to the Profilux access point / hot spot (more on this later), it seems to fix itself when I force the VPN off.
      1. Forcing the VPN off is a bit tricky since it seems to want to restart itself a couple of times before it realizes that you want it to stay off.
4. Once you’ve connected to the GHL via its Access Point, you then enter your home wi-fi network log in information.
   1. *at this point*, please go to the System tab and write down your Profilux “myGHL ID” – you will need to this to access the Profilux via web interface (see below).
5. The Profilux then creates a separate hotspot which has a “Profilux” name on it (and you can then change the name it whatever you want).
   1. The “GHL[xyz]” Access Point no longer shows up, but there’s now the “Profilux[xyz]” hotspot. It’s not clear to my why this is now a “Profilux[xyz]” hotspot where before it was the “GHL[xyz]” Access Point – not sure if that’s semantics or a security issue, or whatever, but there you go.
   2. One question that I haven’t yet figured out is whether you should go with Auto IP or Manual IP. I went with Auto IP because that seemed easiest (I mean, who doesn’t choose “Auto” for stuff like this). Not sure if that’s a source of the problems I’m facing now.
6. Once you’ve created the Profilux hotspot, you then need to add a SECOND Profilux device, which I understand is supposed to handle the connection via your home wi-fi network.
   1. Here is the point where I’m stuck: when I try accessing this via my home network, it always says connect failed. I can access this second Profilux when connected directly to the direct Profilux Hotspot.
      1. I do have the IP assigned to the Profilux via the Eero network. My current theory is that perhaps I don’t have the right port. By default, the port in the GHLConnect App is set to “80” – I need to figure out how to find the actual port assigned to the Profilux via the Eero network.
7. Going forward, note that if you want to connect via the direct Profilux hotspot, you have to FIRST connect to you home network and open the GHLConnect because this seems to be the only way to connect to you GHL account. FROM THERE, you have to switch to the direct Profilux hotspot without closing the GHL App, otherwise you lose the log in information from your GHL account.
   1. It seems like I have to keep the Eero VPN turned off any time I access the GHL App. This can get frustrating because the Eero VPN seems to want to turn itself on automatically (and even after you’ve turned it off) and repeats that when you switch networks (between your home network and the direct Profilux hot spot). It does feel like a bit of whack-a-mole.
8. Currently, I continue to be unable to access the Profilux via my home network. My current attempt at a solution will be to:
   1. See if the port numbering is wrong and whether that fixes anything
   2. Try to see if I can fix this by direct USB connect to my laptop and setting it up that way.
9. I did try accessing the Profilux via the website, but:
   1. First it asks for your myGHL ID (see step 4(a) above).
   2. I’m currently stuck here, because it says that it couldn’t find my Profilux and to confirm that (1) the Profilux is online and (2) that the firmware is 6718 or above.
      1. *NOTE* that the referenced firmware is the “Wi-Fi” specific firmware. On the system page where your myGHL ID is displayed, it will have a DIFFERENT firmware number. You have to go to the Network tab to get the firmware version for your “Wi-Fi” module.
         1. The fact that there are (a) different firmware “modules”, (b) that they’re displayed in completely different sections, and that (c) the information you need to do this is in two different sections, and that it’s entirely unintuitive that (a), (b), and (c) are even things that you have to figure out on your own, is just one example of what I hope this entire long post demonstrates – this software is terrible, unintuitive, and frustrating beyond imaging.

All of the above has cost me hours and hours of frustration and headaches. And I'm still unable to access the Profilux via my home network. I will update this post as further discoveries are made.

Typical....

 

[gerard_zzz]

Luckily there are lots of users around the world who didn't have all this trouble.

 

[JoeinLA]

And unfortunately there appear to be lots of users who do. Ultimately GHL’s call on how they want to support and market this system but sticking your head in the sand and blaming users for not being network specialists or not wanting to spend multiple weekends dealing with frustration is going to cost you customers.

and, frankly, the kind of “if you don’t like our superior product don’t buy it” mentality communicates a level of arrogance and inflexibility and defensiveness that is it’s own turn off to supporting a product or company.

These forums are for communicating and sharing experiences. Hopefully some will find your statements regarding the level of network knowledge and luck required to properly use this system helpful. I don’t disagree with them as much as take issue with the snideness and snarkiness with which they seem to be communicated.

 

[csund]

I guess to summarize this was ultimately an issue on your end. Glad you were able to get that figured so you can enjoy your superior product!

 

[JoeinLA]

As with my/your/our back and forth on the other thread, this will be my last reply to these snide responses.

If by superior you mean one that is incredibly frustrating and painful, then no, I won’t enjoy that at all. ’I am not one who, as you say in the other thread derives pleasure or some sense of superiority by dealing with difficult to use products (re: your statement “There is definitely a level of satisfaction you feel setting something up so easily that so many struggle with.”).

I do think it’s incredibly telling that you feel so inclined to insult and derive satisfaction from those who “struggle” with that which you were able to do so easily. Perhaps you might want to give those types of comments a bit of introspection.

anyways, as in the other thread, I’ll let future readers interpret these posts as they will.

bye bye now.

 

[FullSend]

I'll offer up the only solution I know to the issue you experienced.

In the future if you are having issues connecting to a device start a continuous ping to the IP address you are expecting the device to be at. In your case it would have been "192.168.4.1". If the pings are returning power off the device, the pings should stop returning. In your case the pings would have continued to return, because the router is answering the pings. This would have let you know there is something more than the GHL device not working. Hinting at a duplicate IP on the network.

Glad you figured it out! These things are tough to work through and very frustrating.

 

[csund]

As with my/your/our back and forth on the other thread, this will be my last reply to these snide responses.

If by superior you mean one that is incredibly frustrating and painful, then no, I won’t enjoy that at all. ’I am not one who, as you say in the other thread derives pleasure or some sense of superiority by dealing with difficult to use products (re: your statement “There is definitely a level of satisfaction you feel setting something up so easily that so many struggle with.”).

I do think it’s incredibly telling that you feel so inclined to insult and derive satisfaction from those who “struggle” with that which you were able to do so easily. Perhaps you might want to give those types of comments a bit of introspection.

anyways, as in the other thread, I’ll let future readers interpret these posts as they will.

bye bye now.

I also get a huge amount of satisfaction from being able to read, something others seem to struggle with.

I guess you put more effort into your original post than looking for an answer to your problem.

 

[JoeinLA]

I'll offer up the only solution I know to the issue you experienced.

In the future if you are having issues connecting to a device start a continuous ping to the IP address you are expecting the device to be at. In your case it would have been "192.168.4.1". If the pings are returning power off the device, the pings should stop returning. In your case the pings would have continued to return, because the router is answering the pings. This would have let you know there is something more than the GHL device not working. Hinting at a duplicate IP on the network.

Glad you figured it out! These things are tough to work through and very frustrating.

Thanks for the input - FWIW, I never thought my Profilux wasn't working, just that the way it works is kind of (i.e., exceptionally) tough to figure out All my posts have lamented the user experience...

At this point, I'm pot-committed, as they say, so I'm hoping that the next steps in actually getting all this thing going will be downhill from here - setting up the leak detectors, water level detectors and shutoffs, perhaps light and pump controls, and eventually getting the dosing and ion director boxes up and running.

The Ion Director was the thing that really sold me on the system. It looks to be an amazing tool. As I read the various threads here about it, it seems like issues with the Ion Director are, as with my issues with the Profilux so far, unrelated to failure in hardware as much as the more human-interaction side of things

But certainly the Proilux is a great looking device and certainly feels "quality" as a piece of hardware. I think many of us "complainers" appreciate this and hope that GHL can get the message that providing some level of user-friendliness would go a long way in capturing market share b/c the unanimous opinion seems to be that their hardware is first rate.

 

[FullSend]

Thanks for the input - FWIW, I never thought my Profilux wasn't working, just that the way it works is kind of (i.e., exceptionally) tough to figure out All my posts have lamented the user experience...

I actually have a P4 and a KH Director in boxes still waiting for me to set up.
I'm hesistant because I keep reading threads like this one.

I would think the setting up the network is the most unforgiving piece. Good luck!

 

[JoeinLA]

I actually have a P4 and a KH Director in boxes still waiting for me to set up.
I'm hesistant because I keep reading threads like this one.

I would think the setting up the network is the most unforgiving piece. Good luck!

Ha! if I can actually help with the P4, let me know. I think the three things that were the primary cause of my difficulties were (1) my VPN app, which seems to interfere with directly connecting to the P4 AP/hotspot, (2) AutoIP vs. Static IP (and this was more a function of not getting to the 8.8.8.8 DNS server as I'm still on Auto IP (but plan on changing that eventually)), and (3) the overlapping IP addresses.

As others have pointed out, my lack of understanding of networking played its own role, and it sounds like you have that part well in hand!

Let me know how it goes with the KH Director, as I'll almost certainly be getting one of those eventually.

 

[*Ruffian*]

Network problems can be a PITA. The only issue I have had with GHL products is the USB Driver. I have to use a specific computer. However, I only needed it for firmware updates and Light Composer. Other than that, everything has gone pretty smooth.

I have recently installed the KH Director and am still figuring it out. The device is very sensitive to the configuration. Reagent pump needs to be calibrated to .1 ml and make sure you have enough of a vent on the reagent bottle. Starting to get consistent readings now. Awaiting my ION Director and expect the same.

My goal is to fully automate this tank other than cleaning the glass and changing filter floss. I am close, just need to add the ION Director and auto feeder.

I takes a little trial and error to get the programming logic working, but once you understand it, you should be able to do anything.

It is a sense of accomplishment when you see your tank handle water changes, top off, feeding and lights all from a single app. I did a lot of research on components to make sure everything would work with the profilux. If you ever have questions feel free to reach out.

 

[n2585722]

Sorry to hear you had such a hard time getting it going. I don't have any experience with GHL but the two brands I do have experience with I can say there is a learning curve to any controller if you have not used that brand before or used a controller before. Any of them can probably do what you need. It is just a matter of getting used to how the one you have works. More than likely the more you do with it the easier it will get to figure out how to accomplish what you want to do with it. Hang in there.

 

[JoeinLA]

Sorry to hear you had such a hard time getting it going. I don't have any experience with GHL but the two brands I do have experience with I can say there is a learning curve to any controller if you have not used that brand before or used a controller before. Any of them can probably do what you need. It is just a matter of getting used to how the one you have works. More than likely the more you do with it the easier it will get to figure out how to accomplish what you want to do with it. Hang in there.

Honestly, it’s nice to hear that each system has its own learning curve - I suppose there will be headaches regardless of system. FWIW, I’m starting to actually use the GHL for monitoring and heater/ light / pump / skimmer control and so far I’m quite pleased. I do think the network setup was absolutely horrendous and, at least to me, GHL would gain more market share if they hired a dedicated UX person. But all that being said, I’m starting to be affirmatively pleased with the controller, and I’m very much looking forward to exploring the system’s potential and also getting an KH and Ion director.

‘Fair enough, now that the networking issues seem to have been worked out, the tutorials amd other instructions are starting to actually be helpful. GHL, for the love of God, if you could only improve that initial customer experience, I think you’d save yourself and the rest of us an enormous amount of headache.

 

[HuneyBear]

Most of the recent network connection problems that are had seem to be involving the mesh networks. You are dealing with a wireless connection to a wireless connection that’s constantly reconnecting for security. The Wifi chip in the Profilux is a simple 2.4G chip. I wish they would just add a Lan port on it like the Doser myself, or made a card to add to put a lan port in but that’s not really feasible.

A cheap 2.4g non mesh router for just the P4 is the ticket to easier connection. I’d say they should sell their own but that’s a whole different market that already exists. I know that’s another $35-$50 but, what is your time and frustration worth. I have a dual band router and it works just fine as long as you have the right channel. Those that run the mesh networks are the ones that need the add-on router.

 

[Mistahbrock]

I’m not sure if this is just a rant thread, but I wanted to detail my experiences with the GHL Connect software in case anyone is considering getting a GHL Profilux 4. I am using this (or at least trying to) on an iPad Pro, via the GHL Connect App, on an Eero Pro mesh network and have 1 gig internet service. TLDL: the headache you'll get from reading this post will give you a sense of the headache you'll get from this software.

1. When you first boot up the app on your home network, you’ll need to log in to your, or create a new, GHL account
2. You then select “Add Device”, and choose the Profilux new device icon. Note, this is the first of two Profilux devices you’ll need, and this first Profilux represents the Profilux via direct access through its internal hotspot.
3. Then, you have to disconnect from your home wi-fi network and connect to the Profilux’s own internal access point (it’ll be the “GHL[xyz]” when you search for new wi-fi hotspots). The default password is “Starfish”. This is all straightforward in the app itself.
   1. This was my first problem – once on the GHL Access Point, I kept getting a connection failed over and over. This led me to spending 30-45 minutes watching various youtubes trying to figure out if I had done anything wrong or missed a step.
   2. I believe the problem was with the VPN that comes with the Eero security software. Whenever I’m having a problem connecting to the Profilux access point / hot spot (more on this later), it seems to fix itself when I force the VPN off.
      1. Forcing the VPN off is a bit tricky since it seems to want to restart itself a couple of times before it realizes that you want it to stay off.
4. Once you’ve connected to the GHL via its Access Point, you then enter your home wi-fi network log in information.
   1. *at this point*, please go to the System tab and write down your Profilux “myGHL ID” – you will need to this to access the Profilux via web interface (see below).
5. The Profilux then creates a separate hotspot which has a “Profilux” name on it (and you can then change the name it whatever you want).
   1. The “GHL[xyz]” Access Point no longer shows up, but there’s now the “Profilux[xyz]” hotspot. It’s not clear to my why this is now a “Profilux[xyz]” hotspot where before it was the “GHL[xyz]” Access Point – not sure if that’s semantics or a security issue, or whatever, but there you go.
   2. One question that I haven’t yet figured out is whether you should go with Auto IP or Manual IP. I went with Auto IP because that seemed easiest (I mean, who doesn’t choose “Auto” for stuff like this). Not sure if that’s a source of the problems I’m facing now.
6. Once you’ve created the Profilux hotspot, you then need to add a SECOND Profilux device, which I understand is supposed to handle the connection via your home wi-fi network.
   1. Here is the point where I’m stuck: when I try accessing this via my home network, it always says connect failed. I can access this second Profilux when connected directly to the direct Profilux Hotspot.
      1. I do have the IP assigned to the Profilux via the Eero network. My current theory is that perhaps I don’t have the right port. By default, the port in the GHLConnect App is set to “80” – I need to figure out how to find the actual port assigned to the Profilux via the Eero network.
7. Going forward, note that if you want to connect via the direct Profilux hotspot, you have to FIRST connect to you home network and open the GHLConnect because this seems to be the only way to connect to you GHL account. FROM THERE, you have to switch to the direct Profilux hotspot without closing the GHL App, otherwise you lose the log in information from your GHL account.
   1. It seems like I have to keep the Eero VPN turned off any time I access the GHL App. This can get frustrating because the Eero VPN seems to want to turn itself on automatically (and even after you’ve turned it off) and repeats that when you switch networks (between your home network and the direct Profilux hot spot). It does feel like a bit of whack-a-mole.
8. Currently, I continue to be unable to access the Profilux via my home network. My current attempt at a solution will be to:
   1. See if the port numbering is wrong and whether that fixes anything
   2. Try to see if I can fix this by direct USB connect to my laptop and setting it up that way.
9. I did try accessing the Profilux via the website, but:
   1. First it asks for your myGHL ID (see step 4(a) above).
   2. I’m currently stuck here, because it says that it couldn’t find my Profilux and to confirm that (1) the Profilux is online and (2) that the firmware is 6718 or above.
      1. *NOTE* that the referenced firmware is the “Wi-Fi” specific firmware. On the system page where your myGHL ID is displayed, it will have a DIFFERENT firmware number. You have to go to the Network tab to get the firmware version for your “Wi-Fi” module.
         1. The fact that there are (a) different firmware “modules”, (b) that they’re displayed in completely different sections, and that (c) the information you need to do this is in two different sections, and that it’s entirely unintuitive that (a), (b), and (c) are even things that you have to figure out on your own, is just one example of what I hope this entire long post demonstrates – this software is terrible, unintuitive, and frustrating beyond imaging.

All of the above has cost me hours and hours of frustration and headaches. And I'm still unable to access the Profilux via my home network. I will update this post as further discoveries are made.

Hello folks

I have been a first happy, and then increasingly grumpier GHL Profilux 4 owner for the past years, well since the release of the p4.

I soon found out that the GHL software was buggy and setting up the wifi is easiest to setup in the GHL control center via usb.

There is still an unfunctional autodetect ip addresse and the software is still full of artefacts and bug.

This is also the case in the GHL connect app on IOS

Yesterday I pointed out a couple of quircks in the latest Control center and got another teenish response claiming that my computer was the problem.

My test was made on two different windows 11 machines but this is how GHL responds.

I have reached a saturation point with this company and will not write them anymore.

GHL makes great hardware, but their programming skills are less than impressive and the react poorly on feedback.

So I predict many years of bugs and clumsy app and software from GHL.

Unless the either opensource the code or hire some skilled coders for the software side of the products they build.

And Id recommend Neptune Systems to any newcomers into buying a controller .

Hopefully you have succes setting up the box via usb / com port
( check the serial port for the p4 in device manager )

Best regards, Brock