New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Too slow reaction on user input via buttons #426
Comments
Hab's gerade mal mit einem Button in JARVIS probiert, damit geht es recht schnell, zumindest ausreichend. Daher muss es an VIS liegen. Hat jemand eine Idee, was ich machen kann, falls es irgendwo eine Konfiguration oder sowas gäbe?! Vielen Dank im Voraus!!! @Zefau: FYI |
I checked again also with the VIS-Inventwo buttons. Same problem... |
I think this could be a problem with the debounce time in VIS. After you press a button there is a 1 second debounce time until the button deactivates. This debounce time can be lowered in the settings of VIS under Setup->Settings->States Debounce Time. You might have to restart iobroker after changing this settings. |
@kahlering : That is the solution! Many many thanks!!! |
Describe the bug
A clear and concise description of what the bug is.
I try to create a VIS for remote control of my FireTvCube. Unfortunately the buttons (tested with
ctrl-Icon State
/Buld on/off
) in VIS reacts too slow in terms of multiple clicks. Use Case: I would like to navigate multiple steps to the right. But the VIS will react only on a few when I click them in "normal" speed as I'm used to by using a "normal" remote control.Problem: Several clicks will be missed
To Reproduce
Steps to reproduce the behavior:
ctrl-Icon State
orBulb on/off
+ assign a DPdebug
by each click recognizeddebug
outputExpected behavior
A clear and concise description of what you expected to happen.
Same number of clicks and
debug
outputsScreenshots & Logfiles
If applicable, add screenshots and logfiles to help explain your problem.
Don't know what might be helpful here but I'm open to measure something in case this is requested :-)
Versions:
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: