Remove `zwave` and `ozw` integration support

[raman325]

Breaking change

Removes zwave and ozw support from the integration.

Proposed change

Type of change

• [ ] Dependency upgrade
• [ ] Bugfix (non-breaking change which fixes an issue)
• [ ] New feature (which adds functionality)
• [ ] Breaking change (fix/feature causing existing functionality to break)
• [x] 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:

[codecov-commenter]

Codecov Report

Merging #277 (598f628) into main (05d6d37) will decrease coverage by 4.91%. The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #277      +/-   ##
==========================================
- Coverage   89.06%   84.14%   -4.92%     
==========================================
  Files          10       10              
  Lines        1088      801     -287     
==========================================
- Hits          969      674     -295     
- Misses        119      127       +8     

Impacted Files	Coverage Δ
custom_components/keymaster/binary_sensor.py	80.24% <ø> (-2.72%)	:arrow_down:
custom_components/keymaster/config_flow.py	92.47% <ø> (-3.28%)	:arrow_down:
custom_components/keymaster/const.py	100.00% <ø> (ø)
custom_components/keymaster/helpers.py	76.08% <ø> (-12.12%)	:arrow_down:
custom_components/keymaster/services.py	73.33% <ø> (-12.47%)	:arrow_down:
custom_components/keymaster/__init__.py	89.16% <100.00%> (-1.39%)	:arrow_down:
custom_components/keymaster/sensor.py	95.91% <100.00%> (ø)
custom_components/keymaster/exceptions.py	87.50% <0.00%> (-12.50%)	:arrow_down:
... and 3 more

[firstof9]

Tested the changes locally, and they do work.

[raman325]

@firstof9 thanks for adding the tests, clearly never got a chance to do it

[rcdailey]

I saw this in the release notes and grew concerned:

• No reference from the release notes to documentation explaining how this is a breaking change or what manual actions I need to take (unless I missed it)
• Does this mean I can't use my Schlage Smart Deadbolt anymore (since it's zwave; provided via the zwavejs2mqtt plugin)?

[raman325]

I saw this in the release notes and grew concerned:

• No reference from the release notes to documentation explaining how this is a breaking change or what manual actions I need to take (unless I missed it)
• Does this mean I can't use my Schlage Smart Deadbolt anymore (since it's zwave; provided via the zwavejs2mqtt plugin)?

Locks using zwave_js will still work. Newer version of HA don't have the zwave or ozw integrations, so we got rid of the corresponding code. It's listed as a breaking change because it was worth highlighting, but it's not really a breaking change since keymaster is now pinned to versions of HA that no longer have those integrations anyway

[Monkey-Shiner]

I saw this in the release notes and grew concerned:

• No reference from the release notes to documentation explaining how this is a breaking change or what manual actions I need to take (unless I missed it)
• Does this mean I can't use my Schlage Smart Deadbolt anymore (since it's zwave; provided via the zwavejs2mqtt plugin)?

Locks using zwave_js will still work. Newer version of HA don't have the zwave or ozw integrations, so we got rid of the corresponding code. It's listed as a breaking change because it was worth highlighting, but it's not really a breaking change since keymaster is now pinned to versions of HA that no longer have those integrations anyway

Thank you for the clarification!

[lishan89uc]

HAHAHAHA YOU scared the **** out of me ROFL!!!!! I thought my beautiful fe 599 will no longer work LOL!!!!