The unknown, critical & warning status is not se for the general API HTTP request. They are only set on login. So when token has a valid validation date in the statefile but is not more valid (because retired) the other checks doesn't terminate before validating their data.
During a firmware upgrade the token saved in the statefile will not be valid anymore even it should by validation date. In this case the user must find the statefile an delete it to force a new login.
Fixes # (issue)
With a simple clean of the token and a retry we can retry ones with a new login. On this retry we can set the http-status parameter so when the retry fails the check will be aborted with a status error.
Type of change
[x] Patch fixing an issue (non-breaking change)
[ ] New functionality (non-breaking change)
[ ] Functionality enhancement or optimization (non-breaking change)
[ ] Breaking change (patch or feature) that might cause side effects breaking part of the Software
Community contributors
Description
Fixes # (issue) With a simple clean of the token and a retry we can retry ones with a new login. On this retry we can set the http-status parameter so when the retry fails the check will be aborted with a status error.
Type of change