Let Claude in Home Assistant put tiles on a screen (0.2.51)
Four Home Assistant events change a screen the way the app's own editor does: esp_screens_add_tile (add or change), esp_screens_remove_tile, esp_screens_move_tile and esp_screens_order_tiles. An event names the screen by device name, shown name, area or title, and may set the size, the direct control, the display, the icon, the colour and the spot; a tile with a control or a forecast becomes double-width by itself. apply_tile_event returns the new layout and Manager.save does the validating and the pushing, so nothing can get past the twenty-tile limit, a duplicate entity or an occupied spot. Every event is answered with esp_screens_tile_result, and every screen publishes what it shows as sensor.esp_screens_<node>, with the page, row, column, width, control and display per tile. So an assistant can read a screen before it moves anything, and a refused event says why and changes nothing. The Claude skill gains a Tiles section with the events, the fields, what each kind of entity can do, how to read a screen first, and the rule to show the plan and wait for a yes. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
@@ -192,10 +192,13 @@ for these two events; the per-screen actions work without it.
|
||||
### Ask Claude
|
||||
|
||||
Use Claude Code in Home Assistant? **Settings → Claude → Install for Claude Code** writes an
|
||||
ESP Screens skill to `/homeassistant/.claude/skills/esp-screens`, so Claude knows these events
|
||||
and every field, color, and icon. Then ask, for example: "Show an alert on all my screens when
|
||||
the mailbox is full." **Download for claude.ai** gives the same skill as a zip to upload in
|
||||
Claude under Customize → Skills. Nothing is written until you press the button.
|
||||
ESP Screens skill to `/homeassistant/.claude/skills/esp-screens`, so Claude knows the events, the
|
||||
tile settings and every field, color and icon. Then ask, for example: "Put the vacuum on the living
|
||||
room screen", "Give the living room lights a brightness slider and make that tile wide", "Move the
|
||||
vacuum to page 1" or "Show an alert on all my screens when the mailbox is full." Claude reads what a
|
||||
screen shows from `sensor.esp_screens_<screen>` and asks before it changes anything. **Download for
|
||||
claude.ai** gives the same skill as a zip to upload in Claude under Customize → Skills. Nothing is
|
||||
written until you press the button.
|
||||
|
||||
<p align="center">
|
||||
<img src="docs/images/editor-settings.png" width="80%" alt="Settings in ESP Screens: New screen and Firmware & USB, the firmware updates, the Alerts cheatsheet, and the Claude skill">
|
||||
|
||||
Reference in New Issue
Block a user