> ## Documentation Index
> Fetch the complete documentation index at: https://developer.plugchoice.com/llms.txt
> Use this file to discover all available pages before exploring further.

# go-e

> Add go-e Chargers from their reset card: the phone joins the charger's own hotspot and points it at Plugchoice under its own Chargepoint ID.

Link sets up a go-e Charger from the reset card that comes with it. The phone joins the charger's own Wi-Fi hotspot and points the charger at Plugchoice. It shows how the charger reaches the internet, and can connect it to Wi-Fi. Your user stays near the charger while it's set up.

| | |
| - | - |
| Models | All go-e Chargers: the PRO, Gemini, Gemini flex, Core and HOME |
| Onboarding method | `local_hotspot` (or `manual_ocpp`, by hand) |
| What the phone needs | `wifi`, `lan`, `socket` |
| Network setup | Yes, by reconnecting it (`reconnect` has `network: true` and `needs` `wifi`, `lan`, `socket`) |
| In a browser | By hand, or in the Plugchoice app when the charger goes to your user's own account |

## Adding a charger

**1. The reset card**

The back of the reset card has the charger's serial number, its hotspot key and a QR code. Your user scans the QR code, or types the serial number and hotspot key instead. The card's default password isn't needed.

![Find the reset card: the charger's code, scanned](https://developer.plugchoice.com/images/sdk/go-e-card-light.webp)

**2. The setup**

The phone joins the charger's hotspot (`go-e-` and its serial number); your user taps **Join** when the phone asks. Link checks that it's the charger on the card and points it at Plugchoice. It takes this at once, without a restart.

**3. Its connections**

Before the phone leaves the hotspot, Link shows how the charger will reach the internet: Ethernet, Wi-Fi or its own SIM, with the mobile network it's on. Your user can connect it to a Wi-Fi network from the ones the charger can see, or type another. Then the phone returns to its own network.

![How the charger connects: Ethernet, Wi-Fi and its mobile connection](https://developer.plugchoice.com/images/sdk/go-e-network-light.webp)

![Choose a Wi-Fi network: the networks the charger can see](https://developer.plugchoice.com/images/sdk/go-e-networks-light.webp)

**4. Online**

Link adds the charger to Plugchoice by its Chargepoint ID and waits until it connects.

What to know:

* **No restart.** A go-e keeps its hotspot on, so your user doesn't switch it off first.
* **Its Chargepoint ID stays.** A go-e connects as the ID at the end of its OCPP address, and Link keeps it. A charger without one gets `go-e-` and its serial number, the name of its hotspot.
* **The current operator comes along.** When the charger used another OCPP backoffice, it stays the charger's operator, with Plugchoice connected alongside.
* **Its charging history comes along.** A go-e keeps its sessions in go-e's cloud. Plugchoice imports them from there, with the meter reading at the start and end of each, and the card's number where go-e has it.
* **No cards.** A go-e doesn't show its RFID cards' numbers, so none are imported.
* **The right card.** Link checks that the charger it reaches matches the reset card.
* **No internet during the setup.** The phone is on the charger's hotspot for part of it, which has no internet. The SDK keeps the hosted flow working, and keeps the screen awake, because the hotspot drops when the phone locks.

## Reconnecting it, or changing its network

The `reconnect` action gets a go-e that's already on Plugchoice reaching Plugchoice again, or moves it to another network, such as a new Wi-Fi router. Your user scans the reset card again. Link checks that the charger still connects with the Chargepoint ID it has on Plugchoice, points it at Plugchoice when it doesn't, shows its connections so your user can connect it, and waits until it's back online. It imports nothing again.

## What your app needs

* **iOS**: the Hotspot Configuration and Access Wi-Fi Information entitlements, `_http._tcp` in `NSBonjourServices` (Link finds the charger on its hotspot by name) and `NSLocalNetworkUsageDescription`. On iOS 18 and later, AccessorySetupKit asks once per charger instead of on every join. See [iOS](https://developer.plugchoice.com/sdk/ios.md).
* **Android**: the charger serves its setup over a plain WebSocket on its hotspot (`ws://`). Android blocks plain connections in release builds unless your network security configuration allows them. See [Android](https://developer.plugchoice.com/sdk/android.md).
* **React Native**: the config plugin sets up iOS, `_http._tcp` included; Android's network security configuration is yours to set. See [React Native](https://developer.plugchoice.com/sdk/react-native.md).

In a browser, Link can't join the hotspot, so your user sets the charger up [by hand](https://developer.plugchoice.com/sdk/chargers/other.md), or in the Plugchoice app when the charger goes to their own account.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.