Is there any reason timediff is always 0 for ButtonUpOrDown?
I looked through the Node.js code and am thinking either it's a firmware issue in the button, the code's wrong, or that it's not supposed to show up.
Reason being, if I listen for commands, the button tells me them. If I listen for up or down, it's relative to your distance from the Bluetooth host. That means I'd need timediff to figure out on my own how to debounce clicks.
Is there any reason timediff is always 0 for ButtonUpOrDown?
I looked through the Node.js code and am thinking either it's a firmware issue in the button, the code's wrong, or that it's not supposed to show up.
Reason being, if I listen for commands, the button tells me them. If I listen for up or down, it's relative to your distance from the Bluetooth host. That means I'd need
timediffto figure out on my own how to debounce clicks.