Skip to main content
Your app opens Link with an action. The action says what the link session does; the hosted flow decides how, for each brand and model. Every action but add works on one charger, which must be in the client session’s scope. See Client sessions and scopes.

Open an action

The SDK passes the action to the hosted flow without reading it. A new action therefore works in an SDK you already shipped, through the custom form, before the SDK gets a helper for it.

Add a charger

add is the default. Your user agrees to share their charger with you (the first time), picks the brand and model, and follows the steps for it: joining the charger’s hotspot, finding it on the home network, sending it the Wi-Fi over Bluetooth, signing in to the brand’s account, or typing its Chargepoint ID. Link waits until the charger is online, asks the electrical setup questions for models that have them, shows what it saves (settings, cards, charging history and the operator, asking whether your user uses one when the charger had none), and closes. What each brand needs is on Supported chargers.

Set a charger up

setup asks the electrical setup questions and applies the answers to the charger: one or three phases, the maximum current per phase, the grid type and the phase rotation. Offer it where the charger’s electrical_setup capability is capable.

Reconnect a charger, or change its network

reconnect gets a charger reaching Plugchoice again, whether it went offline or only needs a new network, such as a new Wi-Fi router. Link reaches the charger the way its brand connects: the home network for an Alfen, a Ratio io7 or a Volt Time Source or Source 2, the brand’s cloud for Easee or Zaptec, its hotspot for a Charge Amps, an Enovates, a go-e, a Peblar, a Volt Time ENO one for business or a Webasto, Bluetooth for a Ratio io5 or io6, SolarEdge, Teltonika, Wallbox or Volt Time One, Source 2s or Two Pro, or the steps to point it at Plugchoice by hand. It checks the charger’s OCPP connection and sets it when it’s wrong, shows the charger’s connections (Wi-Fi, Ethernet or mobile) on a screen of their own where its brand reports them, with the one it uses where the charger has that setting, and waits until it’s online. It imports nothing again, and asks the setup questions only when the charger’s setup isn’t done. Every charger can be reconnected. Use it for a Network settings button too: the charger’s reconnect capability says with network whether Link can change its network, and with needs what the phone must have. See Devices and capabilities.

When a charger can’t do an action

If the charger can’t do the action here (its model has no flow for it, or the phone lacks what it needs), or the action is one the hosted flow doesn’t know, Link shows what the charger can do instead and lets your user pick. The result’s action says which action the link session ended up doing.