You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have some rules in pimatic so that after a button on a remote is pressed, it sends a signal to a switch.
But many times homeduino takes a long time to send after receiving.
I've already tried reducing the wait time on the listenBeforeTalk() method from 1 sec to 500 millis, but it still takes a long time (about 2 seconds a lot of the times). If I reduce it to 100 millis it works quickly, but then it is much less reliable (will talk before listening to everything :D ).
I've checked if the remote was sending for too much time, but it is not. It only repeats the signal for less than half a second, so that is not the problem.
Could it be that, when not receiving anything anymore, the package identification is taking too long to go to the last state (STATUS_RECORDING_END), causing the delay?
I'm not sure if this should be posted here or in RFControl...
The text was updated successfully, but these errors were encountered:
I have some rules in pimatic so that after a button on a remote is pressed, it sends a signal to a switch.
But many times homeduino takes a long time to send after receiving.
I've already tried reducing the wait time on the listenBeforeTalk() method from 1 sec to 500 millis, but it still takes a long time (about 2 seconds a lot of the times). If I reduce it to 100 millis it works quickly, but then it is much less reliable (will talk before listening to everything :D ).
I've checked if the remote was sending for too much time, but it is not. It only repeats the signal for less than half a second, so that is not the problem.
Could it be that, when not receiving anything anymore, the package identification is taking too long to go to the last state (STATUS_RECORDING_END), causing the delay?
I'm not sure if this should be posted here or in RFControl...
The text was updated successfully, but these errors were encountered: