paulw

Lee, I have never had to use a wait on a scene, has this always been the case? Or, have I just not hit the right mix of commands to create a problem? I have had to use a wait with x10 commands.

Also, your programs will need to have the folder conditions repeated, in addition to any other conditions you may have for them. They will not run just because the folder conditions have been satisfied.

Had a similar problem with a EZFlora running in parallel with a Rainbird controller. For many weeks it was fine. Then I came home one night to have my pump running with no zones active, seems to have been that way for several hours. I was using the EZFlora exclusively but had left the Rainbird there as backup should I want to use it. Turned out the Rainbird had activated the pump. Removed the Rainbird controller and have not had a problem since.

Just a hint when using folders with logic. Just because the conditions for the folder are met, does not mean all the programs will run. The programs within the folder must contain the same condition(s) from the folder in addition to any other required conditions. You will find this in the docs, but easily overlooked. I'm sure more than one of us has fought that fight.

I just use one button, when it is off it is 'at home' when pushed it is 'away'. It has no links to anything. You can use that for testing in your logic, along with any other items like sunset etc. to give the lived in look.

SH will replace any v35's. From my experience if you have any of them, replace them all whether they are causing issues or not.

Sorry for the slow response. The new access points worked fine, but I ended up replacing all my v.35's, even the ones which were not giving any issues. That made the biggest difference. I also ran into the fact that I had a new central ac unit installed which was putting noise on the lines whether running or not. Ended up putting a filter on both sides of the 220 line which took care of that. Currently my system is running fine, sort of hate to say that out loud. Thanks for your concern and input.

I'm with Tim, try to organize by where device is located, but things do go down hill from there.

Been there done that twice! Feel your pain. They replaced 18 of mine due to the issue you are having. However, they replaced them with v35's which drove me nuts. They replaced them all again and life is good! aLf, would suggest you just call customer service, just have your invoice info available. Paul

Thanks for the response. Pointed me away from focusing on the switching code. Problem turned out to be the device you identified, appears to just be a timing issue. All is well, thanks again.

Here is a more detail log, of the same issue, two pushes of the same RL button. The only insteon network activity should be from the push of the button, nothing should be generated from the ISY or elsewhere. I know little on reading the log, any pointers there would be appreciated. I do know that the entry "Thu 06/24/2010 05:56:43 AM : [ 11 C8 44 1] DON 3" is the one that is kicking my unwanted program true. Thu 06/24/2010 05:56:41 AM : [iNST-SRX ] 02 50 11.C8.44 00.00.03 C7 11 00 LTONRR (00) Thu 06/24/2010 05:56:41 AM : [ 11 C8 44 3] DON 0 Thu 06/24/2010 05:56:41 AM : [iNST-SRX ] 02 50 11.C8.44 00.00.03 C7 11 00 LTONRR (00) Thu 06/24/2010 05:56:41 AM : [iNST-SRX ] 02 50 11.C8.44 00.00.03 C7 11 00 LTONRR (00): Process Message: failed Thu 06/24/2010 05:56:41 AM : [iNST-SRX ] 02 50 11.C8.44 12.9F.46 41 11 03 LTONRR (03) Thu 06/24/2010 05:56:42 AM : [ Time] 05:56:44 2(0) Thu 06/24/2010 05:56:42 AM : [ Time] 05:56:44 2(0) Thu 06/24/2010 05:56:42 AM : [iNST-SRX ] 02 50 11.C8.44 00.00.03 C7 11 00 LTONRR (00) Thu 06/24/2010 05:56:42 AM : [iNST-ACK ] 02 62 0A.9D.32 0F 11 BF 06 LTONRR (BF) Thu 06/24/2010 05:56:42 AM : [iNST-ACK ] 02 62 0A.9D.32 0F 11 BF 06 LTONRR (BF): Process ACK: duplicate ignored Thu 06/24/2010 05:56:42 AM : [ 11 C8 44 3] DON 0 Thu 06/24/2010 05:56:42 AM : [iNST-SRX ] 02 50 0A.9D.32 12.9F.46 2B 11 BF LTONRR (BF) Thu 06/24/2010 05:56:43 AM : [ Time] 05:56:45 2(0) Thu 06/24/2010 05:56:43 AM : [iNST-SRX ] 02 50 11.C8.44 12.9F.46 42 11 03 LTONRR (03) Thu 06/24/2010 05:56:43 AM : [iNST-ACK ] 02 62 0A.9D.32 0F 11 BF 06 LTONRR (BF) Thu 06/24/2010 05:56:43 AM : [iNST-ACK ] 02 62 0A.9D.32 0F 11 BF 06 LTONRR (BF): Process ACK: duplicate ignored Thu 06/24/2010 05:56:43 AM : [ 11 C8 44 1] DON 3 Thu 06/24/2010 05:56:43 AM : [iNST-SRX ] 02 50 0A.9D.32 12.9F.46 2B 11 BF LTONRR (BF) Thu 06/24/2010 05:56:43 AM : [ Time] 05:56:46 2(0) Thu 06/24/2010 05:56:43 AM : [iNST-ACK ] 02 62 0A.9D.32 0F 11 BF 06 LTONRR (BF) Thu 06/24/2010 05:56:43 AM : [iNST-ACK ] 02 62 0A.9D.32 0F 11 BF 06 LTONRR (BF): Process ACK: duplicate ignored Thu 06/24/2010 05:56:44 AM : [ Time] 05:56:46 2(0) Thu 06/24/2010 05:56:44 AM : [iNST-SRX ] 02 50 0A.9D.32 12.9F.46 2B 11 BF LTONRR (BF) Thu 06/24/2010 05:56:44 AM : [iNST-SRX ] 02 50 0A.9D.32 12.9F.46 2B 11 BF LTONRR (BF): Process Message: failed Thu 06/24/2010 05:56:46 AM : [ Time] 05:56:49 2(0) Thu 06/24/2010 05:56:48 AM : [ Time] 05:56:51 2(0)

Decided to get at it with a rested brain, for whatever good that is. For starters I deleted the program that was running which should not have been and re-coded it (no change). After that I found the following log entry which would make me suspect a RL issue. It is from two pushes of the same B button. Thu 06/24/2010 05:47:16 AM : [ 11 C8 44 2] DON 0 Thu 06/24/2010 05:47:18 AM : [ 11 C8 44 1] DON 2

In using a RemoteLinc to control an EZFlora (due to tidal issues, we run our system manually), I found the buttons a little too sensitive to wrong entries. So, I am trying to use “ergodic’s†example in the Wiki to program the on buttons for three pushes before starting any zone. I used the same grouping of a control and body program for each push as in the example. In my current testing mode, I am only turning on a light not the EZFlora. When I programmed one button, all seemed well. I copied the code over to three other buttons and changed the labels to make unique code for each switch. All code has been checked and rechecked, and again....... I am seeing some very strange behavior when a pushing RL buttons. For a couple of switches the program state changes (in program summary) are slow taking place for each push. The other two switches are very prompt. There are times (not always) that another button’s body program will go true on one of the pushes of an unrelated button, sometimes the second push, sometimes the third push. Always seems to be the same program going true. The body programs only have “then†code. I even tried disabling the body programs as they are always controlled by a run, no change. Has anyone had problems with copying code? Or, any other ideas.

Sorry, mixed controllers in my response.

I always use a naming convention which identifies where and what. For example: Kit KL-A Yard Lite Location, Kitchen KL-A, KeyLinc button A (In this case there is only 1 KL in the kitchen) What it controls, Yard Lite

Any recommendation on devices that can be used successfully to access the ISY99?

Couple of possible options. If your system can put out an x10 code you can use that, or your system may have some dry contacts usable to communicate to the outside which can be programmed to various alarm conditions. Some systems have the dry contacts as a plug-in option. On my home system I use the x10 as my x10 environment is very solid. (used to own an alarm company)

My problem was trying to recover from a brain ****! Knew there was a way to flag for a run at startup but had never done it and ..... Kept looking for it on the detail tab, went looking again after your response, finally found it.

Is there a way to test for these conditions.

When one understands the rules of a game, one can play the game I'm new enough to ISY that I'm sometimes not sure I understand the rules

kingwr: Your last paragraph was where I was putting my money. See my comment below to obrekc on the ReDimSwitch. A bit complicated but it works and I only have one place where the levels are being set so changes are easy, and the re-dimming always uses the same code. oberkc: The ReDimSwitch is turned true elsewhere whenever there is the need to reset the lights due to something else, like the alarm activation, which has changed their level. My reason for questioning this was to determine if it was my misunderstanding of the processing sequence, or something else. Seems to be either a documentation issue, or a bug. Runs fine with setting the ReDimSwitch false as part of the normal evening sequence, even though it serves no purpose there unless ReDim is active.

Let me start by a recap of what I am doing. I have lights which dim as the night goes on (Five seperate programs each similar to 'Front Final Shut down'. Each program sets the lights to a lower setting, and runs the 'else' from the previous program leaving the current program as the only 'true' program. These lights can be set to a full brightness for example, when the alarm system is armed remotely, thus there is the 'ReDim' folder which has five programs which test for the appropriate 'true' program, and runs the 'then' to reset the lights. The ReDimSwitch is a program with no code to act as a switch. It is set to 'true' whenever there is a need to reset the lights. The reason for the repeat of the folder IF condition in the programs residing in the 'ReDim' folder, was to force each program to be evaluated. Without that the programs in the folder would not run, per the documentation on folders. The whole program "front final shut down" is not being run, just the "then". Was expecting the "Re Dim Final" to go out and run the 'then' of "front final shut down", come back and continue with the next instruction which was turning off the 'ReDimSwitch'. I assumed this, as there is no change in any of the 'IF' conditions. However it appears that the ISY is acting like there has been a change in status and starts 'Re Dim Final' from the top. I was wondering that since the 'then' from 'Front Final Shut Down' was being executed, that it was being considered as a change is state even though it was true to start with. My resolution to this issue was turning off 'ReDimSwitch' in 'front final shut down' which keeps the ReDim folder from being true. At this point I am just trying to understand why it behaved as it did.

Oberkc, Still getting some execution sequences under my belt but, I did not expect the 'Rd Dim Final' IF to be re-evaluated as there was no change in status. Paul [u]Re Dim Folder[/u] If Program 'ReDimSwitch' is True Then Allow the programs in this folder to run. [u]Re Dim Final (program in Re Dim folder)[/u] If Folder 'Re Dim' is True And Program 'Front Final Shut Down' is True Then Run Program 'Front Final Shut Down' (Then Path) { Run Program 'ReDimSwitch' (Else Path)} <- never executed see below Else - No Actions - (To add one, press 'Action') [u]Front Final Shut Down (program)[/u] If Time is 11:18:00PM Then Send X10 'L1/Off (11)' Run Program 'Front 4 Level' (Else Path) Run Program 'ReDimSwitch' (Else Path) <- moved here to stop loop Else - No Actions - (To add one, press 'Action') [u]Front 4 Level (program)[/u] If Time is 10:48:00PM Then Send X10 'L1' Send X10 'C1/Preset Dim (4)' Run Program 'Front 3 Level' (Else Path) Run Program 'ReDimSwitch' (Else Path) Else - No Actions - (To add one, press 'Action')

In the following code, will the IF be re-evaluated even if 'Front 1 Level' is already true? If Folder "Re Dim is True and Program 'Front 1 Level' is True Then Run Program 'Front 1 Level' (Then Path) Else No actions It seemed to create a loop for me, until I changed the condition of the folder in 'Front 1 Level'

I have found the problem, and the problem is me!