Add Yandex devices: YNDX-00530, 00531, 00532, 00534, 00535, 00537, 00538 #3999
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed change
Add support for manufacturer-specific features of the following Yandex devices:
(YNDX-00534 and YNDX-00535 wireless switch quirks are only really there for automation triggers' sake)
Additional information
I've used code from Koenkk/zigbee-herdsman-converters#8345 and Koenkk/zigbee-herdsman-converters#9017 as reference for cluster attributes and commands.
Known issues (fixed):
Dimmer is pretty much untested. I'll test it when I have time.Some of the endpoints added in replacement signatures are 'fake' and only work if the device is set into a 'decoupled' mode, if the endpoints are used in HA in any way when the device is not in the 'decoupled' mode, HA hangs until the requests time out.Known issues (wontfix):
SKIP_CONFIGURATION: True
is added to replacement signature, devices don't get stuck in "Configuring" stage, but attribute reporting doesn't workChecklist
pre-commit
checks pass / the code has been formatted using Black