KS220M dying out of nowhere
I have the exact same issue as described in this previous post:
https://community.tp-link.com/en/smart-home/forum/topic/641150
I'm disappointed to see that there was no answer resolving the issue from 2 years ago.
I currently have several KS220M installed in three bathrooms in my house. Everything works for a while, but then they just stops working (never all at the same time. When this happens, it's like the affected dimmer's hardware has crashed. Even the physical buttons do nothing, Nothing works. ie. If I attempt to trigger it using the motion sensor, the physical button, or the app and the light doesn't change states (sometimes it is stuck off, other times it is stuck on). It continues to look online in the app.
When I press the restart button on the right, bellow the main switch, the switch reboots and works again for a while.
This is happening often enough that I may have to remove them. 🙁
Has anyone else had this same issue and found a fix?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
AndreyPl wrote
As explained here, the latest firmware 1.1.6 includes the relevant modifications. If your devices still experience similar issues after disconnecting from all the open-source platforms, please contact support team for further investigation. ▷ Solution for ES20M/KS220M Freeze Issue: Sudden Unresponsiveness and Temporary Recovery via Restart
- Copy Link
- Report Inappropriate Content
I think I have solved the issue of the TP Link KS220 dimmer switches continuously disconnecting. I also run a Home Assistant server which seems to be getting blamed for the problems. However, my solution involves the router that the switches connect to. Since you cannot assign a static IP address to the switch and you have to get a DHCP address from your router, it may not be stable. I have an ASUS router which has "IP binding" capability. You can find the IP address of the switch from the Tapo app under Device info. Then go to your router and you should be able to see a list of the devices connected. Find the IP of the switch and select "IP binding". This will ensure that the device (switch) will get the SAME IP address every time. This has solved it for me. Hope it helps.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@Techguy61 The issue I am having is not a communication issue (which might be sorted by a fixed or reserved DHCP IP address). The issue myself and others have been experiencing is that the switch itself crashes and becomes unresponsive. The physical buttons stop working until the swtich is reset by pressing the buttons on the front of the switch. This would have nothing to do with IP communication. 🙁
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 4632
Replies: 46
Voters 0
No one has voted for it yet.
