core: Belkin WeMo plugs and switches are not being discovered

The problem

Upgraded from 0.110.5 to 0.111.2. Belkin WeMo plugs and switches are not being discovered. Changed discovery to static and added devices as static. 111 still not finding devices. Reverting back to 110.5 fixed issue.

Environment

Home Assistant Core release with the issue: 0.111.2
Last working Home Assistant Core release (if known): 0.110.5
Operating environment (Home Assistant/Supervised/Docker/venv): Docker
Integration causing this issue: WeMo
Link to integration documentation on our website: https://www.home-assistant.io/integrations/wemo/

Problem-relevant `configuration.yaml`

wemo:
  discovery: false
  static:
    - 192.168.17.52
    - 192.168.17.53
    - 192.168.17.55
    - 192.168.17.56
    - 192.168.17.57

Traceback/Error logs

Logger: homeassistant.components.wemo
Source: components/wemo/__init__.py:169
Integration: Belkin WeMo (documentation, issues)
First occurred: 1:52:10 PM (5 occurrences)
Last logged: 1:52:10 PM

Unable to get description url for WeMo at: 192.168.17.53
Unable to get description url for WeMo at: 192.168.17.52
Unable to get description url for WeMo at: 192.168.17.57
Unable to get description url for WeMo at: 192.168.17.56
Unable to get description url for WeMo at: 192.168.17.55

Additional information

I’ve also checked the state in dev tools. The state is unavailable.

2020-06-13 13:51:41 INFO (MainThread) [homeassistant.setup] Setting up wemo
2020-06-13 13:51:42 INFO (MainThread) [homeassistant.setup] Setup of domain wemo took 0.3 seconds.
2020-06-13 13:51:42 INFO (Wemo HTTP Thread) [pywemo.subscribe] Listening on port 8989
2020-06-13 13:51:42 DEBUG (MainThread) [homeassistant.components.wemo] Adding statically configured WeMo devices...
2020-06-13 13:51:46 DEBUG (MainThread) [homeassistant.components.ssdp] Discovered wemo at http://192.168.17.153:49153/setup.xml
2020-06-13 13:51:46 DEBUG (MainThread) [homeassistant.components.ssdp] Discovered wemo at http://192.168.17.155:49154/setup.xml
2020-06-13 13:51:46 DEBUG (MainThread) [homeassistant.components.ssdp] Discovered wemo at http://192.168.17.156:49153/setup.xml
2020-06-13 13:52:10 ERROR (SyncWorker_0) [homeassistant.components.wemo] Unable to get description url for WeMo at: 192.168.17.53
2020-06-13 13:52:10 ERROR (SyncWorker_3) [homeassistant.components.wemo] Unable to get description url for WeMo at: 192.168.17.52
2020-06-13 13:52:10 ERROR (SyncWorker_4) [homeassistant.components.wemo] Unable to get description url for WeMo at: 192.168.17.57
2020-06-13 13:52:10 ERROR (SyncWorker_7) [homeassistant.components.wemo] Unable to get description url for WeMo at: 192.168.17.56
2020-06-13 13:52:10 ERROR (SyncWorker_8) [homeassistant.components.wemo] Unable to get description url for WeMo at: 192.168.17.55
2020-06-13 13:52:10 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=wemo>
2020-06-13 13:52:55 DEBUG (MainThread) [homeassistant.components.ssdp] Discovered wemo at http://192.168.17.152:49153/setup.xml
2020-06-13 13:52:55 DEBUG (MainThread) [homeassistant.components.ssdp] Discovered wemo at http://192.168.17.157:49153/setup.xml

About this issue

Original URL
State: closed
Created 4 years ago
Reactions: 1
Comments: 33 (16 by maintainers)

Most upvoted comments

Newbie, Really sorry,if I am interrupting this discussion.

I also have a terrible time while upgrading Hassio 108.6 to 112.x We have following Wemo devices that were working without much hiccups until 108.6.

1x Wemo maker (garage door opener) 15x Wemo LED bulbs. 6x Wemo Switches/2 insight switches.

After upgrading to 112.x, none of the Wemo devices discovered. So about 80% of our home smart devices and automatons went offline.

So reverted back to 108.6 and now all Wemos are working as usual. So I have no idea , why Wemo discovery broken down in these recent upgraded releases!

But now stuck with 108.6 release without a hope to upgrade any further. So really looking forward for some good news. Thanks. FYI: All devices are in Ubiquiti network & HA in RPI.

(Background: Mechanical engineer ~ close to zero knowledge in coding etc, but using Homeasistant for past 4 years, by reading various forums/posts and tips that posted by awesome peoples like you!! Thanks a lot for all that great work!).

elliotthome on Jul 29, 2020

Yep, looks that way. I added some more debug logging just to confirm, and bumped the timeout to 30, and that works. As you can see, it takes a hair over 5 seconds just to build and send the ssdp requests, which would cause it to exit early with a 5 second timeout. With 30 seconds it idles for a long time as the responses were received nearly instantly.

sending ssdp requests 0:00:00.000020
done 0:00:05.015394
1 sockets are ready 0:00:05.015665
checking socket 0 response 0:00:05.015726
found entry with valid description
1 sockets are ready 0:00:05.039055
checking socket 0 response 0:00:05.039137
found entry with valid description
0 sockets are ready 0:00:30.064761
seconds_left expired: 0, total time: 0:00:30.065165, entries: 1
[<WeMo Switch "Wemo Mini">]

kpine on Jul 27, 2020

I think it’s taking too long to enumerate all of the sockets and send the SSDP requests, and by the time it’s done the timeout is already expired and it never polls the sockets.

kpine on Jul 27, 2020

@esev thanks for summarising and, at least for me, this is broadly accurate. A couple of differences…

Post-0.110.7 my WeMo devices haven’t appeared unless I’ve added them to the static part of the config – auto-discovery has been completely broken. I’ve had a perennial issue (since 2016) with WeMo devices (particularly WeMo Motion) where auto-discovery is unreliable and historically I’ve done as you suggest, i.e. restart HA until they appear.
I haven’t experienced this – once a device is connected it’s remained available, although not reporting re your 3rd point.
Yes, although in the case of the WeMo Motion the state is not being updated slowly but rather not being updated at all. Your description of the UI switch is accurate.

Thanks for all you work on this – looking at the other mentioned issues you seem to have been busy!

orbsmiv on Jul 26, 2020

@orbsmiv see https://github.com/home-assistant/core/issues/37544 for the issue of the state not changing properly.

esev on Jul 26, 2020