-
-
Notifications
You must be signed in to change notification settings - Fork 33.9k
Bump pyvera to 0.3.16 #146089
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
Bump pyvera to 0.3.16 #146089
Conversation
Update vera integration with the latest pyvera package
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.
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!
Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍 |
Please run |
Tests pass when run locally - both test/components/vera/*.py (that I potentially touched) and tests/components/recorder/test_purge.py (that failed in the PR build). The failed test failed because of insufficient (?) timeout (or just slower agent VM). |
Tests have passed now... I suggest to not touch the PR anymore 😃 |
Proposed change
Vera integration to support dual setpoint thermostats.
maximvelichko/pyvera#159
maximvelichko/pyvera@0.3.15...0.3.16
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
.To help with the load of incoming pull requests: