Repository navigation
Added
- The hardware gate checks that ESPHome firmware works, not only that
it boots (workbench phase 4). A flash entry withfunctional: true
builds its ESPHome image with WiFi, the native API and one GPIO
switch; after the boot marker the newfunctionalstage finds the
device's address in its boot log, connects withaioesphomeapi,
checks its name and entities, and switches the switch on and off over
the API.aioesphomeapiis the newbenchextra, installed in the
-fullimage.
Fixed
-
The functional stage says why a device's API did not answer. A
timeout read "did not answer: " with nothing after it; it now gives
the wait, and the row adds the WiFi signal the device logged, naming
-85 dBm or weaker as too weak to hold a link. Found on the first
covbench run, where the board joined at -97 dBm. -
An unreachable ESPHome dashboard ended the hardware gate with a
traceback. The ESPHome image build let the dashboard client's error
escape, so one bad dashboard lost the whole night's report. It is now
a failedflashrow for that framework and the run carries on. -
The header overflowed between 1536 and 1760px. With advanced mode
on and unsaved changes, the group names and long labels that appeared
at 1536px pushed the theme, settings and docs buttons off screen, and
the "Unsaved changes" chip wrapped. The labels now appear from 1800px
(the Design labels from 1366px) and the chip stays on one line. The
ui-themesgate now sweeps 1280-1920px in that state.