Skip to content

Document EEBUS SHIP-ID configuration #910

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 24, 2025
Merged

Document EEBUS SHIP-ID configuration #910

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 10 additions & 1 deletion docs/reference/configuration/eebus.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -93,7 +93,16 @@ interfaces:

### `shipid`

Hiermit kann die zu verwendende Geräte-ID (SKI) definiert werden.
Hiermit kann die zu verwendende SHIP-ID definiert werden.
Dies sollte nur für Entwicklungszwecke notwendig sein.

Normalerweise generiert evcc die SHIP-ID automatisch aus der `machine-id` (auf realer Hardware) oder einer zufällig generierten Plant-ID (in Container-Umgebungen wie Docker), die in der Datenbank gespeichert wird.
Du kannst eine explizite Plant-ID über `plant` in der `evcc.yaml` oder die `EVCC_PLANT` Umgebungsvariable setzen – empfohlen für bessere Portierbarkeit.
Die SHIP-ID ist fest mit dem Zertifikat verknüpft – ändert sich eines von beiden, muss die Kopplung mit den Geräten neu durchgeführt werden.

:::warning Achtung
Ändere diesen Wert nicht manuell, wenn du nicht genau weißt, was du tust.
:::

**Beispiel**:

Expand Down
11 changes: 10 additions & 1 deletion i18n/en/docusaurus-plugin-content-docs/current/reference/configuration/eebus.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -93,7 +93,16 @@ interfaces:

### `shipid`

Defines the Device ID (SKI) to be used.
Defines the SHIP-ID to be used.
This should only be necessary for development purposes.

Normally evcc generates the SHIP-ID automatically from the `machine-id` (on real hardware) or a randomly generated plant ID (in container environments like Docker), which is stored in the database.
You can set an explicit plant ID via `plant` in `evcc.yaml` or the `EVCC_PLANT` environment variable – recommended for better portability.
The SHIP-ID is tied to the certificate – if either changes, pairing with devices must be redone.

:::warning Warning
Don't change this value manually unless you know exactly what you're doing.
:::

**For example**:

Expand Down