Single button works, double or long press doesn't work

[joshivic]

hello,

Single button press registers in homekit, double or long press doesnt work.

node 12.13.1

[joshivic]

could you please fix this, how do I donate to this project

[joshivic]

Hello,

I telnet into the lutron bridge pro to observe the button presses.

Device Id: 15
Device type: PJ2-3BRL

*** Single button press ***

on button
~DEVICE,15,2,3
~DEVICE,15,2,4

up arrow button
~DEVICE,15,5,3
~DEVICE,15,5,4

favourite button
~DEVICE,15,3,3
~DEVICE,15,3,4

down arrow button
~DEVICE,15,6,3
~DEVICE,15,6,4

off button
~DEVICE,15,4,3
~DEVICE,15,4,4

*** Double button press, ***

on button
~DEVICE,15,2,3
~DEVICE,15,2,4
~DEVICE,15,2,3
~DEVICE,15,2,4

up arrow button
~DEVICE,15,5,3
~DEVICE,15,5,4
~DEVICE,15,5,3
~DEVICE,15,5,4

favourite button
~DEVICE,15,3,3
~DEVICE,15,3,4
~DEVICE,15,3,3
~DEVICE,15,3,4

down arrow button
~DEVICE,15,6,3
~DEVICE,15,6,4
~DEVICE,15,6,3
~DEVICE,15,6,4

off button
~DEVICE,15,4,3
~DEVICE,15,4,4
~DEVICE,15,4,3
~DEVICE,15,4,4

*** Long button press ***

on button
~DEVICE,15,2,3 button held down
..
..
~DEVICE,15,2,4 button release

up arrow button
~DEVICE,15,5,3 button held down
..
..
~DEVICE,15,5,4 button release

favourite button
~DEVICE,15,3,3 button held down
..
..
~DEVICE,15,3,4

down arrow button
~DEVICE,15,6,3 button held down
..
..
~DEVICE,15,6,4 button release

off button
~DEVICE,15,4,3 button held down
..
..
~DEVICE,15,4,4 button release

[smockle]

Hi @joshivic, thank you for providing these logs. Although I do not plan to develop this plugin further, the logs you have provided could help someone else add support for this feature.

[jvic1234]

Smockle,

Can you continue the development if we fund the project. I wish I was smart to even understand the scripts. I took a look but don’t understand them. Maybe you can tell me which file to edit.

[scooter133]

I Too have been looking at getting those features to work. Though I'm not an expert on these plug-ins. I understand why needs to happen, though since things happen serially you need to be able to have a saved state that you can reference on.

The way it works now is that the code is looking just at the Button up. Once it gets the 4 for button release, it fires the code to do the action. It's not looking at 3, and it's not keeping track of the state of that last buttons's state. Thats what makes it hard. The routine just processes the log entries one at a time as they come in.
Remote ID 5, Button 5, Button Down, Toss that Command.
Remote ID 4, Button 5, Button Up, Turn on

You need to know for long press when button was pressed, 3, and for how long, was it long enough before you get the Button up, 4? I don't know hot to keep track of that state, these are all just events that come into the queue and get processed. For Double press you need to Ideally, need to keep track of the time time difference between the 3,4 first press and the difference between the 4,3 repeat press down, and then the 3,4 up timing to see if it wasn't lingering on the start or end of the double press. Meanwhile someone in the other room is playing with the buttons and sending in other events that need processing.

It's Messy.