Max Gramser
93c789dc48
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>
2.2 KiB
2.2 KiB
Test results app 0.2.51 / firmware 0.2.43 (2026-09-16)
Tiles from a Home Assistant event, a sensor that reads back what a screen shows, and the Claude skill that teaches both. App only: the firmware, the protocol and the stored layouts are unchanged. See CHANGELOG 0.2.51 and RELEASING "Compatibility 0.2.51".
Automated
- Python (
.venv-portal): 193 tests OK. Newtests/test_tile_events.py(18 tests): finding a screen by device name, shown name, area or title; adding, changing, moving, removing and ordering tiles; a control or a forecast widening its own tile; a widened tile keeping its spot only when the cell beside it is free; the refusals (unsupported entity, unknown page, row or column, an occupied spot, a full page, twenty tiles, an entity that is not on the screen); the snapshot a screen publishes; and one event end to end throughManager.tile_loop, which savesscreens.json, answers withesp_screens_tile_resultand publishes the layout sensor. A refused event writes nothing. tests/test_claude_skill.pychecks the new section: the four events, the result event, the sensor, what each kind of entity can do, the rule to wait for a yes, and both new YAML examples.- C++ (
clang++ -std=c++17 -Wall -Wextra -Werror -I . -I components/smart_display): 13/13 PASS, unchanged this release. generate_packages.py --checkgreen; the board profiles and packages are untouched.
Against the running Home Assistant
Without sending anything to a screen:
- Subscribed to
esp_screens_add_tileover the websocket, fired that event over the REST API the same way Claude in Home Assistant does (POST /api/events/..., 200) and received it with its data intact. - Published
sensor.esp_screens_probewith tile attributes over the REST API (201), read it back unchanged, and deleted it again (200). That is the pathManager.publish_layoutsuses.
Not tested / for the owner
- The full round trip with the app running on Home Assistant: update ESP Screens to 0.2.51, install the skill again from Settings → Claude, and ask Claude for a tile. The screens themselves need no update.
- Ordering by how often something is used: Claude reads that from Home Assistant's own history.