Can the 8 button remote, reflect the status of a light?

[Blackbird]

As my remote works now is I push the kitchen button (1-A) and the light on the remote is green and turns on the kitchen light.  Push again and the light turns red and the kitchen lights go out.  Problem is if the status on the remote is "off" and I turn my kitchen light on by the light switch, the next time I go to turn the lights off with the remote, I have to push the button twice.  I was wondering if there was a way to write a program that would be like this.

 

If

Status of kitchen light is on

Then

Set status of remote 1-A to on

 

I don't see the option to set a status in the then section.

 

Anyone have an idea how to make this work?

 

Thanks

[oberkc]

I don't believe so.  Remotelincs typically transmit only...no recieve...no status.

[MWareman]

I don't believe so. Remotelincs typically transmit only...no recieve...no status.

Can remotelincs be set in on-only mode? (I still don’t have one of these....)

 

If so, they could drive a program that turns the scene on if the associated device status is off, and off if the associated device status is not off...

[oberkc]

My recollection was that they can be set to four- or eight-scene mode. In the four scene mode, there are discrete ON and OFF buttons for each scene. In the eight mode, buttons are toggled. I did not recall a non-toggle mode, but I quickly checkef the manual and it appears to have one. Good thought.

[larryllix]

With only one LED and 24 detected button push methods, how would any status be shown for the devices?

[oberkc]

With only one LED and 24 detected button push methods, how would any status be shown for the devices?

 

My perceptions are that the sole purpose here is to avoid having to press a button twice, rather than a direct display of status.  If a scene for which the remotelinc button is controller is turned on by other means, pressing the remotelinc could first send an ON command, rather than OFF command, apparently, forcing the operator to press twice to turn the scene off, or vice versa.

[larryllix]

My perceptions are that the sole purpose here is to avoid having to press a button twice, rather than a direct display of status.  If a scene for which the remotelinc button is controller is turned on by other means, pressing the remotelinc could first send an ON command, rather than OFF command, apparently, forcing the operator to press twice to turn the scene off, or vice versa.

Ahhh. I misread. It's the same old syncho error between devices.

 

Thanks oberkc-kenobi!

[oberkc]

Ahhh. I misread. It's the same old syncho error between devices.

 

Thanks oberkc-kenobi!

 

You are welcome, jedi yodallix

[Blackbird]

Yes I'm lazy, I don't want to have to push the button twice like a chump!  The options for the remote button is LED, Beep, 4-secen, 8 scene toggle(checked) and 8-scene non- toggle and it does show a current status but I cant change it

[oberkc]

The current status shown, I understand, is the last recieved command.  Like I said, I don't believe you can change the status externally.  Larryllix has the best idea I believe, which is to put the remotelinc into non-toggle mode and create a program (triggered by the proper button command) to turn the lights off (if on) or on (if off).

[Blackbird]

The current status shown, I understand, is the last recieved command.  Like I said, I don't believe you can change the status externally.  Larryllix has the best idea I believe, which is to put the remotelinc into non-toggle mode and create a program (triggered by the proper button command) to turn the lights off (if on) or on (if off).

But no dim?

[larryllix]

But no dim?

You can have six commands from one button, but only four buttons. Or you could write ISY programs  to toggle On/Off and dim/brighten on right side buttons and repeat for another device on the left side, having eight devices but not as nice. The devices don't have to do what the style of the mini-remote is doing.

 

ISY always knows where the device's status is at then.

 

With ISY, there is always a way!

[oberkc]

But no dim?

 

Good question.  I do not know for sure.

 

Do you actually use all eight scenes, or could you get by with four?

[ScottAvery]

So, you can't really have a program respond reliably with the button linked directly to the device, which you would need to dim smoothly.  Dimming programmatically would require fixed set points.

 

The best option actually breaks your desire to not push twice, but should work once you get used to the pattern:

 

Set to non-toggle On and link buttons directly to each device/scene.

Create a program for each button looking for Fast On  (double click)

* first line of THEN sets a short delay (2 seconds perhaps)  to allow the fast on command to complete

* second lien turns the device/scene off

 

Usage  single click for on.  double click for off. press and hold for dimming.

 

not perfect, as there is a full on and delay before off, but it would give you smooth dimming.