fix(type3): prevent invalid history response in GetStateAlarmFromHistory#15
Open
Heliospeed wants to merge 1 commit intoXav-74:betafrom
Open
fix(type3): prevent invalid history response in GetStateAlarmFromHistory#15Heliospeed wants to merge 1 commit intoXav-74:betafrom
Heliospeed wants to merge 1 commit intoXav-74:betafrom
Conversation
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.
Cette PR corrige un problème rencontré lors de l’exécution du cron de
rafraîchissement de l’historique pour les alarmes Verisure de type 3.
Dans certains cas, l’API Verisure retourne une réponse invalide ou incomplète
Cela provoquait les erreurs suivantes dans Jeedom :
Cette correction est juste en prévention et n'entraîne pas de changement fonctionnel en dehors de la suppression de ces erreurs.