MQTT: Birdseye enabled/disabled and mode change support #8291
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.
Added two new MQTT topics for adjusting the enabled/disabled state per camera as well as the mode.
This is in draft as there are a few things I'm not a big fan of. This is most likely due to my lack of python experience.
BirdseyeModeEnum
is a string and camera metrics are using multiprocessing ctypes to sync data between processes. I hacked in an integer based index for support. You probably have a better idea of how this should be done.last_active_frame
wouldn't get cleared. So there is some logic to zero out the last active frame which works... But is this how it should be done? https://github.com/blakeblackshear/frigate/compare/dev...sberryman:frigate:sberryman/mqtt-birdseye-mode?expand=1#diff-032726a7034bcbf31b308cd4452c695b71839494197d463764e5389604af23efR590-R596This is a solution for issue #3244