Handle empty alarm list#22
Open
EmTeedee wants to merge 1 commit into
Open
Conversation
nimda2
pushed a commit
to nimda2/ioBroker.divera247
that referenced
this pull request
Jun 22, 2026
When the v2 alarms endpoint returns success but no active (non-archived) alarm, reset the 'alarm' state to false and clear the internal tracking so a previously triggered alarm does not stay stuck. Also warn when the API responds with success=false. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi,
I am an unprivileged user, so as soon as alarms are closed, I don't see anything about them anymore.
The adapter didn't set alarm to false as expected.
A sample return from the API in this case:
The pull request handles an empty items list and just sets the alarm state to false.