Current implementation missed motion events on GK-200MP2-B #159
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
On my camera IN_MODIFY would do the trick. I also added IN_ATTRIB to be able to trigger a motion event with "touch".
flreinhard
force-pushed
the
fix-mqtt-inotify
branch
from
c43ef3f to
9e45ace
Compare
|
Thank you for your pr. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
On my camera IN_MODIFY would do the trick. I also added IN_ATTRIB to be able to trigger a motion event with "touch".
The camera cannot access the internet. Motion events and images are sent to homeassistant via MQTT.