Skip to content

Remove state attributes from the active binary sensors#388

Open
rhammen wants to merge 1 commit into
custom-components:masterfrom
rhammen:remove-binary-sensor-attributes
Open

Remove state attributes from the active binary sensors#388
rhammen wants to merge 1 commit into
custom-components:masterfrom
rhammen:remove-binary-sensor-attributes

Conversation

@rhammen

@rhammen rhammen commented Jul 7, 2026

Copy link
Copy Markdown
Contributor

Removes the extra_state_attributes dump from the charger and installation active binary sensors.

Why

Also (non-breaking): the charger's Zaptec DeviceId is now surfaced as the device Serial number in the device registry, matching the Zaptec app.

⚠️ Breaking change: the active charger/installation binary sensors no longer expose Zaptec fields as state attributes. Anything reading those attributes should switch to the dedicated entities.

Part of #297. Follow-up PR will add sensors for the few values that don't have an entity yet.

🤖 Generated with Claude Code

The charger and installation "active" binary sensors dumped the full
Zaptec object state as extra_state_attributes, refreshed on every poll.
Because that attribute set changes on nearly every poll and can exceed
Home Assistant's 16 KB limit, it caused recorder "State attributes ...
exceed maximum size" warnings (custom-components#382) and is the leading suspect for the
companion-app black screen (custom-components#386). Almost all of these values are already
exposed as dedicated entities, and the attributes have seen no real
troubleshooting use (custom-components#297).

Also surface the charger's Zaptec device id as the device serial number
in the device registry, matching what the Zaptec app shows. This is an
additive, non-breaking change.

BREAKING CHANGE: The active charger and installation binary sensors no
longer expose the Zaptec object fields as state attributes. Automations,
templates or dashboards that read those attributes must use the dedicated
entities instead.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@sveinse sveinse added this to the v0.9.0 milestone Jul 8, 2026
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.

2 participants