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
The Radar motion detection module seems to call when_activated and when_deactivated over and over, many times per second, spamming the device API with updates. obviously, this is bad.
I have almost no idea why this could be happening, aside from perhaps loose pins on the detector, or perhaps a defective detector. The status light that is directly tied into the radar detector's output pin lights up consistently though, and does not flash. Though, it may not be flashing because the updates happen so frequently. Perhaps some kind of visual or audible cue that a network request is being made will make diagnosing easier.
It is possible that the DitigalInputDevice class from GPIOZero repeats back and fourth between the active and inactive state, causing the methods to be called repeatedly. Other classes in GPIOZero have the capability of ignoring subsequent requests of the same type. See Button and DigitalInputDevice
The text was updated successfully, but these errors were encountered:
The Radar motion detection module seems to call
when_activated
andwhen_deactivated
over and over, many times per second, spamming the device API with updates. obviously, this is bad.I have almost no idea why this could be happening, aside from perhaps loose pins on the detector, or perhaps a defective detector. The status light that is directly tied into the radar detector's output pin lights up consistently though, and does not flash. Though, it may not be flashing because the updates happen so frequently. Perhaps some kind of visual or audible cue that a network request is being made will make diagnosing easier.
It is possible that the
DitigalInputDevice
class fromGPIOZero
repeats back and fourth between the active and inactive state, causing the methods to be called repeatedly. Other classes in GPIOZero have the capability of ignoring subsequent requests of the same type. See Button and DigitalInputDeviceThe text was updated successfully, but these errors were encountered: