Jimbo.Automates

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.

Ok, I'll look at it when I return from vacation at the end of the month. May have to delete and re-add but maybe a force update will do it.

That's not surprising, I'll have to force an update for this but not sure if PG interface supports this, but I'll check. Can you ungroup them both, then group and see if they go under the proper one? Also, check the PG3 UI nodes page to see if it shows the proper parent. If there are issues I can try to get a fix in the beta.

Thanks for the debug, this is fixed in the current beta.

I've updated the readme to give this info: https://github.com/jimboca/udi-poly-homekit/blob/beta/README.md Hopefully more clear now.

Correct

The Homekit and Ecobee plugins have been released to beta, but require an update of IoX that is not available yet. But for the adventurous I can provide instructions on how to get it working if you PM me. In the meantime check out the release information GitHubudi-poly-homekit/README.md at 5c1294fcc22b8aab06ae32c8251...Polyglot PG3x Node Server: HomeKit Accessory Protocol (HAP) controller hub with a local WebSocket API for other Node Servers (e.g. `udi-poly-ecobee` in Local mode). - jimboca/udi-poly-homekitGitHubudi-poly-homekit/CONFIG.md at 5c1294fcc22b8aab06ae32c8251...Polyglot PG3x Node Server: HomeKit Accessory Protocol (HAP) controller hub with a local WebSocket API for other Node Servers (e.g. `udi-poly-ecobee` in Local mode). - jimboca/udi-poly-homekithttps://github.com/UniversalDevicesInc-PG3/udi-poly-ecobee/blob/e3bb3624872b167209d912efba1e003c82c22099/README.md GitHubudi-poly-ecobee/CONFIG.md at e3bb3624872b167209d912efba1e...Contribute to UniversalDevicesInc-PG3/udi-poly-ecobee development by creating an account on GitHub.

Those devices should work with the beta release without disabling security, but I can't say for sure. I think I have one and will check firmware.