Hello all,

Me again.

I am now trying to set up a keypad linc button to only send an "off" signal - that part has been done and is working great. (set keypad linc secondary button toggle mode to "Non-Toggle [Off]" - add to a scene as a controller and then the other items I want to turn off added as responders).

All good works like a charm.

Now we get to the tricky bit. The keypadlinc pad is by the door and I want it to "light" if any of the responders are switched on by a person. Ok - I also got that to work by writing a program the monitors for each of the "responders" to get switched - and if so then it sets the keypadlinc button to "On" (created a scene where the keypad linc button is a responder and program turns on the scene).

This also works fine - and whenever I turn something on - the keypadlinc secondary button lights up - all good so far.

Here is the issue - when I click the keypad linc button - it turns everything off still as it should - but the keypad linc button stays lit (which I thought it would anyway due it no longer being defined as a toggle switch). So I thought the way around this would be to write a program to capture when the keypad linc button is pressed - and then just set its own LED to "off" (I used a scene for this where the keypad linc button is simply a responder - so I set the scene to off).

However, this program simply will not "fire" - or its not working (I have the If statement checking if the keypadlinc button is switched off OR if the status is off.

Anyone any idea on how I can what I thought would be a simple process to work to turn off the LED when I click the keypadlinc button?

Here is the program watching for the keypadlinc button press:

MainLevelAllOffLEDReset - [ID 0025][Parent 0022]

If
        'MainLevel / Kitchen Area / Entry / KitEntPad3_5_MainAllOff' Status is Off
     Or 'MainLevel / Kitchen Area / Entry / KitEntPad3_3_InAllOff' is switched Off
 
Then
        Set 'MainLevel / Kitchen Area / Entry / Scenes / MainLevelOffLEDControl' Off
 
Else
   - No Actions - (To add one, press 'Action')

noticed an error in the program - here is the corrected version (still does not work :-) ).

Note that I also cleared the log and then clicked that keypad linc button - and - nothing in the log at all - completely empty (as it happens the admin console generates errors when the log is empty ). But - it is empty.

So does that mean that when a keypadlinc button is set up like this and someone presses it that the EISY does not get any kind of notification?

MainLevelAllOffLEDReset - [ID 0025][Parent 0022]

If
        'MainLevel / Kitchen Area / Entry / KitEntPad3_5_MainAllOff' Status is Off
     Or 'MainLevel / Kitchen Area / Entry / KitEntPad3_5_MainAllOff' is switched Off
 
Then
        Set 'MainLevel / Kitchen Area / Entry / Scenes / MainLevelOffLEDControl' Off
 
Else
   - No Actions - (To add one, press 'Action')

14 hours ago, SMonk said:

Here is the issue - when I click the keypad linc button - it turns everything off still as it should - but the keypad linc button stays lit (which I thought it would anyway due it no longer…

I think I would figure out why this is happening, rather than trying to create a bandaid program to correct the first error. I assume that you now have a program somewhere that is turning it on and now a program trying to turn it off. It sounds as if the first program is winning.

I discovered the reason. I needed to introduce a delay into the process before attempting to turn off the LED. If looks like the program was performing the command to turn off the LED - but it looks like the system had not "settled" down to all the activities that were happening. The button controlled (turned off via a scene) 90 insteon devices - as a result this took a little time to complete.

I added a 10 second delay just prior to setting the LED scene to off - and this works pretty reliably. 5 seconds and it never worked.

Thought I should let everyone know.

Thanks. High Insteon traffic including collisions is an issue. The devices and the protocols are not sophisticated enough and maybe can’t be based on the backbone it travels including the electrical wire where it communicates at the zero crossing points.

You could look at event viewer after that scene command is issued and likely see the high traffic and when it stops.

I always add 1 or 2 second waits between critical device updates. Of course no way to easily account for other programs running at the same time.