core: Belkin WeMo Device Unavailable & Then After Uninstalling/Reinstalling Integration, No Entities
The problem
Belkin WeMo has been configured through the native integration for quite some time. The device became unavailable yesterday in HA and persisted after a reboot and upgrade to 2022.7.3. Removing the integration, rebooting, and the re-adding the integration worked, however there are now no entities. I’ve also rebooted the device, pulled power and reconneted, and tested it from the WeMo app (that works fine). It’s on my network, but HA has not reassigned the entity…
What version of Home Assistant Core has the issue?
2022.7.3
What was the last working version of Home Assistant Core?
2022.7.2
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Belkin WeMo
Link to integration documentation on our website
https://www.home-assistant.io/integrations/wemo
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Logger: pywemo.subscribe
Source: /usr/local/lib/python3.10/site-packages/pywemo/subscribe.py:369
First occurred: 08:32:03 (10 occurrences)
Last logged: 08:53:06
Received event for unregistered device 10.0.0.111
Additional information
No response
About this issue
- Original URL
- State: open
- Created 2 years ago
- Reactions: 4
- Comments: 22 (6 by maintainers)
I’ll start by kindly asking to point me in the right direction if I’m wrong to post on this old-ish issue.
I’m posting because I’m experiencing the same issue immediately after upgrading to core-2023.9.2 from core-2023.9.1 on 2023-09-12. Naturally, my first move was to restore to the backup of core-2023.9.1 but that didn’t fix this issue. I have 14 wemo devices (wall switches mainly, some plug-in outlets) and all but one have completely disappeared as devices from HA. The one that remains is showing as unavailable.
I’ve rebooted, reset WiFi and factory reset a couple wemo devices to no avail. I have a flat network with no subnets or VLANs to worry about when troubleshooting this. All wemo devices still work perfectly in the Wemo app; it’s only local API communication that seems to have stopped.
I’m just wondering where I could start on this. I’m not even sure if the problem lies with HA or Wemo. May I ask for some help to troubleshoot that to at least narrow down if it’s a HA issue or something else?
Edit: After I posted this yesterday, I added one device manually via config file static entry to no avail. Today, in the morning I checked and still only had one Wemo device listed and that one device was still unavailable. Having made zero changes since last night, in the afternoon today I walked by one of my motion sensors that turns on a couple Wemo lights via HA automation (which unsurprisingly failed to work since this issue started) and it worked this time! I checked and now all of my Wemo devices have been re-auto discovered and added back. I have no idea why that is since I still have no idea why they disappeared in the first place.
Turn off the power to the devices for a few seconds. They usually come back after that. The way the devices communicate with the WeMo app is independent of the way Home Assistant communicates with them. Sometimes they stop responding to Home Assistant but continue communicating with Belkin’s cloud. Sometimes it’s the opposite.
I’m guessing they’re all light switches?
Any chance they’re on a different VLAN from Home Assistant?
@esev Super helpful. I’ll add all of those ports to my firewall rule. If firewall rules don’t work, I’ll move the WeMo to the same network as my HA instance.
@TonySherman in case it helps, WeMo devices don’t always use the same ports. Even the same device may use a different port after a reboot. Here are the ones that PyWemo tries: https://github.com/pywemo/pywemo/blob/c34e74629a67d74b9dbdf2490d70df215989b0bf/pywemo/ouimeaux_device/__init__.py#L38
Just mentioning this in case there are firewall rules that look for only specific ports.
same exact problem