apostolakisl

I think LeeG was getting at this, but you probably set the wrong ramp rate. Make sure you are bringing up the scene by tapping the scene on the left hand side of the screen in the "tree". It will list all the ramp rates for each device in the scene at the bottom of the screen. Make sure the load device has the ramp rate you want. Typically I check the "apply to all" box as rarely do I want different devices in a scene to respond differently.

First try at trying to screw up the "ACK" situation. I ran the "if off and switched off" program from one of my switches about 25 times without a single error. I re-enabled all of the programs that work that way so we shall see. At this point, it is really the "wife test" as she will certainly inform me when/if it screws up.

Installed like clockwork. I see no problems. I did not experience anything out of the usual on the first query time nor do I have any problems with the program summary page display. Look forward to seeing if it those ACK issues stop giving me headaches.

Yes, I wrote those programs. http://www.universal-devices.com/mwiki/ ... _Variables And yes, I use them for situations just like this where things recur on a schedule. I have it set up so you can have things recur on virtually any date type situation from every so many days, weeks, months, years, and so on. So, if you have a recurring situation, it might be worth the effort. But a one-off situation wouldn't make sense. You can also use ISY's date function to activate/de-activate the program on certain dates just like oberkc did above, but if you don't plan on ever using it again after the end date, you probably would want to just delete it. I do use that date function above to set all the kids school vacation days at the beginning of the year. But I have to say, it is kind of a PITA putting all those lines of code in for each vacation and I may just foget about next year and simply manually enable/disable it.

If this is just a one-off situation, I highly suggest you simply write the program, leave it disabled, enable on the desired date, then delete when you are done with it. Or you can disable it until you decide you want it again.

I assume you made a backup of your ISY prior to starting any of this. You could always restore that backup to ISY and put the old PLM back in. You would still need to restore any of your devices that did get successfully updated to the new PLM.

I have been having problems with this program type for several months now, perhaps 6. So, if a change occurred around 2.8.16, that could have something to do with it.

The lack of ACK's back to the device has got to be something more than simple lack of comm. Reasons to say this: 1) The comm going the other direction never has an issue. 2) ISY initiated events always get through (ie programs run on ISY and execute events at the switch without fail.) 3) Tests of my comm (Scene tests) are now 100% successful. I have to wonder if this ACK is actually being sent in the first place, or if it is being formated improperly so the switch doesn't recognize it. I will also note that the problem is now consistent between 2 PLM's. I will also note that I didn't always have this problem. The biggest change to my system since this problem began is ISY firmware.

I got the filter and installed it on the breaker. I ran scene tests by the boat load. 100% success. The program still misbehaves. In fact the program design: if status off and switched off then turn on 25% misbehaves in general. When one of the lights associated with one of these programs is on and I turn it off, it will still run and go back on to 25%. It does it randomly about 50% of the time. I am thinking that this entire program structure is going to need to be abandoned.

Hopefully the filter I ordered last weekend will arrive today. I ran a number of scene tests with that circuit off and they went perfect, then they failed with it on. It was reproducable about 5 times each way during a 15 minute span, so I feel like filtering the circuit should help. Also, after I moved the PLM off of that branch panel things worked better as well.

OK, but I don't get it. How can the message go one direction so successfully and go the other direction so poorly. But still, even if it thought there were three button presses, none of them should have been a button that ran that program.

I am not at all very good with these Insteon communication logs, but. It would appear to me that this particular switch is needing 2 hops to get the messages back and forth. I don't mean to be a whiner, but I would think that we should accept that Insteon may need "hops" to get the message around, it was after all built around the premise that the perfect comm was no longer a necessity (as opposed to x10). If we are going to forgo the "hops" then we are giving up a big feature of Insteon. Having said that, I appreciate that you guys think you have a solution to this problem and are working on a fix. Thanks.

I did it again. Wed 12/21/2011 8:01:54 PM : [iNST-SRX ] 02 50 05.15.36 19.75.34 41 13 04 LTOFFRR(04) Wed 12/21/2011 8:01:54 PM : [standard-Cleanup][05.15.36-->ISY/PLM Group=4] Ma x Hops=1, Hops Le ft=0 Wed 12/21/2011 8:01:54 PM : [ 5 15 36 1] DOF 4 Wed 12/21/2011 8:01:54 PM : [iNST-SRX ] 02 50 05.15.36 19.75.34 42 13 04 LTOFFRR(04) Wed 12/21/2011 8:01:54 PM : [standard-Cleanup][05.15.36-->ISY/PLM Group=4] Ma x Hops=2, Hops Le ft=0 Wed 12/21/2011 8:01:55 PM : [iNST-ACK ] 02 62 12.29.64 0F 11 3F 06 LTONRR (3F) Wed 12/21/2011 8:01:55 PM : [iNST-SRX ] 02 50 12.29.64 19.75.34 27 11 3F LTONRR (3F) Wed 12/21/2011 8:01:55 PM : [standard-Direct Ack][12.29.64-->ISY/PLM Group=0] Max Hops=3, H ops Left=1 Wed 12/21/2011 8:01:55 PM : [ 12 29 64 1] ST 63 Wed 12/21/2011 8:01:55 PM : [iNST-ACK ] 02 62 05.15.36 0F 11 3F 06 LTONRR (3F) Wed 12/21/2011 8:01:55 PM : [iNST-SRX ] 02 50 05.15.36 19.75.34 27 11 3F LTONRR (3F) Wed 12/21/2011 8:01:55 PM : [standard-Direct Ack][05.15.36-->ISY/PLM Group=0] Max Hops=3, H ops Left=1 Wed 12/21/2011 8:01:55 PM : [ 5 15 36 1] ST 63 Above is impropper Below is propper Wed 12/21/2011 8:02:31 PM : [iNST-SRX ] 02 50 05.15.36 00.00.04 C7 13 00 LTOFFRR(00) Wed 12/21/2011 8:02:31 PM : [standard-Group][05.15.36-->Group=4] Max Hops=3, H ops Left=1 Wed 12/21/2011 8:02:31 PM : [ 5 15 36 4] DOF 0 Wed 12/21/2011 8:02:31 PM : [ 5 15 36 4] ST 0 Wed 12/21/2011 8:02:31 PM : [iNST-SRX ] 02 50 05.15.36 19.75.34 41 13 04 LTOFFRR(04) Wed 12/21/2011 8:02:31 PM : [standard-Cleanup][05.15.36-->ISY/PLM Group=4] M ax Hops=1, Hops Left=0

Device communication events was selected.

You are looking at a log that contains both a correct and incorrect execution. Above is the log of me doing it twice. The first time I pushed button b, the program did not run (which is correct), the second time the programs did run (which is wrong).

I went ahead and disabled all programs on the ISY to elliminate as many variables as possible and to clean up the log from extranous activity. I only lef these two programs active. If Status 'Master Bedroom / Master-Cans over Bed L' is Off And ( Control 'Master Bedroom / Master-Cans over Bed L' is switched Off Or Control 'Master Bedroom / Master-Keypad' is switched Off ) Then $itest += 1 Else - No Actions - (To add one, press 'Action') If Status 'Master Bedroom / Master-Cans over Bed L' is Off And ( Control 'Master Bedroom / Master-Cans over Bed L' is switched Off Or Control 'Master Bedroom / Master-Keypad' is switched Off ) Then Set 'Master Bedroom / Master-Cans over Bed L' 25% Set 'Master Bedroom / Master-Keypad' 25% Else - No Actions - (To add one, press 'Action') I then turned button B off. The first time, it just shut off and nothing else happened. I turned it back on and turned it off again. This time both programs falsely ran. 5.15.36 is the KPL, 12.29.64 is the 2476D switch that carries the load. 0Wed 12/21/2011 5:40:30 PM : [ 5 15 36 4] DON 0 1Wed 12/21/2011 5:40:30 PM : [ 5 15 36 4] ST 255 2Wed 12/21/2011 5:40:31 PM : [ 5 15 36 1] DON 4 3Wed 12/21/2011 5:40:31 PM : [ 5 15 36 1] ST 127 4Wed 12/21/2011 5:40:31 PM : [ 12 29 64 1] ST 132 5Wed 12/21/2011 5:40:33 PM : [ 5 15 36 4] DOF 0 6Wed 12/21/2011 5:40:33 PM : [ 5 15 36 4] ST 0 7Wed 12/21/2011 5:40:33 PM : [ 5 15 36 1] DOF 4 8Wed 12/21/2011 5:40:33 PM : [ 5 15 36 1] ST 0 9Wed 12/21/2011 5:40:33 PM : [ 12 29 64 1] ST 0 10Wed 12/21/2011 5:40:38 PM : [ 5 15 36 4] DON 0 11Wed 12/21/2011 5:40:38 PM : [ 5 15 36 4] ST 255 12Wed 12/21/2011 5:40:40 PM : [ 5 15 36 4] DOF 0 13Wed 12/21/2011 5:40:40 PM : [ 5 15 36 4] ST 0 14Wed 12/21/2011 5:40:40 PM : [ 5 15 36 1] DOF 4 15Wed 12/21/2011 5:40:41 PM : [ 12 29 64 1] ST 63 16Wed 12/21/2011 5:40:42 PM : [ 5 15 36 1] ST 63

OK, so I added the program to do the counter thing in variables. It took 4 tries of hitting the button b on the kpl but on the fourth try it did falsley execute both that program (increasing the variable by 1) and the program to turn the lights on to 25%.

what does it stand for? device on? Is this what is shown when a device has the on button pressed?

It's a 2476d v37.

And also, I did pull the hard disconnect tab on the one 2d kpl I have just to get that out of the equation. That didn't fix the problem. And I did add the variable counter program. I just tested it, but it worked properly (no false trigger), so I guess it has stopped doing it every time.

If you can control your ISY from a smartphone webpage, you must have something like "touchswitch" installed on your ISY. Touchswitch is a webpage that lives on the ISY's webserver and runs on pretty much any internet browser. To have this, you must have paid for it and installed it. So, think back, did you ever do that? And the reason you are not getting to your ISY from outside your LAN is that you are probably not using the correct IP address. 192.168.x.x will work inside your lan, but otherwise you need to know your WAN. I suggest setting up dyndns on your router to give yourself a url that updates as your ip address changes.

If your wife's fast twitch muscle fibers are deficient, perhaps consider getting a kpl and setting the various buttons to do the tasks instead of doing the double tap. You also won't have the screwy off then back on thing. You can even label them if she has a grey matter deficit and can't remember things. PS I am just being cute here, I really mean no insult to your wife.

Yeah, I know about that and anticipate having it fixed shortly. But I don't understand how a program that is supposed to only trigger from the "main off" on that KPL is getting triggered by button "b". It should be able to repeat commands a million times. The program is a "switched on" program so only a direct press of the button should be able to do it.

The KPL is 05.15.36 I have some noise in the system right now. I have ordered a filter. If it helps, I could turn off the breaker that I know is creating noise and do it again, although not till I get home. This is from this am. And Jahn, I could write that program, but I can 100% confirm the "then" clause ran as I had the laptop in hand when I pushed the button and watched the program summary as it said "running then". It took 4 or 5 seconds before that program ran. The primary program ran immediately. I could make one giant scene with all those lights if you think it would help. I do believe that would reduce insteon traffic quite a lot. I don't know of any downside to such a huge scene, perhaps you could comment. 6:51:58 AM : CLI-WBug: Connecting to datafeed.weatherbug.com 6:51:58 AM : CLI-WBug: Successfully Processed WBug Response 6:52:07 AM : [ELK 0 19 0] Zone : Kitchen Motion : Violated (51/2/0) 6:52:07 AM : [ELK 0 19 0] Zone : Kitchen Motion : Open (52/1/0) 6:52:13 AM : [ELK 0 19 0] Zone : Kitchen Motion : Normal (51/0/0) 6:52:13 AM : [ELK 0 19 0] Zone : Kitchen Motion : EOL (52/2/0) 6:52:25 AM : [iNST-SRX ] 02 50 05.15.36 00.00.04 C7 13 00 LTOFFRR(00) 6:52:25 AM : [standard-Group][05.15.36-->Group=4] Max Hops=3, Hops Left=1 6:52:25 AM : [ 5 15 36 4] DOF 0 6:52:25 AM : [iNST-SRX ] 02 50 05.15.36 19.75.34 41 13 04 LTOFFRR(04) 6:52:25 AM : [standard-Cleanup][05.15.36-->ISY/PLM Group=4] Max Hops=1, Hops Left=0 6:52:25 AM : [iNST-SRX ] 02 50 05.15.36 19.75.34 42 13 04 LTOFFRR(04) 6:52:25 AM : [standard-Cleanup][05.15.36-->ISY/PLM Group=4] Max Hops=2, Hops Left=0 6:52:26 AM : [iNST-SRX ] 02 50 05.15.36 19.75.34 47 13 04 LTOFFRR(04) 6:52:26 AM : [standard-Cleanup][05.15.36-->ISY/PLM Group=4] Max Hops=3, Hops Left=1 6:52:26 AM : [iNST-ACK ] 02 62 00.00.10 CF 13 00 06 LTOFFRR(00) 6:52:27 AM : [ 5 15 36 4] ST 0 6:52:27 AM : [iNST-ACK ] 02 62 00.00.14 CF 13 00 06 LTOFFRR(00) 6:52:27 AM : [ 5 15 36 1] DOF 4 6:52:27 AM : [iNST-ACK ] 02 62 00.00.15 CF 13 00 06 LTOFFRR(00) 6:52:27 AM : [ 16 14 69 1] ST 0 6:52:28 AM : [ 16 31 B6 1] ST 0 6:52:28 AM : [iNST-ACK ] 02 62 00.00.17 CF 13 00 06 LTOFFRR(00) 6:52:28 AM : [ 12 27 C4 1] ST 0 6:52:28 AM : [iNST-ACK ] 02 62 00.00.1A CF 13 00 06 LTOFFRR(00) 6:52:29 AM : [iNST-ACK ] 02 62 00.00.24 CF 13 00 06 LTOFFRR(00) 6:52:29 AM : [iNST-ACK ] 02 62 00.00.22 CF 13 00 06 LTOFFRR(00) 6:52:30 AM : [iNST-ACK ] 02 62 00.00.23 CF 13 00 06 LTOFFRR(00) 6:52:30 AM : [iNST-ACK ] 02 62 00.00.12 CF 13 00 06 LTOFFRR(00) 6:52:31 AM : [iNST-ACK ] 02 62 00.00.13 CF 13 00 06 LTOFFRR(00) 6:52:31 AM : [iNST-ACK ] 02 62 00.00.1D CF 13 00 06 LTOFFRR(00) 6:52:32 AM : [ 16 1C 78 1] ST 0 6:52:32 AM : [iNST-ACK ] 02 62 0D.C0.60 0F 13 00 06 LTOFFRR(00) 6:52:32 AM : [iNST-SRX ] 02 50 0D.C0.60 19.75.34 23 13 00 LTOFFRR(00) 6:52:32 AM : [standard-Direct Ack][0D.C0.60-->ISY/PLM Group=0] Max Hops=3, Hops Left=0 6:52:32 AM : [iNST-ACK ] 02 62 0F.85.FA 0F 13 00 06 LTOFFRR(00) 6:52:33 AM : [ 7 7E A6 1] ST 0 6:52:33 AM : [iNST-ACK ] 02 62 0D.18.B3 0F 13 00 06 LTOFFRR(00) 6:52:33 AM : [iNST-ACK ] 02 62 0D.18.B3 0F 13 00 06 LTOFFRR(00): Received an ACK for a different device 6:52:33 AM : [ 18 BB 19 1] ST 0 6:52:33 AM : [ 13 42 65 1] ST 0 6:52:33 AM : [ 6 54 2B 1] ST 0 6:52:33 AM : [ 0 7B 38 5] ST 0 6:52:33 AM : [ D 19 7C 1] ST 0 6:52:33 AM : [ 16 40 DE 1] ST 0 6:52:33 AM : [iNST-SRX ] 02 50 0F.85.FA 19.75.34 27 13 00 LTOFFRR(00) 6:52:33 AM : [standard-Direct Ack][0F.85.FA-->ISY/PLM Group=0] Max Hops=3, Hops Left=1 6:52:33 AM : [iNST-ACK ] 02 62 1B.28.71 0F 13 00 06 LTOFFRR(00) 6:52:34 AM : [iNST-SRX ] 02 50 0D.18.B3 19.75.34 23 13 00 LTOFFRR(00) 6:52:34 AM : [standard-Direct Ack][0D.18.B3-->ISY/PLM Group=0] Max Hops=3, Hops Left=0 6:52:34 AM : [iNST-ACK ] 02 62 13.46.B5 0F 13 00 06 LTOFFRR(00) 6:52:34 AM : [iNST-ACK ] 02 62 13.46.B5 0F 13 00 06 LTOFFRR(00): Received an ACK for a different device 6:52:34 AM : [iNST-SRX ] 02 50 1B.28.71 19.75.34 2B 13 00 LTOFFRR(00) 6:52:34 AM : [standard-Direct Ack][1B.28.71-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 6:52:35 AM : [iNST-ACK ] 02 62 12.24.E6 0F 13 00 06 LTOFFRR(00) 6:52:35 AM : [iNST-SRX ] 02 50 13.46.B5 19.75.34 2B 13 00 LTOFFRR(00) 6:52:35 AM : [standard-Direct Ack][13.46.B5-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 6:52:35 AM : [iNST-SRX ] 02 50 12.24.E6 19.75.34 27 13 00 LTOFFRR(00) 6:52:35 AM : [standard-Direct Ack][12.24.E6-->ISY/PLM Group=0] Max Hops=3, Hops Left=1 6:52:35 AM : [iNST-ACK ] 02 62 12.29.64 0F 11 3F 06 LTONRR (3F) 6:52:36 AM : [iNST-SRX ] 02 50 12.29.64 19.75.34 27 11 3F LTONRR (3F) 6:52:36 AM : [standard-Direct Ack][12.29.64-->ISY/PLM Group=0] Max Hops=3, Hops Left=1 6:52:36 AM : [ 12 29 64 1] ST 63 6:52:36 AM : [iNST-ACK ] 02 62 05.15.36 0F 11 3F 06 LTONRR (3F) 6:52:36 AM : [iNST-ACK ] 02 62 00.00.1F CF 11 00 06 LTONRR (00) 6:52:36 AM : [ 5 15 36 4] ST 255 6:52:36 AM : [iNST-SRX ] 02 50 05.15.36 19.75.34 27 11 3F LTONRR (3F) 6:52:36 AM : [standard-Direct Ack][05.15.36-->ISY/PLM Group=0] Max Hops=3, Hops Left=1 6:52:36 AM : [ 5 15 36 1] ST 63 6:52:37 AM : [iNST-ACK ] 02 62 00.00.1F CF 13 00 06 LTOFFRR(00) 6:52:37 AM : [ 5 15 36 4] ST 0 6:52:48 AM : [iNST-SRX ] 02 50 12.29.64 00.00.01 C7 13 00 LTOFFRR(00) 6:52:48 AM : [standard-Group][12.29.64-->Group=1] Max Hops=3, Hops Left=1 6:52:48 AM : [ 12 29 64 1] DOF 0 6:52:48 AM : [ 5 15 36 1] ST 0 6:52:48 AM : [ 12 29 64 1] ST 0 6:52:58 AM : CLI-WBug: Connecting to datafeed.weatherbug.com 6:52:58 AM : CLI-WBug: Successfully Processed WBug Response 6:53:05 AM : [iNST-SRX ] 02 50 16.31.B6 00.00.01 CB 11 00 LTONRR (00) 6:53:05 AM : [standard-Group][16.31.B6-->Group=1] Max Hops=3, Hops Left=2 6:53:06 AM : [ 16 31 B6 1] DON 0 6:53:06 AM : [ 16 14 69 1] ST 255 6:53:06 AM : [iNST-SRX ] 02 50 16.31.B6 19.75.34 41 11 01 LTONRR (01) 6:53:06 AM : [standard-Cleanup][16.31.B6-->ISY/PLM Group=1] Max Hops=1, Hops Left=0 6:53:06 AM : [ 16 31 B6 1] ST 255 6:53:06 AM : [iNST-ACK ] 02 62 00.00.1F CF 11 00 06 LTONRR (00) 6:53:06 AM : [ 12 27 C4 1] ST 255 6:53:06 AM : [ 5 15 36 4] ST 255 6:53:09 AM : [ELK 0 19 0] Zone : Kitchen Motion : Violated (51/2/0) 6:53:09 AM : [ELK 0 19 0] Zone : Kitchen Motion : Open (52/1/0) 6:53:11 AM : [ELK 0 19 0] Zone : Kitchen Motion : Normal (51/0/0) 6:53:11 AM : [ELK 0 19 0] Zone : Kitchen Motion : EOL (52/2/0) 6:53:12 AM : [ELK 0 19 0] Zone : Kitchen Motion : Violated (51/2/0) 6:53:12 AM : [ELK 0 19 0] Zone : Kitchen Motion : Open (52/1/0) 6:53:14 AM : [ELK 0 19 0] Zone : Kitchen Motion : Normal (51/0/0) 6:53:15 AM : [ELK 0 19 0] Zone : Kitchen Motion : EOL (52/2/0)

The switch is now doing it every time. I confirmed that the program below is running the then clause and turning the lights on. This brings me to the only two possibilities. 1) The switch is sending the wrong address (button b is sending the main off as well as b off) 2) ISY is seeing button b turn off and erroneously interpreting that as the main off. I did try factory resetting the KPL and restoring it. That did not fix the problem. If Status 'Master Bedroom / Master-Cans over Bed L' is Off And ( Control 'Master Bedroom / Master-Cans over Bed L' is switched Off Or Control 'Master Bedroom / Master-Keypad' is switched Off ) Then Set 'Master Bedroom / Master-Cans over Bed L' 25% Set 'Master Bedroom / Master-Keypad' 25% Else - No Actions - (To add one, press 'Action')