Skip to content

Harden provider parity across Ring View - #6

Merged
thomasgregg merged 1 commit into
codex/ring-mqtt-recordingsfrom
codex/ring-mqtt-parity-hardening
Sep 13, 2026
Merged

Harden provider parity across Ring View#6
thomasgregg merged 1 commit into
codex/ring-mqtt-recordingsfrom
codex/ring-mqtt-parity-hardening

Conversation

@thomasgregg

Copy link
Copy Markdown
Owner

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

  • Auto-discover a renamed Ring-MQTT Event Select and its same-device Snapshot camera when creating a new card.
  • Keep Device snapshot camera in one always-visible Snapshots section for both providers; mark it required only when the selected preview mode needs it.
  • Add provider-profile fixtures covering official Ring recording/activity and Ring-MQTT Event Select/activity sources.
  • Assert identical visual-editor schemas across those profiles.
  • Measure and compare phone/desktop card and viewer geometry for the media frame, title/activity block, mode switch, header actions, and visitor controls.
  • Document the exact source mapping for recording, Live, dashboard stills, snapshots, Ding alerts, activity, and door access.
  • Document Ring-MQTT’s one-time Home Assistant camera setup for its _live RTSP 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

  • Renamed MQTT Event Select and Snapshot entities.
  • Disabled or ambiguous same-device snapshot cameras.
  • Ring-MQTT-only and mixed installations.
  • Optional versus preview-required snapshot configuration.
  • Official and MQTT activity sources with identical visible placement.
  • Native camera playback versus direct Event Select video without layout drift.

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.

@thomasgregg
thomasgregg merged commit a8fc1ec into codex/ring-mqtt-recordings Sep 13, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant