Bug: Multiple Charge Points are created with identical internal cpid ("charger")
Environment
Home Assistant 2026.7.2
OCPP integration v0.10.15
Two OCPP 1.6J charge points
Each charger has a unique Charge Point ID (CPID)
Example:
RATIO_P00000000004199
RATIO_P00000000012534
Problem
When configuring multiple charge points on the same OCPP Central System, the integration stores the internal configuration with:
"cpid": "charger"
for every discovered charger.
Although the WebSocket path and BootNotification correctly identify each charger with its unique CPID, the configuration keeps using the same internal value (charger).
This causes:
devices being overwritten
entities belonging to the wrong charger
firmware information being mixed
duplicate entity problems
only one functional charger appearing in Home Assistant
BootNotification is correct
The log clearly shows that both chargers connect correctly.
Example:
Websocket path:
/RATIO_P00000000004199
BootNotification accepted
charge_point_serial_number:
P00000000004199
and
Websocket path:
/RATIO_P00000000012534
BootNotification accepted
charge_point_serial_number:
P00000000012534
Therefore the problem is not caused by duplicate Charge Point IDs.
Root cause
The generated core.config_entries contains:
"RATIO_P00000000004199": {
"cpid": "charger"
}
"RATIO_P00000000012534": {
"cpid": "charger"
}
Both entries use the same internal identifier.
Changing them manually to
"RATIO_P00000000004199": {
"cpid": "RATIO_P00000000004199"
}
"RATIO_P00000000012534": {
"cpid": "RATIO_P00000000012534"
}
followed by recreating the Central System completely solves the issue.
After this modification:
both chargers appear correctly
each charger has its own entities
firmware versions remain separated
live measurements update independently
no device information is mixed
Expected behaviour
The integration should automatically use the discovered Charge Point ID as the internal cpid.
Instead of
"cpid": "charger"
it should generate
"cpid": ""
for every discovered charger.
Additional note
This is not Ratio-specific.
The problem should affect any installation with more than one OCPP charge point if automatic discovery assigns the same internal cpid ("charger") to every charger.
Bug: Multiple Charge Points are created with identical internal cpid ("charger")
Environment
Home Assistant 2026.7.2
OCPP integration v0.10.15
Two OCPP 1.6J charge points
Each charger has a unique Charge Point ID (CPID)
Example:
RATIO_P00000000004199
RATIO_P00000000012534
Problem
When configuring multiple charge points on the same OCPP Central System, the integration stores the internal configuration with:
"cpid": "charger"
for every discovered charger.
Although the WebSocket path and BootNotification correctly identify each charger with its unique CPID, the configuration keeps using the same internal value (charger).
This causes:
devices being overwritten
entities belonging to the wrong charger
firmware information being mixed
duplicate entity problems
only one functional charger appearing in Home Assistant
BootNotification is correct
The log clearly shows that both chargers connect correctly.
Example:
Websocket path:
/RATIO_P00000000004199
BootNotification accepted
charge_point_serial_number:
P00000000004199
and
Websocket path:
/RATIO_P00000000012534
BootNotification accepted
charge_point_serial_number:
P00000000012534
Therefore the problem is not caused by duplicate Charge Point IDs.
Root cause
The generated core.config_entries contains:
"RATIO_P00000000004199": {
"cpid": "charger"
}
"RATIO_P00000000012534": {
"cpid": "charger"
}
Both entries use the same internal identifier.
Changing them manually to
"RATIO_P00000000004199": {
"cpid": "RATIO_P00000000004199"
}
"RATIO_P00000000012534": {
"cpid": "RATIO_P00000000012534"
}
followed by recreating the Central System completely solves the issue.
After this modification:
both chargers appear correctly
each charger has its own entities
firmware versions remain separated
live measurements update independently
no device information is mixed
Expected behaviour
The integration should automatically use the discovered Charge Point ID as the internal cpid.
Instead of
"cpid": "charger"
it should generate
"cpid": ""
for every discovered charger.
Additional note
This is not Ratio-specific.
The problem should affect any installation with more than one OCPP charge point if automatic discovery assigns the same internal cpid ("charger") to every charger.