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, and closes. What each brand needs is on Supported chargers.
Change a charger’s network
network sends a charger its network settings from the phone. Link shows only the network steps, then waits until the charger is online again. Offer it only where the charger’s network_setup capability is capable and the phone has every transport it needs. See Devices and capabilities.
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
reconnect brings a charger that went offline back to Plugchoice, the way its brand connects: the Wi-Fi from the phone for a Volt Time One, its hotspot for a Peblar, the home network for an Alfen, or the steps to point it at Plugchoice by hand. Every charger can be reconnected.
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’saction says which action the link session ended up doing.