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.
Come ben descritto nell'issue #73, questa PR risolve il problema verificatosi a fine anno.
Il problema si manifesta l'ultimo giorno del mese (per dicembre, il 31) in questa porzione di codice:
pun_sensor/custom_components/pun_sensor/coordinator.py
Lines 180 to 192 in dcdae92
Avendolo modificato nella commit bf13936 (rispetto alla precedente 1630326) per scaricare i dati del giorno successivo (PUN orario e prezzo zonale), il giorno successivo del 31/12 è il 01/01 che quindi modifica il mese di
date_startperdendo tutto lo storico dei prezzi del mese di dicembre. Infatti nel log si notano pochissimi file XML:Questo è chiaramente errato e viene sistemato da questa PR.