The card does not modify entities or Home Assistant backend state, so rollback affects only the frontend resource and dashboard YAML.
- Open HACS → Frontend → Ring View.
- Choose Redownload and select the previously working release.
- Refresh Home Assistant with cache bypass, or restart the Companion app.
- Confirm the resource still points to
/hacsfiles/ring-view/ring-view.js.
When rolling back from v0.7.0, select v0.6.3 as the previously working
release. Version v0.6.3 simply ignores the four interactive-dashboard options
if they are still present in YAML. No entity or backend state is changed.
- Replace
<config>/www/ring-view.jswith the bundle from the previously working release. - Keep the same resource URL and refresh with cache bypass. If necessary, append a temporary version query such as
?v=0.1.0to the resource URL.
If no custom-card version is suitable, remove the test card from the dashboard and restore the pre-existing Home Assistant picture-entity recording card and live tile. Remove the JavaScript resource only after no dashboard references custom:ring-view.
During initial rollout, do not replace the existing native cards until recording playback, live startup, and live-session teardown have been verified on the target Home Assistant installation.