Wemo fails after latest update

[Irish-link]

The problem

For me personally this is non critical. Fans, and some outlets. Nothing that can't be turned on by hand.

After the latest update the Wemo integration no longer starts. I have tried reloading multiple times. I have reverted back to an older config I had but unfortunately that was a few months ago for a full backup. (I know but for some reason my switch was off for backup on update)

RPI4-64.

I have old Wemos. Some are the in wall switches, and some are outlet switches that have the ability to be homekit. However all of them are on firmware for locally run. Non of them have been updated to use the new cloud stuff. They are on a specific wifi vlan that HA is also connected to and has not had an issue connecting prior. The only thing that has changes is the latest update.

If there could be some help I would appreciate. If we are moving away from Wemo then by all means let me know and i'll start to finally find a replacement using ZHA.

Thanks!

LOGS

Logger: homeassistant.config_entries Source: config_entries.py:751 First occurred: 7:07:53 AM (4 occurrences) Last logged: 11:42:35 PM

Error setting up entry Wemo for wemo Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/config_entries.py", line 751, in __async_setup_with_context result = await component.async_setup_entry(hass, self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/components/wemo/init.py", line 133, in async_setup_entry await discovery.async_discover_and_schedule() File "/usr/src/homeassistant/homeassistant/components/wemo/init.py", line 272, in async_discover_and_schedule for device in await self._hass.async_add_executor_job( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ pywemo.discover_devices ^^^^^^^^^^^^^^^^^^^^^^^ ): ^ asyncio.exceptions.CancelledError: Global task timeout

---

/LOGS

What version of Home Assistant Core has the issue?

core-2025.4.4

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

wemo

Link to integration documentation on our website

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

Diagnostics information

No response

Example YAML snippet

Anything in the logs that might be useful for us?

Logger: homeassistant.config_entries
Source: config_entries.py:751
First occurred: 7:07:53 AM (4 occurrences)
Last logged: 11:42:35 PM
Error setting up entry Wemo for wemo

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 751, in __async_setup_with_context
    result = await component.async_setup_entry(hass, self)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/wemo/__init__.py", line 133, in async_setup_entry
    await discovery.async_discover_and_schedule()
  File "/usr/src/homeassistant/homeassistant/components/wemo/__init__.py", line 272, in async_discover_and_schedule
    for device in await self._hass.async_add_executor_job(
                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        pywemo.discover_devices
        ^^^^^^^^^^^^^^^^^^^^^^^
    ):
    ^
asyncio.exceptions.CancelledError: Global task timeout

Additional information

No response

[home-assistant[bot]]

Hey there @esev, mind taking a look at this issue as it has been labeled with an integration (wemo) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of wemo can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign wemo Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

wemo documentation wemo source _{^{(message by IssueLinks)}}

[Spectre5]

The underlying pywemo library has no had any recent changes, but I've also been encountering a lot of issues with my wemo devices since a recent HA update.

@Irish-link you might try setting static IPs for your devices and disabling discovery. That said, I already disable discovery and have static IPs but am getting all kinds of different issues. @esev do you know if any recent changes in the core wemo component may be affecting the WeMo?

I'm getting different types of errors, but a couple examples are

2025-04-30 19:08:44.212 ERROR (SyncWorker_4) [homeassistant.components.wemo] Unable to get description url for WeMo at: 192.168.X.X
2025-04-30 19:08:52.700 WARNING (SyncWorker_3) [urllib3.connectionpool] Retrying (Retry(total=5, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ReadTimeoutError("HTTPConnectionPool(host='192.168.X.X', port=49153): Read timed out.")': /remoteaccess.xml

[prosenba1]

Hi @Irish-link have you find a solution?

[Irish-link]

Unfortunately no, ever since I updated to HA core-2025.4.4 the issue has persisted. Static IPs haven’t changed anything for me.

Edit - 5-12-2025. I have remove the integration and then added it back. Still nothing.

As a work around I added a custom add-on for homebridge. Inside the add-on store I added a repository "https://github.com/tronikos/home-assistant-addons" and installed homebridge. I used this to add my wemo devices and control them and then from there added the homebridge connection into homeassistant. This allowed my automation that use those switches to work seamlessly again without issue.

[Spectre5]

I don't think anything meaningful changed in the Wemo component in the last update or the, but my issues seem to be resolved. Maybe it was a random temporary wifi issue on my side, but only my Wemo's were acting up when I last posted.

[cliss]

I'm on 2025.4.2 and I noticed that none of my Belkin devices are working. If I go into Settings → Devices & Services → Belkin WeMo and then pick any of my switches, there are radio buttons to turn them on/off, but the radio buttons appear to be disabled.

I turned on debug logging and reloaded the integration, but nothing useful shows up, as far as I can tell.

Edit: Just realized that apparently the integration has dropped my devices on the floor?

This entity is no longer being provided by the wemo integration. If the entity is no longer in use, delete it in settings.

[op4lat]

Interesting... I have Core 2025.5.3 and the lights are "still working". When I say still working, sometimes they disappear, and reappear after either power resetting the hub, or after a while. They don't appear in the upstream phone app, tho. So they're working as much as they can but I can control them most of the time in home assistant.

Anyways, the point of this post: This same errors look very familiar to what the Govee lights have:

Wemo:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 751, in __async_setup_with_context
    result = await component.async_setup_entry(hass, self)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/wemo/__init__.py", line 133, in async_setup_entry

Govee:

Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 749, in __async_setup_with_context
result = await component.async_setup_entry(hass, self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/govee/init.py", line 72, in async_setup_entry
await hass.config_entries.async_forward_entry_setup(entry, component)

@sircambridge mentions why it breaks https://github.com/LaggAt/hacs-govee/issues/234#issuecomment-2938442012

@MatthewWaanders created a PR https://github.com/LaggAt/hacs-govee/issues/234#issuecomment-2954267489 and it seems he has fixed it (update: I can control my govee lights after manually patching)

I wonder if anyone can take a look at the PR and see if Wemo could have the same medicine. (I don't speak Python)

Update: just updated to Core 2025.6.1 and I cannot control the lights anymore (connected to a hub), but I can still control the switches.

[MatthewWaanders]

Seems to be the same issue on first glance, I'll see if I have time to take a look somewhere this week. Not a python dev either but these fixes seem relatively minor in a straightforward codebase so I'll see

[cliss]

Update: my stuff started working again, with no intervention on my part. 🤨

It had been broken for the better part of a week, at least.

[op4lat]

Really? and you didn't update anything? and light bulbs are working? I just even restarted the integration, and I still can control my light bulbs 🤷‍♂

[cliss]

Really? and you didn't update anything? and light bulbs are working? I just even restarted the integration, and I still can control my light bulbs 🤷‍♂

I only have plugs, but yes, they're back.

Although I lied; I forgot I updated to HA 2025.6.1. Apologies!

[op4lat]

Ah, ok. Yeah, switches are working fine. Thanks for confirming

[op4lat]

As a work around I added a custom add-on for homebridge. Inside the add-on store I added a repository "https://github.com/tronikos/home-assistant-addons" and installed homebridge. I used this to add my wemo devices and control them and then from there added the homebridge connection into homeassistant. This allowed my automation that use those switches to work seamlessly again without issue.

Do you only have switches, or do you have light bulbs (with the hub)? switches are working fine without any modification, but the light bulbs are no responsive for me.

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.