ISY Program not dtecting when a Control is turned On

[ricke]

I created a simple test Program to watch when a SwitchLinc is turned on and then take a few actions. I have this program enabled and when I test this by turning on the SwicthLinc the program does not run. The ISY console status does show that the SwitchLinc is in fact ON.

If I test the Then section of the program it definitely works. Here is the code:

 

If

Control 'Main Hallway Lights (garage)' is switched On

 

Then

Set 'Family Floods (0F.15.D6.1)' 20%

Wait 10 seconds

Set 'Family Floods (0F.15.D6.1)' Off

 

Else

- No Actions - (To add one, press 'Action')

 

What could be blocking the program from detecting when the light control is going on so that it can activate the actions?

 

Thanks!

Rick

[LeeG]

The SwitchLinc Current State as On could have been from a previous command. Run Tools | Diagnostics | Event Viewer with Level 3-Device communications events selected. Watch for Insteon traffic from the SwitchLinc when the On paddle is pressed. If the On command is received and Program Last Run Time does not indicate the Program was triggered be sure the Program was Saved.

 

If the Program was Saved likely there is intermittent comm with the SwitchLinc.

[ricke]

Surprisingly even though all of the lighting buttons are working the Log at Level 3 only seems to be showing Setting the Time via NTP. I tried a number of INSTEON buttons and they were not being registered by ISY.

What I noticed playing around with things is that if I control a light through the ISY admin console, the state change is noticed in the detail pane to the right of a switch and in the log, but if I use the physical SwitchLinc to turn on/off the light, the ISY console doesn't seem to register that state change even though the light does turn on or off.

 

Why wouldn't using the hardware light switch be seen by the ISY admin console?

 

Thanks,

Rick

[LeeG]

Either the link records in the device and/or PLM have been lost or there is a comm problem. In this case it is more likely a link record problem since the device can be controlled through the Admin Console. Controlling the device through the Admin Console uses Insteon Direct commands which are not dependent on link records for their operation.

 

Pressing a button/paddle requires link records in both the device and the PLM for the ISY to be aware of the button/paddle press. The device does not send any commands if its link records have been erased. The PLM does not receive commands if its link records have been erased.

[ricke]

Hmm that woudl mean that a whole bunch of links are missing. I used the network view in teh admin console to see all status and any of the lights that say On if I turn them off using the light switches nothing happens. I power cycled the ISY99 box and restarted the consoel but I still dont see that state info being reflected. It definitely used to work. Very odd.

 

Rick

[LeeG]

Assuming the Current State column is not all blank and many devices are not indicating state changes a File | Restore Modem (PLM) is the place to start. There could be other causes. All the devices not reporting state changes are on the opposite 120V leg to the ISY PLM and something has happened to the Access Points that are coupling the two 120V legs.

 

PLMs have been known to lose link records. Sometimes means the PLM is approaching failure but not always.

[stillen_i30]

Ricke, I had this same problem not too long ago. Mine stemmed from when relocating my plm into a tight spot, the set button on the plm was inadvetantly pressed thus resetting the plm. I ended up spending a whole weekend re-programming everyone of my numerous devices for state changes to show in the isy when changed locally. Seach my name thru previous threads as others suggested alternate "easier" ways to get it to work again than what I did.