radar based motion detection rapidly calls both activate and deactivate. #3
Labels
No labels
bug: confirmed
bug: unconfirmed
documentation
duplicate
enhancement
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
kerrishaus/portal-rpi#3
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The Radar motion detection module seems to call
when_activatedandwhen_deactivatedover 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
DitigalInputDeviceclass fromGPIOZerorepeats 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