Add Noonlight integration#45718
Conversation
|
It seems that this PR is targeted against an incorrect branch since it has a parent PR on one of our codebases. Documentation that needs to be updated for an upcoming release should target the |
✅ Deploy Preview for home-assistant-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
There was a problem hiding this comment.
Pull request overview
Note
Copilot was unable to run its full agentic suite in this review.
Adds a new documentation page for the Noonlight integration, explaining setup, entities, actions, options, and usage examples for emergency dispatch automations.
Changes:
- Introduces integration docs with prerequisites and config flow steps, including sandbox vs production safety guidance
- Documents entities, action schema, dispatch lifecycle, options, and troubleshooting guidance
- Provides YAML automation examples for dispatch and cancellation flows
| | Entity | Type | Description | | ||
| | ------ | ---- | ----------- | | ||
| | `binary_sensor.noonlight_<site>_dispatch_pending` | Binary sensor | `on` during the cancelable entry-delay grace window. Use it to drive a CANCEL button in your dashboard. | | ||
| | `binary_sensor.noonlight_<site>_dispatch_active` | Binary sensor (safety) | `on` while a dispatch is live with Noonlight (responders requested). | | ||
| | `binary_sensor.noonlight_<site>_api_reachable` | Binary sensor (connectivity, diagnostic) | `on` while the [heartbeat](#heartbeat) confirms Noonlight is reachable and your token is valid. | |
| automation: | ||
| - alias: "Intrusion - Noonlight police" | ||
| triggers: | ||
| - trigger: state | ||
| entity_id: binary_sensor.front_door_glass_break | ||
| to: "on" | ||
| actions: | ||
| - action: noonlight.dispatch_police | ||
| data: | ||
| entry_delay_seconds: 30 | ||
| instructions: "Triggered by {{ trigger.to_state.name }}" |
| {% note %} | ||
| Caller, address, and site-label changes are **not** made in the options — they change what is sent to responders, so they are handled by the [Reconfigure](#reconfigure) action instead. | ||
| {% endnote %} |
c0ffeeca7
left a comment
There was a problem hiding this comment.
Thank you for contributing, 👍
As this PR is related to a code PR, please rebase and point this PR against the next branch.
If you do not want to rebase, try the following.
- Close this PR.
- Switch to the
nextbranch and pull the latestnextbranch. - Create a new branch based on that.
- Please restore the original PR template (see PULL_REQUEST_TEMPLATE.md)
|
Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍 |
5a83b50 to
8d1bff6
Compare
|
Rebased onto the latest |
c0ffeeca7
left a comment
There was a problem hiding this comment.
Please restore the original PR template (see PULL_REQUEST_TEMPLATE.md)
|
Restored the original PR template and filled it in (type of change, parent PR links, and checklist). Thanks for the review! |
8d1bff6 to
4caf82b
Compare
|
Thanks for the detailed review @c0ffeeca7! Addressed all three points:
|
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
4caf82b to
ad1a023
Compare
Proposed change
Documentation for the new
noonlightintegration, which connects Home Assistant to Noonlight's emergency-services dispatch API so automations can request a real police, fire, or medical response. The page covers setup (sandbox/production environments and the production safety acknowledgment), the entities and actions, the dispatch lifecycle, options, the reachability heartbeat, multi-property setups, and example automations.Type of change
currentbranch).currentbranch).nextbranch).nextbranch).Additional information
Checklist
currentbranch.nextbranch.