Tessera 0.4.100 · firmware 0.63.0
Sounds you choose yourself, Settings you can find again, a camera that costs nothing while you do not use it, and a video call that has its picture the moment you answer.
New
- Choose the sounds your screens play, or cut your own. Under Events, Calls has the ringtone, Doorbell the chime and Alerts a sound for alerts, each with six sounds to choose from for every screen and, if you like, another per screen, or none. An audio editor cuts your own from any sound file or song. Each kind has a Volume slider and each screen a Test key. Nothing changes by itself: calls ring and doorbells chime as before, as loud as before, and alerts stay silent until you choose a sound.
- Settings you can find again. The Settings page and a screen's Settings tab open on a short list with one line per part that says what is set now, the way Home Assistant's own Settings do.
- A board with a camera is offered Screen camera. New screen has a Plugins step for a board whose hardware needs a plugin: Screen camera is ticked, with the reason beside it, and goes into the screen's first firmware unless you untick it. A screen you already have gets a card above it that asks once. Nothing is added without your yes, and a no is remembered.
- Screen camera costs nothing while you do not use it (Screen camera 0.7.3). The camera, its encoders and its buffers start with the first use and are given back after it. Measured on a Guition 10.1 with the video never opened: 35 KB of internal memory and 0.7 MB of PSRAM, where it was 138 KB and 10 MB, and the processor as idle as without the plugin. Its settings are on the screen itself as well, under Settings, Plugins.
- A video call has its picture the moment you answer. The cameras of both screens start while the call rings: the first picture came 0.1 to 0.3 seconds after the answer on a Guition 10.1 and a reTerminal D1001, where it took 2 to 5 seconds. Nobody sees a picture before the answer.
- Fewer entities per screen in Home Assistant. A screen's measuring sensors (heap, PSRAM, the loop stack and a few more) are switched off in Home Assistant by default. Debug mode switches them on while it is on, and you can switch one on yourself. A screen that is in Home Assistant already keeps the sensors it has.
- A tap on the screensaver answers at once, as the finger lands, with the light up at once.
Fixed
- A video call answered at once could say "no picture of this camera" while the other screen's camera was still starting.
- On the ESP32-P4 screens an alert, and any card that dims the page behind it, could have a thin dark line along two of its sides.
- The ESP32-P4 screens with echo cancelling build with ESPHome 2026.11 again.
- The editor on a phone and a laptop: pages no longer run off the side of a phone, a finger that drags a tile no longer opens the page's menu, and a tile for a full page offers a new page.
- The Alarm page under Events is translated in every language.
Tested
The whole check of the project on the released commit and every board built by CI on both ESPHome versions. An update on a Home Assistant with a Guition 4 inch, a CYD, a Guition 10.1 and a reTerminal D1001: the app and each screen took the release and kept their layouts. Calls were run between the Guition 10.1 and the reTerminal D1001, the camera's memory and processor use were read on both boards before and after use and over sixty rounds of viewers coming and going, and the alert's edge was read back from the 10.1's frame buffer. The sounds were played on the Guition 10.1 and the reTerminal D1001 and recorded with a microphone. Not seen on glass: the firmware on the boards the project does not own, which CI builds and nobody ran.
How to get it
Update Tessera Screen Manager in Home Assistant, then use Update on each screen in Tessera for the new firmware. Screen camera updates on the Plugins page.