SmartThingsCommunity
New Device (Matter Lock)Aqara U200
@ctowns Will we automatically switch to a profile that supports lock codes? I believe this device supports lock codes, however that was not the profile selected during the certification process.
Test Results
57 files ±0 363 suites ±0 0s :stopwatch: ±0s 1 747 tests ±0 1 747 :white_check_mark: ±0 0 :zzz: ±0 0 :x: ±0 3 040 runs ±0 3 040 :white_check_mark: ±0 0 :zzz: ±0 0 :x: ±0
Results for commit e731c8bc. ± Comparison against base commit 926083a4.
:recycle: This comment has been updated with latest results.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
| File | Coverage | |
|---|---|---|
| All files | 92% |
:white_check_mark: |
| /home/runner/work/SmartThingsEdgeDrivers/SmartThingsEdgeDrivers/drivers/SmartThings/matter-lock/src/lock_utils.lua | 97% |
:white_check_mark: |
| /home/runner/work/SmartThingsEdgeDrivers/SmartThingsEdgeDrivers/drivers/SmartThings/matter-lock/src/init.lua | 91% |
:white_check_mark: |
Minimum allowed coverage is 90%
Generated by :monkey: cobertura-action against e731c8bc35c6a10a55b196e7fed9776d94f81f74
@ctowns Will we automatically switch to a profile that supports lock codes? I believe this device supports lock codes, however that was not the profile selected during the certification process.
We will not automatically switch to a profile that supports lock codes. We currently only support switching to a profile without lock codes because the generic matter-lock fingerprint matches to a profile with lock codes (base-lock).
Also, if we know the device does support lock codes, can we override the profile that was selected during the WWST submission? I think it would probably be best if manufacturer fingerprints matched to the correct profile if possible without relying on profile switching in the driver if we can. What do you think?
@ctowns Will we automatically switch to a profile that supports lock codes? I believe this device supports lock codes, however that was not the profile selected during the certification process.
We will not automatically switch to a profile that supports lock codes. We currently only support switching to a profile without lock codes because the generic
matter-lockfingerprint matches to a profile with lock codes (base-lock).Also, if we know the device does support lock codes, can we override the profile that was selected during the WWST submission? I think it would probably be best if manufacturer fingerprints matched to the correct profile if possible without relying on profile switching in the driver if we can. What do you think?
Ah - we are cautious about that for good reasons. Yes, I do think we should push back on the existing submission and recommend that they use a different profile.
As a result of testing the U200 actual device, it does not support power source cluster, so battery capability should be removed. I updated as below.
https://github.com/SmartThingsCommunity/SmartThingsEdgeDrivers/pull/1413
Can this ticket be closed, since we now have a fingerprint for this device?
