Skip to content

v0.2.0

Choose a tag to compare

@github-actions github-actions released this 06 Sep 23:41
· 32 commits to main since this release
f6cdffe

Added

  • Five actions for callers that are not a Companion button — a dashboard card, a
    script, an automation: notify_switchboard.acknowledge, snooze, unsnooze,
    silence and unsilence. A refused or invalid call raises a translated error
    instead of being logged and swallowed.
  • A temporary, person-wide silence (silence / unsilence), from 1 to 1440
    minutes. It shows in binary_sensor.<person>_silenced with an until
    attribute, survives a restart, expires on the minute, and is bypassed by a
    critical message. Your configured silence entities are read, never touched.
  • Three optional per-target texts: Wording of the message and Wording of
    the back-to-normal message
    , both templates with the target's alert available
    as alert, and Title by default, used whenever a call gives no title. All
    three are empty by default.
  • A warning when the same unknown target or unusable person has been refused
    three times — a dashboard card left pointing at a renamed target.

Changed

  • binary_sensor.<person>_silenced is on when either kind of silence is
    running. Its sources attribute still lists the configured entities only.
  • A message silenced only by a temporary silence is dropped rather than held
    until morning: an hour of requested quiet should not become tomorrow. A
    configured night silence still holds it.
  • A message held for the morning re-checks the silence before going out and
    waits again if the night is still on. A critical message goes out
    regardless.
  • New Change somebody's devices and Edit a target menu entries open a
    form filled with what is stored, and a rejected form hands back what you
    typed. Opening a target to change one word no longer resets its other fields
    to their defaults.
  • Acknowledging is credited in the logbook to the person who tapped the card or
    the button, not to the integration.
  • The five actions are callable by any Home Assistant user, by design: the wall
    tablet runs under a non-admin account and its cards are the main caller. What
    bounds them is the target's own acknowledgement list, not the caller's role.