FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

HS110(UK) v4.1 beta firmware times out with the HomeKit probe in 0.11.0.1 · Issue #1788 · python-kasa/python-kasa · GitHub

Repository navigation

HS110(UK) v4.1 beta firmware times out with the HomeKit probe in 0.11.0.1 #1788

Open

Description

Three of my HS110(UK) plugs stopped working in Home Assistant after updating to 2026.10.1. I can reproduce it outside Home Assistant with python-kasa.

All three are hardware 4.1, running 1.1.1 Build 201203 Rel.135822. This is the old TP-Link compatibility beta that restored the local API (I think my plugs may be locked on this old compatibility firmware and can't be changed).

Testing the same plugs from the same machine:

  • python-kasa 0.10.2: discovery and updates work.
  • python-kasa 0.11.0.1: discovery succeeds, but updates time out.
  • 0.11.0.1 with Module.IotHomeKit removed during module initialization: updates work on all three, including a second update.

A fourth HS110(UK), hardware 2.1 on 1.5.10 Build 191125 Rel.094314, works with the unmodified 0.11.0.1.

To reproduce:

import asyncio
from kasa import Discover

async def main():
    device = await Discover.discover_single("PLUG_IP")
    try:
        await device.update()
    finally:
        await device.disconnect()

asyncio.run(main())

The update fails with:

Timeout after 5 seconds sending request to the device PLUG_IP:9999

Direct system.get_sysinfo requests still work. Debug logging shows that the update now includes smartlife.iot.homekit.setup_info_get, added in #1566. Skipping that module fixes the timeout. Third-Party Compatibility is also enabled in the Kasa app.

Could the HomeKit probe be skipped for these devices, or handled so it doesn't prevent the rest of the update?

Activity

  1. ZeliardM commented on Oct 11, 2026

    Collaborator

    Do these devices support HomeKit natively or not? Sorry, not sure. If they do, can you get a fixture for them with the latest python-kasa? Trying to figure out why they timeout with the query. Thanks!

  2. AlecRust commented on Oct 12, 2026

    Author

    @ZeliardM no my HS110(UK) do not support HomeKit natively.

  3. ZeliardM commented on Oct 12, 2026

    Collaborator

    @AlecRust ok, thanks. My older HS300 and KP115 don't either and my EP25 do. Those are the devices I tested this on originally. I will go back and do some further investigation on the polling and answers and how it's actually handled. Thanks!

  4. ZeliardM commented on Oct 12, 2026

    Collaborator

    @AlecRust So it seems to be an issue with the older firmware as others who have reported this with the same plug I have but older firmware get the errors but I don't on the newer firmware. So it stands to reason that something in the older firmware has something to do with the ordering of the calls or calling items that are not supported right after system calls. We can re-order the calls but I don't think that removing it completely is the right call. Can you test by putting the HomeKit call later in the list instead of right after the system call? See if it still works after you reorder them? Let me know.

  5. AlecRust commented on Oct 13, 2026

    Author

    @ZeliardM yes, moving IotHomeKit to the end of the module order fixes it!

    Also to be clear, I've confirmed with TP-Link that although I was on some old beta firmware for HA support, there is no new firmware available for these plugs.

  6. psiberfunk commented on Oct 17, 2026

    Cross-linking, since this thread and #1791 haven't met yet: #1791 tracks the same regression with a protocol-level repro (#1803 was closed as its duplicate today). #1792 is an open fix that sends the HomeKit query in its own request instead of batching it.

    On the reorder-vs-separate question above, here's the evidence from all the threads:

    • Moving HomeKit later works on HS110(UK) hw 4.1 (this issue), KP115 (#1791) and EP10 (home-assistant/core#185971).
    • One report says it does not: HS103(US) hw 5.0 / fw 1.0.3 reportedly still times out with HomeKit last (home-assistant/core#185971). It's a single report and nobody has confirmed it.
    • The trigger isn't HomeKit-specific. On KP115 and HS110 hw 4.1, a made-up foo.bar module right after system hangs the same way (#1791, #1792). So a reorder only works while whatever lands after system is a module that device supports.

    #1792 (ee5061e) has been run on real hardware: EP10 hw 1.0 / fw 1.0.2 (two people, one of them inside HA), HS103 hw 5.0 / fw 1.0.3 (9 plugs across two people), and KP115 hw 1.0 / fw 1.0.7. It hasn't been run on this issue's HS110(UK) hw 4.1 / fw 1.1.1 yet. @AlecRust or @igiannakas, could one of you try ee5061e on those plugs? That's the one gap #1791 calls out.

    More reports of the same thing: #1799 (KP100 hw 3.0), #1803 (HS200 hw 5.0), and downstream home-assistant/core#185971, home-assistant/core#185900 and home-assistant/core#185859. HA 2026.10.2 (released yesterday) still pins 0.11.0.1, so affected HA users stay broken until a python-kasa release lands in HA.

  7. AlecRust commented on Oct 17, 2026

    Author

    @psiberfunk tested #1792 on all three of my HS110(UK) plugs and it works, including after reconnecting. Energy readings work too. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions


      Back | FazBrowse Home | New Git URL