apostolakisl

Try manually doing a "run then" on your first two programs. Does the light turn on, but not turn off? Any time a device turns on by Insteon command, but fails to turn off, there is a good chance that the device itself is a source of power line noise. Try putting a filter between the Insteon switch and the device (low voltage transformer). Of course it is also possible that at the time you specified to turn the light off, that something else in your network is making noise. If it works fine in your "run then" tests but then at your sunset plus time it doesn't, this would point to something else as the source of noise.

The PIR's on my alarm system trigger on clouds and stuff too. I had to disable them because of so many false alarms.

Typically IP cameras have the motion detection built into them. You really don't need to use an Insteon motion detector. Even if you camera doesn't have that as part of the firmware, there are applications that monitor the cameras that will do it. Purchase one program and it can monitor dozens of cameras, rather than purchasing dozens of insteon motion detectors.

I was just looking over the 5.0 firmware stuff. I think this sort of camera control would best be accomplished using the new node server in 5.x. The node could then be implemented into programs giving ISY full control of the camera and having the ability to respond to various states the camera may be in. I don't see any chance that ISY will be able to directly email a snapshot, but it certainly could instruct the camera to do so, assuming the camera has a published API. I would love to see someone write the node server for foscam since I have a bunch of them.

Here is a link to the foscam CGI commands. http://www.ipcamcontrol.net/files/Foscam%20IPCamera%20CGI%20User%20Guide-V1.0.4.pdf I think it includes just about everything and perhaps then some. ISY should be able to execute those commands via the network module. Of course the camera can not send any commands to ISY. Not sure about this, but perhaps the 5.0 firmware would let a camera response cause a variable to be set? Probably not, but 5.0 is allowing a lot of things to set variables so perhaps a network module reply as well.

Typically those features would be built into the camera's firmware. For foscam they are. The only thing is that you would want ISY to turn the feature on and off. With foscam you can send REST commands to the camera which ISY network module should be able to do (I haven't done it but I am pretty sure others have). But as far as emailing the image, ISY can't do that. The foscam units will do that or you can run a dedicated camera monitoring application on your computer and it can do all the motion detection, emailing, etc. I don't now how you could have ISY tell an application running on a computer to turn the features on and off though. The software would need to be controllable via scripts and you would need to set up some software that receives ISY commands and triggers the scripts.

Still, though, it has to be a trigger. If the variable were an integer variable, then it could change, the "if" would in fact be false, but the program would continue to run through the waits and repeats. Once engaged in an "atomic" section, that section will finish no matter what, but breaks points such as wait and repeat will allow trigger events to start the program over and from there it could be true again, or false. If it stays true, the program will start over from scratch after a trigger event. For example, if your if statement said If time is 6am or time is 6:00:10 am Then wait 5 seconds do stuff wait 10 seconds do more stuff The program will start over at 6:00:10 and the "do stuff" part will run twice, but the "do more stuff" part will only happen on the second round. EDIT: To further illustrate If time is 6am or (time is 6:00:10 am and something else that is false) Then wait 5 seconds do stuff wait 10 seconds do more stuff This program will trigger at 6 and at 6:00:10. The second trigger will be false. So, the result will be "do stuff" happens once, "do more stuff" never happens. In short, "if" clauses only evaluate on triggers. Whether the contents are true or false is basically irrelevant without a trigger. A program is true if the last run was a "then" and false if the last run was an "else". The only way a "then" or "else" happens is if there is a trigger. This is true whether it is a "wait", a "repeat", or if it is a program without those items. An "if" sections current state of being "true" or "false" outside of a trigger really isn't relevant to any ISY program. The only relevant state of a program is what it was at the time of the last trigger. A wait or repeat simply open up the possibility that a trigger can occur, it is not a trigger itself and if no trigger exists, then the "if" clause status state is irrelevant as far as the continued execution of the "then/else" containing a "wait/repeat".

When you say "What this means is that if a program's Then clause changes a condition which causes the program's overall condition to become false (or if the program's Else clause changes a condition which causes the program's overall condition to become true), the current atomic statement group will complete, and at that point execution will transfer from the Then clause (or the Elseclause) to the Else clause (or the Then clause)."" The above statement needs some clarification. Just because the conditions in the "if" changed, that does not mean the program will re-eval at a wait/repeat. The change in the "if" must have also been a trigger. So "6am" is no longer true after a wait, but the program will keep going because there was no trigger (times are only triggers at the stated time). The variable on the other hand as I understand is a state variable, so if it changes, the "if" triggers and a wait/repeat will terminate the program and run the "else".

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.