This should resolve the hassfest CI errors and the nice benefit is that lock-manager is guaranteed to load after either integration (dependencies are for integrations that must be enabled and available for the integration to load, after_dependencies will wait for integrations that are listed to be available if they are enabled before loading this integration).
I haven't looked too deeply into the automations that you have set up to enable and disable alerting but this should make it easier to remove that extra logic.
Type of change
[ ] Dependency upgrade
[x] Bugfix (non-breaking change which fixes an issue)
[x] New feature (which adds functionality)
[ ] Breaking change (fix/feature causing existing functionality to break)
[ ] Code quality improvements to existing code or addition of tests
Talked to @firstof9 - this is already fixed in the new repo, so withdrawing. I will keep my other PR open here for visibility and resubmit in the new repo when ready
Proposed change
This should resolve the
hassfest
CI errors and the nice benefit is thatlock-manager
is guaranteed to load after either integration (dependencies
are for integrations that must be enabled and available for the integration to load,after_dependencies
will wait for integrations that are listed to be available if they are enabled before loading this integration).I haven't looked too deeply into the automations that you have set up to enable and disable alerting but this should make it easier to remove that extra logic.
Type of change
Additional information