Skip to content

Add icons, state translations and enum mapping for OpenEVSE status sensor - #180329

Open
firstof9 wants to merge 4 commits into
home-assistant:devfrom
firstof9:openevse-status-enum-fix
Open

Add icons, state translations and enum mapping for OpenEVSE status sensor#180329
firstof9 wants to merge 4 commits into
home-assistant:devfrom
firstof9:openevse-status-enum-fix

Conversation

@firstof9

@firstof9 firstof9 commented Aug 26, 2026

Copy link
Copy Markdown
Contributor

Breaking change

The OpenEVSE status (Charging status) sensor states are now converted to snake_case enum values (e.g., charging, not_connected, gfci_self_test_failure). Existing automations or scripts checking for previous raw state values (such as Charging or not connected) will need to be updated to match the new enum state values.

Proposed change

Adds icons and state translations for OpenEVSE sensors/binary sensors, maps the charging status sensor to snake_case enum options (SensorDeviceClass.ENUM), and updates tests and snapshots.

This supersedes and resolves review comments on #174420.

Type of change

  • Dependency upgrade
  • Bugfix (non-breaking change which fixes an issue)
  • New integration (thank you!)
  • New feature (which adds functionality to an existing integration)
  • Deprecation (breaking change to happen in the future)
  • Breaking change (fix/feature causing existing functionality to break)
  • Code quality improvements to existing code or addition of tests

Additional information

  • This PR fixes or closes issue: fixes #
  • This PR is related to issue: openevse: Add icon translations #174420
  • Link to documentation pull request:
  • Link to developer documentation pull request:
  • Link to frontend pull request:

Checklist

  • I understand the code I am submitting and can explain how it works.
  • The code change is tested and works locally.
  • Local tests pass. Your PR cannot be merged unless tests pass
  • There is no commented out code in this PR.
  • I have followed the development checklist
  • I have followed the perfect PR recommendations
  • The code has been formatted using Ruff (ruff format homeassistant tests)
  • Tests have been added to verify that the new code works.
  • Any generated code has been carefully reviewed for correctness and compliance with project standards.

If user exposed functionality or configuration variables are added/changed:

If the code communicates with devices, web services, or third-party tools:

  • The manifest file has all fields filled out correctly.
    Updated and included derived files by running: python3 -m script.hassfest.
  • New or updated dependencies have been added to requirements_all.txt.
    Updated by running python3 -m script.gen_requirements_all.
  • For the updated dependencies a diff between library versions and ideally a link to the changelog/release notes is added to the PR description.

To help with the load of incoming pull requests:

@home-assistant

Copy link
Copy Markdown
Contributor

Hey there @c00w, mind taking a look at this pull request as it has been labeled with an integration (openevse) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of openevse can trigger bot actions by commenting:

  • @home-assistant close Closes the pull request.
  • @home-assistant mark-draft Mark the pull request as draft.
  • @home-assistant ready-for-review Remove the draft status from the pull request.
  • @home-assistant rename Awesome new title Renames the pull request.
  • @home-assistant reopen Reopen the pull request.
  • @home-assistant unassign openevse Removes the current integration label and assignees on the pull request, add the integration domain after the command.
  • @home-assistant update-branch Update the pull request branch with the base branch.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component, problem in config, problem in device, feature-request) to the pull request.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component, problem in config, problem in device, feature-request) on the pull request.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds translated enum states and icons to improve OpenEVSE entity presentation.

Changes:

  • Maps charging statuses to enum-compatible snake_case values.
  • Adds state translations and icons.
  • Updates status tests and snapshots.

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 1 comment.

Show a summary per file
File Description
homeassistant/components/openevse/sensor.py Adds status enum mapping.
homeassistant/components/openevse/strings.json Adds status translations.
homeassistant/components/openevse/icons.json Adds entity and state icons.
tests/components/openevse/test_sensor.py Tests status mappings.
tests/components/openevse/snapshots/test_sensor.ambr Updates enum snapshots.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment thread homeassistant/components/openevse/sensor.py

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 5 out of 5 changed files in this pull request and generated no new comments.

]

STATUS_MAP: dict[str, str] = {
"unknown": "unknown",

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

wouldn't it be easier to just replace any dash or space with an underscore?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants