Is there a way to import existing devices into the ESPHome dashboard?

ESPHome
1

I created a Bluetooth Proxy on an ESP32 from the ESPHome creation wizard website.

The device is working and connected to my network (it has a IP address).

Is there a way to import it into the ESPHome dashboard to be displayed alongside my manually created (via yaml) devices? I don’t see an obvious way to do it but the ESPHome BT proxy page implies that it’s possible (see under the “for advanced users” section):

image
image705×408 25.6 KB

If I click the link it opens a “my home assistant” link but when I click it I get a 404 error. I think that’s because it’s looking for the ESPHome Dashboard add-on that don’t have on HA Container install. But I’ve installed the dashboard in Docker so the dashboard does exist and shows all my other devices.

Any instructions for this anywhere? Google doesn’t seem to be any help.

2

Hmm. I thought it automatically showed up in your esphome add-on dashboard for you to adopt, like this:

0wo3bk0f3agc1
0wo3bk0f3agc11170×1052 29.7 KB

It may only be a matter of waiting until it is discovered.

I only have devices I created in YAML so am not an expert on this.

3

Not if it’s on a different VLAN… I have that issue and haven’t figured out a work-around other than to re-flash a device from within the ESPhome dashboard. ie: when I bought Athom presence sensors that were pre-configured.

1 Like
4

Download the yaml from GitHub. There is a pointer on the page you installed from.

5

Yeah, the youtube video’s I saw had that same “adopt” button but mine hasn’t showed up.

It’s been way over 24 hours and I’ve restarted HA a few times. And I’m on the latest version of ESPHome (2024.7.3)

And it’s on the same VLAN as everything else so that shouldn’t be an issue.

Could it be that the standalone docker version of the ESPHome dashboard has different functionality than the add-on?

6

I’ll give that a try.

I created the yaml file and a generic “Bluetooth Proxy” device showed up but it is showing as offline and still no “adopt” button.

Restarted both HA and the ESPHome container. Still no joy.

the proxy does show up in the esphome integration in HA just not in the ESPHome dashboard.

7

I had this problem when I created my two ratgdo. HA and ESPHome are both in docker containers on the same network as everything else. I created the ratgdo from the website and everything there said it would just show up in the dashboard and I could adopt. Except they never showed up. I ended up having to manually create the ESPHome device from the dashboard and download from there.

1 Like
8

Yeah, I think that’s what I’ll have to do.

It’s not technically that big of a deal but that’s as long as everything just works.

right now I can’t find a way to read any logs from the device or perform any updates to the device since it doesn’t show up anywhere except the Unifi network interface.

And that means that I can’t even perform an OTA transition from the web installed version to a yaml coinfigured version without connecting it back to my PC and doing a manual download.

I’m really kind of surprised there’s not even a built-in web interface that I can visit for the device.

9

it doesn’t seem that the bluetooth-proxy project on the ESPHome project site adheres to the “sharing ESPHome devices” documentation.

the “dashboard_import” module is likely missing from the project?

it looks like it might be time for a bug report.