Add MQTT screensaver command (#54)#77
Merged
Merged
Conversation
Resolves the request in #54 for a way to *command* the screensaver from Home Assistant (previously HA could only observe screen/state, not start the frame). Adds a `Screensaver` button entity at `immortal/<id>/screensaver/set`. On press it launches PhotoFramePreviewActivity — the exact same photo-frame surface the launcher's header screensaver button opens (HomeActivity.onStartScreensaver). Mirrors the go_home command and discovery pattern. This shows the in-app photo frame as a foreground Activity, not the system dream, so it's consistent with the header button: screen/state stays "interactive" while showing, and go_home dismisses it. We deliberately don't attempt to start the system dream (no public API; Somnambulator/IDreamManager reflection is device-fragile on the Portal's Android 9/10). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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
1 participant
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.
Closes #54.
Home Assistant could already watch
immortal/<id>/screen/state(off/interactive/dreaming) and wake/sleep viascreen_power, but there was no way to command the screensaver to start. This adds aScreensaverbutton entity atimmortal/<id>/screensaver/setthat shows the photo frame on demand.What it does
On press, the handler launches
PhotoFramePreviewActivity— the exact same photo-frame surface the launcher's header screensaver button opens (HomeActivity.onStartScreensaver). It mirrors the existinggo_homecommand branch and thebutton()discovery pattern.Design notes
screen/statestaysinteractivewhile the frame is showing, and the existinggo_homecommand dismisses it.IDreamManager.dream()via reflection, both device-fragile on the Portal's Android 9/10. The author of [Feature] MQTT command to trigger the screensaver/dream on demand #54 anticipated this ("no DreamManager/Somnambulator workaround needed") — reusing the photo-frame activity is exactly that clean internal path.Scope
Start-only button (matches the issue's "ON starts the dream now"); stop is already covered by
go_home. Image-fetch hardening and any "report dreaming state" wiring are out of scope here.Builds clean; unit suite passes locally.
🤖 Generated with Claude Code