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>

tests/test_settings_page.py

@@ -91,7 +91,8 @@ class Firmware(unittest.TestCase):
             self.assertIn('- action: open_settings', text, name)
             self.assertIn('- id: go_home', text, name)
             self.assertIn('runtime_tiles::auto_home', text, name)
-            self.assertIn('SCREEN_FIRMWARE_VERSION: "0.2.44"', text, name)
+            version = re.search(r'SCREEN_FIRMWARE_VERSION: "([0-9.]+)"', text)[1]
+            self.assertGreaterEqual(tuple(map(int, version.split('.'))), (0, 2, 44), name)
 
     def test_the_hold_strip_covers_the_top_bar_and_no_more(self):
         for name, text in self.profiles.items():