Add iOS Live Activities documentation#1303
Add iOS Live Activities documentation#1303rwarner wants to merge 6 commits intohome-assistant:masterfrom
Conversation
New page covering Live Activities (iOS 16.2+): payload fields, start/ update/end lifecycle, dismissal policy options, cross-platform YAML patterns with Android Live Updates, iPad limitations, iOS 18 rate limiting, privacy disclosure, and annotated screenshots from all major scenarios. - docs/notifications/live-activities.md — new page - docs/notifications/commands.md — adds end_live_activity to iOS command table; notes clear_notification also ends Live Activities - docs/notifications/basic.md — adds Live Activities subsection under iOS/macOS Specific (with sample automation); adds cross-platform tip callout and combined YAML example in Android Live Updates section - sidebars.js — registers live-activities under Notifications - static/assets/ios/ — 12 screenshots cropped from simulator video Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
Open to discussing the main "Live Activities" page and perhaps combining with Android and maybe using "Live Widgets" instead or something? Then referencing android like I did in the iOS section for more details in the "Live Activities page" |
Replace live_activity: true with live_update: true throughout. Both iOS and Android now use the same field — a single YAML automation targets both platforms with no platform-specific keys required. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
Can we combine the docs between iOS and Android? Since it uses the same tags but ignores the one that is not needed on each platform, can we make 1 doc with information boxes when needed to differentiate between platforms? @TimoPtr can help you if you need an android reviewer as well |
There was a problem hiding this comment.
Pull request overview
Adds end-user documentation for iOS Live Activities in the Home Assistant companion app docs, and wires the new page into the Notifications section navigation.
Changes:
- Adds a new Live Activities documentation page with lifecycle (start/update/end) examples and payload field reference.
- Updates notification command docs to include
end_live_activityand clarifiesclear_notification+tagbehavior. - Updates the main notifications basics doc to explain that
live_update: truetargets both Android Live Updates and iOS Live Activities, and registers the new page insidebars.js.
Reviewed changes
Copilot reviewed 4 out of 22 changed files in this pull request and generated 3 comments.
Show a summary per file
| File | Description |
|---|---|
docs/notifications/live-activities.md |
New Live Activities doc page with examples, payload fields, and limitations. |
docs/notifications/commands.md |
Adds end_live_activity and clarifies clear_notification behavior with tag. |
docs/notifications/basic.md |
Cross-platform note tying live_update: true to iOS Live Activities + adds an iOS subsection. |
sidebars.js |
Adds Live Activities page to the Notifications sidebar. |
static/assets/ios/live-activity-security-solo.png |
Adds a new screenshot asset referenced by the Live Activities page. |
|
Converting to draft until the above is done |
…stamp placeholder - commands.md: fix end_live_activity requirement from iOS 16.2+ to 17.2+ - live-activities.md: clarify that title/message are top-level data fields while Live Activity options go in the nested data.data block - live-activities.md: replace hard-coded Unix timestamp in dismissal_policy example with a placeholder so the snippet stays evergreen Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
… page Both iOS and Android use live_update: true — merge the iOS live-activities.md and Android Live Updates section (basic.md) into one unified reference page. - live-activities.md: rewritten to cover both platforms with platform badges, a shared payload fields table with per-field platform indicators, and platform-specific behavior sections (iOS Dynamic Island/rate limits/privacy, Android status bar chip/Samsung note/always-on display) - basic.md: collapse the verbose Android Live Updates section and iOS Live Activities section into short summaries linking to the combined page Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
Okay, I combined the more detailed information between Android's Live Updates and iOS's Live Activities into one page that dives into the specifics. Whereas the introduction page for notification has links that points people to that combined page. Let me know if I should update anything beyond that. Or whomever usually looks through the documentation to give it a once over. |
|
Drafting just so we dont merge it by mistake before the other PRs |
| ### Live Updates | ||
|
|
||
| On Android 16.0+ you can create "Live updates" notifications. These notifications are pinned to the top of the notification shade and appear on the lockscreen and always-on display. They will also display as a chip in the status bar with an optional short text. This might vary by manufacturer. | ||
| On Android 16+, `live_update: true` displays a persistent notification pinned to the top of the notification shade, the Lock Screen, and the always-on display, with a status bar chip. |
There was a problem hiding this comment.
I'm not a big fan to this new sentence having live_update as a the subject seems a bit weird.
|
|
||
| ### Option 2 — `end_live_activity` command  | ||
|
|
||
| Use this when you want to end the Live Activity without affecting other notifications. Requires iOS 17.2+. |
There was a problem hiding this comment.
| Use this when you want to end the Live Activity without affecting other notifications. Requires iOS 17.2+. | |
| Use this when you want to end the Live Activity without affecting other notifications using this specific tag. Requires iOS 17.2+. |
Do we really need that? It seems adding one more option that might be easy to bypass by using another tag.
There was a problem hiding this comment.
I agree with @TimoPtr. Can you please provide a real use case where you can't use the above command and need this one.
I don't see dismissal_policy as reason as you can wait in the automation and send the clear notification later.
There was a problem hiding this comment.
I am not familiar with how often people actually use this. It was more so included because we have the option.
From what I understand, the user could theoretically specify a longer timeout than the OS default of 4 hours. So if they wanted the live activity to complete but hang out more like 6 - 8 hours they could possibly do so with this.
Other than that, you could dismiss the live activity without clearing away other notifications that have the same tag without effecting them.
I'm fine with removing if you guys deem it unnecessary documentation fatigue and unnecessary code add
|
We have to consider here that although both platform's features have "Live" in their name and they have some overlap, they are not entirely the same. This shouldn't be an issue on the Introduction page but on the new page users might get the idea that these features are limited to Android 16+ when most of it is available on all versions. Perhaps we could rename the new page to something neutral like "Progress notifications". The Android 16+ requirement could then be limited to just the first paragraph (and the I'm also working on a PR for customization of the progress bar, if this is also added to the iOS notifications the documentation could be shared on the new page. |
- basic.md: add BETA badge to iOS Live Activity mention - commands.md: add iOS badge to end_live_activity row - live-activities.md: remove platform icons from page header (both platforms) - live-activities.md: update default dismissal policy with exact Apple doc value (4 hours) - live-activities.md: convert iPad limitation to :::warning admonition - live-activities.md: group rate limiting, expiry, privacy into :::note with Apple doc links for 8-hour and 4-hour limits Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Correct, perhaps we need to define a couple additional YAMLs marked as From searching, it seems like the following is the situation:
I'm open to tweaking things, I had tried to open the conversation when I first posted it since it seems we want to use the same PR Updates
Replied to all comments that need feedback |

Proposed change
Documents iOS Live Activities (iOS 17.2+), which lets Home Assistant automations push real-time state to the Lock Screen. Covers the full payload spec, start/update/end lifecycle, dismissal policy options, cross-platform YAML patterns shared with Android Live Updates, iPad limitations, iOS 18 rate limiting, and privacy disclosure behavior.
Changes:
docs/notifications/live-activities.md— new page with payload field reference, lifecycle examples, and screenshotsdocs/notifications/commands.md— addsend_live_activityto the iOS command table; notesclear_notificationwith atagalso ends a matching Live Activitydocs/notifications/basic.md— adds Live Activities subsection under iOS/macOS Specific with a sample automation; updates the Android Live Updates section to show thatlive_update: truetargets both platforms with a single field (no separate iOS key needed)sidebars.js— registers live-activities under Notificationsstatic/assets/ios/— 12 screenshots extracted and cropped from a simulator recordingType of change
Checklist
Additional information