Single Button Press on 2342-2 Mini Remote to Trigger a Program

[CoolToys]

Trying to figure out a wife approved way to use the mini remote.  Ideally every time I press the A Down button the "Bedtime" or "All Off" program should run.  I tried to use both On or off so no matter what it was before the press the other answer would run the program.  Didn't work, not sure what a Mini keypad sends.  I have two, one is an 8 Scene and it works great for turning scenes on and off with a single press.  The other is a 4 scene.  Same model numbers.  They both appear in the admin console as 2432-222 v.39.  I tried options to change the four scene to an 8 scene it didn't help.  Only the bottom four buttons were read by the admin console when I did that.  

I can see the status of all 8 buttons, but if a button is "off" and I press it, it changes to "on".  When only the "off" option was in the program it was better but took two presses sometimes.  Trying to make it more consistent like the scene controller mini I use downstairs.

Is there a way to use a single keypress to start a program?  I have tried "Toggle" and "non-toggle" 8 scene options.  Neither work.

The "Master Bed Cabinets" is a wall switch, and those lights come on just after sunset.  That works every time.

The Kelly Bed Keypad is a Insteon 5 Button in a plug in adapter.  It has the same issue as the mini keypad.  If it is off, pressing "off" does nothing.  I added the keypad to an "all lights" scene as a controller so it would give her the temporary illusion of working.  Everything turns off, but not as the "All Off" program does. I understand that the Keypad status changes to "on" when the scene is on, so that is why it works as a scene.  Does the eisy ignore commands that equal the current state?

The MB Mini keypad I need to press on, wait about four seconds and then off each night.  Adding it to the scene didn't really help like it did for the 5 button.  The 8 button toggle downstairs controls 8 different scenes perfectly which makes it all the more confusing.

Is there a way for the eisy to "see" a button press and react regardless of the current status of that button?  i.e. pressing "off" when status is already "off" still sends "off" so the eisy can run the program or am I stuck with scenes in toggle mode?  The 4 scene only appears to work as a four scene keypad, I tried to update to 8 scene toggle like the other one and the bottom two buttons become toggles the top two don't appear to do anything.  No activity in the event viewer so I changed back to four scene.  Four on and four off buttons.

I also tried adding it to a "scene" that included just one of the lights in the program.  When I pressed off, that light turned off but the program didn't run.

The program makes it look like someone walking the house turning off all the lights, like Lutron does after you use learning mode to teach it your patterns.  

Edited September 10, 2023 by CoolToys
Additional details for clarity

[JCBond]

Have you tried setting the remote in Toggle mode and then have the program react to both changes?

something like the above?

[CoolToys]

@JCBond yup tried that and still didn't work.  The other remote is in toggle mode but set as controller for the scenes.  It works fine.  The one I use upstairs doesn't appear to accept the change to toggle mode, so maybe that is the issue.  For the money I'll order another one and see what happens.

 

[CoolToys]

So as I found with the sunrise to sunset program, something was lost in translation when migrating from the ISY to the eisy.  

I deleted the V.39 four scene remote, added it back and left it in its default state and tested this to see if it would turn off the light, yes it worked, so I have reprogrammed as @JCBond suggested, and used the "control" option as he showed for the buttons instead of "status".  I think status is a held value and control is a temporary value so it can resend over and over.

Also note that I needed to set both conditions to "on" as the switch didn't ever send "off" and that may have been the issue all along.  
 

MB Keypad Status Toggle - [ID 0002][Parent 0001]

If
        'MB Mini - A Down' is switched On
     Or 'MB Mini - A Up' is switched On
 
Then
        Set 'Scott's Office Lamp' Off
 
Else
   - No Actions - (To add one, press 'Action')

UPDATE - Well the bummer is it still doesn't properly trigger the program, so maybe it is the program itself and I am getting way too fancy with it trying to mimic a human walking the house turning off lights?
 

Edited September 23, 2023 by CoolToys
clarification of both "on" Update

[CoolToys]

So Maybe the program is the problem?  It's hard to test the whole thing without taking a computer to bed. That will be tonights work I guess.  All variables are state, toggled to 1 with other events during the day.  It stopped between the two wait statements each of the last two nights when the MB Mini or Bed Keypad was used.  The Master Bed Cabinet switch works the best but still not 100%

 

All Off - BedTime - [ID 0016][Parent 0001]

If
        $Edit_Guest is 0
    And 'Master Bed Cabinets' Status is not Off
    And (
             'Master Bed Keypad.On' is switched Off
          Or 'Master Bed Cabinets' is switched Off
          Or 'MB Mini - A Up' is switched On
          Or 'MB Mini - A Down' is switched On
        )
 
Then
        $Interior_Motion  = 0
        $Snack_Walk  = 0
        $Alarm  = 0
        $Kitchen_Motion  = 0
        Set 'House Front' Off
        Set 'Garage Lights' Off
        Wait  2 seconds
        Set 'Garage Front Porch Lite' Off
        Set 'Holiday Lights' Off
        Set 'Temp Home Night' On
        Set 'Back Patio' Off
        Set 'FamRm Dining' Off
        Set 'Scott's Office Lamp' Off
        Set 'LR Pool Table' Off
        Set 'HallwayOutletCurio' Off
        Set 'LR Center Outlet Top' Fast Off
        Set 'LR Center Outlet Bot' Fast Off
        Set 'LR Lamp Scene' Off
        Set 'Entry Art Niche' Off
        Set 'Stairwell 3 Way' Off
        Set 'Upstairs Hallway 3 Way' Off
        Wait  4 seconds
        Set 'Cat's Room Lamp Scene' Off
        Set 'Dining' Off
        Set 'Party Night' Off
        Set 'MB Closet' Fast Off
        Set 'Studio Fan' Off
        Set 'Master Bed Cabinets' Fast Off
        Wait  4 seconds
        Set 'Studio Button Light' Off
        Set 'Studio A' Off
        Set 'Studio B' Off
        Set 'Studio C' Off
        Set 'Studio Closet' Off
        Set 'MB Closet Hers' Fast Off
 
Else
   - No Actions - (To add one, press 'Action')
 

 

[CoolToys]

So tonight I pressed all of the buttons hoping any one of them would trigger the program.  None did.  When I went to the admin panel and ran the "then" part it worked perfectly, I think the program is ok.  Clearly the way I am defining the "if" is the failure.  Ugh....  Maybe I will try with a UD Mobile button in a couple days when I am home again.

 

[CoolToys]

More testing.  After trying as a 4 scene, and 8 scene non-toggle, the mini remote was factory reset to 8 scene non-toggle.  The admin panel always show the status as "ON".  I guess it never times out?  When I switch to Toggle Mode, same problem.  Whatever the last press is remains the state.  So maybe there isn't a way to do a one button?  

Other options I tried:
Using another program to change the status to "OFF" so at night the first press turns it "ON".  The only option is to "Write Changes".  
Making it a "responder" to a scene to change its "status".  Doesn't work.

For the wired keypad I simply added it to a scene "House_Front" so it's Status Changes to "ON" when the lights out front turn on. Then the "OFF" Button always works as it should.  

Down to the mini remote.  It did work before upgrading to eisy.  So I did like my sunrise/sunset, deleted it and all references and started over looking at old backups to make sure I was doing it the same way.  No luck.  

Edited September 24, 2023 by CoolToys
notes on fixing wired keypad

[lilyoyo1]

3 hours ago, CoolToys said:

More testing.  After trying as a 4 scene, and 8 scene non-toggle, the mini remote was factory reset to 8 scene non-toggle.  The admin panel always show the status as "ON".  I guess it never times out?  When I switch to Toggle Mode, same problem.  Whatever the last press is remains the state.  So maybe there isn't a way to do a one button?  

Other options I tried:
Using another program to change the status to "OFF" so at night the first press turns it "ON".  The only option is to "Write Changes".  
Making it a "responder" to a scene to change its "status".  Doesn't work.

For the wired keypad I simply added it to a scene "House_Front" so it's Status Changes to "ON" when the lights out front turn on. Then the "OFF" Button always works as it should.  

Down to the mini remote.  It did work before upgrading to eisy.  So I did like my sunrise/sunset, deleted it and all references and started over looking at old backups to make sure I was doing it the same way.  No luck.  

There is no timeout for the remote. Your options are toggle, non toggle on and non toggle off. 

For what you're trying to do, you're better off using it as a 4 button so that you have separate on/off buttons. Then you can program normally using toggle mode. 

If you must use it as an 8 button, non toggle on mode is best, you'll just need to use variables to keep track of your button presses and write programs accordingly to ensure the variable is correct regardless of how you control your system. Due to the amount of work involved, this is why I recommend using your remote in 4 button mode.

Everytime you turn on the lights, the variable is set to 1. If the variable is 1 and you hit the remote in non toggle on mode, then you would have a program run that turns it off and sets the variable to 0 

If the variable is 0 and the remote sends an on command, the lights would turn on and set the variable to 1. 

Edited September 24, 2023 by lilyoyo1

[CoolToys]

@lilyoyo1, I don't have any preference on how the remote is set up.  I want to press one button and have it activate a program no matter what.  The method you suggested was posted elsewhere and I tried it. Since I couldn't make it work I started a new thread. For whatever reason, in four scene, 8 scene non-toggle and 8 scene toggle, the program does not activate.  In Toggle if I slowly pressed twice it would work about 50% of the time.  When I check the status of the remote in the admin panel it is always in the last position.  When I add it to a scene it will turn off the scene every time.  

I am sure there is a way to do this since it used to work.  I just got the ISY Cookbook to start seeing if there is a way to build a flag program or something else.  Basically I want the remote to send "off" and the eisy to receive "off" and run a program every time I press the top left button.  I had it working before upgrading and thought it might be as easy as my sunset problem of removing and re loading the code and device.  That didn't help.

I have a 6 button keypad in a plug adapter (no longer available) on one side of the bed that works fine.  Press "Off" the Bedtime program runs.  I just want the same thing on both sides of the bed.  

For fun I dug out an old X-10 controller and each time I press "X-1 OFF" it works fine too.  I would rather use the mini remote but until I figure it out, X-10 sits by the bed.

Edited September 26, 2023 by CoolToys
6 button keypad working.

[CoolToys]

More testing this morning, finally broke down and rebooted my eisy.  Didn't help.

This morning, sitting at my desk, both mini remotes in hand and my  iPhone with UD mobile and the admin panel on my screen a lot of nothing happens.

The mini remotes both turn the scenes on and off.  The admin panel doesn't reflect the change.  The Garage Lights scene is the easiest monitor and control.  

Pressing mini remote "GAR" button, the light goes on and off.  The Admin panel only says "ON" unless I query.  Pressing "ON" on the admin panel works about 1/3 of the time and UD Mobile mirrors what the admin panel says, right or wrong. 

It's like the PLM didn't get it's coffee and can't "hear" any changes or the eisy stopped listening to the PLM.

More troubleshooting ahead but Jeep needs a recall fixed so I have to stop.