I’m still getting those dependencies errors as well on a completely fresh build.
Is hass.io able to add custom things like I’ve been doing in hassbian like lockitron and ring and haaska?
FYI:
Issue resolved.
Been digging around with the Wemo app and HASS since my last post, un-install and re-installed the app, deleted all devices, re-added all devices, changed WiFi, changed names, added one device at a time while rebooting HASS, but was still unsuccessful.
After a couple hours, I just gave up and decided that I would just rely on the app to control the switches, while adding the device back into the app for the last time, I got a firmware update notification after adding the fourth device went ahead and did the update, continued adding the remainder devices, after everything was added and working, I decided to reboot HASS again just for the hell of it, after all what’s the worst that can happen, and what do you know, all switches are recognized and configured in HASS, and functioning, even my previously configured automation’s worked.
1 Like
Well I’ll be damned, good find! I’ll check the firmware on all my devices when I get home 
Can you post the firmware version of your Wemo switches? Mine isn’t showing any firmware updates available, and I’d like to rule that out.
Plug-in Switch = WeMo_WW_2.0010966.PVT-0WRT-SNS
Light Switch = WeMo_WW_2.0010966.PVT-0WRT-LS
Dang, that’s not it for me then. Mine are all that one except for one switch which is on 2.00.11
I guess you can try deleting them from the app and add them back one at a time to the app and HASS and see what happens.
I’m suspecting that my plug-in was causing the issue, and after it upgraded it worked.
I had the exact same issue when upgrading to Stretch. What solved my issue was setting a static IP for my Wemo Switch in both my router and in Homeassistant
My wemos are already on 2.0010966 firmware version, so I’m not sure it’s the solution
You could try enabling the Wemo beta in the Google Play store.For the iPhone beta, you will need to apply. https://www.surveymonkey.com/r/VWM8ZZX The beta will also update the firmware.
So I too had the issue with wemo not being detected after upgrading, Moved to HassIO and kaboom their they are. (I use wemo motion to turn on kitchen lights) I thought problem solved but after a few hours it would become unresponsive, I could see the sensor in the front end it was just not updating. Restarts would sometimes pop up with the Wemo error others would work for a few hours again.
So yesterday I deleted Wemo static out of my config and just let it be auto detected… No issues since then, It’s now been about 24h without issue.
My wemo has worked perfectly for months on my old Ubuntu 17.04 server. This week I got a new nuc and started fresh with Ubuntu 17.10 then copied my config files over.
Wemo is now not working at all. Same errors as above. I’ve tried all the recommendations in this thread to no avail.
If I boot up old server wemo works…
I’m having this issue as well. My three Wemo Mini outlets were working fine on .59.2 and then they suddenly weren’t.
I tried everything in this thread, but to no avail.
Edit to add: Still not working on .60
Been there. I added the IPs of the switch and of the gateway as static hosts, they reappeared.
They are no more discoverable since… 58?
For me it’s the opposite, if I use Static Addresses, it doesn’t work, only works with Discovery “ON”
I was using static addresses, but have since tried hashing them out leaving wemo: and discovery: open; hashing out discovery and unhashing the static IPs.
Error during setup of component wemo Traceback (most recent call last): File “/srv/homeassistant/lib/python3.5/site-packages/urllib3/connection.py”, line 141, in _new_conn (self.host, self.port), self.timeout, **extra_kw) File “/srv/homeassistant/lib/python3.5/site-packages/urllib3/util/connection.py”, line 83, in create_connection raise err File “/srv/homeassistant/lib/python3.5/site-packages/urllib3/util/connection.py”, line 73, in create_connection sock.connect(sa) ConnectionRefusedError: [Errno 111] Connection refused During handling of the above exception, another exception occurred: Traceback (most recent call last): File “/srv/homeassistant/lib/python3.5/site-packages/urllib3/connectionpool.py”, line 601, in urlopen chunked=chunked) File “/srv/homeassistant/lib/python3.5/site-packages/urllib3/connectionpool.py”, line 357, in _make_request conn.request(method, url, **httplib_request_kw) File “/usr/lib/python3.5/http/client.py”, line 1107, in request self._send_request(method, url, body, headers) File “/usr/lib/python3.5/http/client.py”, line 1152, in _send_request self.endheaders(body) File “/usr/lib/python3.5/http/client.py”, line 1103, in endheaders self._send_output(message_body) File “/usr/lib/python3.5/http/client.py”, line 934, in _send_output self.send(msg) File “/usr/lib/python3.5/http/client.py”, line 877, in send self.connect() File “/srv/homeassistant/lib/python3.5/site-packages/urllib3/connection.py”, line 166, in connect conn = self._new_conn() File “/srv/homeassistant/lib/python3.5/site-packages/urllib3/connection.py”, line 150, in _new_conn self, “Failed to establish a new connection: %s” % e) urllib3.exceptions.NewConnectionError: <urllib3.connection.HTTPConnection object at 0x694d8c50>: Failed to establish a new connection: [Errno 111] Connection refused During handling of the above exception, another exception occurred: Traceback (most recent call last): File “/srv/homeassistant/lib/python3.5/site-packages/requests/adapters.py”, line 440, in send timeout=timeout File “/srv/homeassistant/lib/python3.5/site-packages/urllib3/connectionpool.py”, line 639, in urlopen _stacktrace=sys.exc_info()[2]) File “/srv/homeassistant/lib/python3.5/site-packages/urllib3/util/retry.py”, line 388, in increment raise MaxRetryError(_pool, url, error or ResponseError(cause)) urllib3.exceptions.MaxRetryError: HTTPConnectionPool(host=‘192.168.1.16’, port=49153): Max retries exceeded with url: /setup.xml (Caused by NewConnectionError(’<urllib3.connection.HTTPConnection object at 0x694d8c50>: Failed to establish a new connection: [Errno 111] Connection refused’,)) During handling of the above exception, another exception occurred: Traceback (most recent call last): File “/srv/homeassistant/lib/python3.5/site-packages/homeassistant/setup.py”, line 193, in _async_setup_component component.setup, hass, processed_config) File “/usr/lib/python3.5/asyncio/futures.py”, line 380, in iter yield self # This tells Task to wait for completion. File “/usr/lib/python3.5/asyncio/tasks.py”, line 304, in _wakeup future.result() File “/usr/lib/python3.5/asyncio/futures.py”, line 293, in result raise self._exception File “/usr/lib/python3.5/concurrent/futures/thread.py”, line 55, in run result = self.fn(*self.args, **self.kwargs) File “/srv/homeassistant/lib/python3.5/site-packages/homeassistant/components/wemo.py”, line 89, in setup port = pywemo.ouimeaux_device.probe_wemo(address) File “/srv/homeassistant/lib/python3.5/site-packages/pywemo/ouimeaux_device/init.py”, line 30, in probe_wemo timeout=10) File “/srv/homeassistant/lib/python3.5/site-packages/requests/api.py”, line 72, in get return request(‘get’, url, params=params, **kwargs) File “/srv/homeassistant/lib/python3.5/site-packages/requests/api.py”, line 58, in request return session.request(method=method, url=url, **kwargs) File “/srv/homeassistant/lib/python3.5/site-packages/requests/sessions.py”, line 508, in request resp = self.send(prep, **send_kwargs) File “/srv/homeassistant/lib/python3.5/site-packages/requests/sessions.py”, line 618, in send r = adapter.send(request, **kwargs) File “/srv/homeassistant/lib/python3.5/site-packages/requests/adapters.py”, line 508, in send raise ConnectionError(e, request=request) requests.exceptions.ConnectionError: HTTPConnectionPool(host=‘192.168.1.16’, port=49153): Max retries exceeded with url: /setup.xml (Caused by NewConnectionError(’<urllib3.connection.HTTPConnection object at 0x694d8c50>: Failed to establish a new connection: [Errno 111] Connection refused’,))
I am running on Hassio. I can switch on and off my Wemo plugs, but the status on the fronted is not displayed when I switch them on/off with Alexa or the iPhone App. This has been going on for more than two years now and there has been no attempt to fix it by the HA team.
I’m a bit late to the party with this, but this is how I fixed mine (I have a weird setup)
I have 4 Wemos and I also have 6 Sonoff S20 switches set up to emulate Wemos.
I was on 0.54 and Rasbian and all worked fine. Did fresh install in stretch and HA in VirtualEnv to v0.60 (now 0.61), restored my config and I noticed that my Wemos showed an error in the config. I tried setting them as static but it still didn’t work, and I was getting similar errors to all of you.
In the end I realised from looking in the logs that it was discovering my S20s as Wemos (after all they were emulating them!) and this was causing the Wemo component to bomb out.
I had two fixes that worked:
1 - Unplug my 6 sonoffs and restart HA. I could then plug them in again
2 - Changed the sonoffs to Hue emulation.
I stuck with 2. Another workaround would have been to turn off emulation entirely and use my habridge to present the switches to Alexa, but I have found that to be unreliable.
I hope this helps someone
Thank you. Unplugging all my Wemo Minis and then restarting HA before plugging them in again actually worked (I also hashed out all the static addresses and let Discovery set up everything).
Thanks, your tip put me on the right path. My 1 wemo has been MIA since I have been playing with espurna on a wemos D1 Mini pcb. Sure enough starting HA with the espurna board off and my wemo is back. p.s. I am running Hassio 0.65.6 if anyone is interested.