LeeG

karwas The ISY issues a Get Next command to read next PLM link record. Any Insteon activity that reaches the PLM will adversely affect what link record the Get Next command retrieves. Link 30 Link 31 Link 32 Link 33 Link 34 Link 35 Link 36 A Get Next reads Link 31. An Insteon message is processed that is associated with Link 34. The next Get Next command will read Link 35, skipping 32, 33, and 34, making the PLM link count appear less than is actually there. The other case is Link 34 is read with a Get Next. An Insteon message is processed that is associated with Link 30. The next Get Next reads Link 31, 32, 33 and 34 again. making the PLM link count appear more than is actually there. When running a Show PLM Links Table no Insteon message must reach PLM. Otherwise the PLM Link count will be too high or too low.

Can't tell much from X10 messages as far as which device produced the traffic. Don't think you will find much that helps identify which device. The traffic below came from an X10 Pro Maxi Controller. X10 traffic is in 2 parts .... 02 52 59 00 02 52 = PLM identifier for X10 message 59 = 5 is G; 9 is 6 00 = first part of X10 message - contains House/Unit code 02 52 52 80 02 52 = PLM identifier for X10 message 52 = 5 is G; 2 is On command 80 = command message - contains House/X10 Command Fri 03/04/2016 12:09:26 AM : [X10-RX ] 02 52 59 00 Fri 03/04/2016 12:09:26 AM : [ X10] G6 Fri 03/04/2016 12:09:28 AM : [X10-RX ] 02 52 52 80 Fri 03/04/2016 12:09:28 AM : [ X10] G6/On (3) Fri 03/04/2016 12:09:29 AM : [X10-RX ] 02 52 59 00 Fri 03/04/2016 12:09:29 AM : [ X10] G6 Fri 03/04/2016 12:10:41 AM : [X10-RX ] 02 52 59 00 Fri 03/04/2016 12:10:41 AM : [ X10] G6 Fri 03/04/2016 12:10:43 AM : [X10-RX ] 02 52 53 80 Fri 03/04/2016 12:10:43 AM : [ X10] G6/Off (11) Fri 03/04/2016 12:10:44 AM : [X10-RX ] 02 52 59 00 Fri 03/04/2016 12:10:44 AM : [ X10] G6 Google the Internet for X10 House/Unit/Command charts. A PLM Guide also has X10 charts. 

No secrets in post #2. The original post #1 would leave the devices running when the State Variable changed to 0. My post #2 example insures the devices are not left running when Variable changes to 0. The If is triggered by the change in Variable value. The If evaluates as False causing Else to run turning the devices Off. ISY has worked this way for all the years I have been using them.

All KPL buttons, primary and all secondary buttons are linked back to the PLM when the KPL is added to the ISY. If a Secondary button does not appear in an Event Viewer trace at LEVEL 3, either the KPL or PLM have lost the link or a comm issue exists. Image attached is KPL with no additional Scenes. All 8 buttons have links to PLM.

I was referring to the original Then. The Off statements in the original post #1 would not accomplish anything constructive and could lead to early device problems. If $PoolHeating is 1 Then Set 'Pool Equipment / FilterPump' On Set 'Pool Equipment / PoolHeater' On Wait 3 hours Set 'Pool Equipment / PoolHeater' Off Set 'Pool Equipment / FilterPump' Off Run Program 'HeatPool' (Then Path) Else - No Actions - (To add one, press 'Action') "When I have variable PoolHeating to 1 I want the pump/heater to come on for 3 hours then off for 3 hours and repeat till I set variable to 0. One approach could look like the following If $PoolHeating is 1 Then Set 'Pool Equipment / FilterPump' On Set 'Pool Equipment / PoolHeater' On Wait 3 hours Set 'Pool Equipment / PoolHeater' Off Set 'Pool Equipment / FilterPump' Off Wait 3 hours Run Program 'HeatPool' (Then Path) Else Set 'Pool Equipment / PoolHeater' Off Set 'Pool Equipment / FilterPump' Off I really don't like to do this. Part of this forum activity (in my view) is to provide the OP with enough information where they can write the Program themselves. Insteon is DIY. Helping the OP get to that point is important.

Yes. The Program runs until the State Variable is changed to 0 (per OP). The probably that the State Variable could be changed during the 1-2 second period when the Then turned the devices Off and before the Then turned the devices back On is so low that the devices would remain On. When the State Variable is changed the 3 hour Wait is interrupted. The If would be False driving the Else which turns the devices Off.

The Off statements in the Then clause turns the Pump and Filter Off. The next statement in Then repeats the Then clause which immediately turns the Pump and Heater back On. Not likely the pump has even stopped spinning but the point is devices are immediately turned On again. That 1-2 second Off cycle does not do either device any good. Much better to have the Else clause turn the devices Off.

Thanks. Device 1C.4F.CD failed to respond the three attempts the ISY sent to device. Is it possible it is unplugged or the power to the socket has been turned Off?

Be sure to use the EZFlora primary (Zone 1). With the event viewer at LEVEL 3, Query zone 1 then Restore Device. Post the event trace.

Yes, the ISY has always been event driven.

That would be a problem. The ISY and old PLM must be powered Off. The new PLM powered On and allowed to cycle up. Then power up the ISY. When the ISY and Admin Console are up issue the Restore Modem (PLM). The ISY understands the PLM was changed and updates all devices with new PLM address. If the ISY was not powered down then it is not looking for a PLM change. The Red ! indicates the ISY has a problem sending something to the EZFlora. Run Tools | Diagnostics | Event Viewer at LEVEL 3 to see problem. If the EZFlora is an I2CS device and was not updated with new PLM address that would be a problem. Do a Restore Device to EZFlora to see if that resolves Red !.

That helps. The ISY is event driven. When the State Variable is changed to 0 this Program is triggered (If runs). The If is evaluated, found False so Else is executed. This Program is triggered again (run If) only when Variable value is changed. ISY Programs are triggered to run If by some event occurring or directed to run by some other Program. ISY Programs are not running in a loop check checking the If condition(s).

If the Variable is being set to various values besides 0 & 1 (such as 0, 1, 2, 3), then more data about your operating environment is needed.

"yeah but if I put that in the else my pump will never turn on when I'm not heating pool right. " The Else runs once when Variable changed to other than 1. How will this interfere? If you only want Program to turn On devices drop the Else statements. That means that something else is required to turn those devices Off when variable changed which is a little unusual.

The EZFlora does not send Zone state messages so not sure what EZFlora issue is occurring. There is a step by step procedure in Wiki for PLM replacement. What is the hardware level of "new" PLM, on White sticker? http://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:File_Menu#Replace_Modem_.28PLM.29

The Variable must be a State variable. Also need some cleanup in Else. If $PoolHeating is 1 Then Set 'Pool Equipment / FilterPump' On Set 'Pool Equipment / PoolHeater' On Wait 3 hours Run Program 'HeatPool' (Then Path) Else Set 'Pool Equipment / PoolHeater' Off Set 'Pool Equipment / FilterPump' Off EDIT: Removed the Off statements in Then. No need for them.

Only one RF device can be put into linking mode at a time. Otherwise the RF devices link to each other. After one RF device update is complete, take it out of linking mode and put the next RF device into linking mode.

The ISY Log shows change of device Status where Event Viewer shows message traffic. Each has its own purpose. Leak Sensor 2-Dry / Leak Sensor 2-Wet Status 100% Mon 2016/02/08 03:01:45 PM System Log - Wet On Leak Sensor 2-Dry Status 0% Mon 2016/02/08 03:01:45 PM System Log 2491T - Main Humidity 71% Mon 2016/02/08 03:01:47 PM System Log Leak Sensor 2-Dry Status 100% Mon 2016/02/08 03:02:26 PM System Log Leak Sensor 2-Dry / Leak Sensor 2-Wet Status 0% Mon 2016/02/08 03:02:26 PM System Log - Wet Off 2491T - Main Humidity 70% Mon 2016/02/08 03:02:58 PM System Log

Insteon does not support assigning an On Level when turning On a Scene. Set Scene 'xxxx' On 50% - this is not supported by Insteon rest/nodes/<scene number>/cmd/On/128 - this is not supported by Insteon

Eric2XU Ok, lets do this the other way. What does the Secondary button D being displayed at 31% mean to you? Button D intensity is less than it would be at 100%? A linked device is set to 31% when button D Status is 31%? Something is different about button D when its Status is 31%? ????

Here is what you should see BathroomLight - [iD 00A1][Parent 0001] If From 8:05:00AM To 8:10:00AM (same day) Then In Scene 'SwitchLinc4' Set 'SwitchLinc4' 30% (On Level) In Scene 'SwitchLinc4' Set 'SwitchLinc4' 2.0 Sec (Ramp Rate) Else In Scene 'SwitchLinc4' Set 'SwitchLinc4' 100% (On Level) In Scene 'SwitchLinc4' Set 'SwitchLinc4' 0.3 Sec (Ramp Rate) These are the trace records for the In Scene statements setting 30% On Level and 2 second ramp rate followed by setting 100% On Level and .3 second Ramp Rate 5 minutes later. Sat 02/27/2016 08:04:46 AM : [ Time] 08:05:00 0(0) Sat 02/27/2016 08:04:46 AM : [D2D EVENT ] Event [1D 1E DB 1] [OL] [76] uom=0 prec=-1 Sat 02/27/2016 08:04:46 AM : [ 1D 1E DB 1] OL 76 Sat 02/27/2016 08:04:46 AM : [D2D EVENT ] Event [1D 1E DB 1] [RR] [27] uom=0 prec=-1 Sat 02/27/2016 08:04:46 AM : [ 1D 1E DB 1] RR 27 Sat 02/27/2016 08:04:47 AM : [All ] Writing 2 bytes to devices Sat 02/27/2016 08:04:47 AM : [1D 1E DB 1 ] Memory : Write dbAddr=0x0032 [4C] cmd1=0x2E cmd2=0x00 - Set 30% On Level Sat 02/27/2016 08:04:47 AM : [iNST-TX-I2 ] 02 62 1D 1E DB 1F 2E 00 01 06 4C 00 00 00 00 00 00 00 00 00 00 7F Sat 02/27/2016 08:04:47 AM : [iNST-ACK ] 02 62 1D.1E.DB 1F 2E 00 01 06 4C 00 00 00 00 00 00 00 00 00 00 7F 06 (00) Sat 02/27/2016 08:04:47 AM : [iNST-SRX ] 02 50 1D.1E.DB 22.80.0B 2B 2E 00 (00) Sat 02/27/2016 08:04:47 AM : [std-Direct Ack] 1D.1E.DB-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sat 02/27/2016 08:04:47 AM : [1D 1E DB 1 ] Memory : Write dbAddr=0x0021 [1B] cmd1=0x2E cmd2=0x00 - Set 2 second ramp rate Sat 02/27/2016 08:04:47 AM : [iNST-TX-I2 ] 02 62 1D 1E DB 1F 2E 00 01 05 1B 00 00 00 00 00 00 00 00 00 00 B1 Sat 02/27/2016 08:04:47 AM : [iNST-ACK ] 02 62 1D.1E.DB 1F 2E 00 01 05 1B 00 00 00 00 00 00 00 00 00 00 B1 06 (00) Sat 02/27/2016 08:04:48 AM : [iNST-SRX ] 02 50 1D.1E.DB 22.80.0B 2B 2E 00 (00) Sat 02/27/2016 08:04:48 AM : [std-Direct Ack] 1D.1E.DB-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 -------------------- Sat 02/27/2016 08:10:01 AM : [ Time] 08:10:01 0(0) Sat 02/27/2016 08:10:01 AM : [D2D EVENT ] Event [1D 1E DB 1] [OL] [255] uom=0 prec=-1 Sat 02/27/2016 08:10:01 AM : [ 1D 1E DB 1] OL 255 Sat 02/27/2016 08:10:01 AM : [D2D EVENT ] Event [1D 1E DB 1] [RR] [29] uom=0 prec=-1 Sat 02/27/2016 08:10:01 AM : [ 1D 1E DB 1] RR 29 Sat 02/27/2016 08:10:01 AM : [All ] Writing 2 bytes to devices Sat 02/27/2016 08:10:01 AM : [1D 1E DB 1 ] Memory : Write dbAddr=0x0032 [FF] cmd1=0x2E cmd2=0x00 - Set 100% On Level Sat 02/27/2016 08:10:01 AM : [iNST-TX-I2 ] 02 62 1D 1E DB 1F 2E 00 01 06 FF 00 00 00 00 00 00 00 00 00 00 CC Sat 02/27/2016 08:10:01 AM : [iNST-ACK ] 02 62 1D.1E.DB 1F 2E 00 01 06 FF 00 00 00 00 00 00 00 00 00 00 CC 06 (00) Sat 02/27/2016 08:10:01 AM : [iNST-SRX ] 02 50 1D.1E.DB 22.80.0B 2B 2E 00 (00) Sat 02/27/2016 08:10:01 AM : [std-Direct Ack] 1D.1E.DB-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sat 02/27/2016 08:10:01 AM : [1D 1E DB 1 ] Memory : Write dbAddr=0x0021 [1D] cmd1=0x2E cmd2=0x00 - Set .3 second Ramp Rate Sat 02/27/2016 08:10:01 AM : [iNST-TX-I2 ] 02 62 1D 1E DB 1F 2E 00 01 05 1D 00 00 00 00 00 00 00 00 00 00 AF Sat 02/27/2016 08:10:01 AM : [iNST-ACK ] 02 62 1D.1E.DB 1F 2E 00 01 05 1D 00 00 00 00 00 00 00 00 00 00 AF 06 (00) Sat 02/27/2016 08:10:02 AM : [iNST-SRX ] 02 50 1D.1E.DB 22.80.0B 2B 2E 00 (00) Sat 02/27/2016 08:10:02 AM : [std-Direct Ack] 1D.1E.DB-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 You should see these same type statements when running the correct Program.

KYnewbie It is certainly doable. Your last Event trace looks like the example Program you posted in initial post to this forum topic. Then In Scene 'Bath Light Night' Set 'Master Toilet Light' 30% (On Level) In Scene 'Bath Light Night' Set 'Master Toilet Light' 2.0 Sec (Ramp Rate) What you need is what I posted in #3. Then In Scene 'Master Toilet Light' Set 'Master Toilet Light' 30% (On Level) In Scene 'Master Toilet Light' Set 'Master Toilet Light' 2.0 Sec (Ramp Rate) These statements will update the On Level (applied locally) and Ramp Rate (applied locally) fields of Master Toilet Light so these values will control what happens when Master Toilet Light paddle is pressed to turn load On to 30% in 2 seconds.

Eric2XU Everything MWareman has posted is right on. I thought adding some background might be helpful. Insteon does not support an override On Level on a Scene command. http://isy/rest/nodes/8052/cmd/DON/128 - Insteon Scene command has no field for the 128 value ISY has the Adjust Scene Program Action for changing a Scene device On Level and Ramp rate (as MWareman indicated) Only a KPL Primary load control button (Main A 8 button; ON/Off buttons 6 button) can be controlled with a Direct command. KPL Secondary buttons can be turned On/Off only with a Scene command. Again, this is an Insteon requirement. The On Level values 1-254 have no affect on Secondary KPL buttons. Setting a Secondary KPL button to 30% On Level has no visual affect. No need to set a Scene KPL Secondary button to anything but On or Off. A Scene definition of a KPL Secondary button with 0% On Level will turn the Secondary KPL button Off with a Scene On command. Hope these details help.

The link records being updated are associated with the ISY Scene (where PLM is Controller). Perhaps the Program that is setting the SwitchLinc On Level (applied locally) and Ramp Rate (applied locally) data was not saved or saved under a different name. These updates cannot apply when the SwitchLinc paddle is pressed. It is not possible for a SwitchLinc paddle to initiate an Insteon Scene number 0x2B Thu 02/25/2016 10:56:48 PM : [ Time] 22:56:50 1(0) Thu 02/25/2016 10:56:48 PM : [3C 7A 2 1 ] Link 2 : 0FE8 [A22B3D94BA4C1B01] Saving [..........4C....] Thu 02/25/2016 10:56:48 PM : [3C 7A 2 1 ] Link 2 : 0FE8 [A22B3D94BA4C1B01] Saving [............1B..] Thu 02/25/2016 10:56:48 PM : [All ] Writing 2 bytes to devices Thu 02/25/2016 10:56:48 PM : [3C 7A 2 1 ] Link 2 : 0FE8 [A22B3D94BA4C1B01] Writing [..........4C1B..] Thu 02/25/2016 10:56:48 PM : [iNST-TX-I2CS] 02 62 3C 7A 02 1F 2F 00 00 02 0F EF 08 A2 2B 3D 94 BA 4C 1B 01 09 Thu 02/25/2016 10:56:48 PM : [iNST-ACK ] 02 62 3C.7A.02 1F 2F 00 00 02 0F EF 08 A2 2B 3D 94 BA 4C 1B 01 09 06 (00) Thu 02/25/2016 10:56:49 PM : [iNST-SRX ] 02 50 3C.7A.02 3D.94.BA 2F 2F 00 (00) Thu 02/25/2016 10:56:49 PM : [std-Direct Ack] 3C.7A.02-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Ignore the "previous message ignored". These are records sent when the SwitchLinc paddle is pressed that are not used by the ISY.

The Program Status (True/False) reflects the last evaluation of the If clause. When the If evaluates as True the Program Status is True. When the If evaluates as False the Program Status is False. The Event Viewer at LEVEL 3 will show the the messages the PLM passed to the ISY which the Program used to drive the If clause. Post the Programs as they may help in the evaluation as well as the event messages.