Seems broken in the US too...

[khxnv]

Hello, I think my device - Kasa KP303 (hw ver 2.0) - recently updated firmware to 1.1.2 [not sure what it was previously]... but for the past week or two this plugin hasn't been able to link with the device. I've tried uninstalling and clearing it and such; but to no avail... Tried the other TP-link plugin and it didn't work either. So I guess these plugins are dead now - unless they are used "offline".

One thought that might be useful to see how to revive it would be to look at the TPLink module for a program call Bitfocus Companion. There's module in there that might have code to work around the problem. I'm not more than a user so I don't really know.

Thanks

[jneilliii]

Enable debug logging in the plugins settings, restart OctoPrint and let's look at octoprint.log and the tplinksmartplug log and see what's going on. I can't debug with simply statements it doesn't work.

[jneilliii]

You could also test the latest release candidate, which as additional compatibility for other devices. Go into software update settings and change release channel to release candidate and update when prompted.

[leftyfb]

@jneilliii This is trying to talk to a HS300 that I stupidly updated a while ago after working perfectly fine for years. It also broken compatibility with my Home Assistant.

2025-11-15 16:10:55,301 - octoprint.plugins.tplinksmartplug.debug - DEBUG - ImmutableMultiDict([('checkStatus', '192.168.0.247')])
2025-11-15 16:10:55,302 - octoprint.plugins.tplinksmartplug.debug - DEBUG - Checking status of 192.168.0.247.
2025-11-15 16:10:55,306 - octoprint.plugins.tplinksmartplug.debug - DEBUG - {'connection_type': {'device_family': 'IOT.SMARTPLUGSWITCH', 'encryption_type': 'KLAP', 'http_port': 80, 'https': False, 'login_version': 2}, 'host': '192.168.0.247', 'timeout': 5}
2025-11-15 16:10:55,801 - octoprint.plugins.tplinksmartplug.debug - ERROR - Error connecting to device: Device response did not match our challenge on ip 192.168.0.247, check that your e-mail and password (both case-sensitive) are correct. 

It still fails even putting in my credentials

[jneilliii]

It still fails even putting in my credentials

If you are running the latest release candidate version it could be the same issue we're seeing documented here on the upstream python module that is handling communication. Luckily it looks like they are already working on a fix for a future update in this PR.

[github-actions]

This issue has been automatically marked as stale because it has not had activity in 14 days. It will be closed if no further activity occurs in 7 days