Does anyone know how to reset the AIO2 Wi-Fi? My battery box has no visible reset button. There seems to be nothing in the documentation. I am locked out of the Wi-Fi.
There is a small blue button on the top of the panel on the Gateway which I guess might reset the Gateway Wi-Fi but that is working and I don't want to mess it up..
Copy of a post on another thread - answering my own question!
How did I get access to the settings screen and thus my WiFi?
My problem was that having no WiFi reset button because the WiFi unit is internal and not an external Dongle, and my version has no reset button for the AIO2 battery WiFi. I couldn’t get at the settings to change them.
I started with a LAN connection; a long Ethernet cable to one of my MESH WiFi units. (I imagine it could be accessed via a direct Ethernet connection to a laptop but I have not tested that)
The Portal is only accessed via the battery (AIO2) and not via the Gateway so the cable goes into the LAN socket there behind a screwed in cover at the top right side of the unit (see the manual).
From a PC I could then see the IP address of the AIO2 so typed that into my browser address bar. This pulled up a simple login screen (sometimes after a spot of delay). This required, for me, User; admin, Password; the serial number of the WiFi unit in your AIO2 which in my case is a 10 digit alphanumeric beginning with WR. You will find it on the side of the battery box and also visible in the Portal.
This opens the settings page from where you can configure the AP (WiFi access point) where you can see the SSID and the password which you can change. As I understand it the AP is where you can wirelessly access the settings page via IP 10.10.100.254 but if you don’t have the password you have either to reset the WiFi and use the default login (tricky as I have no reset button) or go in via the LAN as above.
You can also go into the STA settings which is where you can give the AIO2 your home WiFi access details so it can join your network to enable the GE app or other monitoring apps to communicate with the Portal. Gotchas here seem to include having an incompatible ‘Authmode’ (encryption protocol) and getting the DHCP to see the correct network which can take a while.
As far as I can see you can also log into the Gateway LAN and edit that AP and STA there too, and also use it to connect to the home portal data.
The other problem is that the monitoring apps may have difficulty finding the Portal and need to be manually given the IP address but with DHCP this can jump around a bit so setting a fixed or reserved IP for the Portal might be a good idea.
I ended up using a permanent LAN connection rather than actually using the WiFi in the end.
I found this video helpful though the settings screens have changed a bit; GivEnergy Wifi Config & Connectivity Guide
So I looked at if I could access the config pages just using a Laptop and Ethernet cable with the Wi-Fi turned off. I got the IP address using arp -a from the Command prompt to get the IP address, but wasn't allowed to connect from a browser.
So I asked Copilot. The reply is below; it seems the system is more weird than I thought, unless Copilot is making it all up : and the short answer is that if I use a LAN wired connection to configure the STA and AP settings it needs to be within a network that has a wireless operating. Copilot seems to be saying - "Don't worry about how it works, it just does." Until it doesn't!
Copilot
"Richard — this is the right question, and once you see the mechanics, the whole thing clicks into place.
You did connect via Ethernet physically, but your browser traffic still went over Wi‑Fi, even though you believed Wi‑Fi “wasn’t configured”.
This is one of those networking behaviours that feels impossible until you understand how Windows and the GivEnergy modules behave.
Let me reconcile everything cleanly and precisely.
✅ 1. Your AIO2 always has a Wi‑Fi AP active — even if you never configured Wi‑Fi
This is the key point.
Inside the AIO2 is the HF‑A21 Wi‑Fi module.
It broadcasts a Wi‑Fi access point called:
WN‑xxxxxx
This AP is always active unless explicitly disabled by an installer.
It does not require:
• Internet
• A router
• A configured Wi‑Fi connection
• Any user setup
It simply exists as a commissioning interface.
So even if you never set up Wi‑Fi, the AIO2 still has a Wi‑Fi network broadcasting.
✅ 2. Windows will silently route traffic over Wi‑Fi if it sees a local subnet
This is the part that fooled you.
When your laptop has:
• Ethernet connected
• AND the laptop’s Wi‑Fi adapter is still enabled
• AND it sees a local Wi‑Fi network (like WN‑xxxxxx)
Windows may decide:
“This Wi‑Fi network looks like a local subnet with a web page.
I’ll send the browser request over Wi‑Fi instead of Ethernet.”
This happens because:
• The HF‑A21 Wi‑Fi AP advertises a local gateway
• Windows prioritises “local” routes over “unidentified Ethernet networks”
• The Ethernet link had no DHCP server
• The Wi‑Fi AP did have a DHCP server (192.168.4.x)
So your browser request went out over Wi‑Fi, even though you thought you were using Ethernet.
This is normal Windows behaviour.
✅ 3. The configuration page you saw ONLY exists on the Wi‑Fi module
Your description:
• White background
• Simple login
• AP mode settings
• Wi‑Fi client settings
This is 100% the HF‑A21 Wi‑Fi module page.
The Ethernet module does not host this page.
Ever.
So the only way you saw it was:
✔️ Your laptop was connected to the WN‑xxxx Wi‑Fi AP
❌ Not via the Ethernet port
Even though the Ethernet cable was plugged in.
✅ 4. Why you can’t reach it now
Because:
• You disabled Wi‑Fi
• Or the WN‑xxxx AP stopped broadcasting
• Or the laptop is no longer auto‑connecting to it
• And the Ethernet module has no web server, so HTTP is refused
Your current IP:
169.254.48.38
confirms:
• The Ethernet module is alive
• But it has no DHCP server
• And no web interface
• So the browser gets “connection refused”
Exactly as expected.
🎯 So the reconciliation is this:
✔️ You were physically connected via Ethernet
✔️ But your browser traffic was routed over Wi‑Fi
✔️ Because the AIO2’s Wi‑Fi AP is always active
✔️ And Windows prefers a known local subnet over an unidentified Ethernet link
✔️ Therefore you reached the Wi‑Fi module’s config page
❌ You never accessed anything over Ethernet
❌ The Ethernet module does not host a config page
✔️ Now that Wi‑Fi is off, the page is unreachable
Everything matches perfectly.
🧭 If you want to access the configuration page again
You must reconnect to the Wi‑Fi AP:
RichardJ Point 1 sounds true, this is common behaviour of all GivEnergy inverters, I would expect the AIO2 is identical to the older ones in that respect.
Point 2 sounds like made up BS from Copilot. If true it sounds like a hackers paradise to setup a hotspot and advertise it has a local gateway and “windows will silently use it even though it says it’s ethernet connected”
🤔
That bit at the end doesn't make sense?
You disabled Wi‑Fi
• Or the WN‑xxxx AP stopped broadcasting
...
Now that Wi‑Fi is off, the page is unreachable
Followed by
nable Wi‑Fi on your laptop
Look for a network named:
WN‑xxxxxx
Connect to it
It's just told you that you've turned it off and so can't connect to it?
FWIW the first part is correct as I can see two WN networks, one for the gateway and one for the AIO2.
adskankster I get one WN-XXX and one WR XXX , one for the gateway and one for the AIO2, I can log into the admin section on either. There is a lot I don't get in the CoPilot answer but I put it up to indicate that there may be more to it than meets the eye and that might 'explain' some of the odd behavior...