Summary
The Homie schema at GET /api/v2/homie/schema declares the following values for evse/status:
UNKNOWN, AVAILABLE, PREPARING, CHARGING, SUSPENDED_EV, SUSPENDED_EVSE, FINISHING, RESERVED, FAULTED, UNAVAILABLE
However, firmware has been observed publishing UNPLUGGED on evse/status, which is not declared in the schema. This was reported by a user whose integration raised an error when the value was not in the expected options list.
Questions
- Is
UNPLUGGED an intentional EVSE status value? If so, could it be added to the schema's enum format for evse/status?
- Is there a corresponding
PLUGGED value (or similar) that may also be published but not yet declared in the schema?
- Are there other properties where the firmware may publish values not yet reflected in the Homie schema?
Context
The OCPP-based status values in the schema (AVAILABLE, PREPARING, CHARGING, etc.) are well-documented, but UNPLUGGED does not appear in the OCPP 1.6 or 2.0.1 ChargePointStatus enumerations either. It appears to be a SPAN-specific addition.
Third-party integrations rely on the Homie schema as a reference for expected values. When firmware publishes undeclared values, integrations that validate against the schema can break. Keeping the schema in sync with actual published values would help avoid this.
Summary
The Homie schema at
GET /api/v2/homie/schemadeclares the following values forevse/status:However, firmware has been observed publishing
UNPLUGGEDonevse/status, which is not declared in the schema. This was reported by a user whose integration raised an error when the value was not in the expected options list.Questions
UNPLUGGEDan intentional EVSE status value? If so, could it be added to the schema's enum format forevse/status?PLUGGEDvalue (or similar) that may also be published but not yet declared in the schema?Context
The OCPP-based status values in the schema (
AVAILABLE,PREPARING,CHARGING, etc.) are well-documented, butUNPLUGGEDdoes not appear in the OCPP 1.6 or 2.0.1ChargePointStatusenumerations either. It appears to be a SPAN-specific addition.Third-party integrations rely on the Homie schema as a reference for expected values. When firmware publishes undeclared values, integrations that validate against the schema can break. Keeping the schema in sync with actual published values would help avoid this.