[WWSTCERT-13446, WWSTCERT-13450, WWSTCERT-13454, WWSTCERT-13458] SONOFF/SWV1C - #3157
[WWSTCERT-13446, WWSTCERT-13450, WWSTCERT-13454, WWSTCERT-13458] SONOFF/SWV1C#3157yanggx24 wants to merge 7 commits into
Conversation
| [capabilities.valve.ID] = { | ||
| [capabilities.valve.commands.open.NAME] = valve_open_handler, | ||
| [capabilities.valve.commands.close.NAME] = valve_close_handler, | ||
| } | ||
| }, |
There was a problem hiding this comment.
Did You check if Your device works with the zigbe-valve driver default handling ? (without this custom handling)
| [OnOff.ID] = { | ||
| [OnOff.attributes.OnOff.ID] = onoff_attr_handler | ||
| }, |
There was a problem hiding this comment.
Did You check if Your device works with the zigbe-valve driver default handling ? (without this custom handling)
|
Duplicate profile check: Passed - no duplicate profiles detected. |
|
Profile category check: ✅ Passed - all profiles have a category defined. |
|
Invitation URL: |
|
zigbee-valve_coverage.xml
Minimum allowed coverage is Generated by 🐒 cobertura-action against 30cf526 |
Test Results 73 files 543 suites 0s ⏱️ For more details on these errors, see this check. Results for commit 30cf526. ♻️ This comment has been updated with latest results. |
|
Thanks for the review. Yes, I checked this behavior with the SONOFF SWV1C device. The device uses the Zigbee OnOff cluster for valve control and reports the valve state through the OnOff attribute. The custom handlers were added to explicitly map:
This is also needed because the device reports the OnOff value as I can also re-test without the custom handlers and confirm whether the default zigbee-valve handling covers this device correctly. |
Has this implementation been tested with the valve left open for longer than ten minutes? Several Hydro ONE users have reported that the valve closes itself after approximately ten minutes because of its device-side manual watering duration. From the current PR, it appears that Open only sends the standard Zigbee On command and does not read or update the SONOFF Could you confirm whether the tested devices remained physically open beyond ten minutes, and which model and firmware version were used? It would also be useful to know whether newer firmware has removed the default limit or whether the WWST integration is expected to configure |
|
To make it clear: the valve won't stay open for longer than 10 minutes, even when it was opened "manually" (Zigbee On command)? |
Yes. |
| sub_drivers = require("sub_drivers"), | ||
| health_check = false, | ||
| shared_device_thread_enabled = true, |
There was a problem hiding this comment.
Add the new sonoff subdriver to the sub_drivers.lua file in this driver and use lazy loading.
| health_check = false, | ||
| shared_device_thread_enabled = true, |
|
@yanggx24 Please update Your branch. |
I have merged the latest code, is there anything else missing? |
|
@KKlimczukS Hello,what else do I need to do? |
|
I have updated the branch with the Sonoff sub-driver lazy-loading changes, synchronized it with the latest main, and added the coverage test fix. The device was tested with SONOFF SWV1C firmware v1.1.0. The 10-minute automatic shutoff is device-side behavior, and the private 0xFC11/0x501D support is outside this WWST certification PR. Could you please re-review the latest commit and let me know if any blocking changes remain? |
I think this PR should include the changes required to configure private attributes if that's the plan for later. |
|
Thanks for the feedback. I’d prefer to keep this PR limited to SWV1C. SWV2C is a different hardware product, maintained by a different developer, and its development timeline is separate from SWV1C. There is already a dedicated PR for SWV2C, so I don’t think it would be appropriate to merge the two devices into this submission. The current SWV1C PR also does not include any private-attribute or custom-capability support. I would like to keep it that way. Private-attribute support is not part of this WWST submission. This is also consistent with the SmartThings PR guidance, which does not allow custom Capabilities for WWST submissions and may reject drivers using custom Zigbee, Z-Wave, or Matter clusters:
For these reasons, I suggest keeping this PR focused on the standard SWV1C implementation, while handling SWV2C and any future private-attribute support separately. |
Check all that apply
Type of Change
Checklist
Description of Change
Summary of Completed Tests