Kasa HS103 plug

Supported devices: Plugs: EP10, EP25[^1], HS100[^2], HS103, HS105, HS110, KP100, KP105, KP115, KP125, KP125M[^1], KP401; Power Strips: EP40, EP40M[^1], HS107, HS300, KP200, KP303, KP400; Wall Switches: ES20M, HS200[^2], HS210, HS220[^2], KP405, KS200, KS200M, KS205[^1], KS220, KS220M, KS225[^1], KS230, KS240[^1]; Bulbs: KL110, KL120, KL125, KL130, KL135, KL50, KL60, LB110; Light Strips: KL400L5, KL420L5, KL430; Hubs: KH100[^1]; Hub-Connected Devices[^3]: KE100[^1]; Plugs: P100, P105, P110, P110M, P115, P125M, P135, TP15; Power Strips: P210M, P300, P304M, P306, TP25; Wall Switches: S210, S220, …

Excerpt saved from home-assistant.io on 2026-10-23.

Workaround until a fixed python-kasa reaches a Home Assistant release. This is the cause described in python-kasa#1791 and #1792. python-kasa 0.11.0.1 adds a HomeKit probe right after `system` in the same request, and some legacy firmware never answers that request, so the update times out and the entry sits in `setup_retry`. The small custom integration below stops python-kasa from sending that probe. It does not touch any library files. Tested on Home Assistant Container 2026.10.1 (python-kasa 0.11.0.1). I have not tried HA OS or Core, but custom integrations load the same way there. Two …

Excerpt saved from GitHub on 2026-10-23.