I have waited over a year to add this *coming soon* device to our kasa network - to replace a leviton occupancy sensor switch that doesn't have dimming.

This was to control a light over a kitchen island.
 

It does have decent features, like IFTT integration and ambient light detection, and it dims fine - working well with our LED lights.

However - the motion sensor itself is just garbage. At best it has a 45deg field of view *wedge* at 10ft.

This means you have to either walk directly at it - or directly across it to activate. I can easily walk parallel to its view - but 5ft apart - and it will not activate.
We have a clear line of sight to an entry door, 15ft away on a 30 deg angle opposite the sensor - and nothing.
entering the kitchen beside the switch requires passing it by 5 to 10ft for it to detect motion, where entering through the same area but with the island between, it will not activate at all - and you can walk right out the door without a peep.
 

There are times we can manually turn it on before it even detects us at all.

The leviton however, would practically detect you just by thinking about entering the room - from any entrance. It's only flaw is it is not dimmable (or smart)

This Kasa sensor is laughable (and angering) comparatively.
 

Icing on the cake is that we have it triggered to start at 50% brightness.
When it works, and you want it brighter, and raise the percentage with the button, after about 10-15 seconds it automagically dims back down to the set point.

Really?!
This is repeatable multiple times until -  amusingly - LOWERING the brightness holds the new manual setting and then brightening after that will finally hold the new setting.

This issue occurs when using the app as well.

Geolocation works well, turns on though IFTT just fine - but never turns off until it detects movement to then turn off. But if you don't walk in front of it, that doesn't happen. *sigh*

Sure - it has "extras" - but it is a ultimately a motion switch that is dimmable.

One would think Kasa would make it's primary functions the stellar part - because everything else is secondary and it would be "expected / understandable" to be the glitchy part as that can normally be fixed with software updates. Heck - for all i know a piece of plastic film on the inside of the sensor area that someone forgot to take off is the issue.
But for the price? 90% not worth it.

**And although it was programmed correctly (and I checked the sticky post from Kasa on this) the issues remain.

@Carl , @Ryan