How do I install the Ha IOS Push Live Activities skill?

Run npx skillmds@latest add home-assistant/ha-ios-push-live-activities in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Ha IOS Push Live Activities safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Ha IOS Push Live Activities?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Ha IOS Push Live Activities free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Ha IOS Push Live Activities?

home-assistant (@home-assistant) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Ha IOS Push Live Activities by home-assistant

Name: Ha IOS Push Live Activities
Author: home-assistant

Ha IOS Push Live Activities

Live Activities and push notifications across the local-push and remote-push delivery flows. Use when implementing or fixing notifications, Live Activities, payload parsing/promotion, alerting behavior, or the SharedPush parser (including the vendored relay copy).

File contents

Live Activities & Push Notifications

When implementing or fixing anything related to Live Activities (or push notifications generally), always check BOTH delivery flows — local push and remote push. They are handled by different code paths, so a field, behavior, or fix applied to one is easily missed in the other (e.g. a payload key parsed for APNs but dropped over local push, or alerting/sound handled differently per flow).

Remote push (APNs / cloud): Home Assistant → the push relay (Sources/PushServer) → APNs → the app / Sources/Extensions/NotificationService. The payload already carries a homeassistant dictionary.
Local push (WebSocket / NEAppPushProvider): delivered over the on-network channel and handled by Sources/Extensions/PushProvider + Sources/Shared/Notifications/LocalPush (LocalPushManager, LocalPushEvent). The payload arrives as a flat {message, data} shape and is reshaped by LegacyNotificationParserImpl (Sources/SharedPush/Sources/NotificationParserLegacy.swift), which must explicitly promote data fields into homeassistant — any field not in that promotion list is silently dropped on this flow only.

Both flows converge on NotificationCommandManager → HandlerStartOrUpdateLiveActivity → LiveActivityRegistry (Sources/Shared/LiveActivity), with the UI rendered by Sources/Extensions/Widgets/LiveActivity.

Practical checklist when changing this area:

If you add or read a notification/Live-Activity payload field, confirm it survives both the local-push parser promotion list and the remote-push payload.
Verify alerting behavior (sound, haptics, banner suppression, the silent flag) on both flows — local push presents notifications through LocalPushManager, not the system directly.
Sources/SharedPush is vendored as a separate copy under Sources/PushServer/SharedPush (the relay). Keep the two parser copies in sync when a parsing change is relevant to both the app and the relay; some logic intentionally lives in only one copy (e.g. the Live Activity live_update promotion is app-only, since the relay/cloud path already carries a homeassistant dict). When you change one copy, decide explicitly whether the other needs the same change.
Add/extend tests for both flows (e.g. Tests/Shared/LocalPushManager.test.swift for the local path, Sources/PushServer/Tests/SharedPushTests for the relay/parser).

---name: ha-ios-push-live-activitiesdescription: Live Activities and push notifications across the local-push and remote-push delivery flows. Use when implementing or fixing notifications, Live Activities, payload parsing/promotion, alerting behavior, or the SharedPush parser (including the vendored relay copy).---# Live Activities & Push Notifications**When implementing or fixing anything related to Live Activities (or push notifications generally), always check BOTH delivery flows — local push and remote push.** They are handled by different code paths, so a field, behavior, or fix applied to one is easily missed in the other (e.g. a payload key parsed for APNs but dropped over local push, or alerting/sound handled differently per flow).- **Remote push (APNs / cloud)**: Home Assistant → the push relay (`Sources/PushServer`) → APNs → the app / `Sources/Extensions/NotificationService`. The payload already carries a `homeassistant` dictionary.- **Local push (WebSocket / `NEAppPushProvider`)**: delivered over the on-network channel and handled by `Sources/Extensions/PushProvider` + `Sources/Shared/Notifications/LocalPush` (`LocalPushManager`, `LocalPushEvent`). The payload arrives as a flat `{message, data}` shape and is reshaped by `LegacyNotificationParserImpl` (`Sources/SharedPush/Sources/NotificationParserLegacy.swift`), which must explicitly **promote** `data` fields into `homeassistant` — any field not in that promotion list is silently dropped on this flow only.Both flows converge on `NotificationCommandManager` → `HandlerStartOrUpdateLiveActivity` → `LiveActivityRegistry` (`Sources/Shared/LiveActivity`), with the UI rendered by `Sources/Extensions/Widgets/LiveActivity`.Practical checklist when changing this area:- If you add or read a notification/Live-Activity payload field, confirm it survives **both** the local-push parser promotion list and the remote-push payload.- Verify alerting behavior (sound, haptics, banner suppression, the `silent` flag) on **both** flows — local push presents notifications through `LocalPushManager`, not the system directly.- `Sources/SharedPush` is vendored as a separate copy under `Sources/PushServer/SharedPush` (the relay). Keep the two parser copies in sync when a parsing change is relevant to **both** the app and the relay; some logic intentionally lives in only one copy (e.g. the Live Activity `live_update` promotion is app-only, since the relay/cloud path already carries a `homeassistant` dict). When you change one copy, decide explicitly whether the other needs the same change.- Add/extend tests for both flows (e.g. `Tests/Shared/LocalPushManager.test.swift` for the local path, `Sources/PushServer/Tests/SharedPushTests` for the relay/parser).

Frequently asked questions