Core: Wemo switches are operating the wrong wemo switches

[jwl17330536]

Home Assistant release with the issue:

0.84.6

Last working Home Assistant release (if known):
0.83.? is my best guess. I can't remember when I first noticed this. I was too busy to investigate the cause of it for awhile and went with my work-around of removing the wemo entities from .storage/core.entity_registry and restarting. I originally thought it was maybe something that I had done or switches were moved around my house.

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

Ubuntu virtual environment: https://www.home-assistant.io/docs/installation/raspberry-pi/

Component/platform:

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

Description of problem:
Wemo switches are getting mixed up. For example, I will discover all my wemo switches and when I turn on the family room wemo it will turn on as expected. I'll restart HASS and when I go to turn on that same family room wemo then the office lamp wemo will turn on instead. I've seen occasions where I turn one wemo on/off and multiple wemo's will respond and do the same on or off. Going to .storage/core.entity_registry and deleting all the wemo's from my system and restarting HASS will fix this... until another restart.

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

wemo:
  discovery: true

Traceback (if applicable):

None found

Additional information:
The "discovery: true" is what I'm using now, but using static addresses had the same issue.

[MartinHjelmare]

CC @sqldiablo

[sqldiablo]

I had a similar report of this a week or two back from someone else. There is a change that will be in 0.85 that I'm hoping will fix it, but I'll investigate this some more once I get a little time to take a look at it.

[geekofweek]

Similar problems that I was just about to open an issue for. I've been slowly trying to figure out what causes it (holidays and all).

• Only happens after some time, a restart will fix it for a while
• I moved it from Static to only Discovery only with no change
• Disabled discovery no change
• I removed all of the Wemo devices from core entity registry and let it re-create, no change

What I've found is that I will loose connection to one of the switches, which is later on followed by an unable to re-probe:

WARNING (MainThread) [homeassistant.components.switch.wemo] Lost connection to Lower Backyard Lighting
ERROR (SyncWorker_12) [pywemo.ouimeaux_device] Unable to re-probe wemo at 192.168.X.XXX

[sqldiablo]

Thanks for the info, @geekofweek. I had some corruption take out my dev environment, but I'll resume working on this issue as soon as I'm back up and running. I have just the wemo light component left. The other components just need some more testing and they'll be good to go.

[zombu2]

is any of you running haswitchplate by any chance?

[sqldiablo]

Related to issue: https://github.com/pavoni/pywemo/issues/121

[sqldiablo]

Now that 0.85 has released, can you guys please check if this issue persists in the new version? @geekofweek, @jwl17330536 @meatheadmike

[geekofweek]

I'll give it a shot once the docker build is complete and report back if I see anything one way or another.

[sqldiablo]

Much appreciated. I'm still a couple days out from having my servers restored from backup so I can start developing again. It has been a nightmare. Fortunately, I kept current with pushing changes to my github fork, so I didn't lose any work. Once I'm back up and running, I hope to finish the changes to make Home Assistant handle rediscovery instead of pywemo, which should fix pretty much all of the pending rediscovery issues. I still want to fix pywemo as well, but at least getting Home Assistant working better will buy me some time to get pywemo fixed too.

[jwl17330536]

Thanks for the work @sqldiablo. I've updated to 0.85 and I'll let you know what I find.

[jwl17330536]

It has worked across 3 restarts and a few hours. Mine seems to either be working or at least working for a longer time! Thanks again!

[meatheadmike]

I haven't had much time to test. And unfortunately I wont be able to this weekend since I have a visitor in from out of town. I'm still running pr https://github.com/pavoni/pywemo/pull/125 and I haven't had to reboot HA since I installed that version. However my problematic insight switches are in storage at the moment, so I can't say for sure that the issue is fixed. What I can say is that nothing is worse than it was :)

[zombu2]

seems it has to do with mdns and part of the wemo switch firmware crashing as in register and states
when these switches go bonkers check the wemo app i bet that one won't work right either

[callifo]

I'll keep an eye on it too, had this quite a lot in the last few builds (0.82-0.84). No issues on 0.85 yet.

[sqldiablo]

@geekofweek, have you had a chance to test this out and see if it's working any better?

@zombu2: Are you still experiencing this issue on the latest (0.85.1) build of Home Assistant?

[geekofweek]

I haven't noticed any issues, wanted to get a few days of constant run time in since I usually saw the error after a few days.

[sqldiablo]

Sounds good. Please let me know how it goes.

[meatheadmike]

I just updated to 0.86.0b0 and it's been a bit of a disaster. None of my wemo dimmers were discovered. Interestingly I can see them in the logs. And there's no errors. But in the UI they are simply unavailable. When I use the Wemo app I can dim and switch on/off without any problems. I even see stuff like this when I do so:

2019-01-18 08:18:59 INFO (Wemo HTTP Thread) [pywemo.subscribe] Received event from <WeMo Dimmer "Kitchen lights">(192.168.1.206) - Brightness 40 2019-01-18 08:18:59 INFO (Wemo HTTP Thread) [homeassistant.components.switch.wemo] Subscription update for Kitchen lights 2019-01-18 08:19:00 INFO (Wemo HTTP Thread) [pywemo.subscribe] Received event from <WeMo Dimmer "Kitchen lights">(192.168.1.206) - BinaryState 0 2019-01-18 08:19:00 INFO (Wemo HTTP Thread) [homeassistant.components.switch.wemo] Subscription update for Kitchen lights 2019-01-18 08:19:03 INFO (Wemo HTTP Thread) [pywemo.subscribe] Received event from <WeMo Dimmer "Kitchen lights">(192.168.1.206) - BinaryState 1 2019-01-18 08:19:03 INFO (Wemo HTTP Thread) [homeassistant.components.switch.wemo] Subscription update for Kitchen lights

Again though, completely in accessible in the UI in both Lovelace and the old UI. Nor do they show up in states.

[meatheadmike]

FYI - I'm using discovery with static addresses

[arsaboo]

Why not configure the switches directly? I have had no issues with Wemo switches.
Also, did you add the switches to the UI? Check if the switches are available in states.

[meatheadmike]

My switches are fine. The dimmers are what have issues. They do not show up in states. I have reverted to my custom components that used an older branch of pywemo and everything seems fine now (well not everything, this latest release was a disaster for other reasons too - but my dimmers are functional again).

[sqldiablo]

@meatheadmike, can you make the code and logger config changes here: https://github.com/home-assistant/home-assistant/issues/20006#issuecomment-455044682 and send me your logs? I'm trying to understand these two issues, their root cause, and whether they're related.