Closed MHofer closed 4 years ago
I think you are right, looks like something got missing in the logic while migrating this capability from v1.7 to v1.8. I'll try to reproduce it and come back in case of doubts, meanwhile I'm tagging this as a bug
Fixed by #517
setting a higher debounce time has no effect, even if the "setInterruptDebounce" is set to 10000ms, every activity is immediately registered and processed in the code there is only one assignment for "_last_interrupt_millis" at line 47 of the node.cpp file, in my opinion this variable must also be updated when processing an interrupt otherwise the query at line 525 "(millis () - _last_interrupt_millis <_interrupt_debounce) "always false and the interrupt is processed
did I miss something?
i use version 1.8 and the door sensor