Yes, like EspControl it needs api:. There is no MQTT route.
The screen works entirely through ESPHome's native API and Home Assistant's ESPHome integration:
Tessera sends the tiles to the screen as ESPHome actions, called through Home Assistant.
The screen follows the entities on its tiles through the API's state subscription, so any entity works without publishing it to MQTT first.
A tap goes out as a Home Assistant action over the same connection.
You don't have to set that up by hand. When Tessera installs a screen, it writes the api: block with the screen's own encryption key into its YAML, adds the screen to the ESPHome integration and turns on "Allow the device to perform Home Assistant actions". No MQTT broker, long-lived token or blueprint is involved.
MQTT can keep running for your other devices, the screen just doesn't use it.
Got a screen running? Tell others which board you have and what works on the Tessera website. It helps everyone pick a screen that works.
tessera
Discussion 1
Add a commentYes, like EspControl it needs
api:. There is no MQTT route.The screen works entirely through ESPHome's native API and Home Assistant's ESPHome integration:
You don't have to set that up by hand. When Tessera installs a screen, it writes the
api:block with the screen's own encryption key into its YAML, adds the screen to the ESPHome integration and turns on "Allow the device to perform Home Assistant actions". No MQTT broker, long-lived token or blueprint is involved.MQTT can keep running for your other devices, the screen just doesn't use it.
Got a screen running? Tell others which board you have and what works on the Tessera website. It helps everyone pick a screen that works.
Want me to keep building? Consider supporting monthly or buying me a coffee, much appreciated!
Original on GitHub