Tessera adds a screen to Home Assistant by itself when it knows the screen's key: when the screen's YAML is in the ESPHome folder Tessera reads, the one ESPHome Device Builder uses too. Every screen from New screen is there, and so is a screen you build with Device Builder from its file in that folder. Add a screen shows what you see while it happens.
Add a screen by hand when:
- it was built outside that folder, for example with the ESPHome command line on your own computer, from a YAML Tessera doesn't see;
- its card under Screens in Tessera says "Tessera can't add it to Home Assistant by itself". Usually Home Assistant can't reach the screen then: it is on another network segment or VLAN that mDNS doesn't cross, or a guest network or client isolation keeps it away.
Doing it by hand never hurts.
Add the device
- In Home Assistant, open Settings → Devices & services.
- Home Assistant has usually found the screen already: click Add on the discovered ESPHome device. Not there? Choose Add integration → ESPHome, and enter the screen's IP address and port
6053. The screen shows its address on its settings page, under This screen; your router lists it too. - Asked for an encryption key? Paste the screen's API key: Copy API key in Tessera, or
api:,encryption:,key:in the screen's YAML. Not the OTA password, that one is only for updates over Wi-Fi.
The screen then shows up in Tessera's sidebar, ready for its tiles: Your first page.
Actions
A tile needs Home Assistant's permission to control anything: Allow the device to perform Home Assistant actions. Tessera turns it on for a screen added this way too, and turns it back on as soon as Home Assistant reports that it ignored a tap. When it can't, the screen's page in Tessera says so, with an Allow actions button. In Home Assistant the switch is under Configure on the screen's ESPHome entry.
Good to know
- Copy API key copies nothing? That happens when Home Assistant is opened over plain
http. The key then appears selected in a box: press Ctrl+C, or Command+C on a Mac. - Home Assistant asks for the key again later. For a screen whose YAML Tessera reads, Tessera answers by itself. Otherwise paste it as in step 3.
- The screen is its own device. Its brightness, standby and the other screen settings are entities of that device, so an automation can change them.