-
Notifications
You must be signed in to change notification settings - Fork 675
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
Inovelli New Zigbee Dimmer #1435
Conversation
Creating Inovelli Quirk Files for an upcoming release
Creating the Inovelli VZM31-SN Quirk for an upcoming release
Creating Inovelli Quirk Files
Typo identified on Line 30, correcting as required.
Update VZM31-SN.py
Updates to address some validation errors.
Updated for isort
Updated for isort
Updated w/ Black
Updated w/ Black
Update VZM31-SN.py
Removing Line 103 due to flake8 error D211
More format fixes
zhaquirks/inovelli/VZM31-SN.py
Outdated
} | ||
|
||
replacement = { | ||
MODELS_INFO: [("Inovelli", "VZM31-SN")], |
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.
remove this from replacement
zhaquirks/inovelli/VZM31-SN.py
Outdated
ENDPOINTS: { | ||
1: { | ||
PROFILE_ID: zha.PROFILE_ID, | ||
DEVICE_TYPE: DeviceType.DIMMABLE_LIGHT, |
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.
@Adminiuga should we map DeviceType.DIMMER_SWITCH
to the light platform so that quirks don't have to change the device type like this?
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.
PLEASE do. In development of this device I had to override in the very beginning to even get any dim levels. All dimmers need 0-100% brightness_pct attribute, etc, as provided by the light domain.
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.
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.
@kreene1987 what kind of dimmer is it? two gang or single gang?
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.
isn't
DeviceType.DIMMER_SWITCH
a "remote" device? Device really should report itself as "Dimmable_Light".
Check Section 7.5.5 of Zigbee HA Profile, document 05-3520-29. DIMMER_SWITCH is mandated to have client on/off, level control and identity clusters.
Great point. I didn’t check this before hand.
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.
If it is a single gang device, then the endpoint id 1 should be of a DIMMING_LIGHT device type, and the 2nd endpoint should be of a DIMMER_SWITCH device type. Similar to how GE46857 implemented it, none of the others got it right.
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.
Similar to how GE46857 implemented it, none of the others got it right.
Can you link me to where this quirk is stored? I couldn't find GE or Jasco as a manuf in the quirks folder.
We'll get right on it for testing.
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.
Why not change the firmware of the device so that it reports itself as the correct device types? You can do it with a quirk but if you can change the firmware to be more accurate it may help other platforms as well.
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.
Yes, I meant that the correct fix is to update the device firmware. There's no quirk for GE 45857, but you can find signature in https://github.com/home-assistant/core/blob/bc194cd209d4261bf7e15aa89eac09be5685c3db/tests/components/zha/zha_devices_list.py#L1674
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.
Why not change the firmware of the device so that it reports itself as the correct device types? You can do it with a quirk but if you can change the firmware to be more accurate it may help other platforms as well.
Thanks for the feedback all, we will discuss with the engineer.
@InovelliUSA I believe you need to remove the - from the file name as well |
Thanks, we will check it out. |
Updating per recommended changes
Update parameter for firmware 9
Update for firmware v9
Update with second signature depending on firmware.
Swapping v9 class to topmost.
Updates per review recommendations
Format fix
Update VZM31SN.py
Update deprecated command
Update ordering of imports for isort
Update __init__.py
Update __init__.py
Syntax changes to resolve test failures
Update __init__.py
Update __init__.py
Removed unused imports and corrected / from naming
Update __init__.py
Codecov Report
@@ Coverage Diff @@
## dev #1435 +/- ##
==========================================
- Coverage 80.47% 80.35% -0.12%
==========================================
Files 225 229 +4
Lines 6505 6827 +322
==========================================
+ Hits 5235 5486 +251
- Misses 1270 1341 +71
Continue to review full report at Codecov.
|
Pull Request Test Coverage Report for Build 2258930270
💛 - Coveralls |
Additional Parameter added
Update __init__.py
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.
Thanks for the PR!
We've recently restructured our ZCL command and attribute definitions to hold more information. Could you make some changes to ensure this PR can be merged?
Updated for v10 firmware changes
Syntax updates and v10 firmware changes
@puddly I believe the most recent update should have the requested changes covered if you're able to confirm? |
Parameter size change with v10 firmware
Update parameter size w/ v10 firmware
Prepping files for the release of our new zigbee dimmer.