Conversation
Add `event_type: event_entity` blueprints that listen to state changes of Home Assistant `event.*` entities instead of bus events. Matter remotes (and Hue/Z2M event entities) expose one event entity per button; the switch is identified by its device id and buttons are told apart by a stable `entity_index` derived from the entity unique ids. - models.py: event-entity listener, registry lookup, discovery reports the device name alongside the id - panel: discovery dialog shows device names, protocol filter uses the blueprint service for event-entity blueprints (Matter shows up) - blueprint + image for the IKEA BILRESA dual button (E2489) - README: Matter roadmap status Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TgMsRMiBrUXar5McMMt8zX
Port the remaining pieces of PR #59 onto the event-entity connection type: - event data now carries the Matter `endpoint` (parsed from the unique id, also used to order the button index) and `presses`, the press / notch count Matter reports for batched multi-press events - blueprint actions accept `scale_field` (multiply service data fields by `data.presses` and run once, for relative values like brightness steps) and `repeat` (run the sequence N times, for discrete actions) - IKEA BILRESA scroll wheel blueprint + image (from #59, verified there on a live device), conditions rewritten to the plain key/value form Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TgMsRMiBrUXar5McMMt8zX
macpit
changed the title
10 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
event_type: event_entity. Listens to state changes of Home Assistantevent.*entities instead of bus events. Matter remotes (and Hue / Zigbee2MQTT event entities) expose one event entity per button; the switch is identified by its device id, buttons are told apart by the Matterendpoint(parsed from the unique id) or a stableentity_index– both survive renaming. Event data also carriespresses(Matter batches fast scrolling / multi presses into onemulti_press_Nevent).scale_fieldandrepeat(from Add Matter support (generic event-entity connection type) + IKEA BILRESA scroll wheel #59): multiply service-data fields bydata.pressesand run once (brightness steps on a scroll wheel), or repeat the sequence N times (discrete actions). Capped at 50.servicefor event-entity blueprints so Matter shows up.Closes #46, closes #51, supersedes #59 (thanks @tz8 – the scroll wheel blueprint, image and the scale/repeat idea are taken from there; the connection type was reimplemented on top of the generic listener with a registry based button index).
Test plan
data.presses/data.endpoint/data.entity_indexavailable in templatesscale_field:multi_press_2→ step 5 becomes 10, runs once;repeat: pressesruns the sequence 3× for 3 pressesfrontend/(rollup), hard reload needed at the same version because of the 31 day cache header – solved by the version bump🤖 Generated with Claude Code
https://claude.ai/code/session_01TgMsRMiBrUXar5McMMt8zX