Replies: 1 comment
-
|
@ianloomis TP-Link has, essentially, when updating their older Kasa devices started merging firmware and functionality from their older IOT style devices and moving devices that support it to to their SMART style devices. This causes problems across the board since the command structure and features change when they do this and it becomes difficult to keep separate what is what. Right now the library only has a fixture file for V1 firmware 1.8.11. That gives the structure of the device. That doesn't mean other devices won't work because the model is supported, it just means things may be different and won't know until a new fixture file has been provided. There is a watchdog that affects some Tapo bulbs, known L530 and L900, that causes them to restart every 10 minutes, which is what sounds like is happening here as well. Why they do this and with only certain bulbs is not understood and it is not something that can be changed. Communication with the bulbs is lost for about a minute and should be restored shortly after the reboot. If this functionality is not desired, then yes, you will probably have to get different bulbs that don't phone home. If possible, would you be able to follow the guidelines here to grab fixture files for both your V2 and V3 bulbs so the documentation for the library can be updated accordingly and these features and functionality listed for others in the future: https://python-kasa.readthedocs.io/en/stable/contribute.html#contributing-fixture-files You can attach the fixtures here and I can create a PR to get the library updated. All personal information is redacted from the fixtures so there's no worry about that. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I want to start off by saying this project is amazing and has been very well documented and easy to setup and use so thank you!
While diving head first into the HA world, I have been looking for a good way to re-use a number of TP-LINK KL110's that I have acquired over the years as I've dipped my toes in home automation (using the Kasa app and Google Assistant). I admittedly know alot more now and have a more robust "homelab" and am looking to go the local only route with these bulbs but have ran into some issues.
I followed all the steps and was easily able to get all my bulbs added to an IOT VLAN, blocked internet access, as well as pointed DNS to my Pihole and pointed both the
n-deventry.tplinkcloud.comas well asn-devs.tplinkcloud.comto 0.0.0.0. I noticed they also call out to NTP and Nist for time sync. HA handles all the automations and I haven't had issues with those being out of sync.About half of my fleet of bulbs are on the V2 firmware (1.0.13) and the rest on V3 (1.0.15). All of the V3 bulbs refuse to stay connected and seem to drop out every 10 minutes. I noticed others have had issues with other TP-LINK products on certain firmwares and it's forced "phone home" basically ripping it from the DHCP pool. I didn't see anything regarding these bulbs so wanted to put this out there that I think there is an issue with that particular firmware patch. I think I'm going to scour Amazon now and see if I can get some hands on ones that have not connected to the internet and keep them on either V1 or V2.
Maybe I'm dumb as well, which is why I put it in Q&A. Has anyone else experienced this issue and have a solution?
Beta Was this translation helpful? Give feedback.
All reactions