-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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.
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
Spurious warnings regarding linked monitors #3287
Comments
The warning is doing it's job. Telling you that Monitor is an invalid function for this setup. Monitor 1 (the high res) should be NoDect |
Yes, and this is how it is when my "away" running state is set - all low res monitors are MoDect and all high res monitors are NoDect. I only mentioned it because it's not something that was noted in prior versions. I suppose I can adjust my "home" running state for low and high res monitors to "monitor" for those cameras I don't want to be recording in any way.
|
Hmmm...my suggestion of setting both to "monitor" doesn't alleviate the warnings as they're rooted in the fact that there's a linked monitor and of course that's immutable by running state. Any suggestions on clearing up these warnings in my use case? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Describe Your Environment
Describe the bug
Most of my cams are represented as two monitors; one for high res in 'nodect' and one for low res, where analysis is performed, which can be in mode 'modect' or 'monitor'. The high res monitor lists the low res monitor as a linked monitor. The mode for the low res monitor (modect/monitor) is dependent on run state (some cams "idle" when home, all cams "active" when away). Since updating from 1.34.x to 1.36.x, the following warning messages continuously occur:
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Seems to be a new warning as it did not appear at all under the same circumstances in 1.34.x. So I'd expect no warnings.
The text was updated successfully, but these errors were encountered: