fix: fix grid_status #466
Merged
fix: fix grid_status #466
Conversation
This file contains 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
ericdegroot
changed the title
|
Thanks! |
alandtse
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I recently had a Powerwall 3 installed, and I have no local API access. I'm using Tesla Custom Integration to integrate the battery into my Home Assistant setup via the owner cloud. The grid status binary sensor provided by that integration always inaccurately showed as 'Clear' or
off. I traced this back to thePowerwallSite.grid_statusproperty in this project. Changing this property to lookup the value inself._site_datainstead ofself._site_summaryfixed the issue for me. Your test mock data suggests that site data was always the correct source, but I do not have access to any other powerwalls to see if this is unique to Powerwall 3 cloud access.