Max Gramser
da20782d3d
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>
37 lines
2.3 KiB
Markdown
37 lines
2.3 KiB
Markdown
# Installation and everyday use
|
|
|
|
See [the full installation guide](https://github.com/MaxGramser/homeassistant_espscreen/blob/main/docs/EASY_SETUP.md).
|
|
|
|
Open **Settings → New screen** to install a screen: connect it via USB to the
|
|
Home Assistant machine, choose the board, name and USB port, then click **Install**.
|
|
The profile with unique keys goes into the ESPHome folder of the HA configuration,
|
|
any missing Wi-Fi goes into `secrets.yaml` (existing secrets are left untouched), and the
|
|
build and flash run in the same window; it then shows the API key
|
|
for pairing. Pairing itself happens in Home Assistant under **Settings → Devices & services** (a button in the window and on the *not yet in Home Assistant* card under My screens). Each screen has its own profile. **Settings → Firmware & USB** is
|
|
for existing profiles: check, build or reinstall via USB or
|
|
the IP address (OTA). Existing ESPHome profiles in the HA config folder are
|
|
found automatically.
|
|
|
|
**Settings** (top right) also has the nightly firmware updates, the **Alerts** cheatsheet
|
|
(an alert on one screen, or on every screen with the `esp_screens_show_alert` event)
|
|
and **Claude**: install the ESP Screens skill for Claude Code in Home Assistant, or
|
|
download it for claude.ai, and ask Claude for the alert automation.
|
|
|
|
At the top of the editor you set the **Top bar** for each screen: the name on the left, up
|
|
to six items on the right (time, analog clock, date, or an entity with an icon, such as
|
|
temperature, a door, the alarm, or "last changed"). Drag to reorder, tap
|
|
to configure; firmware 0.2.32 or newer renders them.
|
|
|
|
After pairing via the HA ESPHome integration, choose the tiles in ESP Screens.
|
|
**Tile settings** has click behavior, larger values and mini-sliders.
|
|
**Screen settings** has brightness and standby. **Inspector** helps with
|
|
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.
|