Harden provider parity across Ring View - #6
Merged
thomasgregg merged 1 commit intoSep 13, 2026
Conversation
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.
Summary
Finish the official Ring / Ring-MQTT parity pass by making source discovery, editor structure, visible geometry, and documentation consistent across provider profiles.
What changed
_liveRTSP path.Provider boundary
Within capabilities exposed to Home Assistant, both profiles use the same Ring View fields, modes, controls, spacing, and status design. Sources can also be mixed by role.
Two-way audio remains intentionally limited to the official Ring Live view camera. Ring-MQTT exposes a one-way RTSP gateway and no microphone return path that Ring View can attach to. The editor remains structurally identical and shows a capability warning when talkback is enabled for an unsupported Live camera.
Edge cases covered
Verification
npm test -- --run— 187 tests passed.npm run check— passed.npm run build— passed.npm run test:browser— 116 tests passed on phone and desktop.git diff --check— passed.Stack
PR 5 of 5. Base:
codex/ring-mqtt-recordings.