-
-
Notifications
You must be signed in to change notification settings - Fork 28.5k
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
Add Aquacell integration #117117
base: dev
Are you sure you want to change the base?
Add Aquacell integration #117117
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.
Hello @Jordi1990,
When attempting to inspect the commits of your pull request for CLA signature status among all authors we encountered commit(s) which were not linked to a GitHub account, thus not allowing us to determine their status(es).
The commits that are missing a linked GitHub account are the following:
-
d31c5a29f65544e2547d0357f993719cee722ebb
- This commit has something that looks like an email address (jordi.epema@gmail.com�[2~). Maybe try linking that to GitHub?. -
8ce3b08c3f9a12171a03bfaf5cb76ccf4a40c553
- This commit has something that looks like an email address (jordi.epema@gmail.com�[2~). Maybe try linking that to GitHub?. -
0dcd424b22cd256911e472553f398ad971888d0d
- This commit has something that looks like an email address (jordi.epema@gmail.com�[2~). Maybe try linking that to GitHub?. -
b2c518bfd35918dfcf649c421bfe03e32d36c313
- This commit has something that looks like an email address (jordi.epema@gmail.com�[2~). Maybe try linking that to GitHub?.
Unfortunately, we are unable to accept this pull request until this situation is corrected.
Here are your options:
-
If you had an email address set for the commit that simply wasn't linked to your GitHub account you can link that email now and it will retroactively apply to your commits. The simplest way to do this is to click the link to one of the above commits and look for a blue question mark in a blue circle in the top left. Hovering over that bubble will show you what email address you used. Clicking on that button will take you to your email address settings on GitHub. Just add the email address on that page and you're all set. GitHub has more information about this option in their help center.
-
If you didn't use an email address at all, it was an invalid email, or it's one you can't link to your GitHub, you will need to change the authorship information of the commit and your global Git settings so this doesn't happen again going forward. GitHub provides some great instructions on how to change your authorship information in their help center.
- If you only made a single commit you should be able to run
(substituting "Author Name" and "
git commit --amend --author="Author Name <email@address.com>"
email@address.com
" for your actual information) to set the authorship information. - If you made more than one commit and the commit with the missing authorship information is not the most recent one you have two options:
- You can re-create all commits missing authorship information. This is going to be the easiest solution for developers that aren't extremely confident in their Git and command line skills.
- You can use this script that GitHub provides to rewrite history. Please note: this should be used only if you are very confident in your abilities and understand its impacts.
- Whichever method you choose, I will come by to re-check the pull request once you push the fixes to this branch.
- If you only made a single commit you should be able to run
We apologize for this inconvenience, especially since it usually bites new contributors to Home Assistant. We hope you understand the need for us to protect ourselves and the great community we all have built legally. The best thing to come out of this is that you only need to fix this once and it benefits the entire Home Assistant and GitHub community.
Thanks, I look forward to checking this PR again soon! ❤️
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.
Hello @Jordi1990,
When attempting to inspect the commits of your pull request for CLA signature status among all authors we encountered commit(s) which were not linked to a GitHub account, thus not allowing us to determine their status(es).
The commits that are missing a linked GitHub account are the following:
-
d31c5a29f65544e2547d0357f993719cee722ebb
- This commit has something that looks like an email address (jordi.epema@gmail.com�[2~). Maybe try linking that to GitHub?. -
8ce3b08c3f9a12171a03bfaf5cb76ccf4a40c553
- This commit has something that looks like an email address (jordi.epema@gmail.com�[2~). Maybe try linking that to GitHub?. -
0dcd424b22cd256911e472553f398ad971888d0d
- This commit has something that looks like an email address (jordi.epema@gmail.com�[2~). Maybe try linking that to GitHub?. -
b2c518bfd35918dfcf649c421bfe03e32d36c313
- This commit has something that looks like an email address (jordi.epema@gmail.com�[2~). Maybe try linking that to GitHub?. -
b02c3de21c93f2675a8055ae5ecf35f6926428b1
- This commit has something that looks like an email address (jordi.epema@gmail.com�[2~). Maybe try linking that to GitHub?.
Unfortunately, we are unable to accept this pull request until this situation is corrected.
Here are your options:
-
If you had an email address set for the commit that simply wasn't linked to your GitHub account you can link that email now and it will retroactively apply to your commits. The simplest way to do this is to click the link to one of the above commits and look for a blue question mark in a blue circle in the top left. Hovering over that bubble will show you what email address you used. Clicking on that button will take you to your email address settings on GitHub. Just add the email address on that page and you're all set. GitHub has more information about this option in their help center.
-
If you didn't use an email address at all, it was an invalid email, or it's one you can't link to your GitHub, you will need to change the authorship information of the commit and your global Git settings so this doesn't happen again going forward. GitHub provides some great instructions on how to change your authorship information in their help center.
- If you only made a single commit you should be able to run
(substituting "Author Name" and "
git commit --amend --author="Author Name <email@address.com>"
email@address.com
" for your actual information) to set the authorship information. - If you made more than one commit and the commit with the missing authorship information is not the most recent one you have two options:
- You can re-create all commits missing authorship information. This is going to be the easiest solution for developers that aren't extremely confident in their Git and command line skills.
- You can use this script that GitHub provides to rewrite history. Please note: this should be used only if you are very confident in your abilities and understand its impacts.
- Whichever method you choose, I will come by to re-check the pull request once you push the fixes to this branch.
- If you only made a single commit you should be able to run
We apologize for this inconvenience, especially since it usually bites new contributors to Home Assistant. We hope you understand the need for us to protect ourselves and the great community we all have built legally. The best thing to come out of this is that you only need to fix this once and it benefits the entire Home Assistant and GitHub community.
Thanks, I look forward to checking this PR again soon! ❤️
b02c3de
to
03a448a
Compare
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 @Jordi1990
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!
03a448a
to
72efa0d
Compare
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.
Consider adding tests, which would greatly increase the code quality. I have some examples that are very extendible and work really well :)
Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍 |
Please keep your first PR to only contain 1 platform, so please move the binary sensor to a follow up |
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.
Also, if it's ready for review, please use the button for that
Change sensor entity descriptions
Use icon translations Removed reauth Removed last updated sensor Changed lid in place to binary sensor Cleanup
Fixed sensors not updating properly
Bump aioaquacell
Inlined validate_input method Renaming of entities Do a single async_add_entities call to add all entities Reduced code in try blocks
Cleaned up unused code Removed traces of reauth
Add tests
095897b
to
60a5b84
Compare
@joostlek Ready to review, wasn't sure if you've noticed. |
Oh i did not |
Proposed change
This PR adds the Aquacell integration, which can be used to monitor recent models of the Aquacell water softening device. Useful to monitor the salt levels of the device and track salt consumption over time. The API is reverse engineered from the mobile app.
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: