We only did discovery for the key at setup time. If it changed, a reload of the integration was needed to update the key. We now update it every time we update the lock detail.
Type of change
[ ] Dependency upgrade
[x] Bugfix (non-breaking change which fixes an issue)
[ ] New integration (thank you!)
[ ] New feature (which adds functionality to an existing integration)
[ ] Deprecation (breaking change to happen in the future)
[ ] Breaking change (fix/feature causing existing functionality to break)
[ ] Code quality improvements to existing code or addition of tests
Additional information
This PR fixes or closes issue: fixes #
This PR is related to issue: #116855
Link to documentation pull request:
Checklist
[x] The code change is tested and works locally.
[ ] Local tests pass. Your PR cannot be merged unless tests pass
Proposed change
We only did discovery for the key at setup time. If it changed, a reload of the integration was needed to update the key. We now update it every time we update the lock detail.
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: