Tessera 0.4.96 · firmware 0.60.0
New screen now says when the board on the cable is a screen Home Assistant already has, and lets you install that screen again or replace it. No firmware change: the screens keep 0.60.0.
What was broken
Home Assistant keeps one ESPHome device per board, keyed on its MAC address. A board that was a screen before (say "Living room") and is flashed again with New screen under a new name could not be added: Home Assistant kept its old device, asked that device's key of the new firmware for ever, and the wizard waited for a screen that never came. Nothing said why.
What changed
- The wizard asks first. Installing from this browser, it reads the board's MAC address right after connecting and asks Home Assistant whether the board is a screen there already, before anything is built. If it is, the wizard names that screen and offers two ways: install that screen again, or replace it with the new one. Replacing writes the new firmware first; then the old screen leaves Home Assistant with its entities, its YAML stays in the ESPHome folder, and the new screen pairs by itself.
- The USB port is asked once. A port this page was given before and that is plugged in now is used again without Chrome's picker, when it is the only one remembered: the same screen on the same cable, as after a build that failed or a Wi-Fi that was wrong. Another board on it is still caught by the chip check.
- Over the other ways (USB on the Home Assistant machine, a file) the board's MAC is not known before the build: remove the old device under Settings → Devices & services → ESPHome yourself, and the new screen pairs. docs/EASY_SETUP.md, chapter 3, says so.
Tested with the New screen wizard in Chrome on a reTerminal D1001 that Home Assistant had under another name: the wizard named it, replacing built and wrote the firmware, the old device left Home Assistant and the new screen paired.
How to get it
Update Tessera Screen Manager in Home Assistant. No screen needs an update for this.