> ## 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.

# Enovates

> Add Enovates chargers from their label: the phone joins the charger's own hotspot and points it at Plugchoice under its own Chargepoint ID.

Link sets up an Enovates charger, such as the ENO one, from the label in its installation guide. The phone joins the charger's own Wi-Fi hotspot, signs in to it, and points it at Plugchoice. Your user stays near the charger while it's set up.

| | |
| - | - |
| Models | All Enovates chargers |
| Onboarding method | `local_hotspot` (or `manual_ocpp`, by hand) |
| What the phone needs | `wifi`, `socket` |
| Network setup | Yes, by reconnecting it (`reconnect` has `network: true` and `needs` `wifi`, `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. A restart**

An Enovates only opens its Wi-Fi hotspot for setup when it starts. Your user switches it off at its breaker, waits 10 seconds, switches it on again, and waits until its light is back to its usual colour.

![Restart the charger: switch its breaker off, wait, and switch it on again, then wait for its light](https://developer.plugchoice.com/images/sdk/enovates-restart-light.webp)

**2. The label**

The installation guide has a label with an **ENO install** QR code, and above it the hotspot's name (SSID) and passkey. Your user scans the ENO install code, not the **User app** code next to it, or types the hotspot's name and passkey instead.

![Find the charger's label: the ENO install code, scanned](https://developer.plugchoice.com/images/sdk/enovates-label-light.webp)

**3. The setup**

The phone joins the charger's hotspot; your user taps **Join** when the phone asks. Link signs in to the charger with the passkey, checks that it's the charger on the label, and points it at Plugchoice. Before the hotspot closes, Link shows how the charger will reach the internet (Ethernet, Wi-Fi or mobile). Your user can connect it to a Wi-Fi network or change its mobile settings there. 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/enovates-network-light.webp)

**4. Online**

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

What to know:

* **Its Chargepoint ID stays.** Link leaves the charger's Chargepoint ID as it is. A charger without one gets its serial number.
* **The current operator comes along.** When the charger used another OCPP backoffice, it stays the charger's operator, with Plugchoice connected alongside.
* **No cards or history.** An Enovates doesn't keep its RFID cards or charging history where Link can read them, so nothing is imported.
* **The right label.** Link checks that the charger it reaches matches the label.
* **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 an Enovates that's already on Plugchoice reaching Plugchoice again, or moves it to another network, such as a new Wi-Fi router or Ethernet. Your user restarts the charger and scans its label. 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.

## What your app needs

* **iOS**: the Hotspot Configuration and Access Wi-Fi Information entitlements 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**: nothing beyond the SDK's setup. The charger serves its setup over a secure WebSocket, which the SDK trusts for that charger only. See [Android](https://developer.plugchoice.com/sdk/android.md).
* **React Native**: the config plugin sets everything up. 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.