-
-
Notifications
You must be signed in to change notification settings - Fork 31.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update powerwall for tesla_powerwall 0.5.0 which is async #107164
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @bubonicbob
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!
Hey there @bdraco, @jrester, @daniel-simpson, mind taking a look at this pull request as it has been labeled with an integration ( Code owner commandsCode owners of
|
Since I don't have a powerwall, I need some help to update the fixture data so that the tests will pass. I saw these samples from a similar project but still the powerwall firmware is a few years old. Also accepting donations to get my own powerwall(s)! 💰 |
I have power walls and I have access to 5 powerwall sites as well so I will test this throughly before merging |
This comment was marked as outdated.
This comment was marked as outdated.
I fixed the cookie authentication and improve the error reporting a bit Everything seems to be working now |
Pushing to a production system for additional testing |
One system went well The other one had the order of the serial numbers change so it generated a new unique id and all new entities |
I don't think there is anything we can do about the unique id order without doing the migration first |
In the future, is there an official way to request that a CI be started? According to the process, I should wait to click the "ready for review" until after CI has passed. |
Once we accept a PR and merge, you won't have to ask for the CI to be started anymore |
Need to check if that config flow line is covered, config flows are supposed to have 100% coverage before merging, but if it's existing we can override it |
Missing coverage is new on the config flow so we do need to fix that |
before
after
|
Hmm, all but one are technically new uncovered lines of code but I'd have to think about how to even test them. They all have to do when a sensor meter isn't available. Perhaps the code should make more usage of |
I'll take care of the sensor tests |
I took care of the config flow test as well. I didn't think it was fair to ask you to do that since the coverage wasn't great for that in the first place |
Also if you like, you should add yourself to |
I am updating the other sites now
|
Oh thank you! My partner is giving me sideways glances how much time I'm spending on this anyhow. 👀 |
I might have to hold off on that until the day I get my own powerwall. It was a big productivity limitation for me on this and made it much harder to understand the HA portion of the code. |
Looks like we have an exception trap missing somewhere
|
testing
|
No worries. I'll take care of any issues that pop up from the change. Great first contribution by the way. Most people usually start off working on a device they own 🚀 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @bubonicbob
All you integration owners deserve thanks for maintaining this awesome HA system. 👏 |
Everything working well on all 5 sites. Will merge is CI gives us a 👍 |
Proposed change
Updates the tesla-powerwall library to 0.5.0 and therefore requires a few async updates to the component.
changelog: jrester/tesla_powerwall@v0.4.0...v0.5.0
Type of change
Additional information
Checklist
ruff format homeassistant tests
)If user exposed functionality or configuration variables are added/changed:
If the code communicates with devices, web services, or third-party tools:
Updated and included derived files by running:
python3 -m script.hassfest
.requirements_all.txt
.Updated by running
python3 -m script.gen_requirements_all
..coveragerc
.To help with the load of incoming pull requests: