tmorse305

Hi Bob, Increasing the Short Pole time to 20 solved the problem. I made the problem worse by moving the poling level to 'debug' while I was troubleshooting the problem. I'm going to change the short poling interval back to 10, but change the logging level to 'error' which should achieve smaller files. Thanks for your help with this problem!

Thanks Bob, I'll open a ticket. Keep you posted. Update: Benoit has a theory that maybe the log files are too big, so they're taking too long to process. I going to change short poll to 20 and see what happens.

Hi Bob, Here are the first 8 minutes of the log file. I have it filtered on slot 5 activity, but the whole 8 minutes are there. For the first second or 2 it looks like a normal update, then nothing until minute 3:45.301. Then another big pause until 7:33.976 where it is reported as disconnected. PG3x log.xlsx

I looked through the first 7 minutes of the 6/6 PG3x log but did not see any errors. I've included the first 30 seconds or so of the 7/6/26 PG3x log. Vue is PG3x plugin slot 5. Thanks Bob. start of June 6 PG3x.txt

Hi @bpwwer , I'm able to list the files using "sudo ls -lrt /var/polyglot/pg3/ns/000xxxxxxxxx_5/logs" but for some reason I can't "cd" to the directory and actually look at the files. I figured out a workaround, attached are the final entries of June 5. The log seems to end without an error. But at 12:07am on June 6 Vue fails. There is no June 6 log as I haven't restarted the plugin yet. So, I can't see the error which occurs between 6/5/26 23:59 and 6/6/26 00:07 Does re-authentication occur at midnight? end of June 5.txt

Thanks Bob, I appreciate your explanation. I can look at the backed up log files. What is the path to them?

The VUE plugin on my eisy has started to fail every few days. I can't download the log, the system says it can't be found. Pressing restart solves the problem and once it's running the log file is available. The file however only contains log info starting with the restart. Is this an eisy problem or a plugin problem? Thank you for any advice

I found a solution. In the Kasa app they provide a way to disable the KLAP security feature or something equivalent to that. Go to Me > Settings > Third-Party Compatibility and turn it on. I restarted the plugin and it found the 2 plugs with V1.1.1 firmware. Success!

Update: I believe my issue is related to the firmware version of the EP10 plug. The plugs not recognized by the plugin are v1.1.1. All other plugs are v1.0.5. Attached is an ominous message from the release notes, I'm not liking the sound of the 2nd bullet point. @Jimbo.Automates , have you run into this version? I had 2 brand new plugs that I plugged in and it forced me to upgrade to 1.1.1 when I added them to my network. There are some threads on the web that talk about downgrading the plugs, but so far I have not found the bin files. The TP-Link website says they don't support downgrading because of security issues. 2nd Update: python-kasa and KLAP authentication - Smart Home Community talks about the implementation of KLAP 1.(KASA Local Authentication Protocol). Hopefully this is something Jim can work with to allow V1.1.1 to work with the plug in.

Hi @Jimbo.Automates, Any updates on this issue? I have the same problem. Just added 2 plugs and they will not discover. I tried reinstalling the plugin and now I'm stuck at only 18 counting the controller. Thank you.

I just received an email from ecobee acknowledging UDI access. I stopped the plugin days ago when the trouble started. I restarted it but still only the controller node. Tried discover but no luck. When I looked in the log there are no errors, the plugin seems to be able to access ecobee, not sure why the thermostats don't populate.

Give him a chance, it's the weekend, maybe he's away. He was on the forum yesterday, see attached.

Hi @Jimbo.Automates , Same problem here. After reinstalling the plug-in, the plugin acts like it never gets authorized even though ecobee web site indicates success. I just get the controller node. See attached, is the first entry connection status to the thermostats? Thank you

Thanks @sjenkins . I'm not sure what version I upgraded from. I found the problem. I deleted the plugin to start over but when I configured it I used 'Switch' instead of 'switch. All good now, thanks for your help! Thanks for your help!

Hi, I upgraded my Virtual plugin today and I'm now getting 4 error messages. The configuration looks ok, so maybe there are new configuration requirements with V3.1.26? See attached. Thanks for any help!