v0.7.0

Breaking

• data.priority is no longer forwarded to phone (mobile_app) outputs.
  Critical alerts now carry the Home Assistant Companion critical keys instead.
  If you were setting data: {priority: high} to make an Android notification
  urgent, remove it. Every other kind of output — a bare notify.* service, a
  speaker, a webhook — still receives priority untouched.
• notify.notify and notify.send_message are refused as audience entries,
  including when typed by hand. notify.persistent_notification stays allowed.

Added

• Raise the importance when the house is empty, a new setting on the
  What happens when the house is empty step of a target. When nobody in its
  audience is home, the message moves up one step: normal becomes important,
  important becomes critical. It only bites on a target that notifies absent
  people; with a home_only presence rule an empty house means everybody is
  dropped anyway.
• A silence entity can publish a min_priority attribute — the data: block of
  a core schedule becomes state attributes — and then holds only the messages
  below that floor. A night that keeps the shopping list quiet and lets the leak
  alarm through, with no automation of your own. An unreadable floor silences
  everything; when several silences are on, the strictest decides.
• Make phones ring for critical alerts, a new setting on the Target used
  by default step, on by default. A critical message then reaches a phone
  with the Companion critical keys — the iOS critical sound, Android's
  alarm_stream channel. A key you set yourself is never overwritten.
• An audience may name a notify.* service or a notify entity — a kitchen
  speaker, a wall tablet, Telegram, Alexa, a notify group — instead of a person.
  Such an output has no presence, no silence, no snooze and no deferral, and
  receives only your data merged with the target's default data. A notify
  entity receives message and title and nothing else. The pickers list
  services; an entity is reached by typing its id.
• sensor.switchboard_routing_table, listing your targets and people for a
  dashboard card. It never exposes a target's default data.
• notify_switchboard.explain gains escalated and outputs, and its
  priority now reports the raised importance.
• The acknowledged event carries person alongside user_id.

Changed

• sensor.switchboard_routing_table publishes no state_class, so it is not
  compiled into long-term statistics; its two attributes are kept out of the
  recorder.
• A message routed to a notify.persistent_notification audience entry is not
  cleared when the alert ends, so it stays on the dashboard next to its own
  back-to-normal message.