ESPHome continues to deliver significant overhauls with its monthly updates. The May update transforms the Device Builder from a cosmetic refresh to a fundamental overhaul. Also, Device Builder isn't just a UI refresh; it's a workflow overhaul for anyone scaling beyond a couple of smart devices.

As an ESP32 enthusiast who loves ESPHome, this is great news for my smart home. The new Device Builder has just entered public beta. The new tooling is built for people who love to scale their smart home beyond a couple of devices.

You can now build multiple devices at once

Set up job queues

The new ESPHome 2026.5.0 update refreshes the Device Builder with a really essential feature — job queues. This lets you queue multiple devices for compilation at the same time. You can also cancel any job at any time if the compiler gets stuck, preventing cascading failures across the queue.

Old ESPHome only allows compiling one device at a time, and then stops. So you’ll need to go through the same click cycle if you want to build multiple devices, such as Bluetooth proxies, motion sensors, or door sensors, for different rooms. Making each unit is like going through a sequential cycle of compiling builds to flash firmware.

In practice, you save time by updating your entire fleet of devices without babysitting the dashboard.

Choose only the devices you want to update

Checks per device badges

The new Device Builder shows out-of-sync detection badges for each device. They show encryption mismatches, version differences, and config-hash drift at a glance. Also, the new config-hash command makes Device Builder skip reflashing when the configuration matches the one on the disk.

ESPHome’s flash-and-forget workflow is simple, but managing updates across devices was tedious. You only discover config-hash drift or version mismatches when attempting to compile firmware. That forces you to test one device before deploying to the rest of the house.

Compare YAML files and track changes between versions

Helps with searching and debugging

As you build different ESPHome devices, you end up with a pile of config YAML files on the dashboard. Then, it’s difficult to search for information like which GPIO a particular sensor node uses, a custom component, or even an MQTT topic. When you have to, you end up opening and checking each file individually.

That can easily change with the new cross-config YAML search feature, which shows the surrounding context inline. Besides, you can use the YAML diff view to refer to what exactly changed between the two versions. You can search for references and debug patterns across YAML files for the entire fleet without opening files individually.

Using visual component builder with YAML

Catch maximum errors before compiling

The legacy dashboard uses a text editor for YAML with no real-time validation. Otherwise, any typo in the component names or incorrect placement that doesn’t match the predefined structure isn’t easily recognizable when populating a config file. You learn about those mistakes only when the compiler logs them.

The new dashboard offers schema hints in real-time, meaning if you’ve not formatted a value properly, you’ll see a red squiggly line. You can easily add components using the visual component builder interface or edit the YAML directly. If components have dependencies, they are highlighted as well. The built-in pin mapper ensures that the proper GPIO pins, as per their capabilities, are used, preventing wiring or code issues with the microcontroller. Beyond the interface, the Device Builder also speeds up the compilation itself.

Offload compilation to faster hardware

Works without using IP addresses

Compiling firmware in ESPHome is slow when running Home Assistant on SBCs like Raspberry Pi. That’s one reason why home lab users move their Home Assistant instances to a mini PC or NAS for better hardware utilization. Typically, it takes about 5–8 minutes to compile a firmware on a Pi 4’s limited CPU power.

With the new Device Builder, you can offload compilation duties to any system on your home network via mDNS discovery. So you can use your PC, NAS, or mini PC without configuring their IP addresses. Then the task can be offloaded to that system. Only fingerprinting and peer pairing are necessary. No IP is required. And you can continue using the HA instance on a Pi.

Watchdog feed optimized for less CPU usage

Nearly half the processing power needed

​After building several components, it’s necessary to ensure that they continue working without hiccups. The watchdog monitors devices for faults and automatically attempts recovery if an issue arises. Enabling the watchdog for every device and add-on increases CPU load.

The processing requirement for the watchdog monitoring feed has now been cut in half. Idle wake-ups and loop overhead on microcontrollers drop by roughly 50 percent. That frees resources on your microcontroller builds.

Embracing ESPHome’s new Device Builder dashboard

ESPHome’s new Device Builder is in public beta as of June 2026. Install the ESPHome Device Builder (Beta) add-on from Home Assistant’s add-on store, and then toggle ‘Use new Device Builder Preview’ on the add-on’s Configuration tab. There might be edge cases, but breaking changes are minimal and well documented in the changelog.

ESPHome has been an excellent option for building smart home devices and deploying them in your smart home. For someone who builds over 10-15 smart devices, the legacy dashboard felt like a chore to use. Device Builder brings compile queues, cross-config search, and bulk operations — critical for managing over 10 devices at scale.

If you’re managing multiple ESPHome devices, Device Builder finally makes the dashboard feel like a tool built for your smart home’s workflow.