Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

PRESS_LONG and PRESS_LONG_RELEASE behaviour

See original GitHub issue

Description

I’m using RedMatic to query a HM-PB-6-WM55 and I want to use the PRESS_LONG / PRESS_LONG_RELEASE events. The sequence in which the events are produced makes it IMHO impossible to control something useful with it. Here is a long press as seen by a Node-Red debug node:

grafik

At 13:13:52 I started pressing the switch and at 13:13:58 I released the switch again.

Actual behavior:

With a pressed switch a continuous flow of INSTALL_TEST events is created.
The PRESS_LONG event is actually generated when the switch is released
The PRESS_LONG_RELEASE is generated right after the PRESS_LONG event

Expected behavior

The PRESS_LONG event shall be issued after the specified PRESS_LONG time in the device
The PRESS_LONG_RELEASE shall be generated when the switch is released

Ping @hobbyquaker although I do not think this behavior is RedMatic related.

Issue Analytics

State:
Created 5 years ago
Comments:13 (5 by maintainers)

Top GitHub Comments

1reaction

lukicslcommented, Sep 13, 2018

The devices behave different when the transport is set to “secured”, set it to standard

0reactions

stale[bot]commented, Feb 4, 2022

This issue has been automatically closed because of inactivity. Please open a new issue if still relevant and make sure to include all relevant details, logs and reproduction steps.

Dieses Problem wurde aufgrund von Inaktivität automatisch geschlossen. Bitte öffnen Sie ein neues Issue, falls dies noch relevant ist und stellen Sie sicher das alle relevanten Details, Logs und Reproduktionsschritte enthalten sind.