-
-
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
Deprecate speed limit lock in Tessie #113848
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.
We have some methods that also check if an entity is used in an automation. I think we use it in lutron
light platform and harmony
switch platform
Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍 |
It would be better to check this when setting up the entity.
|
Thats going to cause an issue to be created for every integration user even if they have never touched the entity. I assume the repair action would be to disable it? Is there an example of where this has been done before because it seems a fair bit more complex to implement. |
Ok ive seen the way |
|
Co-authored-by: G Johansson <goran.johansson@shiftit.se>
Co-authored-by: G Johansson <goran.johansson@shiftit.se>
@@ -72,18 +83,39 @@ async def test_locks( | |||
assert hass.states.get(entity_id).state == STATE_UNLOCKED | |||
mock_run.assert_called_once() | |||
|
|||
|
|||
async def test_speed_limit_lock( |
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.
Could we just add to test that the issues are created correctly?
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.
Done. Sorry for the delay.
Co-authored-by: G Johansson <goran.johansson@shiftit.se>
@gjohansson-ST I think this needs to make it into 2024.5, so can you please review the final changes you requested? |
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.
Approved once CI passes. I hope I did it correctly with the translations links.
Thanks @Bre77 👍
Proposed change
Disables speed limit lock by default and adds a warning message that it will be removed in 2024.11.0
As requested by @frenck
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: