Jimbo.Automates

The PG3 Plugin for Kasa TP-Link 3.3.9 is released. See the README and CHANGELOG for all information.

Try 3.3.9, hopefully it works since I don't have this device.

The HS200 is a usually a network issue where it couldn't reach the device. My HS300 is working as expected, that error looks like an incorrect Kasa username/password in the Plugin config page? If it looks correct then please restart the plugin and wait a couple minutes then download log package and PM that to me and reference this post.

I only have a non-dimmable switch for testing, but will try to add dimmable.

Released to production, and added Quickstart at the top of Ecobee and HomeKit Plugins.

PG3 Ecobee Plugin 4.1.2, see OP.

All defaults should work, just remember this is beta, I put in a lot of options for testing which should not be necessary once it is proven.

Yes, the Homekit method does have missing features which is a bummer, but being all local is nice since there is no polling delay. I was really hoping Ecobee would allow us to use the local method, and the cloud method for features missing with local but no luck. UDI is working with Ecobee on getting API access back but no promises yet, and sounds like the API is different so will require some development.

If you upgrade eisy to the latest release from earlier this week you can install Homekit and Ecobee from there beta store. I planned to release them both this weekend but had to out of town and couldn't bring my personal laptop. I'll release to production next weekend.

Not sure what happened, I think I may have one of these in a box, I'll take a look when I have time.

The Polyglot Version 3 Node server for ELK Security Version 3.10.16 is released. See the README and CHANGELOG

Thanks for the log, Please try 3.3.8

3.3.7 released to fix the power strip issues.

The PG3 Plugin for Kasa TP-Link 3.3.7 is released. See the README and CHANGELOG for all information.

Please try 3.3.6, that should stop the crashing. I will test the other issues today.

Kasa Plugin 3.3.6 Released, see new post:

The PG3 Plugin for Kasa TP-Link 3.3.7 is released. See the README and CHANGELOG for all information. This post is locked, please create a new post with any issues or questions. Follow this post to be notified on future releases.

I'll search around and see but initial investigation into what can be controlled with Homekit didn't reveal it. My hope is to do add a Homekit+Cloud backend where we do most functions through Homekit and other functions with cloud. But that'll require Ecobee to release the lock on our API key or let us create a new one. I hoped somebody would have an API oath key I could test with but so far nobody has let me know.

Yes, like I mentioned, I have one and will test when I return from vacation.

I'll check mine when I get back from vacation. Impossible to know what really works without actually having the same model/hardware/firmware version. Which is exactly why I refuse to use Kasa for most important things. But I do like their power strips and led strips.

Yeah, they like updating firmware and breaking the hacked API. Next on my list was to update to the latest.

I'm currently on vacation out of the country. I'll try to take a look if I get bored. I've been running it for many days with no crashes.

That's up to UDI, not me. They must run all their regressions and push a release, I have no idea. Yes, the latest beta allows setting your own api_key, but as of now it is not tested because I'd need an oauth api key registered with a redirect URI matching Polyglot’s callback https://polyglot.isy.io/api/oauth/callback Ideally the plugin could use both backends, get some info from cloud that is not available for local and rely on local for most. But that is a big change because my assumption was one or the other when I started.

It should work, but I have no api_key so not possible for me to test. Not currently, backend can only be cloud, websocket or mqtt modes. Not sure what gives that impression. I suppose that could be valid to access some of the settings that are not available in homekit, but I'd need an api_key and more free time to test.

It's on my list to investigate a hold until I change it mode, but so far it doesn't seem possible with the Homekit method. If we switch API keys it'll work for a while until Ecobee shuts us down again. You can use your own API key by adding it to the configuration. If people want to do that I'll get oauth working properly.