Auto-load esphome component upon discovery by Home Assistant about esphome-core HOT 10 CLOSED

Use MQTT or API discovery, that is exactly what it does.

from esphome-core.

@brandond the discovery works - yes - so you get a notification that there are discovered components - but the next step, adding them to home assistant is still manual?

See SERVICE_HANDLERS in https://github.com/home-assistant/home-assistant/blob/7db28d3d91869cc1b2898342bcfce096930ad449/homeassistant/components/discovery.py

There is no esphome entry, which means they are not auto added...

from esphome-core.

I must be confused - what do you need to add them to? The UI? They're available to be used as switches, sensors, lights, etc as soon as they're discovered.

from esphome-core.

It sounds like the ask is to have MQTT and esphome native discovery fire a PLATFORM_DISCOVERED event when a new device is added? I believe that both the esphome and mqtt platforms are maintained in the homeassistant codebase, so the issue probably belongs over there.

from esphome-core.

I would put in an issue or PR in the home-assistant project referencing:

• https://github.com/home-assistant/home-assistant/tree/dev/homeassistant/components/esphome
• https://github.com/home-assistant/home-assistant/tree/dev/homeassistant/components/mqtt

from esphome-core.

Hmm if they are available to be used then sorry I thought you had to do something manual. As you were!

from esphome-core.

Okay so let me see if I have made a mistake.

New Hass.IO install - discovers a whole bunch of ESPHome devices

Based on what you said above

I must be confused - what do you need to add them to? The UI? They're available to be used as switches, sensors, lights, etc as soon as they're discovered.

I thought they could be used. But there are no entities available :-

So they are not available for use unless I manually go into the integrations panel and click configure.

Once I manually configure them, they are "available to be used"

As an aside - despite being able to discover the devices using their name, esphome doesn't seem to then be able to connect to them 👎

from esphome-core.

If it can't connect to the device, it can't discover any of the entities it's hosting, which is why you don't see anything yet.

It appears that mDNS isn't working in your environment, since it can't resolve the .local hostname. Assuming it is actually online, you might try a more recent Dev release that has a built-in mDNS resolver for hosts that don't support it natively.

from esphome-core.

So they are not available for use unless I manually go into the integrations panel and click configure.

That is how the integrations screen is supposed to work. Previously, Home Assistant would add all integrations automatically and it was really hard to exclude an integration. The new config entries require developers to make it an opt-in action (also because otherwise you could pretty much achieve remote code execution without user accepting).

Also, considering adding it to HA is two button presses, I couldn't care less about this - it takes way more time to set up a node on the ESPHome side of things.

Assuming it is actually online, you might try a more recent Dev release that has a built-in mDNS resolver for hosts that don't support it natively.

That PR isn't merged yet 😉 Also, Home Assistant doesn't use esphomeyaml for the API (aioesphomeapi package). So the mDNS change needs to be done there too (plus PR in Home Assistant, which takes some time to go through PR process)

from esphome-core.

Thanks @OttoWinter and @brandond - ill keep an eye on the releases for when native mDNS support lands in esphome.

My use case is for a stateless deploy of ha with eh nodes to a non Hass.IO docker host. I think I'll just write a custom component to handle adding the nodes into ha automatically.

Thanks again

from esphome-core.