Core: Wemo devices no longer show up in HomeKit with auto_start enabled (due to speed up changes)

[juched78]

Version with issue:
Started with Home Assistant 0.85

Last working Home Assistant release (if known):
0.84.6

Operating environment (Hass.io/Docker/Windows/etc.):

Raspberian with docker and HASS.IO.

Component/platform:

https://www.home-assistant.io/components/wemo/

Description of problem:
Wemo lights are no longer appearing in HomeKit when auto_start is enabled in the HomeKit component. If I disable auto_start and create an automation to HomeKit.start after 5 minutes then the lights show up.

It would appear to me with the restructure of the wemo component in 0.85 to speed up startup, that now HomeKit starts before wemo lights are configured, meaning they never show up.

The workaround to start HomeKit after 5 minutes is ok, but a better solution would be for wemo to fire an event once discovery is done (around line 176: _LOGGER.debug("WeMo device discovery has finished"). Then an automation could be made to start up HomeKit immediately after the first discovery is complete.

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

wemo:
  discovery: false
  static:
    - 192.168.XX.XX

Traceback (if applicable):

Additional information:

[juched78]

Perhaps there is an event already which can be used to know once wemo is ready, unsure if component_loaded is fired for wemo.

[H2OKing89]

I'm having the same issue also

[MartinHjelmare]

Firing an event in wemo when discovery is done sounds good.

CC @sqldiablo

[sqldiablo]

Thanks, guys. I'm working through another issue with wemo at the moment, and then I will take a look at adding an event for you.

[jig1056]

Hi all, I'm new to Home Assistant, I'm seeing the same issue. My TP-Link switch shows up in Homekit but my Wemo switch doesn't. I don't follow the susgestions mentioned above. I understand the thought process but not sure how to make it happen. If somone has done it or something like it can you please drop an example in the comments. Thanks, also I'm using Hass.io verison 0.93.2

[jig1056]

OK, I did some more digging and was able to find a solution that works for me. I think it's what you'll were suggesting above. I'm adding the syntax for the next newbie to stumble on this thread :)

1 - add the following to my configuration.yaml file, it will tell Home Assistant to NOT autostart the homekit module.

homekit:
  auto_start: false

2- Now add this to either your automation.yaml file or the automation section of your configuration.yaml file. This will start the HomeKit module 5 mins after Home Assistant is started.

- alias: 'Start HomeKit'
  trigger:
  - event: start
    platform: homeassistant
  condition: []
  action:
  - delay: 00:05  # Waits 5 minutes
  - service: homekit.start

This did the trick for me, my Wemo switch now shows up in HomeKit

[jig1056]

Update.. Looks like we don't have to wait 5 mins, that did seem long. I tried it with 2 mins and it worked just the same.

[yeralin]

Any updates?

Seems like we just need to delay Homekit's initialization before Wemo's.

[stale[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[juched78]

This is still needed, but currently we just wait 5 minutes (or maybe less) and then do the unit call.

[stale[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[juched78]

Still needed. Thank you.

[backflip]

@jig1056, thanks a lot for the delayed startup tip! Fixed an issue I had with Nano Shutter covers not showing up in HomeKit.

[bdraco]

Not much can be done on the HomeKit side I’m afraid sort of a redesign to and remove devices periodically. Ideally the wemo devices are available at startup, but if that’s not possible the delayed HomeKit start is really the only options currently

[stale[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.