You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug] Disabled notification alerts are reported as diagnostic failures #29
@stephenjharrington, fixed in v1.6.2. The diagnostic buttons were sending their display labels instead of the API commands, so every test was rejected before it ran. Individual tests and Run All Tests now call the right checks.
Install it from Settings > Updates without recreating your container. Notification tests still send sample alerts through configured destinations, and delivery can fail if a destination isn't configured or reachable.
Thanks @CoderLuii , updated to 1.6.2 and now only 3 out of 10 tests "fail".
Upon further examination it looks like it's because I have those 3 items diabled in Alerts.
I was on "Balanced" Alerts. If I change to "Everything" Preset then all the tests pass!
Perhaps for Alerts that are disabled, the corresponding Diagnostics test should either be greyed out and/or disabled, rather than saying it failed, which is a bit misleading?
@stephenjharrington, fixed in v1.6.3. Disabled notification tests now show Skipped, with a reason and a separate count. They do not send a sample. You can keep Balanced selected; its three disabled alerts no longer count as failures.
Tests respect the checked DVR's effective settings, including per-DVR overrides. Tested DVR shows which server was checked. Genuine connection and delivery errors still show as failures.
Install from Settings > Updates without recreating your container. Thanks for catching the misleading results.
@stephenjharrington, here's the before/after comparison with demo data: 7 passed, 3 failed becomes 7 passed, 0 failed, 3 skipped. The three disabled alerts stay disabled and are no longer counted as failures.
Activity
CoderLuii commentedon Oct 26, 2026
@stephenjharrington, fixed in v1.6.2. The diagnostic buttons were sending their display labels instead of the API commands, so every test was rejected before it ran. Individual tests and Run All Tests now call the right checks.
Install it from Settings > Updates without recreating your container. Notification tests still send sample alerts through configured destinations, and delivery can fail if a destination isn't configured or reachable.
v1.6.2 release notes
stephenjharrington commentedon Oct 27, 2026
Thanks @CoderLuii , updated to 1.6.2 and now only 3 out of 10 tests "fail".
Upon further examination it looks like it's because I have those 3 items diabled in Alerts.
I was on "Balanced" Alerts. If I change to "Everything" Preset then all the tests pass!
Perhaps for Alerts that are disabled, the corresponding Diagnostics test should either be greyed out and/or disabled, rather than saying it failed, which is a bit misleading?
[-][Bug]:[/-][+][Bug] Disabled notification alerts are reported as diagnostic failures[/+]CoderLuii commentedon Oct 27, 2026
@stephenjharrington, fixed in v1.6.3. Disabled notification tests now show Skipped, with a reason and a separate count. They do not send a sample. You can keep Balanced selected; its three disabled alerts no longer count as failures.
Tests respect the checked DVR's effective settings, including per-DVR overrides. Tested DVR shows which server was checked. Genuine connection and delivery errors still show as failures.
Install from Settings > Updates without recreating your container. Thanks for catching the misleading results.
v1.6.3 release notes
CoderLuii commentedon Oct 27, 2026
@stephenjharrington, here's the before/after comparison with demo data: 7 passed, 3 failed becomes 7 passed, 0 failed, 3 skipped. The three disabled alerts stay disabled and are no longer counted as failures.
stephenjharrington commentedon Oct 27, 2026
Have updated to 1.6.3 and tested/verified fixes.
Great work @CoderLuii , thanks again!