Any chance of someone summarizing a very long thread to help with what is going on:
C8, Mix of 35 KASA HS200, 210, 220. All DHCP connecting through PFSense router/FW. I use TPLINK E75 in AP mode for wifi. I just turned off beamforce and fast roam. I have Aqara motions that worked flawlessly firing lights on/off prior to 2.3.5.152. Sometime in the past 2-3 weeks something has gone wonky. I have light switches bouncing on and off the KASA app trying to upgrade and failing. There is a 2-5 second delay on motion lights turning on (most of the time/very random) When I attempt to use Hubitat device off/on, about 20% instant, rest varies on doesn't do it or delayed. Logs don't seem to show anything. I have tried disabling cloud binding (on by default) doesn't seem to help. All light switches were added using KASA integration app using the Scan Lan. All were found and working perfectly prior to ~2 weeks ago.
I would like to move the KASA local only. Just want understand best way to get back to where I was. Based on what I am reading, I should be moving to static IP's and manually adding? Just need some guidance.
When did you last reconfigure you WIFI/ACCESS points. Any correlation to performance issues?
For the Kasa devices, the TP-Link Kasa phone app has gone wonky. Probably some instability by incorporating Matter capability into the cloud / phone app itself and will like clear out in time. I have seen this myself. This may also impact "cloud" control via Hubitat. So if cloud, go to Lan control (you can do this w/o uninstalling and reinstalling).
For Hubitat issues while in LAN control,
The phone app may be causing the device to have issues (I have seen this). Suggest REBOOTING the device via the Hubitat device preferences section if you encounter issues. That often clears the issue up.
quick polling could also be interfering. If the Kasa device receive one UDP command while executing any other command, it appears to throw it into the bit-bucket. Use only if needed.
You can also disconnect the devices for most devices using the Hubitat Kasa device preferences. AFTER you have converted to LAN control, deselect Bind to Kasa Cloud and save preferences. This will take the Kasa cloud out of the picture.
You can reconnect using the Hubitat device's preferences; however, this does not always work on newer devices).
LAN Note: Generally, LAN works great. However, static IP addresses are called for. Also, some older 2.4 GHz wifi devices (all manufacturers) have issues with the network's WPA setting. They do not like the WPA3 settings and sometimes do not like hybrid (auto) WPA2/WPA3. (saw article on this lately).
For anyone who has an existing install of this, be careful if you go to update to 2.3.6 (released a few days ago) via HPM. In my case it was going to create duplicates of the driver I use which would then have to be manually switched on each device. Looks like it wiped out the IP on one device also, and I cannot figure out how to run the discover again to fix it... button seems to be gone from the app , not sure when that change was made.
I was able to get my device working again by manually setting the IP on the device page. Not sure what happened with the discovery process that wiped it out.
Also, I did send the dev a DM with more details on the issue, I did not want to call it all out on here.
Too late me me, I just upgraded a few hours ago
I now have versions 2.3.5 and 2.3.6 of the app and associated drivers (mono bulbs and plugs in my case). How do I tell which version of the app my devices are using? How do I safely remove the duplicates?
@steve007 I would "Unmatch" in HPM from any Kasa installs you have in there.
Then in your Apps Code, look at the last modified date. The one just recently modified should be the new version, and it should be safe to delete it. If somehow it is in use the hub will not let you remove it. You could then edit the app code that remains, and see what version # is listed inside the code.
Then you can also do the same for the drivers. I would just remove the new code and leave everything on 2.3.5-1 for now. If the manifest file gets fixed then HPM will be able to match up and update correctly. Also, the update seems to be mostly just adding some new drivers for Matter devices so if you have no need for those I don't think updating is needed.
For me, possibly because I had forced it to update before, it installed a duplicate of the app. If anything screwy happens though it is very easy to fix. This is what I did:
In Package Manager Settings run Un-Match on Kasa Integration
In App and Driver code, manually remove any duplicates
Check date/time stamp to see what just got installed
It wont let you remove anything in-use so you cant break anything
Run Match-up in HPM and match to the Kasa Integration (not the legacy cloud package)
It should match the app and all drivers you have installed
Run Update (or Repair) in HPM to be sure everything is updated
This is a mystery that has me perplexed so I'm looking to see if any of you have any ideas where to look.
I have 18 Kasa devices six of which are KL125 or KL135 bulbs. Only this one KL135 comes on at 10:30 in the morning. There are no apps shown as controlling this app. No apps have run on either hub per the logs. The bulb is part of a Group called "Front of House Bulbs" and that is what is controlled by some rules. This started when I moved the Kasa integration from the Main hub to my old C-7 (now called Aux). I don't see any automations on Alexa or HomeKit.
Log from Main Hub (bulb is mesh subbed from Aux Hub)
2023-08-19 10:30:47.543 AMinfoPost Light RGB Bulb-2.3.5-1: setSysinfo: [status: [on_off:1, mode:normal, hue:40, saturation:20, color_temp:0, brightness:100]]
Log from Aux Hub (bulb is controlled from this hub which is running native Kasa Integration)
Totally mystifying. I'm about to write a rule to turn off the bulb at 10:31am. It's the post light out front and it's so annoying that it comes on like this.
A lot can cause this. Things to check: (Some you may have already done; however...)
Hubitat Checks
Make sure the bulb is not still installed on the old hub. Your logs indicate this is the case - so you need to check BOTH hubs for apps that use the bulb.
look at the past logs for the device "Front of House Bulbs" to see if any activation occurs (assume you have description text logging turned on).
Look at the bulb's device page. In the device details section, all the Hubitat apps that use the device are listed. Make sure none of them are causing this action.
Kasa Phone App. Look at the Kasa Phone app and assure there are no schedules set for your bulb.
Amazon / Google.
Make sure there are no routines / rules that use the Kasa phone app.
*Also make sure the Kasa skills are not enabled on these platforms.
SmartThings. If you have ever used SmartThings, open it up and make sure that the Kasa devices are NOT installed. See above.
As I said, I don't see any automations on Alexa or HomeKit. There are no schedules on the Kasa iPhone app. I have to say I'm confused though. It's not "installed" on my main hub, it's linked. This is not abnormal right? I mean the reason for Hub Mesh is to be able to use devices on other hubs, right?
on the main hub it's linked. On the Aux hub (where the Kasa Integration is installed) it's installed but not used by anything on that hub.
You are running a very old version of the app. Also, the wrong driver is installed (multi-plug). I would really suggest removing ALL Kasa devices and the app and start over with the current version.
So as a test, I manually turned that bulb on via the Kasa app this morning. It shows up in the logs. That's also expected right? It's polling for changes so it would show up in the logs. dev:24932023-08-21 08:00:48.002 AMinfoPost Light RGB Bulb-2.3.5-1: setSysinfo: [status: [on_off:1, mode:normal, hue:40, saturation:20, color_temp:0, brightness:100]]
, not sure when that change was made.
