Repository navigation
docs(changelog): the Ring Alarm integration is deployed - #1257
Merged
Merged
Conversation
…er joined ring-mqtt and Mosquitto are running on trinity, signed in by the runbook, and Home Assistant received 24 entities from the alarm. The base station is healthy, but its sensors, keypad and range extender all report waiting-for-join with no contact ever, and some of the household's devices are not on the Ring account at all. What remains is pairing them in the Ring app. architecture.md now says deployed rather than written. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
There was a problem hiding this comment.
🟡 Changes recommended
The public deployment record discloses physical-security coverage gaps that should remain in private commissioning notes.
1 open issue
What changed in this PR
Records the Ring Alarm integration’s deployment following #1256 and updates the sensitive tier’s current deployment status.
Changes:
- Adds a dated deployment record covering healthchecks, authentication, entity discovery and device-pairing observations.
- Marks Mosquitto and ring-mqtt as deployed in the architecture document.
| File | Description |
|---|---|
docs/changelog.md |
Adds deployment results without rewriting the earlier record. |
docs/architecture.md |
Updates trinity’s Ring integration status from written to deployed. |
Review effort: Balanced
…loyed # Conflicts: # docs/architecture.md # docs/changelog.md
… state Review: which alarm devices exist and what state they are in is a physical-security detail, withheld like camera coverage (docs/security.md). The entry now records the deployment, sign-in and discovery only. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Gerrrt
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
A changelog entry for the ring-mqtt deployment (#1256, ADR-0104):
The entry leaves out which alarm devices exist and what state they are in, for the reason
docs/security.mdwithholds camera coverage.architecture.md'strinityrow now says the services are deployed, not written.Why
Changelog entries are written on the day. The entry from earlier today left this "not yet deployed", and
architecture.mdis a current-state document that has to stay true.Blast radius
Docs only. Nothing on any host changes.
secrets/*.sops.yamlVerification
python3 scripts/check_docs.py: docs OK../scripts/lint.sh: passed, with 4 tools skipped locally (yamllint, ruff ×2, ansible-lint; none touch Markdown). CI runs the full set.The facts are from today's deploy:
make upoutput, ring-mqtt's log, the broker's connection log, and Home Assistant's entity registry.make validatepasses (docs only: check_docs and lint, as CLAUDE.md allows)Deployed to the lab and confirmed working
Docs updated (
docs/, service README, ordocs/roadmap.md)🤖 Generated with Claude Code