Missed some drivers, they'll be in the next build.
4 Likes
One precaution. I strongly recommend upgrading to the Community version 6.7.1 from the app prior to migrating. Rationale: Issues from upgrading from very old versions may require some special handling. I need to address as many of these upgrade issues as possible.
Once upgraded to 6.7.1, the migration function is excellent work (tested on my C7 Hub) (thanks @gopher.ny). (Note, there is currently an issue on the C5 hubs that will be corrected in the next release. I tested, and the migration did not work; however, when the error occurred, the migration aborted and no devices were impacted.)
One new command in 6.7.1 is configure. It is intended to be run only when there are issues. Before reporting errors or issues, simply press the configure button on ANY Kasa device. It will then:
- check and update IP addresses for all devices
- run updated for all devices; which will assure all data is correct.
The hope is this will correct any error condition; especially when updating from dated versions.
3 Likes
Yeah, I'm on most current already.
1 Like
I'm still on 6.3.3. Any pitfalls anyone can think of? This version has been rock solid, that's why I never upgraded.
Was on community Kasa Integration 6.7.1 (which was working perfectly) and loaded the built-in Kasa Integration (also listed as 6.7.1). Went to the Migrate Kasa Devices to the Built-In App to migrate my HS220 dimmers and HS200 switches. AFAIK, did not seem to work. I went to the device page and noted that the devices no longer appeared in the list so I went into the built-in app and scanned for my devices, which after rescanning, all appeared and were loaded on the device page.
However, when I tried to see if they re-populated my dashboards, none of the devices appeared on the dashboard so I had to reload all the devices into the Hubitat Dashboard app again. After reconfiguring my lighting dashboard, everything seemed to be back to normal, except for one HS200 non-dimmer switch. I could not get it to load into the dashboard (the icon kept showing as a unknown device even though it appeared as a installed device in the dashboard).
After trying to get it to work from the Hubitat side, I noted that the light on that one HS200 switch is now continuously flashing green (not orange and green, just green). Does anyone know how to resolve this issue and to get the switch to reconnect? Thanks for any help on this (I have very little experience with Kasa as most of my switch/dimmer devices are Tasmota so I appreciate any advice on the Kasa Integration). Except for this one switch, everything seems to be working as before (probably should have left well enough alone, LOL). TIA.
There is no reason to upgrade from a version that is working acceptably. If you do want to convert to the built-in version, then I do recommend updating the community app first.
2 Likes
Open the Kasa App and see if it can control the device. The continual flashing means something is wrong with the switch's installation or the switch itself.
This is normal. Somewhere your devices were uninstalled from the hub and when you rediscovered, they became new devices - so no link to a dashboard. Easy fix:
a. Open the dashboard app for your dashboard.
b. Add in the two "new devices" in the app list.
c. Open the dashboard for edit.
d. Select the buttons without a device (Has ? in tile) and select the new device.
1 Like
Thank you @djgutheinz , for some reason, this one HS200 switch fell off the wifi network either right as I was migrating my Kasa devices to the built-in app, or it had fallen off the wifi network previously and I did not notice until I was checking everything after going through the migration procedure. After a while, it reconnected and now all is good.
As far as the dashboards go, I must have misunderstood how the migration procedure worked as I assumed that the Kasa devices were to “automatically” transfer from the community app to the built-in app when the “Migrate button” was pressed and would thus just repopulate the dashboards automatically as well. This may serve as a heads-up to those that have many Kasa devices they may wish to “transfer” over to the built-in app that are also involved in several rules as well.
Thanks for your help and feedback, and for keeping this integration alive. Really appreciate it!
Mine stayed connected to all the apps they were named in, including a dashboard. Or at least those apps are still listed in the In Use By list
That unfortunately was not my experience (but I probably did not perform the migration properly?). Good to hear it worked for you. That’s how I had expected the migration to work! Again, I probably did something wrong (that’s my wife’s explanation every time something does not work for HER . . . that it was because I did something wrong, lol).
2 Likes
I take that as I should hold off on upgrading to 2.3.3.121, or just hold off on migrating the kasa integration for now. (I have several devices that use the multiplug driver).
1 Like
I just upgraded my hub and migrated devices. All went well and seems to work.
I tried to do a test device lan status just to see if it lists them, but nothing happens with the new built in app. Still works with the user app however.
Uninstalled user app and everything still seems to be working correctly.
PRESS configure on any one device and see if that fixes your issue.
Sure did!
Hi there, hope I'm posting in the right place. Crossing my fingers.
I'm currently running Hubitat 2.3.2.134 and Kasa Integration 5.1.1 (I think; that's what def appVersion() says).
When I upgraded Hubitat to 2.3.2.134 some time ago, I noticed some of the features in the Kasa integration stopped working (changing bulb color, for instance). I could still control the bulbs with my smart speaker so for the time being, I let it go.
Today I decided to clean all this stuff up so I can have a healthy system prior to upgrading to the latest Hubitat code, so I went about deleting all kasa devices and all dashboard elements/routines that referenced them. I then deleted both the bulb and plug driver code with no issue.
However, when I go to delete the "Kasa Integration" in the Apps code, it fails, returning an error that states it is still in use by "Kasa Integration" (i.e. itself). On a whim, I attempted to edit the code, deleting all of it minus the comments but it would not save. So, I took another backup (I took one prior to starting this endeavour) and rebooted. It came back up but I'm still stuck with this integration that I'd like to remove for a number of reasons, chief being getting to newer versions.
Can anyone offer any guidance on next steps, short of factory defaulting the device and starting over, which I really don't want to have to do?
Thank you in advance.
Mike
Since your intent is to remove the devices/app (for now), I suggest:
- Update the Kasa app to the latest version (link at top of this thread).
- Open a Logging Window
- Attempt now to remove the app
- If it works, great. Delete all Kasa Drivers and the Kasa App.
- If it does not work, private message the logs (as TEXT) to me.
If you then want to reinstall, go to the Hubitat built-in version (available in latest HUBITAT version).
Thanks for the info!
Did something happen to the Kasa cloud service today? I just noticed that my logs have been full of these failed token refesh messages repeating every 10 minutes since about 12 hours ago:
info[KasaInt: 6.7.1]: cloudAddDevicesPage
info[KasaInt: 6.7.1]: getTokenFromStart: Result = [[updateFailed: [error_code:-23003, msg:App version is too old]]]
warn[KasaInt: 6.7.1]: getToken: [[updateFailed: [error_code:-23003, msg:App version is too old]]]]
It didn't seem to impact my devices since I don't actually use any cloud features. I just ended up removing my cloud credentials and that stopped the errors.
Can not duplicate on my system. Gets the token first-time.
Problem may be you have not used your Kasa phone App recently. Update that app on your phone, log in on the phone, and verify functionality. Then try getting credentials again.
I recommend doing this for EVERYONE. But that is up to the individual.
