rhizomatics/supernotify v2.16.2-beta1

on GitHub

⚠️ Deprecated

• Archive: purge_interval is ignored, since purges only run nightly or when purge_archive is called. It's gone from the options, and purge_archive no longer returns an interval

📝 Other changes

• Archive: mqtt_retain now defaults to off: with one topic per notification, retained messages built up on the broker forever, since housekeeping only removes files. An archive already set up keeps its setting

✨ Enhancements

• Pushover: new pushover_tags, so an emergency can be cancelled by tag with the pushover.cancel action
• ntfy: the notify entity the ntfy integration creates for each topic can be a target, selecting the ntfy delivery ahead of the generic Notify Entity one, so it gets priority, images and buttons. ntfy_device_id is no longer required, and is used when no ntfy entity is targeted
• LaMetric: the notify entity the LaMetric integration creates for each display can be a target, selecting the lametric delivery ahead of the generic Notify Entity one, so it gets priority sounds, icons and charts. Several displays can be targeted at once. device_id is no longer required, and is used when no LaMetric entity is targeted

🐛 Bug fixes

• Archive
  • purge_archive with days: 0 removed nothing, using the retention days instead, though it reported days: 0. It now removes every archive file
  • A relative archive, media or template path, such as the default supernotify/archive, was found from where Home Assistant was started rather than its config directory as the options say, so could end up elsewhere outside a container install
  • The startup log listed the diagnostics outcomes as the ones archived as events, rather than event_selection
  • An archive: section in the top-level supernotify: YAML, which isn't validated there, replaced the archive options, and with event_selection set stopped Supernotify starting. Settings the options own, like archive, dupe_check, housekeeping and the media and template paths, are now ignored in that YAML, with a single repair naming them
  • An archive: in the old notify: - platform: supernotify YAML was copied over the archive options on every start, undoing any change made in the options. It's now only used to fill in what the options don't have yet, when migrating
  • An archive path that can't be created or written to only logged a warning. It now raises a repair, cleared once the path works
  • An after or before in enquire_archive that isn't a date and time failed with an unexplained error, rather than being rejected with the field named
  • The choices in the notify, enquire_archive and reset_overrides actions - priority, outcome, delivery selection, dry run and kind - were shown in English only, or as PARTIAL_DELIVERY style names. They're now translated
  • Docs rewritten: every option and its default, that events need archiving on and are saved by the recorder, that retained MQTT messages are never cleared, the outcome table, which said ALL was the default, the delivery outcomes, the file naming, and an up to date example. The OTEL recipe's YAML, which Supernotify doesn't read, replaced with the options to set
• Kodi, Discord, Matrix: a delivery with no valid target was counted as a transport error. It's now skipped
• ntfy
  • A notification's data meant for other deliveries, such as clickAction for Mobile Push, was passed to ntfy.publish, which rejects anything it doesn't know, so the message failed. Only the ntfy fields listed in the docs are now passed on
  • Without ntfy_device_id, the delivery was counted as failed. It's now skipped
  • Docs rewritten: targets, all the data keys and their limits, that the image is sent as a URL, and the example config corrected
• LaMetric
  • The title was recorded as sent, though LaMetric has no title and it was never shown. The docs now say only the message is shown
  • Without a device_id, the delivery was counted as failed, logged only at debug level. It's now skipped with a warning
  • lametric_chart_data that wasn't a list was dropped with only a debug log. It's now a warning
  • Docs rewritten: the delivery config used a list rather than the delivery: mapping, the data keys listed, and the example call corrected
• Gotify: docs rewritten: the delivery config used deliveries: rather than delivery:, the default delivery is only used when named, failures in the HACS integration aren't seen by Supernotify, and outdated notes removed
• Pushover
  • pushover_device was sent in data, where the integration ignores it, so every device got the notification. Devices are now sent as the target, and a list is accepted
  • pushover_callback was sent as callback, which the integration ignores, so an emergency was never acknowledged to the webhook. It's now sent as callback_url
  • Docs rewritten: the integration is set up in the UI, not with platform: pushover YAML, the allowlist_external_dirs needed for images, all the data keys and their limits, and the example call corrected
• Persistent: docs extended for notification_id replacing an earlier notification, and for the delivery being opt-in

Full Changelog: v2.16.1...v2.16.2-beta1