-
-
Notifications
You must be signed in to change notification settings - Fork 145
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
Correctly wait for transitions #510
Conversation
59f358b
to
52275bf
Compare
This reverts commit 3aa2f32.
I seemed to have broken something accidentally so I reverted my change. I will continue in #516. |
last_state_change isn't updated quick enough.
* Change (WIP) * Update test_switch.py * Refactor * Revert "Revert "Small refactor"" This reverts commit 3731c99. * Update README.md * Fix the test * Bump to 1.9.0 (#518) * Basic community fixes PR (#460) * Fixes #423 #423 * Do not adapt lights turned on with custom payloads. * Update switch.py * Issue fixes #423, #378, #403, #449 * quickly test #274 * Revert feature requests, this branch only has fixes. Reverted FR 274 * pre-commit fix * Create automerge.yaml * test * Delete automerge.yaml My bad. * Fix #460 and #408 * see @basnijholt 's comment in #450. * @basnijholt requested changes. --------- Co-authored-by: Bas Nijholt <[email protected]> * Undo accidental changes introduced in #509, but adds the changes from #460 (#521) * Release 1.9.1 (#522) * Bump to 1.9.1 * Add CODEOWNERS --------- Co-authored-by: Benjamin Auquite <[email protected]> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Once this is implemented, I highly recommend changing the default config values. e.g. |
I don't quite see the purpose of this? Once a transition finishes, we're updating the light's state via update_entity to see if it correctly matches the last service data. What more needs to be done? If a light is updated outside of home assistant, update_entity should still refresh its state in HASS. Also the current implementation in this PR passes the |
@basnijholt I moved this here for accessibility: The ONLY possible cases where
Please add to this list if you think of any outstanding issues! |
@basnijholt What is the |
This is really great! Glad you got to the bottom of this 3-year-old bug 😄 I changed the manifest.json version to 1.10.0, such that I can tag a new version right away. |
Can we include #513 and #512 in the release? Having |
I prefer to take it one at the time because those PRs are another 500+ lines of code changes. I also don't have time today to review those anymore :-( |
Good idea! Thank you SO much!! |
@all-contributors please add @th3w1zard1 for bugs |
I've put up a pull request to add @th3w1zard1! 🎉 |
@all-contributors please add @th3w1zard1 for maintenance |
I've put up a pull request to add @th3w1zard1! 🎉 |
This PR changes two things:
cnt_significant_changes
)I've named all the PRs with number headings representing the ascending order they should merge in.
Hope this simplifies the changes a bit as I totally agree that having everything in one PR was a bit too much upkeep.