Problem with Wemo

kevince52 · August 14, 2016, 9:39pm

The downgrade mentioned above worked for me.

gregd · August 15, 2016, 7:15am

Fixed in 26.2

zajnic · August 15, 2016, 9:00pm

Thank you. Confirmed fixed on 26.2

kevince52 · August 16, 2016, 12:53pm

26.2 briefly fixed it for me. I updated last night and all worked fine. I restarted this morning after updating my config for new units tag. Now none of my WeMo devices are auto discoverable. Not getting any errors related to WeMo. Just the usual suspects. Netgear, netdisco and some expected envisalink errors. I’ve had all of them and WeMo working fine. I can see all devices through WeMo App. Will try static. Any other thoughts?

eracknaphobia · August 16, 2016, 3:43pm

I can no longer control my wemo led lights since updating. HA finds all my wemo devices through discovery including the lights. I can switch both my wemo switch and wemo light switch on/off just not the light bulbs. Here is what the log is telling me

16-08-16 11:37:23 homeassistant.core: BusHandler:Exception doing job
Traceback (most recent call last):
  File "/usr/local/lib/python3.4/dist-packages/homeassistant/core.py", line 852, in job_handler
    func(*args)
  File "/usr/local/lib/python3.4/dist-packages/homeassistant/core.py", line 717, in _execute_service
    service(call)
  File "/usr/local/lib/python3.4/dist-packages/homeassistant/core.py", line 572, in __call__
    self.func(call)
  File "/usr/local/lib/python3.4/dist-packages/homeassistant/components/light/__init__.py", line 205, in handle_light_service
    getattr(light, service_fun)(**params)
  File "/usr/local/lib/python3.4/dist-packages/homeassistant/components/light/wemo.py", line 129, in turn_off
    self.device.turn_off(transition=transitiontime)
  File "/home/pi/.homeassistant/deps/pywemo/ouimeaux_device/bridge.py", line 236, in turn_off
    return self._queuedevicestatus(onoff=OFF)
  File "/home/pi/.homeassistant/deps/pywemo/ouimeaux_device/bridge.py", line 179, in _queuedevicestatus
    self._setdevicestatus(**self._pending)
  File "/home/pi/.homeassistant/deps/pywemo/ouimeaux_device/bridge.py", line 148, in _setdevicestatus
    isgroup, self.uniqueID, capids, values)
  File "/home/pi/.homeassistant/deps/pywemo/ouimeaux_device/bridge.py", line 81, in bridge_setdevicestatus
    xml_declaration=True)
  File "/usr/lib/python3.4/xml/etree/ElementTree.py", line 778, in write
    short_empty_elements=short_empty_elements)
  File "/usr/lib/python3.4/contextlib.py", line 66, in __exit__
    next(self.gen)
  File "/usr/lib/python3.4/xml/etree/ElementTree.py", line 837, in _get_writer
    yield file.write
  File "/usr/lib/python3.4/contextlib.py", line 336, in __exit__
    raise exc_details[1]
  File "/usr/lib/python3.4/contextlib.py", line 321, in __exit__
    if cb(*exc_details):
  File "/usr/lib/python3.4/contextlib.py", line 267, in _exit_wrapper
    callback(*args, **kwds)
TypeError: string argument expected, got 'bytes'

kevince52 · August 17, 2016, 12:50am

I’m still having intermittent issues with WeMo. I restart sometimes they are there and sometimes not. Still no errors. Odd. Anyone else experiencing this?

drak41 · August 17, 2016, 1:01am

same here, HA can see my wemo lights but can’t set them or do any automation, have to revert back to using the wemo app on my phone

eracknaphobia · August 17, 2016, 12:20pm

I was able to get my wemo lights working again by downgrading to 0.25.2

pip3 install homeassistant==0.25.2

Not a true fix but I’ll take it for now.

kevince52 · August 17, 2016, 6:33pm

Okay. Working for the last 12 hours. Seems to take a long time to discover WeMo devices. Sometimes up to 10 minutes before they appear in frontend or respond to automations. Haven’t tried the static option but will experiment tonight with it. I am on 26.2 and once things appear in frontend they do work as expected.

thechrisreese · August 21, 2016, 8:29pm

Also seeing wemo issues where they are discovered but not able to change state. The switch will trigger but not light bulbs.

ERROR:homeassistant.core:BusHandler:Exception doing job
Traceback (most recent call last):
File “/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages/homeassistant/core.py”, line 852, in job_handler
func(*args)
File “/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages/homeassistant/core.py”, line 717, in _execute_service
service(call)
File “/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages/homeassistant/core.py”, line 572, in call
self.func(call)
File “/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages/homeassistant/components/light/init.py”, line 205, in handle_light_service
getattr(light, service_fun)(**params)
File “/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages/homeassistant/components/light/wemo.py”, line 129, in turn_off
self.device.turn_off(transition=transitiontime)
File “/Users/TVMac/.homeassistant/deps/pywemo/ouimeaux_device/bridge.py”, line 236, in turn_off
return self._queuedevicestatus(onoff=OFF)
File “/Users/TVMac/.homeassistant/deps/pywemo/ouimeaux_device/bridge.py”, line 179, in _queuedevicestatus
self._setdevicestatus(**self._pending)
File “/Users/TVMac/.homeassistant/deps/pywemo/ouimeaux_device/bridge.py”, line 148, in _setdevicestatus
isgroup, self.uniqueID, capids, values)
File “/Users/TVMac/.homeassistant/deps/pywemo/ouimeaux_device/bridge.py”, line 81, in bridge_setdevicestatus
xml_declaration=True)
File “/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/xml/etree/ElementTree.py”, line 775, in write
short_empty_elements=short_empty_elements)
File “/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/contextlib.py”, line 66, in exit
next(self.gen)
File “/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/xml/etree/ElementTree.py”, line 834, in _get_writer
yield file.write
File “/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/contextlib.py”, line 357, in exit
raise exc_details[1]
File “/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/contextlib.py”, line 342, in exit
if cb(*exc_details):
File “/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/contextlib.py”, line 288, in _exit_wrapper
callback(*args, **kwds)
TypeError: string argument expected, got ‘bytes’

Fresh · August 22, 2016, 12:22am

Seems like maybe the fix made for wemo didn’t fix the Link bulbs

thechrisreese · August 28, 2016, 9:41pm

The recent update restored both switches and my bridges bulbs.

eracknaphobia · August 29, 2016, 12:45am

No luck for me 0.27 brought a new error, now none of my wemo devices are discovered.

16-08-28 20:42:33 homeassistant.bootstrap: Unable to prepare setup for platform light.wemo because dependency wemo could not be initialized
16-08-28 20:42:41 homeassistant.bootstrap: Error during setup of component wemo
Traceback (most recent call last):
File “/usr/local/lib/python3.4/dist-packages/homeassistant/bootstrap.py”, line 157, in _setup_component
result = component.setup(hass, config)
File “/usr/local/lib/python3.4/dist-packages/homeassistant/components/wemo.py”, line 84, in setup
for address in config.get(DOMAIN, {}).get(CONF_STATIC))
TypeError: ‘NoneType’ object is not iterable

UPDATE: Seems the discovery: component is not working correctly, at least as it did before. I had to add wemo: to my configuration.yaml to get HA to discover my wemo devices without error.

Naylorweb · August 29, 2016, 7:19pm

Had the same issue, But this has solved it! thank you!

zajnic · August 29, 2016, 10:21pm

I have another problem that all the wemo devices disappeared by itself at the same time. It happen second time, see the log below:

16-08-30 06:55:41 pywemo.subscribe: Resubscribe error for <WeMo LightSwitch “Kids Toilet”> (HTTPConnectionPool(host=‘192.168.115.212’, port=49153): Max retries exceeded with url: /upnp/event/basicevent1 (Caused by NewConnectionError(‘<requests.packages.urllib3.connection.HTTPConnection object at 0x71c6bbf0>: Failed to establish a new connection: [Errno 113] No route to host’,))), will retry in 60s
16-08-30 06:55:44 pywemo.subscribe: Resubscribe error for <WeMo LightSwitch “Kid Toilet Rack”> (HTTPConnectionPool(host=‘192.168.115.213’, port=49153): Max retries exceeded with url: /upnp/event/basicevent1 (Caused by NewConnectionError(‘<requests.packages.urllib3.connection.HTTPConnection object at 0x5dcef650>: Failed to establish a new connection: [Errno 113] No route to host’,))), will retry in 60s
16-08-30 06:55:47 pywemo.subscribe: Resubscribe error for <WeMo Switch “Outdoor Cam”> (HTTPConnectionPool(host=‘192.168.115.208’, port=49153): Max retries exceeded with url: /upnp/event/basicevent1 (Caused by NewConnectionError(‘<requests.packages.urllib3.connection.HTTPConnection object at 0x635d7cf0>: Failed to establish a new connection: [Errno 113] No route to host’,))), will retry in 60s
16-08-30 06:55:50 pywemo.subscribe: Resubscribe error for <WeMo Switch “Steamer”> (HTTPConnectionPool(host=‘192.168.115.205’, port=49153): Max retries exceeded with url: /upnp/event/basicevent1 (Caused by NewConnectionError(‘<requests.packages.urllib3.connection.HTTPConnection object at 0x63a08850>: Failed to establish a new connection: [Errno 113] No route to host’,))), will retry in 60s
16-08-30 06:55:53 pywemo.subscribe: Resubscribe error for <WeMo LightSwitch “Toilet Rack”> (HTTPConnectionPool(host=‘192.168.115.214’, port=49153): Max retries exceeded with url: /upnp/event/basicevent1 (Caused by NewConnectionError(‘<requests.packages.urllib3.connection.HTTPConnection object at 0x71c12690>: Failed to establish a new connection: [Errno 113] No route to host’,))), will retry in 60s
16-08-30 06:55:56 pywemo.subscribe: Resubscribe error for <WeMo LightSwitch “Study Light Switch”> (HTTPConnectionPool(host=‘192.168.115.209’, port=49154): Max retries exceeded with url: /upnp/event/basicevent1 (Caused by NewConnectionError(‘<requests.packages.urllib3.connection.HTTPConnection object at 0x5dd22d90>: Failed to establish a new connection: [Errno 113] No route to host’,))), will retry in 60s
16-08-30 06:55:59 pywemo.subscribe: Resubscribe error for <WeMo Motion “Garage Motion”> (HTTPConnectionPool(host=‘192.168.115.216’, port=49153): Max retries exceeded with url: /upnp/event/basicevent1 (Caused by NewConnectionError(‘<requests.packages.urllib3.connection.HTTPConnection object at 0x63590690>: Failed to establish a new connection: [Errno 113] No route to host’,))), will retry in 60s
16-08-30 06:56:02 pywemo.subscribe: Resubscribe error for <WeMo LightSwitch “Kid Room”> (HTTPConnectionPool(host=‘192.168.115.211’, port=49153): Max retries exceeded with url: /upnp/event/basicevent1 (Caused by NewConnectionError(‘<requests.packages.urllib3.connection.HTTPConnection object at 0x635d7a10>: Failed to establish a new connection: [Errno 113] No route to host’,))), will retry in 60s
16-08-30 06:56:05 pywemo.subscribe: Resubscribe error for <WeMo LightSwitch “Garage Light”> (HTTPConnectionPool(host=‘192.168.115.210’, port=49153): Max retries exceeded with url: /upnp/event/basicevent1 (Caused by NewConnectionError(‘<requests.packages.urllib3.connection.HTTPConnection object at 0x63590690>: Failed to establish a new connection: [Errno 113] No route to host’,))), will retry in 60s
16-08-30 06:56:08 pywemo.subscribe: Resubscribe error for <WeMo Maker “Garage Door”> (HTTPConnectionPool(host=‘192.168.115.215’, port=49153): Max retries exceeded with url: /upnp/event/basicevent1 (Caused by NewConnectionError(‘<requests.packages.urllib3.connection.HTTPConnection object at 0x63a35b90>: Failed to establish a new connection: [Errno 113] No route to host’,))), will retry in 60s
16-08-30 06:56:44 pywemo.subscribe: Resubscribe error for <WeMo LightSwitch “Kids Toilet”> (HTTPConnectionPool(host=‘192.168.115.212’, port=49153): Max retries exceeded with url: /upnp/event/basicevent1 (Caused by NewConnectionError(‘<requests.packages.urllib3.connection.HTTPConnection object at 0x71c574b0>: Failed to establish a new connection: [Errno 113] No route to host’,))), will retry in 60s
16-08-30 06:56:53 pywemo.ouimeaux_device: Unable to re-probe wemo at 192.168.115.212
16-08-30 06:56:56 pywemo.subscribe: Resubscribe error for <WeMo LightSwitch “Kid Toilet Rack”> (HTTPConnectionPool(host=‘192.168.115.213’, port=49153): Max retries exceeded with url: /upnp/event/basicevent1 (Caused by NewConnectionError(‘<requests.packages.urllib3.connection.HTTPConnection object at 0x637c0b10>: Failed to establish a new connection: [Errno 113] No route to host’,))), will retry in 60s
16-08-30 06:57:05 pywemo.ouimeaux_device: Unable to re-probe wemo at 192.168.115.213
16-08-30 06:57:08 pywemo.subscribe: Resubscribe error for <WeMo Switch “Outdoor Cam”> (HTTPConnectionPool(host=‘192.168.115.208’, port=49153): Max retries exceeded with url: /upnp/event/basicevent1 (Caused by NewConnectionError(‘<requests.packages.urllib3.connection.HTTPConnection object at 0x635b24b0>: Failed to establish a new connection: [Errno 113] No route to host’,))), will retry in 60s
16-08-30 06:57:17 pywemo.ouimeaux_device: Unable to re-probe wemo at 192.168.115.208
16-08-30 06:58:40 pywemo.ouimeaux_device: Unable to reconnect with Outdoor Cam in 5 tries. Stopping.
16-08-30 06:58:43 pywemo.subscribe: Resubscribe error for <WeMo Switch “Steamer”> (HTTPConnectionPool(host=‘192.168.115.205’, port=49153): Max retries exceeded with url: /upnp/event/basicevent1 (Caused by NewConnectionError(‘<requests.packages.urllib3.connection.HTTPConnection object at 0x63a20150>: Failed to establish a new connection: [Errno 113] No route to host’,))), will retry in 60s
16-08-30 06:58:52 pywemo.ouimeaux_device: Unable to re-probe wemo at 192.168.115.205

There was no power outage and other product devices were working fine. I wonder if the HASS did sent request to wemo devices that cause it goes down? I had to restart in order to make it working again.

Mattg · August 30, 2016, 10:24am

Same issue for me.

Fresh · August 31, 2016, 12:54pm

Looks like 27.1 is supposed to have a fix for WeMo discover issues…any brave souls here try it out for Link yet?

eracknaphobia · August 31, 2016, 2:54pm

0.27.1 appears to be working on my end. I removed wemo: and went back to discovery: in my configuration and my wemo devices were discovered without any errors.

Fresh · August 31, 2016, 11:31pm

0.27.1 is also working with my WeMo Link devices. I have discovery disabled, and have all WeMo devices statically assigned. All work without issue, and no errors in the logs.

tsimons78 · September 12, 2018, 1:33am

All-
I’ve noticed since going to 0.77 that ONE of my 2 wemo outlets (both have static ip reservations and are pingable by HASS CLI) changes to UNAVAILABLE. I see the following in the log:

2018-09-11 21:21:12 WARNING (Wemo Events Thread) [pywemo.subscribe] Resubscribe error for <WeMo Switch “Living room”> (HTTPConnectionPool(host=‘192.168.1.XXX’, port=49154): Max retries exceeded with url: /upnp/event/basicevent1 (Caused by NewConnectionError(‘<urllib3.connection.HTTPConnection object at 0x7ff9be60f978>: Failed to establish a new connection: [Errno 111] Connection refused’,))), will retry in 60s
2018-09-11 21:21:14 ERROR (SyncWorker_4) [pywemo.ouimeaux_device.api.service] Error communicating with Living room. Giving up
2018-09-11 21:21:17 WARNING (SyncWorker_1) [pywemo.ouimeaux_device.api.service] Error communicating with Living room, retry 0
2018-09-11 21:21:22 WARNING (MainThread) [homeassistant.components.switch.wemo] Lost connection to Living room
2018-09-11 21:21:27 WARNING (SyncWorker_1) [pywemo.ouimeaux_device.api.service] Error communicating with Living room, retry 1
2018-09-11 21:21:38 WARNING (SyncWorker_1) [pywemo.ouimeaux_device.api.service] Error communicating with Living room, retry 2

This repeats over and over again.

Restarting the HASS service brings the switch back online

Thanks,
~Todd