Skip to main content
Link sets up a Teltonika TeltoCharge with the pairing code on its sticker. The phone reaches the charger over Bluetooth, imports its charging history (and its RFID cards, when it isn’t on OCPP yet), shows how it connects to the internet (and connects it to Wi-Fi when needed), and points it at Plugchoice. Your user stays near the charger while it’s set up.

​
Adding a charger

1

The pairing code

Link shows where the charger’s pairing code is: the last 6 digits of the installer code, on the sticker on the charger’s middle plate (or in its manual), with a drawing of the sticker.
2

Pick the charger

Link lists the TeltoCharges nearby, by the name they advertise, such as TeltoCharge-153816 or TeltoCharge2-a1b2c3. Your user picks theirs.
3

Pairing

The phone asks for the pairing code in its own pairing dialog. Link never sees the code. Plugchoice then registers the charger under its Chargepoint ID.
4

The setup

Link imports the charger’s charging history and shows how it connects. Your user can set up Wi-Fi by picking a network from the charger’s own scan (or typing one) and entering its password. They continue once one connection is up, and Link points the charger at Plugchoice.
5

Online

Link waits until the charger connects to Plugchoice.
What to know:
  • It pairs only just after it starts. A TeltoCharge accepts a new phone in the first 5 minutes after it’s switched on, and three wrong codes lock it until it restarts. When the phone doesn’t ask for the code, Link tells your user to switch the charger off and on, and try again.
  • 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. That backoffice’s OCPP password isn’t passed on.
  • Its charging history comes along. Link imports the charger’s sessions of the last two years, with the energy of each. A TeltoCharge doesn’t record which card started a session.
  • Its RFID cards come along when it isn’t on OCPP yet. A charger already on an OCPP backoffice leaves its cards to that backoffice and keeps none of its own.
  • Scanning for Wi-Fi drops its connection for a few seconds. The charger is back on its network shortly after.

​
Reconnecting it, or changing its network

The reconnect action gets a TeltoCharge that’s already on Plugchoice reaching Plugchoice again, or moves it to another Wi-Fi network. Your user picks the charger from the ones nearby, and Link checks that it connects with the Chargepoint ID it has on Plugchoice. Link points the charger at Plugchoice again when it doesn’t point there. Your user sees its connections, where they can give it another Wi-Fi, and Link waits until it’s back online. It imports nothing again.

​
What your app needs

  • iOS: NSBluetoothAlwaysUsageDescription. See iOS.
  • Android: BLUETOOTH_SCAN and BLUETOOTH_CONNECT. See Android.
  • React Native: the config plugin sets them up. See React Native.
In a browser, Link offers your app (the Plugchoice app, on Plugchoice’s own page) or setting the charger up by hand.