Kasa HS220 Dimmer switch not connecting to HA

[Nikhilse120]

The problem

Hello All

I am trying to intregrate the kasa Dimmer swtich HS220 to HA however i am getting below error when i try to connect , if i restart the dimmer switch it get connected to HA for 5 mins and then disconnects again , is some else facing the same issue and is able to fix it

PS : Swtiches works fine from Kasa App

Retrying setup: Unable to connect to the device: 192.168.1.70: [Errno 113] Connect call failed ('192.168.1.70', 9999)

What version of Home Assistant Core has the issue?

core-2023.5.4

What was the last working version of Home Assistant Core?

Not working with any version

What type of installation are you running?

Home Assistant OS

Integration causing the issue

TP link Kasa Smart

Link to integration documentation on our website

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

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

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

Code owner commands

Code owners of `tplink` 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 tplink` Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

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

[jaswope]

~Having the same issue with an HS100 that used to work, after upgrading from 2023.4.6 to 2023.6.1. Exactly the same error except for the IP address (even the port is the same). I haven't specifically checked the status of that device in a little while though, so I can't say for sure the issue showed up between those version.~ EDIT: Resolved with a device restart

[rytilahti]

You could try to use python-kasa manually, or alternatively downgrade homeassistant to the previously known working version, to see if the device can still be controlled that way. If yes, we can start figuring out what has changed in homeassistant that could have broke it for you.

The devices I have (hs110, kp115, kl130, kp303) work just fine with the newest homeassistant release, but they are not connected to the internet nor have I tried to update their firmware. Could it be that yours got a new firmware update that disables or changes how the the local controls work?

[Nikhilse120]

Thank you for your response , I am new to HA , can you please suggest a working version of HA i can try to downgrade ?

[Nikhilse120]

Having the same issue with an HS100 that used to work, after upgrading from 2023.4.6 to 2023.6.1. Exactly the same error except for the IP address (even the port is the same). I haven't specifically checked the status of that device in a little while though, so I can't say for sure the issue showed up between those version.

Hello Jon

Thank for your reply

what version will you recommend to downgrade the HA to test

[jaswope]

You could try to use python-kasa manually, or alternatively downgrade homeassistant to the previously known working version, to see if the device can still be controlled that way. If yes, we can start figuring out what has changed in homeassistant that could have broke it for you.

The devices I have (hs110, kp115, kl130, kp303) work just fine with the newest homeassistant release, but they are not connected to the internet nor have I tried to update their firmware. Could it be that yours got a new firmware update that disables or changes how the the local controls work?

Unsatisfyingly, in my steps to troubleshoot this and gather the information you requested, I had to unplug/re-plug the device, and that resolved the issue for me. I hadn't considered it since the device still appeared to be connected to the network. Very strange, but unfortunately means I don't have much to contribute to the conversation anymore. My apologies.

[pwteneyck]

I'm having the exact same issue:

What version of Home Assistant Core has the issue? Frontend 20230503.3 - latest

What was the last working version of Home Assistant Core? Not working with any version

What type of installation are you running? Debian 10

Integration causing the issue TP link Kasa Smart

From the debug logs:

2023-06-15 13:26:50.233 WARNING (MainThread) [homeassistant.config_entries] Config entry 'Bedroom Lamp HS100(US)' for tplink integration not ready yet: Unable to connect to the device: 192.168.6.52: [Errno 113] Connect call failed ('192.168.6.52', 9999); Retrying in background

[Nikhilse120]

You could try to use python-kasa manually, or alternatively downgrade homeassistant to the previously known working version, to see if the device can still be controlled that way. If yes, we can start figuring out what has changed in homeassistant that could have broke it for you.

The devices I have (hs110, kp115, kl130, kp303) work just fine with the newest homeassistant release, but they are not connected to the internet nor have I tried to update their firmware. Could it be that yours got a new firmware update that disables or changes how the the local controls work?

Hello , i have tested it now by downgrading the version of HA and also used kasa python , still the same error , if i restart the HS220 switch, it gets added to HA for 2 mins and then disconnects again with same error

[rytilahti]

When it gets added to HA, does it display any information about the device? And can you control the device during this period, either by using homeassistant or python-kasa?

I'm just wondering if some recent firmware / product line update has changed the protocol, but it would be weird if they still seemingly work for those few minutes... In case you never get any information out from the device, or cannot change the state using python-kasa or homeassistant, it could be that the device is incorrectly added to homeassistant even when it is not supported at the moment.

[Nikhilse120]

Yes it does display the info for the device , however the control are disabled , please see attached

[pwteneyck]

I'm able to access the smart plug using the python-kasa tool, although interestingly not every machine on my network works. My mac, which is hardwired to the same ethernet switch as my HA server, fails to discover any Kasa devices, while a Linux laptop connected via Wifi finds the plug just fine.

My integration panel shows this error:

and there's nothing in my Devices or Entities from that integration.

UPDATE: Just plugged a second HS100 into an outlet and HA recognized it right away and connected with no issues. The two devices are running the same firmware version

[pwteneyck]

This might not be the best solution, but I fixed my problem by assigning the "bad" plug a new IP address. The plug that HA connected to without a problem used a lower IP (192.168.4.183), so I assigned the first plug to 192.168.4.184, then pulled it out of the power outlet for a bit so it'd have to renew its DHCP. Plugged it back in and HA immediately connected successfully

[Nikhilse120]

I tried the same but still getting the error debug logs File "/usr/local/lib/python3.11/site-packages/kasa/smartdevice.py", line 253, in _query_helper raise SmartDeviceException(f"Communication error on {target}:{cmd}") from ex kasa.exceptions.SmartDeviceException: Communication error on smartlife.iot.dimmer:set_dimmer_transition 2023-06-16 11:00:33.344 WARNING (MainThread) [homeassistant.config_entries] Config entry ' Kitchen_Lights HS220(US)' for tplink integration not ready yet: Unable to connect to the device: 192.168.1.94: [Errno 113] Connect call failed ('192.168.1.94', 9999); Retrying in background

[rytilahti]

I am assuming that the IP address is not correct for the device? If the device is in the same broadcast domain (/network), the dhcp information should be used to update the address when it changes, but for some reason it does not seem to be working for you.

Now, I'm not sure what's causing the problem, but the relevant piece of code updating that address is located here: https://github.com/home-assistant/core/blob/0513117a1104bb7cd6f8a4af23f434c0d1842ee6/homeassistant/components/tplink/config_flow.py#L48-L50

[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.

[rytilahti]

Fix in #98784 might be related.

[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.