Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[BUG] MQTT messages are sent for one camera and not the other. #125

Closed
cjackson234 opened this issue Oct 13, 2021 · 3 comments
Closed

[BUG] MQTT messages are sent for one camera and not the other. #125

cjackson234 opened this issue Oct 13, 2021 · 3 comments
Labels
bug Something isn't working

Comments

@cjackson234
Copy link

Describe the bug
MQTT messages are sent for one camera and not the other. The detection event shows in the UI and is marked as the correct person.

Version of Double Take
v1.4.0-cf68a1a:latest

Expected behavior
MQTT messages are always sent

Hardware

  • OS: Unraid
  • Browser Chrome

Additional context
The only difference I can see is that one camera is 1080p and the other is 2688x1520
@cjackson234 cjackson234 added the bug Something isn't working label Oct 13, 2021
@cjackson234 cjackson234 changed the title [BUG] [BUG] MQTT messages are sent for one camera and not the other. Oct 13, 2021
jakowenko added a commit that referenced this issue Oct 13, 2021
@jakowenko
fix(api): publish camera mqtt topic for misses (#125)
cb3fb22
@jakowenko
Copy link
Owner

Hey @cjackson234, thanks for catching this. Guess it's something that I've overlooked since the beginning.

It appears if the result had no matches, no unknown, but misses, then MQTT topic wouldn't be updated. I have a fix for that I'll test on the beta build tonight and release v1.4.1 shortly after.

Misses are anything that has a confidence > detect.unknown.confidence value which defaults to 40, basically these are the images that aren't good enough to be considered a match, but aren't bad enough to be an unknown.

jakowenko added a commit that referenced this issue Oct 13, 2021
@jakowenko
chore(release): 1.4.1 [skip ci]
a4616bb 
## [1.4.1](v1.4.0...v1.4.1) (2021-10-13)

### Bug Fixes

* account for misses in camera person count ([561ec5c](561ec5c))
* **api:** publish camera mqtt topic for misses ([#125](#125)) ([cb3fb22](cb3fb22))
* **api:** save latest images for misses ([62f586c](62f586c))
* **ui:** don't show update icon if last run was from CodeQL ([8d258ea](8d258ea))
@jakowenko
Copy link
Owner

This should be fixed now in release v1.4.1. Let me know if it resolves your issue.

@cjackson234
Copy link
Author

I also had to update the detect > match > min_area, but all seems to be working!

Thank you so much for all your hard work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jakowenko @cjackson234