IndyUDIuser

https://eisy.local/pg3/dashboard This is working for me today. I find the PG3 website/store confusing and not the best designed, but that's just me. I've been adding these tips to a Word document so I can remember what to do the next time I need to look at my one and only plugin in maybe a year or two from now. Ha ha. The "Launch Polyglot V3" in Admin Console takes me to this link. https://192.168.0.76:3000/ Sometimes it works, sometimes it doesn't. I'll try to avoid it from now on and just browse to the PG3 store directly in my browser using eisy.local as you suggested.

I was able to get into PG3 web pages today. I spent an hour poking around in the screens and finally (I think) got your plug-in updated so it now tells me I am using the Standard edition instead of the free edition. I am glad this is the only plug-in I use. I find the PG3 Store user interface difficult to use and poorly designed. But that's just me (40 years as a software engineer, 25 years as Insteon/UDI user).

That worked fine. Thank you!

Thanks for the advice. I cannot even get into the PG3 application today. Keep getting an "unauthorized" error. What fun.

When I am in Admin Console (current version) and go to Plugins > Launch Polyglot V3 (PG3) I get: I have tried rebooting the EISY from Admin Console, and even restarting EISY by pulling the power cord for 1 minute. Neither helped. I am using Firefox browser from my laptop on the same LAN. How do I resolve this so I can look at my plugins? Thanks in advance. I am using the same login credentials I use to get into Admin Console.

I happened to be in the Plugins panel yesterday and saw there was an update available for the "Notifications(1)" plug-in - the only one I use. So I went ahead and purchased it. Now I have four lines in my plugins list for that one plugin. I tried to activate the one I had just purchased, but I'm not sure I know what I'm doing LOL. Anyways, after the update I got a few PG3 SMS notifications on my phone saying they were from the FREE version. @Jimbo.Automates can you help me out to clean this up? Thanks.

Thanks for the tip. I've never used SSH to get into my ISY. Can you give me a quick instruction how? "CPU Usage" would be a nice feature to put in Admin Console or the new UI version of the console (I forget what it's called).

I have a scene called "Bedroom lights" whose members consist of a wall switch and a lamp module, both in my main bedroom. I have Alexa linked to my EISY so I can say "Turn on bedroom lights", and it turns them on. This has worked reliably for years. Then a couple days ago I noticed with I said "Turn on bedroom lights", the Echo would chime but nothing would happen. Minutes later my wife told me the lights in the other two spare bedrooms had come on for no reason. I was able to reproduce the problem. It happened every time I said "Turn on bedroom lights". So I went in to look at my Alexa setup in IoX (which I haven't touched in over a year) and found that there were at least a half-dozen devices in the "spoken words" list that I had no memory of adding -- including the other two spare bedrooms, and a few devices I would never want Alexa to turn on/off. I deleted all the extra nodes from the list (including bedrooms 2 and 3) and now "turn on bedroom lights" is working properly again. My questions are: 1) How did all these extra devices get added to the list of "spokens"? Is there some automatic or hidden process that tries to "discover" more devices to add, even if I don't need them? Did Amazon do this, or Universal Devices? I haven't messed with the Alexa integration with my EISY in a long time, so maybe there's something occurring that I'm not aware of or have forgotten. 2) Why did Alexa start activating the two switches instead of the "bedroom lights" scene that it's supposed to activate? It's almost as if Alexa heard "bedroom lights" and tried to find any device that had "bedroom" in the spoken. Yet the SCENE called "bedroom lights" (an EXACT MATCH) did NOT get turned on. Which is weird. 3) In recent past I was doing some cleanup work in Admin Console and renamed all of my light switches slightly. But I did not change the scene name "Bedroom lights". And I did not think about the spokens. Did that confuse things for Alexa and cause it to turn on the wrong devices? I'm going to have to be careful to check my spokens list occasionally - a forgotten feature. Now my wife can stop asking why the spare bedroom lights keep coming on. P.S. I have Alexa+ disabled on my Amazon account.

I'm curious ... how do you tell if the EISY is in a loop? Is there a way to see how much CPU usage it is consuming (like you would with Windows for instance)? I don't believe I've coded a looping situation (yet), so I'm wondering how I would know if I did. Thanks.

I would add a third: Those who cannot remember what data they had or where it is. But that falls under your #2 I guess. It sucks getting old.

I don't want to muddy the waters, but based on a recent personal experience, is there a chance your ISY rebooted at about the time these odd notifications started appearing? I have a program that checks for 5 exact times and turns on a device, waits a few seconds, and then turns it off. I found out by accident that if I reboot my EISY, it turns on and then off the device, even though none of those exact times matched the clock time. The "Catch up schedules are restart" setting apparently was the cause. IoX apparently uses some odd logic to determine what to "catch up" on. Perhaps it was trying to "catch up" your programs and sending unwarranted notifications. The setting is under Configuration tab > System tab. I unchecked the checkbox and rebooted my EISY and this time the program did not run unexpectedly. I'm leaving it off. Just a wild guess. Also check the INIT TO settings on your variables to make sure they are what you expect after a power failure.

I would think, since my program says to do things at only specific, EXACT times, when the IoX restarts it should look at the clock time and say "nope, doesn't match any of those SPECIFIC times, so this program is to be ignored". DO NOT run the IF or the ELSE. I don't care if ISY was off for hours due to a power outage or something. If this program was controlling something potentially critical (or dangerous?), turning the device on at the wrong time is not good. But then I know not to trust EISY for such tasks. I am turning off the Catch Up setting.

Apparently it does. I unchecked the box, clicked the Save button below it, and rebooted EISY. The program did not run this time. Then, to double-check, I checked the box and rebooted again. This time the program did run. I checked the log and it shows a Status On entry for the device seven seconds after it had finished polling all my devices, and then a Status Off entry 13 seconds later (as per the delay in the program). So the "catch up" feature is questionable to me.

Yes I do. If this is what is causing this, this doesn't make sense. The program specifies five exact times, so none of them is true at 11:35AM when the system booted up. There was nothing to "catch up" to. But then I don't think like ISY thinks. I'll uncheck it and see if that causes any adverse results. While looking at the Configuration screen I note that there is a "Reboot" button as well as a "Restart IoX". What's the difference? I've always used the Reboot button when I need to restart EISY.

I have the following program to turn a small device on 5 times a day. The program is NOT set to run at startup. Yet when I rebooted my EISY at 11:35AM, the device turned on and off. Why isn't the Run At Startup being honored? Also, in the Summary page, that column shows either ON or a dash. I assume the dash means OFF, so why didn't the developer just use OFF to make this more clear? Thanks. BSMT Deodorizer ON-OFF - [ID 002B][Parent 0058] If ( Time is 7:00:00AM Or Time is 10:00:00AM Or Time is 1:00:00PM Or Time is 4:00:00PM Or Time is 7:00:00PM ) And $sOnVacation is 0 Then Set 'Basement / BSMT Deodorizer / BSMT Sprayer Relay' On Wait 15 seconds Set 'Basement / BSMT Deodorizer / BSMT Sprayer Relay' Off Else - No Actions - (To add one, press 'Action') Turn the deodorizer on once at the top of the hour, several times a day.