Fingerprint Matter bridged devices by product name?

Developer Programs Writing Edge Drivers
1

Matter fingerprints in stock drivers can target a specific device with vendorId and productId, that works fine for native Matter devices if you don’t want to target a whole device type.

However, for bridged devices the way to identify them is by product name since IDs don’t apply.

Is it possible to use product name in the fingerprints for Matter drivers?

2

Hi @mocelet

Our engineering team confirmed that it is possible to create a fingerprint for a Matter bridged device using the productName field.

Currently, there aren’t any stock SmartThings drivers that use productName for bridged devices, but this approach was tested previously as part of this (now closed) PR: Matter Switch: Add Aqara LED Light Bulb T1 fingerprint by ctowns · Pull Request #1176 · SmartThingsCommunity/SmartThingsEdgeDrivers · GitHub

2 Likes
3

Thanks @Itati, doesn’t seem to work with my bridged devices. Tested with IKEA buttons through DIRIGERA and Tapo sensors through Tapo H100.

vendorId: 0x117C
productName: RODRET wireless dimmer

Also tried with vendorId 0, with decimal format (4476) and without vendorId.

Will check tomorrow if I’m missing something obvious.

1 Like
4

Can’t get it to work, it only matches the generic fingerprint but not the manufacturer one.

Tried a silly example with a native Matter device too:

This works:

vendorId: 0x115F
productId: 8194

This doesn’t:

vendorId: 0x115F
productName: Aqara Door and Window Sensor P2
5

The engineering team has requested some additional information to help analyze the issue.

Please leave the fingerprint entries that are already allowing the device to connect.
Make sure to enable driver logs before installing the device, so the full installation process is captured.
After the installation, please submit the Hub logs, so the team can verify why the onboarding is not being detected with the product name.

Driver logs
Logs of the driver:

  • Open the ST CLI
  • Enter the command smartthings edge:drivers:logcat
  • Enter the information requested by CLI
  • Now you must be able to see the logs once you see the message “connected”
    Note: verify that the hub and the computer are in the same network

Hub logs

Provide the Hub logs through the my.smartthings.com:

  1. In the my.smartthings, enter “your hubs”
  2. Enter the corresponding Hub
  3. Click on “Dump Hub Logs”
  4. Change the reason for requesting hub logs if needed
  5. Click on “Dump Hub Logs”
  6. Confirm that the request is submitted
    Note: If you have more than one Hub, the name of the one involved in the issue.

Also, support access to your account

  1. Confirm the email account registered in the forum is the same one you use for SmartThings. If not, please share it with me over DM.
  2. Enable support access to your account:
  1. Go to the SmartThings Web (my.smartthings.com)
  2. Log in to your Samsung Account
  3. Select Menu (⋮) and choose Settings
  4. Toggle on Account Data Access
  5. Select the time period and confirm - In this step, please select “Until turned off”, once the team finishes, we’ll let you know so you can disable it again.

More info about this access here: https://support.smartthings.com/hc/en-us/articles/36170233944852-Enabling-Account-Data-Access-for-Support

7

Thanks @Itati , my custom driver isn’t even joinable and removing the bridge and installing it again would be inconvenient so won’t be able to perform those tests.

Since it’s not something that important, stock drivers don’t even use it and the documentation doesn’t mention it we can just leave it here. I’ll probably end up just targeting generic fingerprints and telling users the compatibility list.

In my previous message I thought I found the solution in using deviceModel instead of productName but just realized that line is ignored and matches everything else :sweat_smile: .

1 Like