Lucid Home Charging Station - won't connect to internet

geosynch

Active Member

Verified Owner
Joined
Jan 21, 2023
Messages
114
Reaction score
85
Cars
Air Touring, Ioniq 5
Referral Code
OWLPTRZ3
I am trying to install a (brand) new Lucid Charging station.

It is all wired in and installed and ready to go, except. I can't get it to connect to WiFi. Let me explain.

It does charge my car, but no more than 12 amps. Yes, I checked the dip switch setting, and it is where I want it (40 amps). I even tried charging the dip switch settings to 32 amps, just to see if something was wonky. But it is stuck at 12 amps.

I suspect this is because the station has never connected to WiFi. But I can't get it to connect.

Following the instructions, I've connected my laptop to the stations SSID (which is the station serial number). So, my laptop is connected to the station -- I can clearly see it is connected, the signalstrength is strong,but there is no internet access. No internet access is expected because the station has no internet access.

THe next step,per the instructions,is to use a browser (I'm using a Chromebook, so Chrome is my only option) and go to the IP address 192.168.5.1 The browser is giving an error message that says connection refused. I tried various different Proxy Server settings, and that didn't help (although I did get different error message is from the browser).

Any help out there? Thanks.
 
I'm going to try with a PC and a Macbook while I await the hive's response.
 
Same result with other browsers. I even tried my phone's wifi and browser. On hold with customer care now. Screensnap is is from the phone.
 

Attachments

  • Screenshot_20250606-171540.webp
    Screenshot_20250606-171540.webp
    30.4 KB · Views: 19
...Following the instructions, I've connected my laptop to the stations SSID (which is the station serial number). So, my laptop is connected to the station -- I can clearly see it is connected, the signalstrength is strong,but there is no internet access. No internet access is expected because the station has no internet access.

THe next step,per the instructions,is to use a browser (I'm using a Chromebook, so Chrome is my only option) and go to the IP address 192.168.5.1 The browser is giving an error message that says connection refused. I tried various different Proxy Server settings, and that didn't help (although I did get different error message is from the browser)...
Is your home wifi subnet 192.168.1.x ? If so, it is breaking the LCHCS's tcp-ip stack.

The LCHCS does not work on 192.168.1.x. You won't be able to connect to 192.168.5.1 when connected to its SSID, if your home wifi is 192.168.1.x. I know it sounds crazy. A firmware bug (a conflicting hardcoded IP address) in the LCHCS that has gone unaddressed for 2+ years.

And once you do get it connected to your home network at 192.168.1.x, your router will show it as on the network, but it won't communicate.

My LCHCS is on my guest network at 192.168.2.x for this reason.
 
Last edited:
It's surprising that Lucid has not fixed this yet @marqie. In my experience, 192.168.1.x is the most-common default home router subnet.
 
@geosynch you are the second person to post about this problem, this week.
 
Turn off your home wifi, leave it off, power cycle the LCHCS, and try to connect to 192.168.5.1 again.
I realize that the two wifi networks should have no problem coexisting, but the LCHCS has a bug.
 
Is your home wifi subnet 192.168.1.x ? If so, it is breaking the LCHCS's tcp-ip stack.

The LCHCS does not work on 192.168.1.x. You won't be able to connect to 192.168.5.1 when connected to its SSID, if your home wifi is 192.168.1.x. I know it sounds crazy. A firmware bug (a conflicting hardcoded IP address) in the LCHCS that has gone unaddressed for 2+ years.

And once you do get it connected to your home network at 192.168.1.x, your router will show it as on the network, but it won't communicate.

My LCHCS is on my guest network at 192.168.2.x for this reason.
Wow. 192.168.1.x is the most common home IP address.

But my home is set up for 10.0.0.x

I'll try the suggestion of turning off the home Wi-Fi and trying again. But not tonight. Got other stuff to do.

Does anyone think this is the reason I can't charge at >12 amps?

Customer Care didn't think the two problems were related.
 
Wow. 192.168.1.x is the most common home IP address.

But my home is set up for 10.0.0.x

I'll try the suggestion of turning off the home Wi-Fi and trying again. But not tonight. Got other stuff to do.

Does anyone think this is the reason I can't charge at >12 amps?

Customer Care didn't think the two problems were related.
They are unrelated.
 
Just for sanity sake. Have you checked the breaker end to see if it's actually sending 40AMPs? It's possible you have a bad breaker.
Great question. This same circuit has supported an EVSE on a NEMA 14-50 plug for the past 10+ years. I swapped out the plug and now have the Lucid unit hardwired in the same spot.

50A breaker, 6AWG wiring, dip switches set for 40A. I even tried setting the DIP switches at the 32 A setting, just to see if I had misread up for down. Same result - 12 A.
 
Anyway, the breaker can't reduce the amount of current. It can only pass whatever amount of current the load demands, or trip.
 
Based on how well Lucid implements SW updates on the Air, I think I'm better leaving my HC off the network.
There haven't been any software updates to the LCHCS for at least two years, so I don't think you have to worry about introducing any new bugs soon.
 
There haven't been any software updates to the LCHCS for at least two years, so I don't think you have to worry about introducing any new bugs soon.
There have been two. But extremely early on, possibly before you got one. It was like… the first few days I got it.

Also I’m an old man now and my memory isn’t what it used to be so it’s possible I’m completely making that up.
 
There have been two. But extremely early on, possibly before you got one. It was like… the first few days I got it...
I recall one update just when I got my LCHCS, but that was well over two years ago.
 
Back
Top