🖥 &📱Both Platforms
Dynamic Actions
- Categories are no longer required for actions! In fact, later in this version series they'll likely become decorated with notes about being deprecated. They'll still be supported for a while, though.
- You can now specify the actions for a notification in the notification itself.
- Uses the same format as Android, so actionable notifications don't need to be defined more than once.
- All notifications can now include a camera
entity_idor maplatitude/longitudeand they will feature the dynamic attachments. You no longer need to use a category of map/camera. - See the updated documentation at: https://companion.home-assistant.io/app/ios/actionable-notifications
Known issues:
- If the actions don't show up, you may need to restart the device. Seems like an issue with upgrading in TestFlight.
- Dynamic actions and image/video (non-camera/map) attachments do not work together yet. This will be fixed in a later beta.
Other Platform-agnostic Notification Changes
- Notifications can now use
tag(instead ofapns-collapse-id) andgroup(instead ofthread-id). This works for devices running older versions of the app, too; the change was done on the Firebase side. - Actions now fires the event
mobile_app_notification_action, in a similar format as the Android app. The existing event will continue to fire, for backwards compatibility. - Added support for
clear_notificationcommand. Like Android, this requires usingtagto choose which notification to remove.
Location changes
- Improves location updates (that is, allow them) when you have the app set to reduced accuracy.
- Fixes another sub-100m-sized zone entering issue.
Miscellaneous
- Update look and feel of settings
- Fix crash in share extension
- Fix a high CPU use bug when in-app settings is open.
🖥 Mac-specific
This is a beta for macOS Catalina (10.15) or later. You can also install from the Mac App Store or disable beta updates in Preferences to stay on stable releases.
- Dynamic actionable notifications do not yet work on macOS.