Jimbo.Automates

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

You can't re-add the node manually. If the configuration is correct then restarting the plugin should add back the node. Sent from my Pixel 8 Pro using Tapatalk

Did you follow all the instructions in the plugin configuration page? https://github.com/UniversalDevicesInc-PG3/udi-poly-ELK/blob/master/configdoc.md ELKID This works by right-clicking on a node in the ISY and adding a note with "ELKID=n" where n is a unique integer Then click on the "export" link provided below which will appear once your ELK is synced Note: Depending on how many devices on your IoX it may take a while to process and generate the export file. Once the file is downloaded, open ElkRP connect to your System, then right click on Automation -> Lighting and import the file.

Nothing happening in the logs, Benoit has stated it's not a plugin issue. Sent from my Pixel 8 Pro using Tapatalk

As I said in my email to you: I have one nagging issue with the beta that I can't resolve with one of my plugs, but if it's working for you then I can promote beta to production. Personally I do not use Kasa plugs or switches for anything that needs to be controlled by IoX, only light strips and power strips. But in the end I would hope that connecting the new Kasa devices to IoX via Matter will be the best solution. But I've not dived into the Matter world at all yet..

Yes I responded before posting my info. Please set to warning and see if you still get the error Sent from my Pixel 8 Pro using Tapatalk

Anyone seeing the "Error processing message from client ... due to high volume", Please check the Kasa plugin log mode. Let me know what your current setting is, and change it to Warning and see if it shows up again.

Okay, I'm traveling today but will try to review this week. Sent from my Pixel 8 Pro using Tapatalk