Support additional Camera device types#2590
Conversation
|
Duplicate profile check: Passed - no duplicate profiles detected. |
|
Invitation URL: |
Test Results 73 files 515 suites 0s ⏱️ Results for commit afca26f. ♻️ This comment has been updated with latest results. |
|
Minimum allowed coverage is Generated by 🐒 cobertura-action against afca26f |
samadDotDev
left a comment
There was a problem hiding this comment.
Will need to re-evaluate after rebase
96ccae6 to
67332b9
Compare
e012e2a to
a25f0c7
Compare
31bd85e to
164095f
Compare
b1faa74 to
297c2e3
Compare
63e0a39 to
17d5bb3
Compare
a19ba8c to
0080716
Compare
| table.insert(main_component_capabilities, capabilities.nightVision.ID) | ||
| end | ||
| if #chime_endpoints > 0 then | ||
| table.insert(main_component_capabilities, capabilities.sounds.ID) |
There was a problem hiding this comment.
We would also need to include audioMute for handling the Enabled attribute on the chime cluster, which is mandatory
| --- @param subscribed_events table key-value pairs mapping capability ids to subscribed events | ||
| function utils.populate_subscribe_request_for_device(checked_device, subscribe_request, capabilities_seen, attributes_seen, events_seen, subscribed_attributes, subscribed_events) | ||
| for _, component in pairs(checked_device.st_store.profile.components) do | ||
| function utils.populate_subscribe_request_for_device(checked_device, parent_device, subscribe_request, capabilities_seen, attributes_seen, events_seen, subscribed_attributes, subscribed_events) |
There was a problem hiding this comment.
Could we just update this function to get the parent device of the checked_device as needed rather than passing on the parent device in the function parameters? If the device doesn't have a parent device, then we would know that it is the parent device.
There was a problem hiding this comment.
Good idea, changed in afca26f as suggested
| deviceTypes: | ||
| - id: 0x0145 # Snapshot Camera | ||
| deviceProfileName: camera | ||
| - id: "matter/chime" |
There was a problem hiding this comment.
A device that supports Camera and Chime would equally match to the generic fingerprint for both Matter Camera and Matter Chime, so it is ambiguous which profile would be used initially. I know we would expect this to be fixed by the match profile logic, but could you add an additional fingerprint that matches on both the Camera and Chime device types and uses the camera profile? Also, this would allow us to set the default name to "Matter Camera" for these devices.
0080716 to
394d80d
Compare
| - component: main | ||
| capability: mechanicalPanTiltZoom | ||
| version: 1 | ||
| - component: main |
This adds support for the following device types: * 0x0140 Intercom * 0x0141 Audio Doorbell * 0x0142 Camera * 0x0143 Video Doorbell * 0x0144 Floodlight Camera * 0x0145 Snapshot Camera * 0x0146 Chime * 0x0148 DoorBell
42bfb6a to
054364c
Compare
This adds support for the following device types: