Smart plug unable to connect after factory reset

[perezjuanj]

Type

Bug

Summary

A previously connected plug (HS103) no longer works after a factory reset. Here are the logs

[23/03/2026, 16:15:36] [KasaPython] STDERR: INFO:     Started server process [811235]
[23/03/2026, 16:15:36] [KasaPython] STDERR: INFO:     Waiting for application startup.
INFO:     Application startup complete.
INFO:     Uvicorn running on http://0.0.0.0:45613 (Press CTRL+C to quit)
[23/03/2026, 16:15:37] [KasaPython] STDERR: [Kasa API] ERROR: Device discovery: Unable to connect to the device: 192.168.159.180:9999: [Errno 111] Connect call failed ('192.168.159.180', 9999) (host=192.168.159.180, alias=Fan)
[23/03/2026, 16:15:38] [KasaPython] STDERR: [Kasa API] ERROR: Device discovery: ("Device connection error: 192.168.159.115: Cannot connect to host 192.168.159.115:80 ssl:<ssl.SSLContext object at 0x7fa264f380> [Connect call failed ('192.168.159.115', 80)]", ClientConnectorError(ConnectionKey(host='192.168.159.115', port=80, is_ssl=False, ssl=<ssl.SSLContext object at 0x7fa264f380>, proxy=None, proxy_auth=None, proxy_headers_hash=None), ConnectionRefusedError(111, "Connect call failed ('192.168.159.115', 80)"))) (host=192.168.159.115)

Details

Multiple plugs work fine with Homebridge but this specific plug does not work under the plugin and it does work under the Kasa app
Reproduction steps:

• Connect recently reset plug back into the Kasa app and use the homebridge-kasa-python plugin

[23/03/2026, 16:15:36] [KasaPython] STDERR: INFO:     Started server process [811235]
[23/03/2026, 16:15:36] [KasaPython] STDERR: INFO:     Waiting for application startup.
INFO:     Application startup complete.
INFO:     Uvicorn running on http://0.0.0.0:45613 (Press CTRL+C to quit)
[23/03/2026, 16:15:37] [KasaPython] STDERR: [Kasa API] ERROR: Device discovery: Unable to connect to the device: 192.168.159.180:9999: [Errno 111] Connect call failed ('192.168.159.180', 9999) (host=192.168.159.180, alias=Fan)
[23/03/2026, 16:15:38] [KasaPython] STDERR: [Kasa API] ERROR: Device discovery: ("Device connection error: 192.168.159.115: Cannot connect to host 192.168.159.115:80 ssl:<ssl.SSLContext object at 0x7fa264f380> [Connect call failed ('192.168.159.115', 80)]", ClientConnectorError(ConnectionKey(host='192.168.159.115', port=80, is_ssl=False, ssl=<ssl.SSLContext object at 0x7fa264f380>, proxy=None, proxy_auth=None, proxy_headers_hash=None), ConnectionRefusedError(111, "Connect call failed ('192.168.159.115', 80)"))) (host=192.168.159.115)

Environment (Required for Bugs)

Plugin Version: Both 3.2.0 and 3.2.0-beta.1
Homebridge Version: 1.11.3
Node.js Version: 24.13.0
NPM Version: 11.6.2
Python Version: 3.11.2
OS: Raspberry Pi OS (64-bit)

Migration Strategy (Breaking Change Only)

No response

Logs (If Relevant)

Additional Context

No response

[github-actions]

❌ Issue validation failed.

Details:

Environment section is too short or missing (expected >=15 chars).
Details should include reproduction steps and expected/actual behaviour.
Issue is still marked as needs-info. Please provide the requested information.

Please update the issue with the requested information.

[ZeliardM]

@perezjuanj Can you get me some debug logs from the kasa CLI? I need to see what else is going on. Were there any firmware updates?

[perezjuanj]

@ZeliardM Sure, we actually had a similar issue a year or two ago but I can't find it. Here are the logs

homebridge-kasa-python.log.txt

[ZeliardM]

@perezjuanj Thanks for those, but can you actually run from the Homebridge terminal the kasa CLI to get the debug logs? You'll need to go to the terminal:
cd kasa-python
source .venv/bin/activate
kasa --debug --username 'username' --password 'password' --host ip_address discover

Give me the output there so I can see what the connection is that it's trying to make.

[perezjuanj]

(.venv) homebridge@homebridgevarlib.txt

Let me know if that works

[ZeliardM]

@perezjuanj You need to put the ip_address of the device, 192.168.1.25 or whatever it is.

[perezjuanj]

Added it manually
{ "name": "KasaPython", "enableCredentials": true, "username": "xxx", "password": "XXX", "enableEnergyMonitoring": false, "hideHomeKitMatter": true, "pollingInterval": 5, "discoveryPollingInterval": 300, "offlineInterval": 7, "waitTimeUpdate": 100, "advancedPythonLogging": true, "logEnergyMonitoring": false, "_bridge": { "username": "0E:B7:57:2B:36:C6", "port": 32750 }, "platform": "KasaPython", "additionalBroadcasts": [ "192.168.159.90" ], "manualDevices": [ { "host": "192.168.159.90" } ] },

Still receiving this error
23/03/2026, 20:00:16] [KasaPython] STDERR: INFO: Waiting for application startup. INFO: Application startup complete. INFO: Uvicorn running on http://0.0.0.0:43397 (Press CTRL+C to quit) [23/03/2026, 20:00:16] [KasaPython] STDERR: [Kasa API] ERROR: Device discovery: Unable to connect to the device: 192.168.159.180:9999: [Errno 111] Connect call failed ('192.168.159.180', 9999) (host=192.168.159.180, alias=Fan) [23/03/2026, 20:00:17] [KasaPython] STDERR: [Kasa API] ERROR: Device discovery: ("Device connection error: 192.168.159.115: Cannot connect to host 192.168.159.115:80 ssl:<ssl.SSLContext object at 0x7fac5af530> [Connect call failed ('192.168.159.115', 80)]", ClientConnectorError(ConnectionKey(host='192.168.159.115', port=80, is_ssl=False, ssl=<ssl.SSLContext object at 0x7fac5af530>, proxy=None, proxy_auth=None, proxy_headers_hash=None), ConnectionRefusedError(111, "Connect call failed ('192.168.159.115', 80)"))) (host=192.168.159.115) [23/03/2026, 20:00:19] [KasaPython] STDERR: [Kasa API] ERROR: Device discovery: Unable to query the device 192.168.159.90:9999: [Errno 104] Connection reset by peer (host=192.168.159.90, alias=Fan) [23/03/2026, 20:00:19] [KasaPython] STDERR: [Kasa API] ERROR: Device discovery: Unable to query the device 192.168.159.90:9999: [Errno 104] Connection reset by peer (host=192.168.159.90, alias=Fan)

It's interesting because I have other plugs of the same model that work fine as soon as they are connected

(.venv) homebridge@homebridgevarlib.txt

[perezjuanj]

my guess is that the IP addresses are being cached somewhere because the plug has a static ip ending in .90 like I have on the json file