Skip to content

Add screensaver coordination and local fallback handling#203

Open
loopy321 wants to merge 7 commits intomsp1974:mainfrom
loopy321:screensaver
Open

Add screensaver coordination and local fallback handling#203
loopy321 wants to merge 7 commits intomsp1974:mainfrom
loopy321:screensaver

Conversation

@loopy321
Copy link
Copy Markdown

@loopy321 loopy321 commented Mar 30, 2026

Summary

This PR updates the VACA Home Assistant integration to coordinate correctly with the companion app screensaver/navigation changes.

It adds the integration-side handling needed for idle-driven dashboard screensaver behavior, preserves the original local screen-off fallback when no screensaver dashboard path is configured, and keeps settings propagation aligned with the app.

Included changes

  • Add integration-side handling for ui_idle-driven screensaver navigation
  • Only trigger dashboard screensaver when the current path is the default home path
  • Preserve local screen-off fallback when no screensaver dashboard path is configured
  • Reset stale idle state on reconnect
  • Allow blank screensaver dashboard path values
  • Update screensaver-related settings propagation so partial updates do not disable the wrong behavior

Validation

Validated with the companion app on the Lenovo tablet:

  • idle transitions trigger dashboard screensaver when configured
  • blank screensaver dashboard path restores original local screen-off behavior
  • reconnects do not leave stale idle state behind
  • settings updates continue to behave correctly with the app-side flow

Related changes

This PR is one part of a coordinated update across the companion app and Home Assistant integrations.

Related PRs:

Recommended rollout: merge and deploy the related PRs together.

@loopy321
Copy link
Copy Markdown
Author

loopy321 commented Apr 3, 2026

Follow-up: this branch now adds a restart-ui custom action/button for the Android-10 Lenovo tablet.

Why it was needed:

  • the Android-10 Lenovo tablet could reach a black-screen zombie state where normal screen-wake and refresh actions were too weak to recover the visible UI
  • testing showed that a real app/UI restart reliably restored rendering
  • this new action exposes that recovery path through Home Assistant, so automations can recover the device without adb

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.

2 participants