I noticed the non-matter Kasa devices are no longer on the Compatibility list. Are they no longer going to be supported within Hubitat?
1 Like
Honestly don't remember that they were ever on there, so it may have just been an unintentional omission. I am not aware of any plans to change the built-in integration, though their future devices are (like some of their new ones already are) likely to be Matter instead.
1 Like
I would not put them there now. Kasa is abandoning the IOT API (used for this integration) for new device type and new HW Versions of some devices. The TP-Link (Tapo) community integration handles these since (these devices use the new protocol).
Below is the current list of the remodel devices) from the TAPO APK file. Again, all of these devices are handled by the community integration above (along with the TAPO devices). I can combine - but it becomes a significant increase in code and drivers.
Dave
type: SMART.KASAHUB
SMART_TAPO_REMODEL_KASA_HUB_KH100 (works with Kasa TRV)
type SMART.KASAPLUG
SMART_TAPO_REMODEL_KASA_PLUG_EP25
SMART_TAPO_REMODEL_KASA_PLUG_KP125M (Matter)
SMART_TAPO_REMODEL_KASA_POWER_STRIP_EP40M
type SMART.KASASWITCH
SMART_TAPO_REMODEL_KASA_SWITCH_HS200
SMART_TAPO_REMODEL_KASA_SWITCH_HS220 (Dimmer)
SMART_TAPO_REMODEL_KASA_SWITCH_KS205 (Matter)
SMART_TAPO_REMODEL_KASA_SWITCH_KS225 (Dimmer, Matter)
SMART_TAPO_REMODEL_KASA_SWITCH_KS240 (Dual Fan Control/Dimmer)
Thanks for the reply gentlemen. What I gather from these comments is that all of the WiFi non Matter Kasa devices I already have installed should continue to work under your integration Dave. And if I add any in the future I should use the new Tapo/Matters version per your list above. Is that accurate?
Matter - use the built-in matter
Kasa (non-matter). If on the list above, try the community (my) TAPO integration first.
Note: depending on when purchased, the HS200 / HS220 may be the old hardware version and use the community version. Confused? Understandable.
Thanks for the "Understandable" comment and the help sir.
I have a HS200-BL. It was working under the Kasa integration but now refuses to show up in Hubitat when I search for everything Kasa. Any clue on that one? One note, I had to use the "BLE bluetooth" smart switch button in the Kasa app to add this one so it is acting differently from all my other 200 switches.
I remain confused and approaching overwhelmed. Thanks for throwing me the rope.
Try my community Tapo Integration (mine). If it works, tell me.
With the immense popularity of these devices, I'm disappointed to see that these aren't officially supported.
1 Like
The change of some Kasa devices to the new API is in the last 8 months or so. The legacy (IOT) devices are supported with the built-in integration. (I was the developer.) I am working on a combined KASA / TAPO integration that will support the legacy IOT API as well as the new. Easy to do; however, hard to do well. Big issue will be transition of existing installations to the new installations w/o breaking the integration.
2 Likes
Tried that. It saw 8 of the 12 devices I have that are working and still did not see the one I'm having trouble adding unfortunately. Good suggestion though!
When running the TP-Link install app, did you first select the below. That is the trigger for the app to look for the new Kasa devices.
So I guess I mucked the app install up somehow. I don't see a Tapo app in the Apps tab. I see two Kasa integration apps. One that says (user) and one does not. Only one of them was there before I attempted the Tapo install. But under the Apps Code tab I see tapo_device_install so I assume the App has been installed but didn't appear in the Apps tab. Where did I go wrong?
You need to install the app by opening the apps tab and selecting Add User App (top-right corner) and then selecting the tapo_device_install app.
Missed that step apparently, but it is there now and working, I think. I also added the plug-switch driver which I assume is the correct one for my non-dimmer switch. It searches but I get this message when I attempt to add a Tapo device. Is that just because it didn't find any?
Device Discovery Complete. Devices available to add 0. Total devices: 0.
Notes: InstalledDevices: Discovery did not end properly. Check LAN and LAN Segments
And is there a way I can send you money for this help Dave. Does github have any equivalent to Patrion or something? I would hope Kasa appreciates you folks that DO THE WORK THAT HUBITAT SHOULD BE DOING on this integration stuff.
My Kasa switches have been randomly failing on Hubitat the last week. I go to the Kasa app and add the switch It asks me if I want it back on the Hubitat or start over (I can't remember the exact wording) and I pick leave it on Hubitat. It continues to install then does an update and works as it should. Not a big deal I was just wondering if this has happened to anyone else?
Are these Matter switches installed using the Hubitat Matter integration?
I do not take donations. I do encourage charitable contributions to the charity of your choice in-lieu of these donations.
3 Likes
No they are a couple years old. I have 2 outlets and 2 bulbs also but with those I just turned off and on the outlet and the lamps they worked after that.
So I should just give up on this switch Dave and replace it with the Tapo version? I really hate it to beat me! LOL
The problem may not be the device but your router instead (I had similar problems). If the switch is still unreachable, do the following:
- Open you router and go to the list of active devices. Is the switch on the list? IP? If not there, then
- Unplug the switch for 30 seconds and then plug it back in. (this clears the switch software but (more important) reconnects the switch to your wifi).
- Reopen your router and see if the swich is there. IP.
- Try to control the switch via the Kasa phone app. If you can, then continue. If not, ouch.
Reinstall the device:
- Open the device in Hubitat and Remove it at the bottom of the device's page.
- Open a log page
- Open the Hubitat (built-In) Kasa integration App.
- Turn on debug logging.
- Switch the device off then on manually
- Start device discovery and see if your device is on the list. If not, private message me the logs @djgutheinz .
- If it is on the list, attempt the installation. If it does not install, again, send me the logs.
