Skip to content

Read Teslemetry operation mode from a local Powerwall - #986

Draft
Bre77 wants to merge 1 commit into
fm/pw-3-backup-reservefrom
fm/pw-4-operation-mode
Draft

Read Teslemetry operation mode from a local Powerwall#986
Bre77 wants to merge 1 commit into
fm/pw-3-backup-reservefrom
fm/pw-4-operation-mode

Conversation

@Bre77

@Bre77 Bre77 commented Aug 21, 2026

Copy link
Copy Markdown
Owner

Proposed change

Fourth rung of the local Powerwall data-reading stack for Teslemetry, on top of PW-3.

Routes the operation-mode select's read-back to the local Powerwall on a paired site, reading the verified top-level default_real_mode string from the local config.json coordinator. The existing local-first write path (with cloud fallback) is unchanged.

The preferred export rule stays cloud-only, as its local config mapping is unconfirmed in aiopowerwall. No entities are added.

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:
  • 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:

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant