Wake a screen or put it to sleep from Home Assistant (0.2.53)
Every screen gets two template buttons, Wake and Sleep, for automations (button.press on button.<screen>_wake / _sleep). Wake does what a tap does: a dimmed screen runs wake_display, a screen that is on only restarts the standby count. Sleep dims right away through dim_display, also with Auto standby off, and closes an alert that is up (reported as remote); it is ignored during a touch calibration. A new non-restored flag, sleep_requested, keeps that standby in place: dim_display dims with standby off, and apply_screen_settings, which runs every minute, no longer wakes such a screen. wake_display clears it (a tap, Wake, an alert), and so does the Auto standby switch when it really turns standby off. Nothing is saved, so the buttons cost no flash writes and may run on every motion. The Claude skill, README, add-on docs and RELEASING describe both buttons. Checked on host builds of both boards over the native API, 24 checks each (timer, Sleep with Auto standby off across a minute tick, alert, calibration), and with ESP32 builds of both Easy profiles (+336 B RAM). Firmware 0.2.45. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
@@ -30,3 +30,7 @@ missing attributes or an offline screen. New cards require firmware 0.2.0.
|
||||
The screen carries the same settings itself (firmware 0.2.44 or newer): hold the top bar for
|
||||
about a second and a half, or put the built-in **Settings** card on a page. What is changed
|
||||
there appears here within a second, and the other way around.
|
||||
|
||||
In Home Assistant every screen also has a **Wake** and a **Sleep** button (firmware 0.2.45 or
|
||||
newer). Press them from an automation with `button.press`: Wake does what a tap does, Sleep puts
|
||||
the screen in standby right away, also with Auto standby off.
|
||||
|
||||
Reference in New Issue
Block a user