esphome/device-builder - CodSpeed

device-builder

Blog Docs Changelog

Performance History

Latest Results

Bump frontend to 0.1.120

auto-bump-frontend

2 minutes ago

Generate nRF52 board pins from ESPHome board data (#1174)

main

8 minutes ago

Merge branch 'main' into nrf52-board-pins

nrf52-board-pins

11 minutes ago

Scope find_by_pio_board to the device's platform (#1175)

main

12 minutes ago

Preserve collision-renamed mDNS name across dashboard advertise refresh (#1176) Co-authored-by: Koan <nick@koston.org>

main

14 minutes ago

Scope find_by_pio_board to the device's platform nRF52 and rp2040 both ship a PlatformIO board called adafruit_itsybitsy, so the platform-blind lookup resolved an nrf52 device to the rp2040 catalog entry and served its GPIOn pins — which ESPHome's nRF52 validator rejects. Add a platform filter (both callers already parse the platform from the YAML); a scoped miss returns None so the caller falls back to the free-text pin field rather than wrong-platform pins. Drop the dead None-guard in the sibling find_by_platform_variant so both platform filters read the same (the field is required, never None).

boards-platform-aware-pio-lookup

16 minutes ago

Preserve collision-renamed mDNS name across dashboard advertise refresh When two dashboards share a hostname-derived friendly name on one LAN, zeroconf's allow_name_change renames the ServiceInfo in place at register time (green -> green-2). refresh() rebuilt the published info from the original friendly name, so async_update_service announced the pre-collision name -- a second, conflicting record instead of an update, and service_instance_name drifted back to the wrong name. Preserve the registered instance name on the refreshed info.

esphbot:koan/advertise-refresh-rename

22 minutes ago

Scope find_by_pio_board to the device's platform nRF52 and rp2040 both ship a PlatformIO board called adafruit_itsybitsy, so the platform-blind lookup resolved an nrf52 device to the rp2040 catalog entry and served its GPIOn pins — which ESPHome's nRF52 validator rejects. Add a platform filter (both callers already parse the platform from the YAML); a scoped miss returns None so the caller falls back to the free-text pin field rather than wrong-platform pins.

boards-platform-aware-pio-lookup

23 minutes ago

Latest Branches

0%

Bump frontend to 0.1.120#1177

6 minutes ago

ae0fd5d

auto-bump-frontend

0%

Generate nRF52 board pins from ESPHome board data#1174

14 minutes ago

ba9f222

nrf52-board-pins

0%

Scope find_by_pio_board to the device's platform#1175

27 minutes ago

8ab1b98

boards-platform-aware-pio-lookup

© 2026 CodSpeed Technology

Home Terms Privacy Docs