apostolakisl

I doubt it was open. It looks like your system ran a full query which, if not scheduled to do so at 5:46, would indicate that you had a power failure and restart. ISY has an option to perform a system wide query at restart which I assume you have checked. Do you have just one single in/single out IO linc? It looks like it is showing up twice 1 second apart with opposite responses following in the system query queue, which I imagine is not real. Since you appear to have remote access to your system, do a manual query now.

Do you still have access to the scanner? If so, CAD files on the buttons would be nice.

If you're asking me, none. Just questioning why multiple nodes on a fanlinc or io linc might cause this odd issue and if I should consider the same problem on my kpls if and when I have any odd behavior. I don't have any fanlincs or iolincs, though I think I will be buying some fanlincs in the future. I have no need for IO lincs as I have all that stuff hardwired to my elk, which is rock solid reliable. And if I were to go with a non Elk I/O device, it would be my webcontrol boards, which I suppose may even be integrated as nodes at some point in the near future, but even if not, they work great using the REST interface. I have a number of wifi to ethernet adapters which work quite nicely with my webcontrol boards and to date has never had a failed com. I can pretty much put them anywhere and get ~100% response.

So would a kpl have the same potential issue?

Makes sense now. If this can happen with 2 separate nodes on the same device, why can't is happen with 2 nodes on 2 different devices? Or can it?

The reason I say this is that I have had a similar experience with my whole house audio turning on when the kpl button I use to turn it on was actually on, and ISY thought it was off, then the 3am query corrected the ISY register and triggered the program. I prevented that issue from ever happening again by changing to a "if control" program. It was certainly rather startling to have the whole house music turn on at 3am! So, in fact had a com issue, but the com issue wasn't at 3am, it was sometime earlier when the kpl was supposed to have shut off along with the whole house music, but didn't, leaving it out of sync with the ISY register. But to your statement "comm issue may be other than no response". Are you saying that a bad comm can result in a wrong answer (on instead of off) instead of just no answer at all? I'm having a hard time figuring out the mechanism. I have never seen that before, but I don't have any devices with trigger reverse and perhaps that feature can cause a false opposite answer..

I'm not understanding how a bad com is causing his 3 am query to trigger the program. If the com is bad, then the query will get a no response from the device. If the program says "if status is on, then . . " then a no response will not trigger the program. The device must actually be on, but ISY thought it was off, and then the query succeeded, thus changing the status in ISY to on and triggering the program.

It is probably that you have "catch up programs at reboot" checked on your configuration page of ISY. You can change that to the grace period and select a period of time, so it only goes back say 15 minutes, or an hour, or whatever.

Is $iphone a state variable or integer? What is the init value? What is causing the variable to change value (programs/rest commands?). Is the program "run at startup" feature enabled?

It really comes down to the details. If you all have are programs like this If time is from a to b Then set light on Else set light off Then the only thing you need to do is shut down the folder with the programs you are transitioning out of, turn on the folder you transition into, and run the if on those programs. That would be a seamless transition..

No, the first variable triggers the program I wrote. That is all. The folder variable is just the folder variable.

I don't believe that a program containing a "status" uses any more processor sitting idle than any other program. I suppose if the "status" object (ie your thermostat) were constantly changing, then the program would be constantly getting triggered. But I doubt the status of your thermostat changes very often, right. It isn't like it is going on/off/on/off/on/off Here you have 3 programs that get triggered when the status changes from on to off or vice versa. 3 programs getting triggered simultaneous is no big deal.

Because the second variable turns the folder off AFTER you run the programs. Please see my program. It runs the programs, waits 10 seconds for good measure then turns the folder off. Turning the one folder off also simultaneously turns the other folder on, so that the programs in that folder can run.

In theory I agree. But depending on how many programs you are dealing with it, there could be a lot of extra programs to accomplish this. The easiest way I see to do this is to copy the if clause of all the programs that are port of your home/vacation routine, but leave blank then/else sections. Run all those programs when the variable changes. Then based on the true/false status comparison between the home vs vacation programs that act on the same devices, you only trigger the else/then clauses that need to be triggered to put all your devices in the current correct state.

Please see your own post #24 Your program above won't work. Please see the program I wrote.

No and Yes The home folder program is active when the second variable is 0. The first variable is not a condition of the folder. Although indirectly it is because the first variable is what triggers the program I wrote above which sets the second variable. The second variable only triggers the folder change if it is a state variable.

It doesn't disable the folder until after you run the else clause of the programs in the folder.

Good point. Just make a second variable for the folder If $s.Home.Away=0 (I assume the s means it is a state variable) Then Run else for all programs for being on vacation wait 10 seconds set folder variable = 0 Run then or if on all programs for being at home (you'll have to decide if the then or if statement is more appropriate depending on the program details) Else Run else for all programs for being at home wait 10 seconds set folder varialbe = 1 Run then/if on all programs for being on vacation Be aware that it is possible that some more complex programs may need special treatment, especially if they are doing fancy stuff with the else clause. But this sort of idea will work for the vast majority of typical programs where you use the "then" section to turn something on and the "else" section to turn something off. Alternatively, you could use the above program to disable all of the vacation programs and enable the at home programs when at home, and then flip it around the other way while on vaction instead of using folders. Disabling a program does not prevent a "run" command from actually running it. Furthermore, using the disable/enable technique will allow you to organize your programs according to what they do instead of when they do it (vacation vs not on vacation) in the program folder tree. It will cause you to have a long program above however since you will need to list every program out.

So just make a program that says If $s.Home.Away=0 (I assume the s means it is a state variable) Then Run else for all programs for being on vacation wait 10 seconds Run then or if on all programs for being at home (you'll have to decide if the then or if statement is more appropriate depending on the program details) Else Run else for all programs for being at home wait 10 seconds Run then/if on all programs for being on vacation I also assume you have all your vacation and home programs that get activated or deactivated in folders that get activated or deactivated depending on the $s.Home.Away value.

They sell these little 6 inch extension cords just for that situation. http://www.amazon.com/6-Inch-Power-Extension-5-Pack-Outlet/dp/B00DVRUTXW/ref=sr_1_1?ie=UTF8&qid=1433424562&sr=8-1&keywords=6+inch+extension+cord&pebp=1433424640418&perid=0F8C8X6XXT2ZV7204941

Your program is not the reason for the error. It is your connection to your ISY. Try closing your connection to ISY and open a new session.

Two points 1) UD is making their own PLM. Not sure when it will be out. 2) You can fix your old PLM and make it better than factory. There is a thread in here about which capacitors to replace. Many success stories there, me included. PS, PLM's don't need to cost $160. It is literally that they saved a few pennies on cheap *** caps.

You should put a ticket in to UD. They will probably see this thread at some point also and give you further instruction. The only other thing is maybe the PLM is bad. You might try disconnecting it and trying to access ISY. You can log into ISY without a PLM, it just goes into "safe mode" of sorts.

Hopefully you have a recent backup of the ISY. A factory reset followed by a restore doesn't take all that long to do. Or, hopefully not needed, but a replacement unit can be restored.

I'm sure you've done a hard reboot. What led's are on? Try a different power supply. Try taking the memory card out and putting it back in.