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

# Easee

> Add Easee chargers through Easee's cloud: the owner signs in, or confirms Plugchoice in the Easee app.

export const Screen = ({name, alt, caption, wide = false}) => {
  const style = wide ? {
    width: '100%'
  } : {
    width: '280px',
    maxWidth: '100%'
  };
  return <figure style={{
    margin: '1.5rem 0',
    textAlign: 'center'
  }}>
      <img className="block dark:hidden" src={`/images/sdk/${name}-light.webp`} alt={alt} style={{
    ...style,
    margin: '0 auto',
    borderRadius: '12px',
    border: '1px solid rgba(128, 128, 128, 0.25)'
  }} />
      <img className="hidden dark:block" src={`/images/sdk/${name}-dark.webp`} alt={alt} style={{
    ...style,
    margin: '0 auto',
    borderRadius: '12px',
    border: '1px solid rgba(128, 128, 128, 0.25)'
  }} />
      {caption ? <figcaption style={{
    marginTop: '0.5rem',
    fontSize: '0.875rem',
    opacity: 0.7
  }}>{caption}</figcaption> : null}
    </figure>;
};

<Note>
  Easee is a preview. It works on real chargers, and how your user signs in may change before it's final.
</Note>

Easee chargers are added through Easee's cloud. Plugchoice becomes the charger's operator at Easee, and Easee's cloud then connects the charger to Plugchoice. Nothing runs on the phone, so this works the same in your app and in a browser.

| | |
| - | - |
| Models | Easee Home, Easee Charge and the other Easee chargers |
| Onboarding method | `vendor_cloud` (or `manual_ocpp`, by hand) |
| What the phone needs | Nothing |
| Network setup | No: the Easee app changes the charger's Wi-Fi |
| In a browser | Yes |

## Adding a charger

Your user chooses how to connect it.

<Screen name="easee-choice" alt="How do you want to connect it: sign in to Easee, or use the Easee app" />

<Tabs>
  <Tab title="Sign in to Easee">
    <Steps>
      <Step title="Sign in">
        Your user enters the email and password of the Easee account that owns the charger. Plugchoice passes them to Easee to sign in, and doesn't keep the password.
      </Step>

      <Step title="Pick the charger">
        Link lists the chargers on the account, with the operator each one has now and whether it's already on Plugchoice. Your user picks one.

        <Screen name="easee-chargers" alt="Which charger: the chargers on the Easee account, with their current operator" />
      </Step>

      <Step title="Plugchoice becomes its operator">
        Plugchoice adds the charger to the site, reads its charging history, and becomes its operator at Easee. The charger usually comes online within a minute.
      </Step>
    </Steps>
  </Tab>

  <Tab title="Use the Easee app">
    <Steps>
      <Step title="Confirm Plugchoice in the Easee app">
        Link opens the Easee app (on a computer, Easee's website). Your user picks the site the charger is in and confirms Plugchoice as its operator.

        <Screen name="easee-app" alt="Confirm Plugchoice in the Easee app: open the app, pick the site, confirm" />
      </Step>

      <Step title="The serial number">
        Back in Link, your user types the charger's serial number: 8 letters and digits starting with E, on the charger's label and in the Easee app.
      </Step>

      <Step title="Online">
        Link waits until the charger connects to Plugchoice.
      </Step>
    </Steps>
  </Tab>
</Tabs>

What to know:

* **The current operator can stay.** Plugchoice replaces the charger's operator at Easee. When it had one, Link names it and your user can keep it connected alongside Plugchoice.

  <Screen name="easee-operator" alt="The charger was found, with its previous operator named and the choice to keep it" />
* **Charging history comes along** when your user signs in: Plugchoice imports the charger's sessions from Easee.
* **Easee may refuse.** A charger on a site that another operator manages can't be switched from the owner's account. Link says so and offers the Easee app instead.
* A charger that already has Plugchoice as its operator isn't switched again; it's just added.

## Reconnecting it

The `reconnect` action offers the same two ways: signing in to Easee, or confirming Plugchoice in the Easee app (no serial number needed then). It makes Plugchoice the charger's operator again when it isn't, and waits until the charger is online. Its network is changed in the Easee app, so its `reconnect` capability has `network: false`.

## When something goes wrong

Link shows these to your user and lets them try again, sign in again, or use the Easee app. You don't need to handle them.

| Problem | What it means |
| - | - |
| [`vendor-sign-in-failed`](/sdk/errors/vendor-sign-in-failed) | Easee didn't accept the email and password. |
| [`vendor-sign-in-required`](/sdk/errors/vendor-sign-in-required) | The Easee sign-in expired. |
| [`vendor-not-permitted`](/sdk/errors/vendor-not-permitted) | Easee didn't let this account change the charger's operator. |
| [`vendor-rate-limited`](/sdk/errors/vendor-rate-limited), [`vendor-unavailable`](/sdk/errors/vendor-unavailable), [`vendor-error`](/sdk/errors/vendor-error) | Easee is busy, can't be reached, or answered something unexpected. |

If neither way works, your user can choose **By hand** and set the charger up as [another OCPP charger](/sdk/chargers/other).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.