are you talking about these?
@djgutheinz
Dave, this is incredible. The kasa plug(115) and the KL135P bulbs work amazingly fast and so far seem very reliable. And at 1/3 the price of LifX
Thank You very much for your work on this, really appreciate it.
Anyone do any analysis of the communication of these Kasa LAN devices? As other wifi devices have a tendency to "phone home to China"
Also my bulb is asking for a firmware update(current 1.0.6), will an update bork local control or affect functionality?
Thanks
PS- yes I'm aware I can block the device from "phoning home" but would choose to not support any company that tries to do these things, some might say "spy"
1 Like
Update as required. The Preference, Bind to Kasa Cloud should eliminate 1) backward communications with Kasa Cloud and 2) non-local (LAN) control via the Kasa Phone App. However, I do not use the unbind feature.
Dave
Nobody pays attention to me, I'm sad
Sorry. Yes, That set wil work with this series. Welcome to the quagmire.
1 Like
These are %50 off right now. Do they work locally with hubitat? Or do they require internet?
https://www.amazon.com/dp/B07FZ6PLJG?smid=ATVPDKIKX0DER&ref_=chk_typ_imgToDp&th=1
They work locally.
1 Like
@djgutheinz
Dave,
Thank you for your wonderful work with the Kasa devices. I now have all of the KP125 and HS300 units in HE and all are working great.
You assistance was essential and I truly appreciate it and I salute you.
1 Like
Has anyone written a rule that turns on/off the HS300 status LEDs. I would like to turn them off during Home+Sleep mode then back on when mode changes to Home+Awake. By specific time would work too. I am not sure how to toggle the attribute LED on and LED off using the simple/basic rule apps. I prefer to avoid RULE ENGINE.
I typically do not use rules. However, the LED is a command (not a preference), so you should be able to key it using rule machine.
Yeah, I include the as custom commands in my rm rules for transitioning to night and day modes, as well as adjusting polling rates
Hi @djgutheinz, I'm using these ( KL130 bulbs) in a new button controller rule (rule machine 5.x) and when setting the color temperature (and not a level), they just turn off instead. Do you have any thoughts on why this may be? I can provide logs and such if you think it may help.
I have been investigating the issue in this thread:
Also of note, this all works correctly in the legacy rule machine. But as we can no longer create new rules there, it would be nice for it to work in the new stuff too.
It is on the fix list for the next release. That will come out one or two weeks after next Hubitat Update (currently in Beta). The issue is that the rule sends a null level, so my original method of handling needs augmentation to handle passing of a null value.
1 Like
Thanks for the pointers. I was able to fix it by adding this to the "def setColorTemperature" section:
if (level == null) { level = device.currentValue("level") }
Not sure if more changes are needed, but at least my new rules are working so far.
I will do it elsewhere, but that is the general idea.
I'm having an issue where my Kasa switches only change state to on or off if they are changed within Hubitat(via the mobile app or in device details). If I turn them on physically they don't change their state within hubitat. If I turn them on physically they don't show any events under the log either. Iv tried rebooting, and removing and adding the kasa integration back into hubitat with no luck.
Any Ideas?
What is your polling set to? I had this same problem when I wanted to use Kasa devices as triggers. The interval is default of 30 minutes.
Edit: if you want to use it as a trigger you can usually safely crank individual devices up to 5 seconds.
Your polling schedule may have somehow been cancelled. You can verify if this is the case by looking at the Schedule section at the bottom of the page for poll or refresh.
To fix, try running Save Preferences. This will restart any scheduled events. If you do this, turn on debug logging and open that log page - looking for warning log entries.
for any manual switch/bulb activation, there will be a delay to the next poll to update the data.
PSA - For anyone that has the Cloud Plugs and Switches instance in HPM that constantly asks you to update, there is an un-match feature in the latest 1.8.6 release. Just tried it and it worked as expected, did not break the normal Kasa instance, does not reappear on match-up, and no longer appears as needing an update.
The new feature is hidden under Package Manager Settings.
1 Like
Activating the recently added login security two-step verification in the Kasa app breaks cloud access to all devices in this integration. Disabling two-step verification restores access.
