This is the best option for now.
It does not matter except in confusion of which application to use for installation. (thank you TP-Link for this confusion.)
Dave
ive had 3 or 4 fail out of about 30 between houeses.. when they do fail i get constant clicking like the solenoid has died. you?
Never had one physically fail. It could be a HW failure or a software insanity. If you don't want to buy a new one, try a hard reset first. It will reset to the factory firmware settings. Resets the device to factory default and will have to re-install in the phone app. (Just had this happen to a KS240 owner. Could not connect to hubitat app but corrected by the factory reset.)
ya at any given time at least 2/3 of mine are in remote location.. thats why i have them. so a reset and reinstall into the app is not possible. for this reason when one fails it goes in the circular bin even if a reset is possible,
actually counted. 54 switches in the app.
Ya. Constant rapid clicking. I've had three H200's and now one HS210 fail in the same way over the past 4ish years in my house. I've got about 20ish Kasa switches/dimmers/3ways throughout the house. It was less of a pain replacing them and fixing rules when they were all on the old Kasa integration. Now I have to start using Tapo as well.
Thanks so much for the clarification and all your work on the integrations.
Is there any difference in Hubitat functionality with Kasa vs Tapo devices? Does the Tapo integration still rely on periodic polling to update device status in Hubitat?
I'm debating if it's "cleaner" to just migrate everything over to the tapo integration. Bunch of work but probably easier maintenance in the future?
They are both the same relative to polling and both work great. If the instant status is critical to you, consider matter devices. But check if the Hubitat instantiation will support the functions you need from the device. I use the Tapo / Kasa Matter devices since they link to the Tapo phone app and provide a backup in-case my hub is down. (Has not happened yet; however....)
So I have 2 P316M associated to my C8 Pro. One of them is working fine and Hubitat can turn on and off individual outlets on that strip without issue. The other one is having problems and gives a credential error:
P316M(US)-2.4.2a: [method:parseKlapHandshake, respStatus:ERROR: localAuthHash != serverHash, action:Check credentials and try again ]
I can control both power strips through the TAPO app without issue. I have removed the problem device and re-added it so it obviously sees it. However it still gives the same credential error. The credentials are not part of the device but the parent TAPO app that both power strips use so I am at a bit of a loss.
Suggestions?
I would remove from the Tapo app then re-install. I have never seen this - but it is possible.
Recommended steps:
- Remove the error device from Hubitat.
- Remove from the Tapo App.
- Unplug the device for at least 1 minute.
- Reinstall into the Tapo App.
- Reinstall into the Hubitat integratin
Rationale: The device holds it's credentials internally (not in the cloud). The credentials may be able to get out of sync between the individual devices. These steps will assure any device-internal data is fixed.
You do not have to uni
It is not the integration if the other plug is being controlled. All code is the same. Just in case, what are the firmware versions of your two units (looking for difference).
Are you sharing your tapo devices with someone else?
PS the device is Matter. You could connect it to the hub using Matter installation.
They are both at 1.05
I am not sharing with anybody else. Both are under the same login and it’s only the TAPO app on my phone and iPad as well as Hubitat.
I could go Matter but I thought I should if it’s something obvious first before just giving up on this approach.
Go to Matter. Below are some notes:
Tapo P316M is a Tapo 6-outlet power strip. Instructions:
- Get setup code from the Tapo phone app:
- Select the Matter Setup Code. There will be an Expires in xxmin, yy sec. If so, then you use this code to install into Hubitat
- Install into the Hubitat Matter infrastructure
- My device came up as a Generic Matter Outlet - but this does not allow control of the inividual outlets. To add the children, (Jan 2026 result)
- Device Info Page - Type. Select "Generic Matter Multi-Endpoint Switch then SAVE
- Commands - Configure, then refresh the browser page. You now have children.
- My device came up as a Generic Matter Outlet - but this does not allow control of the inividual outlets. To add the children, (Jan 2026 result)
Done - Thanks!
Argh. I'm all mixed up. I installed the Kasa community integration several years ago when I first got the hub and used it with a 4 pack of HS103 plugs. Later I added an RGB strip light. Somewhere along the way I think I switched from the community to the built-in Kasa integration but I don't think my current devices (which work fine) are "added" properly. Today I added a 5th HS103 to the Kasa app from my phone and when I go to the Kasa integration and scan, it doesn't find the new plug. I tried adding it as a virtual, then changing the driver and setting the IP, but that doesn't seem to work. To maybe add another hiccup, I have eero mesh network and it uses a /22 instead of a /24 so I don't know if that's causing an issue. The new plug is .191 so it should be within the search range "hostRange: [1, 254]]". I'm worried I'm going to have to delete everything and start over 
.
Both integrations "see" 3 plugs (I don't have one plugged in right now) and the light strip, but neither of them see them as "installed".
A lot going on in your post.
- Only the community integration is currently supported.
- /22 and /24 may matter. What is the IP address of your router? The plug you are adding? For /24, the last two fields matter. (Hub may be on different segment).
- Curious about what you mean by the last statement????? The built-in app doesn't provide a list of installed apps (at least the current version).
Best fix:
- In the Kasa App settings, select "Third-Party Services" then "Third-Party Compatibility". This will allow newer Kasa firmware updates to work using Hubitat.
- This is applicable to new HW versions of various plugs (like your new HS103).
- Uninstall the Community version of the Kasa Integration and NEVER open it again.
- Check your hub IP address vs the Tapo Devices. If the Hub segment (i.e., 192.168.5) is different from any of your devices, you will need to select "Modify LAN Configuration".
- Open the built-in Hubitat Integration
- Enter the segments used by your Hub and devices (i.e., "192.168.5, 192.168.6"). This will cause the app to scan the selected segments.
- Run the Scan and install the new HS103 (if present)
- Test your Kasa devices.
- If any of the devices do not work, go to the device's preference page and use the "Manual IP Update" preference.
Anxious to hear back.
Assume you mean built-in here?
FWIW, my "before I did anything new" state was having the built-in integration installed and the 4 plugs+strip devices present and working.
ok...
- community integration is not present
- the router is .1, the new plug is on a fixed reservation of .191, the hub is .59 so everything in play should be accessible via the assumed /24 range.
- What I meant is...using the built-in Kasa integration I choose to "Scan LAN for Kasa devices" and what it shows me at the end is a list of all of my "old" Kasa devices:
For the fixes:
- Already had the 3rd party support enabled
- done and done
- As above, all pieces of the current puzzle are on the same (x.x.4.1-255) segment, ran scan, does not find the new plug. (I added .5 and .6 on a whim...no change). I also did as suggested and "exercised" the plug via Kasa app then tried again, no change.
- Existing Kasa devices I added way back when (literally these guys have single digit device IDs) all working fine.
I tested on another device uninstalling the device from the Kasa Phone App and then reinstalling. It was then discovered. Something about the reset kicks the device to a dual mode.
Dave
Hot damn!
Well thank you very much.
today, i updated the firmware of a few plugs, and now they are all non-responsive in habitat.
they are still functioning in Kasa app.
they are: EP10, hardware 1.0, software 1.1.1
HS103, hardware 5.0, software 1.1.3
KP115, hardware 1.0, software 1.1.1
their IP addresses are still the same as before, but in the built-in kasa app, it can't discover them any more, and can't control them either.