mirror of
https://github.com/home-assistant/frontend.git
synced 2026-10-01 17:29:02 +01:00
Petar Petrov
ddd1db7961
* Add an ESPHome device setup checklist on the device page. Surface advertised proxy capabilities in a banner and dialog so users can continue Bluetooth, audio, Z-Wave, and serial setup after the device is added. * Harden the ESPHome setup wizard after review feedback. Show cached capabilities while offline, wait for user data before the banner, and expose setup status to assistive tech. * Mark ESPHome serial setup completed when a UART port is in use. * Mark ESPHome Z-Wave setup completed when zwave_js matches the proxy home ID. * Align the ESPHome setup wizard with Sendspin audio and the existing add-integration dialog. Music stays incomplete until Music Assistant is installed and Sendspin is on, and serial setup no longer offers a hardcoded integration list. * Fix storage chart size labels after bidirectional isolate bidiIsolate can return undefined, so the gigabyte formatter needs a string fallback for the type check. * Show the ESPHome setup banner only for music, Z-Wave, or serial devices, and use the finished headline once nothing remains to set up. * Let the ESPHome music row finish once Music Assistant is installed. The Sendspin switch is optional and matched by object id, a finished checklist uses the reminder, and the storage chart label matches dev after the bidiIsolate change. * Give ESPHome music setup its own sequence so Sendspin is enabled after the Music Assistant offer. * Show ESPHome audio install progress after the offer buttons hide, and drop the guest PIN step until that switch exists. * Keep ESPHome setup on the device's own Z-Wave and music steps when discovery already started or Music Assistant is cancelled. A detected controller was treated as not started, cancelling the Music Assistant dialog still enabled Sendspin, and a missing discovery flow opened a generic Z-Wave flow. * Keep ESPHome setup honest when USB usage or Z-Wave flow lookup fails. A failed USB scan was shown as unused ports, overlapping capability requests could overwrite a newer result, and a rejected Z-Wave flow lookup never showed the retry error. * Use the repo consume decorator in the ESPHome setup UI.