Jimbo.Automates

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.

I don't think this will fix it, but please try this: Open Admin Console with IoX Launcher and login Click "Configuration" Tab Click "Netowrking" Tab Click "Network Resources" Tab Click "Add" button at bottom Hit Enter to accept Name as Name.1 Click the "- Select to Edit Content -" in the URL Column In the new window enter "somehost" for the Host Click "Save" So you'll have this Then restart the plugin for the PG3x UI, and if the errors still show go to the Log for the ELK Plugin and "Download Log Package" and PM that to me.

Looks like you found the page, that's the PG3X page showing the error, and I see you attached the log, I'll try to review this today.

The Node Server errors should show up on the PG3X page for the plugin. I don't see a screenshot of the PG3x ELK Plugin page, only a screenshot of the Admin Console. If you restart the plugin do the errors get cleared?

Yes, this is an issue with anyone trying to add a new one. I've emailed and created a ticket with the vendor with no response. I'm setting up a new eisy in my new home and trying to bring back to life an older wireless tags hub but have not been successful yet.

The red exclamations are because as shown on your screen "Node Server Errors" = 1. The debug.log doesn't show the error since it rolls over each night. Is there an error shown on the PG3x Page for this plugin?

This issue has been reported to wireless tags by myself and another developer and they claim there's no issue. I will have to deauthorize mine to test and risk not being able to authorize again... Support from that company has gone from bad to worse. Sent from my Pixel 8 Pro using Tapatalk

I build heartbeat into all my plugins which is used to confirm the plugin is still functional and connected to polyglot and polyglot connection to IoX is good. That is different from API authorization which can fail but heartbeat is still good. Sent from my Pixel 8 Pro using Tapatalk

Yes, ecobee knows if the API authorization succeeded. Sent from my Pixel 8 Pro using Tapatalk

AC is admin console,.it is subscribing to the eisy to capture real time device changes happening on the eisy. Sent from my Pixel 8 Pro using Tapatalk

The subscription is for the live updates,. without it you won't see changes in the AC as they happen. Sent from my Pixel 8 Pro using Tapatalk

That has nothing to do with the elk plugin. It's the UI trying to connect to your eisy. Sent from my Pixel 8 Pro using Tapatalk

If you manually deleted a node, restarting the plugin should add the node back. Sent from my Pixel 8 Pro using Tapatalk

Yes, you should never use that menu to modify a plugin or it's nodes. The plugin handles it's own nodes. Sent from my Pixel 8 Pro using Tapatalk

On startup the plugin must poll all to set initial values. I'll have to review the code but it should wait the defined time to poll again, but it might try more frequently after a failure. But really you shouldn't need to restart IoX every day. Sent from my Pixel 8 Pro using Tapatalk