This moves the sleep-time of ir-command-checks to a config variable. With this change you can reduce the ir sleep-time (or increase it, though i wouldn't know why anyone would wand that).
reducing the sleep time in turn reduces the delay between receiving an ir command and the associated mqtt-message, which can make actions (like pressing a button on a remote and the resulting action based on the mqtt message) feel snappier.
In my example i have one Raspberry PI running this bridge and another one that is connected to the remote control of my sound system and running an mqtt client. With this change, using the volume-buttons on my ir-remote feels snappier (i set it to 0.01 instead of the default 0.2)
This moves the sleep-time of ir-command-checks to a config variable. With this change you can reduce the ir sleep-time (or increase it, though i wouldn't know why anyone would wand that).
reducing the sleep time in turn reduces the delay between receiving an ir command and the associated mqtt-message, which can make actions (like pressing a button on a remote and the resulting action based on the mqtt message) feel snappier.
In my example i have one Raspberry PI running this bridge and another one that is connected to the remote control of my sound system and running an mqtt client. With this change, using the volume-buttons on my ir-remote feels snappier (i set it to
0.01instead of the default0.2)