You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Add _TZ3000_k6fvknrr support (double_power_point_2) and curtain_motor Open/Stop/Close control - #1437
Adds manufacturer ID _TZ3000_k6fvknrr to the double_power_point_2 driver. This hardware revision (productId TS011F) reports its Zigbee interview as a two-endpoint on/off device (endpoint 1: [0,3,4,5,6,57344,57345], endpoint 2: [4,5,6,57345]) with no standard metering clusters (1794/2820), so it was matched against the driver whose endpoint cluster requirements are an actual subset of what the device reports, rather than smartplug or plug.
Adds opt-in Open/Stop/Close control to the curtain_motor driver, using the "V2" Tuya datapoint schema's state DP (dp1: 0=OPEN, 1=STOP, 2=CLOSE). This is gated behind a new has_state setting (default off) since not all devices on this driver support the DP — it adds/removes the windowcoverings_state capability at runtime and fails silently (logged, not thrown) if the device ignores the command.
Test plan
homey app validate --level publish passes
Installed and paired a physical device with manufacturer ID _TZ3000_k6fvknrr under double_power_point_2 — on/off works for both sockets
Enabled has_state on a real curtain_motor device — Open/Stop/Close buttons work as expected
The physically verified _TZ3000_k6fvknrr / TS011F double-power-point identity has now been selectively adopted onto modernize-2026-issues and passes the current validation suite. I am leaving this PR open because the separate curtain_motor Open/Stop/Close behavior has not been adopted; that part needs its own review so we do not couple an identity-only fix to a behavioral change. Tracking: #1469, draft integration PR: #1470.
2026 triage complete. The physically verified _TZ3000_k6fvknrr / TS011F double-socket identity has already been selectively adopted into modernize-2026-issues. The separate curtain Open/Stop/Close work is valid protocol work, but belongs in the shared curtain-family review rather than this mixed PR. It is now preserved with evidence and acceptance criteria in #1472. Closing this historical mixed PR without losing the unresolved curtain work.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
Summary
_TZ3000_k6fvknrrto thedouble_power_point_2driver. This hardware revision (productIdTS011F) reports its Zigbee interview as a two-endpoint on/off device (endpoint 1:[0,3,4,5,6,57344,57345], endpoint 2:[4,5,6,57345]) with no standard metering clusters (1794/2820), so it was matched against the driver whose endpoint cluster requirements are an actual subset of what the device reports, rather thansmartplugorplug.curtain_motordriver, using the "V2" Tuya datapoint schema'sstateDP (dp1:0=OPEN, 1=STOP, 2=CLOSE). This is gated behind a newhas_statesetting (default off) since not all devices on this driver support the DP — it adds/removes thewindowcoverings_statecapability at runtime and fails silently (logged, not thrown) if the device ignores the command.Test plan
homey app validate --level publishpasses_TZ3000_k6fvknrrunderdouble_power_point_2— on/off works for both socketshas_stateon a realcurtain_motordevice — Open/Stop/Close buttons work as expected