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

# Webasto

> Add a Webasto Next from the label in its manual: the phone joins the charger's own hotspot and points it at Plugchoice.

Link sets up a Webasto Next from the label that comes in its manual. The phone joins the charger's own Wi-Fi hotspot, signs in to it and points it 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 | The Next, 11 and 22 kW. Not the Unite. |
| Onboarding method | `local_hotspot` (or `manual_ocpp`, by hand) |
| What the phone needs | `wifi`, `lan` |
| Network setup | Yes, by reconnecting it (`reconnect` has `network: true` and `needs` `wifi`, `lan`) |
| 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 label**

The Next's manual has a label with Network on it: the charger's serial number, its master password, its Wi-Fi key and a QR code. Your user scans the QR code, or types the serial number, Wi-Fi key and master password instead.

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

**2. The setup**

The phone joins the charger's hotspot (its serial number, `NEXT-WS` and six digits); your user taps **Join** when the phone asks. Link signs in to the charger with its master password, checks that it's the charger on the label 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 or Wi-Fi. Your user can connect it to a Wi-Fi network by typing its name and password; the Next doesn't show the networks it can see. Then the phone returns to its own network.

![How the charger connects: Ethernet and Wi-Fi](https://developer.plugchoice.com/images/sdk/webasto-network-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 Next keeps its hotspot on, also once it's on Wi-Fi, so your user doesn't switch it off first.
* **Its Chargepoint ID is its serial number**, `NEXT-WS` and six digits, and stays that way: nobody can change it.
* **The current operator comes along.** When the charger used another OCPP backoffice, it stays the charger's operator, with Plugchoice connected alongside. Webasto's own backend the charger comes with doesn't count when the charger never connected to it.
* **No history or cards.** A Next doesn't show its charging sessions or its RFID cards, so none are imported.
* **The right label.** Link checks that the charger it reaches is the one on the label.
* **A changed password.** When the charger's master password was changed, your user types the new one instead of scanning 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 a Next 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 label again. Link checks that it's the charger on Plugchoice, points it at Plugchoice when it isn'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, 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 more. The charger serves its setup over HTTPS with a certificate of its own, which Link checks against the charger it joined. See [Android](https://developer.plugchoice.com/sdk/android.md).
* **React Native**: the config plugin sets up iOS. 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.