Adding a charger
1
The flyer
The flyer has a QR code next to the charger’s ID, its default password and its password recovery code. Your user scans the QR code, or types the details.
2
Finding the charger
Link looks for the charger on the Wi-Fi network the phone is on. When it isn’t there, your user restarts the charger with its breaker, and the phone joins the setup network the charger opens for 15 minutes after it starts.
3
The setup
Link signs in to the charger with the flyer’s password and adds it to Plugchoice. It reads the charger’s settings, cards and charging history, checks how the charger reaches the internet, points it at Plugchoice, and restarts it.
4
Electrical setup
Once the charger is online, Link asks about its electrical setup and applies it.
- Cards, history and the current operator come along. Plugchoice imports the charger’s cards and charging history. When the charger used another OCPP backoffice, Plugchoice keeps it connected alongside.
- A changed password. When the charger doesn’t accept the flyer’s password, Link offers to reset it with the recovery code. A password an installer set then stops working.
- One app at a time. The charger allows one connection. If Eve Connect or ACE Service Installer is connected, your user closes it and tries again.
- Another charger’s flyer. When the charger it reaches isn’t the one on the flyer, Link stops and asks for the right flyer.
What your app needs
- iOS:
_alfen._tcpinNSBonjourServices, andNSLocalNetworkUsageDescription. iOS only looks for the service types your app declares; without_alfen._tcp, Link can’t find the charger on the home network. If your user denies Local Network access, Link asks them to allow it in Settings. Joining the setup hotspot uses the Hotspot Configuration entitlement, and on iOS 18 and later AccessorySetupKit when you declare it. See iOS. - Android: nothing to add. See Android.
- React Native: the config plugin declares
_alfen._tcpfor you. See React Native.