🐛 Bug fixes
titlewas missing as a top level field in the archived notification, now appears next tomessagefields at the top- Unrecognized scenarios now only logged as warnings if they are
require_scenarios, otherwise logged at debug level. This makes it easier to auto generate scenarios from other components or automations and not have lots of log noise - A blank
targetorcustom_target, as an emptied field in the action's UI editor leaves behind, is now ignored. It was taken as an explicit target, so the default recipients were not used and nothing was delivered - A
targetmapping with an invalid value, such as a mistypedentity_id, is now refused with the validation error. It was silently turned into a list of its keys, so the notification went to a target calledentity_id - An empty list in YAML for targets is now explicitly handled, and treated as selecting no targets, and no default recipient targets. The notification will only be handled by deliveries that don't require targets, or where delivery or scenario configurations inject their own targets.
✨ Enhancements
Mobile Push
2 new platform neutral that will translate into the Android and/or Apple device keys where available:
mobile_push_tap_url- what opens when the notification is tapped, for both platforms: iOSurl, AndroidclickAction. A path such as/lovelace/camerasopens in the Companion App, a full URL in the browser.mobile_push_live_view_entity- the camera iOS streams live when the notification is expanded (entity_id), independently of where the image comes from, e.g. a Frigate snapshot_url as the image and camera.driveway as the live view. It wins over the camera the transport would otherwise hand the device as an image fallback. Android has no live view, so it's left out there, so nothing happens, but also nothing breaks.
What's Changed
- feat: mobile push tap URL and iOS live view entity (package support RFC 8-9) by @lollox80 in #262
- [pre-commit.ci] pre-commit autoupdate by @pre-commit-ci[bot] in #280
Full Changelog: v2.14.0...v2.14.1-beta1