Jimbo.Automates

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.

Kasa TP-Link Beta 3.3.4 released see https://github.com/UniversalDevicesInc-PG3/udi-poly-kasa/blob/beta/CHANGELOG.md Please give it a try and if I don't hear about any issues I will release to production soon. Then I'll start work on adding support for more devices.

That's an Ecobee limitation. We are only allowed to poll their servers every three minutes. The reduced polling will not change this, it only changed some other cases were that polling could be done more often. But, after making major code changes and sending a proposal to Ecobee asking them to give us back access, they haven't even respond to emails. There are unconfirmed rumors that they would implement Matter support, but they won't answer questions about that either. So, I'm actually working on a better solution. Developing a HomeKit plugin, which is done but undergoing testing and hardening for a beta release hopefully this weekend. This will allow you to connect the Ecobee to the HomeKit plugin. But if you rely on using HomeKit currently for Ecobee control, you can't have both... Then major changes to the Ecobee plugin to talk to the HomeKit plugin to get Ecobee data. The nice part is changes are reflected back to IoX very quickly. But this has been a huge development effort so far and I haven't even started on the Ecobee side yet, so will have to really think about the price, it won't be a free upgrade.

We will be working on making changes to the plugin to reduce polling to Ecobee servers in hopes that @Michel Kohanim can negotiate a deal with them. We can temporarily switch to another API key if anyone wants to give it out once we reduce polling.

It's not a cost specifically for forecasts, it's a huge cost for polling in general. Removing forecasts will just help reduce the polling. There are options to greatly reduce polling, but at this point it looks like they will not turn us back on unless UDI pays them a large sum. There is another option to use a HomeKit emulator but that is a major effort. Ecobee added Apple Homekit support, but are ignoring thread/matter support so far even though their newer thermostats have the radios which could support it. I'll be looking into using Matter enabled Nest 4th Gen ($99) or Meross thermostat ($60) per suggestion from @Michel Kohanim

We are working with Ecobee to find a solution and not be forced to pay a large fee. Well have to reduce the polling frequency greatly, and probably get rid of forecasts. Hopefully we can get Ecobee to turn our access back on while we investigate.

I've been working with Michele and we discovered Ecobee has shut us down. No path forward at this point. Will continue to investigate.

It has a persistent connection to the elk which reads and processes all the changes. IF you experience that issue then download log package and PM that to me the before midnight on the day it happens.

I get no response from their support, so I can not give a timeframe, the error is on their side.

Why are the left pointing arrows a problem? I gave you a workaround for the PyISY issue so it is solved for you. The PyISY version used in PG3 is old, and requires a lot of work to upgrade since it is called by PG3 and not my plugin. If I charged a price for the plugin that actually paid for the time I spent creating it and supporting it then it would be very expensive. It's a side job I do to help the community.

The ELK Plugin does not poll the Elk, it connects to the Elk the exact same way the old ISY Elk module did, so it can't make the Elk to busy to do it's job. From your description this does not involve the Eisy and/or Elk Plugin at all, and reviewing your logs there is nothing of interest. I am the developer so you can PM me at anytime, but usually better to post on the forum to allow other users to answer if possible. If you go to the PG3x plugin page for the Elk Plugin and change logging mode to Debug+Modules it will log more information, then if you experience the issue again note the time and download log package before midnight the same day and send that to me with the time. I'll review the log and see if it happened to be going crazy.

It's not a problem, it's just the icons chosen. Also, please stop YELLING.

So that did fix it. It was a bug in a shared library PyISY that we use. Your welcome.

For some reason it won't let me edit my post above. After the last "Save", also hit "Save" at the bottom of the window. There are NO error logs, the errors were in the debug.log.