Update an alarm - a status change, a note, or both
PUT/alarming
Records a status transition as an entry in the alarm's history. An optional note text can be included on that same entry, and a note-only entry (no status change) is also accepted as long as the new status matches the current one. Returns the stored alarm with its complete history, so a caller does not have to read the alarm back to show what was recorded - the entry it contains is the stored one, with the user of the JWT, the server clock and its id. A call that neither changes the status nor carries a note records nothing and returns the alarm unchanged. Responds 404 if the alarm does not exist.
Request
Responses
- 200
- 400
- 401
- 403
- 404
- default
OK
the default error response
Unauthorized — the bearer token is missing, expired or invalid, or carries no role. Errors raised by the security aspects contain an ErrorDto body; requests rejected by the security filter chain may have an empty body.
Forbidden — the authenticated user lacks the required role or access rights.
Entity not found.
the default error response