-
-
Notifications
You must be signed in to change notification settings - Fork 35.5k
Implement support for additional ecobee hold modes #40520
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
Conversation
Hi @jamincollins, 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! |
Hi @jamincollins, 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! |
463e1e8
to
a6c9ef4
Compare
@jamincollins The functionality of this PR looks good to me. You will need to fill out the PR template properly however and describe what it is that this PR is intended to achieve in order for a HA dev to merge it. |
@marthoc I've left items of the PR template at default that didn't seem to make sense or apply. For instance, am I suppoed to do anything with the Additional Information section? It doesn't seems to have anything that applies to this PR. Also on the  Local tests pass. Your PR cannot be merged unless tests pass** checkbox, the local unit tests don't pass, several (unrelated to this change) fail. So, if you can be more specific about what in the PR template needs to be filled out or corrected, I'd be happy to correct it. |
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.
Seems good to me.
@jamincollins I think the best bet would just be to go check all of the boxes under checklist and hope for the best. I have literally no idea, but that's my only thought. I'm really excited for this to get merged :) |
I think this needs to be labeled a breaking change since we used fixed behavior before and will now use the configured device behavior. Please update the description or explain if otherwise. |
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.
Please see comments above
At least in my experience, it's actually the opposite: ecobee isn't respecting settings that hass sets and automatically reverts the hold settings based on some weird interaction of user settings related to hold action and scheduling. I know people are wanting this for different reasons, but I can at least say that the current behavior I feel is "broken" for me, because I've only managed to get to the point where hass changes are applied for 24 hours max. To be clear, I just want to make understanding clear -- code changes are code changes, and I agree in marking it as breaking (but at least, breaking it in a useful way). |
I'll change the description, but as @hakusaro has indicated the current implementation being static is broken. This largely corrects that. |
I can agree with that perspective, however we should still mark it as a breaking change since some users are going to be expecting the broken behavior. |
Waiting on second opinion before making the requested changes. |
The hold mode not being settable and defaulting to holding until next schedule change has been broken for almost 2 years now. Hoping that this gets fixed soon. |
Since ecobee auth broke for everybody due to an unrelated issue, approximately two weeks ago, maybe we can just ship this?We can mark it as a breaking change, etc. Notationally it doesn't matter. I was just pointing out that it's more urgent because the current behavior is defective. |
FYI: I'm going to be switching to Nest Thermostat E soonish (3-5 days). If any developer/contributor wants an Ecobee Lite3, I'd be happy to help get it into the hands of someone who wants to use it for development purposes. I can send my entire account too, if anyone wants to fiddle with temperature sensors (no guarantees that the two I have can be re-paired -- I'm pretty sure the answer is no, so I can just send my entire account instead). |
I've updated the text so its mergeable and will be seen in the release notes. Once PR is rebased (https://developers.home-assistant.io/docs/development_catching_up/) to fix the conflict, this should be good to merge. |
@hakusaro I would happily take your hardware to use it to test! Thanks for the offer. |
@marthoc you can email me at argo at hey dot com (from your github profile email) and we can see if this is the right way to go :) |
b0c1639
to
03d53b9
Compare
* useEndTime2hour - 2 hours * useEndTime4hour - 4 hours * indefinite - Until I change it These changes have been tested with an ecobee3 lite running firmware version 4.5.81.200 Signed-off-by: Jamin W. Collins <[email protected]>
@bdraco should be good to go now |
* 'dev' of https://github.com/home-assistant/core: (98 commits) Bump pymyq to 2.0.13 (home-assistant#44961) Add zwave to ozw migration (home-assistant#39081) Add pressure forecast to HA weather entity model (home-assistant#44965) Deduplicate MQTT entity discovery code (home-assistant#44970) Fix parameters when toggling light (home-assistant#44950) Move MQTT entity helpers to separate file (home-assistant#44838) Helpers type hint improvements (home-assistant#44964) Remove script/test (home-assistant#44967) Add MQTT Number (non optimistic) (home-assistant#44883) Fix Netatmo climate boost for valves (home-assistant#44957) Disambiguate Supervisor HTTPUnauthorized on user/password validation (home-assistant#44940) Add torrent id to Transmission events (home-assistant#44187) Prefix versions in system health (home-assistant#44921) Fix media renderers without volume control (home-assistant#44874) Fix wait_template incorrectly matching falsey values (home-assistant#44938) Upgrade youtube_dl to 2021.01.03 (home-assistant#44942) Upgrade discord.py to 1.6.0 (home-assistant#44941) Fix KNX cover state return open when unknown (home-assistant#44926) Use parent_id to find cause of logbook events with new contexts (home-assistant#44416) Implement support for additional ecobee hold modes (home-assistant#40520) ...
Breaking change
The current state of the ecobee integration always behaves as if the selected hold duration is Until next scheduled activity.
With this change the following settings are now respected:
Users relying on the previous behavior may need to update their automations to account for the support for the new settings.
Proposed Change
The ecobee thermostat has 5 different hold duration settings that a user can specify either on the unit itself or through the ecobee application. These are:
Leaving only Ask every time not implemented, which retains the existing behavior of Until next scheduled activity.
Type of change
Checklist
black --fast 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
.The integration reached or maintains the following Integration Quality Scale:
To help with the load of incoming pull requests: