Custom Driver only reflect changes after recommissioning Matter device

Developer Programs Support
1

We are working to add changes in matter door lock edge driver and we are following this tutorial. When we install the driver on hub, but changes only reflect if we recommission the device with SmartThings app. It does not reflect changes if device is already commissioned.

2

Some functions are only run during certain phases of the device lifecycle. For example, anything run during device_added would not be run just because of an update to the driver. What specifically did you add and where in the lifecycle would it be reflected?

1 Like
3

we updated the profile of door lock to lock-user-pin-schedule-batteryLevel.yml and also added test VID and PID in this for testing inside new-matter-lock/initi.lua

local NEW_MATTER_LOCK_PRODUCTS = {
  {0x115f, 0x2802}, -- AQARA, U200
  {0x115f, 0x2801}, -- AQARA, U300
  {0x147F, 0x0001}, -- U-tec
  {0x10E1, 0x2002},  -- VDA
  {0xFFF1, 0x8000}  --  test 
}
4

My understanding is that normally you would specify one of the implicit profiles in the fingerprints file but that only gets used when commissioning the device. If you want to switch to a different profile once the device has been added you will have to explicitly do so in your driver code.

I am not sure if reinstalling without deleting would also update the profile.

5

I believe we can change profiles also when device is added if I use edge driver builder online tool from SmartThings developer console, I can try any profile on the door lock and it updates without any issue and without requiring to recommission device.

The issue is it is not working with smarthings cli.