v0.5.7 -- Location Awareness + Dots

v0.5.7 -- Location Awareness + Dots

Two coordinated changes ship together in this release: location-aware triggers, and a unified corner-dot pattern across signal-row buttons.

Location-aware triggers means every trigger fire now tells your automation where the signal came from. The event data gains receiver_entity_id, receiver_area_id, and receiver_area_name, resolved live from Home Assistant's area registry. If you use the same physical remote in multiple rooms, you can route your automations by room name without any Jinja templating. Trigger definitions gain an optional Receiver scope: leave it on "Any receiver" (the default, unchanged behavior) or pick one or more receivers so the trigger fires only when one of them observes the signal. Multiple triggers on the same signal are now supported, so you can create one trigger per room, each with its own name and scope. A single physical press captured by several receivers fires each matching trigger once.

The dots polish pass unifies the "this signal has state worth knowing about" indicators on a single dot-in-corner-of-button pattern. The Assign button shows a green dot when a signal is assigned; a small count appears inside the dot when it maps to more than one device command. The Trigger button shows a yellow dot with the same treatment. The old solid-fill "trigger on" styling is gone. Clicking the Trigger button on a signal that already has triggers opens a small picker so you can edit an existing trigger or add another. Assign and Trigger indicators refresh live across browser tabs.

Added

• Location-aware triggers with per-receiver scope. Reported by @blalor, with a workaround and independent endorsement from @Didgeridrew in the community forum thread (GH #34).
• Multiple triggers per signal fingerprint (each with its own receiver scope).
• Corner-dot indicators for Assign and Trigger across signal rows and device command rows.
• Trigger picker popover for signals that already have one or more triggers.
• Live refresh of Assign and Trigger indicators across browser tabs when a signal's assignments or triggers change.
• Spanish (es) translation for the setup and options dialogs. Contributed by @Waterbrain (GH #37, closes #36).

Changed

• The .trigger-on solid-fill styling on the Trigger button is replaced by the yellow corner-dot pattern.
• Signal Monitor tracks ditto attribution per-receiver, so simultaneous captures from different receivers no longer share state.

Notes

• Existing triggers migrate silently: their receiver scope is empty by default, which matches today's "fires on any receiver" behavior. No configuration changes required.
• The new receiver, area, and area name fields on the event payload are additive; automations that ignore them keep working.
• Scoped triggers require a native InfraredReceiverEntity on the receiving side (HA 2026.6+ with ESPHome using the modern platform). Legacy ESPHome-bridge captures continue to fire unscoped triggers.

Closes #34 and #36. Thanks to @blalor and @Didgeridrew for the report and the community-thread endorsement, and to @Waterbrain for the Spanish translation.

Minimum Home Assistant: 2026.4. Full changelog:
https://github.com/DAB-LABS/HAIR/blob/main/CHANGELOG.md