Repository navigation
feat(0.4): three exact standard IAS contacts (#1013) - #1509
Merged
Merged
Conversation
JohanBendz
marked this pull request as ready for review
October 3, 2026 23:19
This was referenced Oct 3, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Coding lane, canonical #1013 (physical #1143 / #868)
Three separate exact Homey Compose profiles, independently physically interviewed:
eWeLink / SNZB-04Standard IAS contact + Power profile — four eWeLink/Tuya/zbeacon exact pairs, per-device status #1013 (EP1 Basic0/Power1/Identify3/PollControl32/IAS Zone1280, battery hardware provisionalOTHER). This responds to community demand for use in the Tuya Zigbee app, while explicitly acknowledging overlapping support in separate Sonoff Zigbee app; no broadeWeLinkinjection into frozen legacydoorwindowsensorCartesian multi-ID matcher._TZ3000_x8q36xwf / TS0203ELIVCO Device Request - [Door Window Sensor] - [ELIVCO] / [TS0203] #1143 (same standard IAS+Power+PollControl shape; battery type/count unprovenOTHER; external 63-minute false-close is a specific >70-minute PUBLIC 0.4 Test check, not an assumed upstream bug)._TZE200_n8dljorx / TS0601Device Request - Door/window sensor - _TZE200_n8dljorx /TS0601] #868 (physical standard IAS+Power WITHOUT PollControl or EF00, original reporter explicitly calls CR2032).zbeacon / DS01(#832) is already exact-present in frozen/0.4doorwindowsensor_4and is preserved as a separate existing-driver physical regression gate, NOT added again.New narrow local standard-ZCL runtime in first profile, imported by other two, handles only IAS
alarm_contact/alarm_batterywith partial flag guards, reactive IAS Zone Enroll fallback and valid standard half-percent battery reports. No manufacturer/DP handler, no startup polling/writes, no old/shared/light runtime edits. Unit tests cover 3 identity and endpoint contracts, negative cross matching, existing zbeacon/legacy protection, dry/open/close, partial IAS frame false-close guard, battery 0/200 and invalid 255, reactive enroll. All 3 independentlyPendingactual hardware feedback during PUBLIC 0.4 Test.Updates generated
app.json,SUPPORTED_DEVICES.md, 0.4 changelog/readiness and exact-identity matrix. Expected once merged: 152 total drivers / 17 new isolated profiles / 31 separately gated exact Zigbee manufacturer/model identities. Frozen 0.3.1 and Draft release PR #1470 untouched. Refs #1013, #832, #1143, #868, #1469.