Firing events off of SeeTouch keypad presses

[neillt]

Is it possible to create an event that is fired when a SeeTouch button is pressed?

Such an event is reported from the repeater as:
~DEVICE,18,8,3
With that being integration ID, button, and 3 for "press". When the button is released the repeater sends:
~DEVICE,18,8,4

The use case I have is to control other systems using keypad buttons. The ugly hack right now is to create a phantom dimmer in the programming which eats up device count, then have the button configured as a device/scene toggle. Then when the button is pressed, it activates the non-existent dimmer, which can fire an event.


Just looking for something cleaner. An example would be an audio zone. It can be labeled "Audio" on the button face, and when the press is seen logic can happen to either turn on or turn off the Russound zone for the room, and then set the LED appropriately. The LED can also be adjusted based on events on the Russound. If the zone is changed via other means an event can run to match the LED to the real status.

[jon102034050]

You can fire an event off of the seeTouch LED status.

[DonMor]

You need to change the default name of the button, if you don't it won't import it, you can also control the led, I'll post it later how to do it

[socalsharky]

You need to change the default name of the button, if you don't it won't import it, you can also control the led, I'll post it later how to do it

Don--Has there been any progress on this? I am trying to do the same thing. I have a hybrid keypad, and I want to use one of the buttons to control my pool lights (which are also integrated into HS3 using Autelis). For some reason, the button for the Pool Lights looks different than all of the other buttons on this hybrid. Why is the status icon listed as "Press" and why is there an "LED On" button shown for that particular button? As of right now, I do not have anything assigned to this button the the RA2 software. Do you have to have some device tied to the button in order for it to work in HS3? This seems to be what neillt was stating above.

[DonMor]

I don't know why you have the Led On there, i look in the program and I don't see how that append, can you post the graphic tab?

you don't need to have anything attach to that button in RA2, the only thing need to be done and you did it is having a button description (Pool Lights)

this even should work for your pool lights

[socalsharky]

I don't know why you have the Led On there, i look in the program and I don't see how that append, can you post the graphic tab?

you don't need to have anything attach to that button in RA2, the only thing need to be done and you did it is having a button description (Pool Lights)

this even should work for your pool lights

Thanks for the response Don. Here is the screenshot:

[DonMor]

something wrong, can you delete that one and re-import to see if that will be recreate?

[DonMor]

here how I would do your event to control the pool with a seetouch and have the led follow:

[socalsharky]

DonMor Thanks Don. I'll give it a try and let you know.

[wkearney99]

Is there a way to track the button press and release on a hybrid keypad?

The Pico remotes can track button press and releases, but what about the SeeTouch keypads?

I just tried and programmed one of the buttons on mine to have nothing attached to it in the Ra2 programming. As in, using the Lutron software I removed any lights from the button (and transferred the programming). I also

When I press this button I see a quick pair of commands:

~DEVICE,158,2,3
~DEVICE,158,2,4

When I hold the button I see the first one and then I see the second one when I release it.

The LED on the keypad does toggle. But the change is not tracked in HS3 via the plug-in. I'm guessing the plug-in is just looking for Ra2 repeater commands, and since the button isn't programmed to do anything in Ra2 there's no command logged.

The LED status is tracked in HS3, but only if an event sets it. I created a manual event and turned the LED on and off. The repeater log shows the values being set (on and off):

~DEVICE,158,82,9,1
~DEVICE,158,82,9,0

The keypad does send press/release when it's used. It does NOT, however, send any messages about the LED changing if there's nothing programmed to it.

Would it be possible to have the Ra2 plug-in allow detecting the button press/releases in HS3?

[DonMor]

What would be the the usage of tracking the release of the SeeTouch button?

[socalsharky]

Bill--you performed those tests on a pico or on a hybrid? I have not done anything like that with my system. How do you view these numerical commands? How do you know what they mean?

[DonMor]

Those commend come from the telnet from the main repeater. If you search lutron integrator on the web you will find the PDF with all the command.

[socalsharky]

Don--I deleted the hybrid keypad in question, and re-imported the RA2 devices. Now the "LED On" button for the Pool Lights is gone. So that is good. However, similar to what Bill mentioned above, clicking on the "Press" button for the Pool Lights has no effect in HS3. The status of the LED in HS3 does not change, and the LED on the physical button does not change. It must have something to do with the fact that there is no switch or dimmer assigned to this button, because all of the other buttons work correctly when "pressed" in HS3.

For some reason, in HSTouch the Pool Lights button has three commands available: Press, LED Off and LED On. Press has no effect in either HS3 and on the physical button. However, the LED Off and LED On commands in HST do in fact change the LED on the physical switch.

Lastly I noticed that the physical button LED changes from off to on (and vice versa) when pressed, but it always reverts to the setting in HST after 1 or 2 seconds.

Something needs to change in HS3 or RA2 for this button to be able to control my pool lights.

[DonMor]

This is normal that the led don't change in HS3 when you don't have switch connect to the seetouch, this is why you need to use the event like the post #8.

For your information the led on the seetouch is not an on or off of the seetouch switch, it is more intelligent, the led will come on or off when all the condition of the programming archive or not. HS3 will receive the press of a seetouch even if no switch attach.

exemple:

seetouch program with Single/Multi-room scene
-No switch attach: Led will always be off, but you can control the led with HS3 with the event
-all off: led will be On when all off, if one device is On the led will be off
-switch 1 at 100%, switch 2 at 0% : led will be on when switch 1 at 100% and switch 2 at 0%

This is my seetouch with no attach switch, with the post 8 I do exactly what you want.