Matter : unable to de-commisioning a device

[Franck-D]

Hello,

After a successfull commissioning of a Matter ble-thread device (Light Bulb example) 

i can't retry the commisioning procedure  even after a 'factoryreset' 

Config:

otb-posix : commit (17 Feb 2023)

Chip-Tool : commit (10 Feb 2023)

Matter Device Bulb : Build from SDK and toolchain (2.3.0-rc1)

With the Chip-Tool CLI :

> chip-tool pairing ble-thread 102 hex:00008848....156 20202021 3840                -> Pairing OK

> chip-tool onoff on 102 1                                                                                        -> Light on OK

> chip-tool onoff off 102 1                                                                                        -> Light off OK

> chip-tool pairing unpair 102                                                                                  -> try to unpair

> chip-tool onoff on 102 1                                                                                        -> Light on  ? why

Try a factory reset on the Matter bulb device:

> uart:~$  ot factoryreset

then i  press button 4 for re-starting commisioning   

> I: Matter service BLE advertising not started - device is already commissioned     ->        ????  Why

The only way is to reflash the firmware into the nrf52840 device

Any idea ?

Thank you

[Marte Myrvold]

Hi,

The Matter device should not be factory reset using the OpenThread CLI factory reset command, but instead, the Matter factory reset command:

matter device factoryreset

The OpenThread command will only reset the OpenThread part of the commissioning, not the entire Matter commissioning.
Please try the Matter command and let me know if you are having any issues when using this command.

Best regards,
Marte

[Franck-D]

Hi Marte,

Thank you for your reply.

Now it works !

I had to re-compile the application with the option  "CONFIG_CHIP_LIB_SHELL=y" in project.conf

To fully de-commisioning i had to do not only a matter command but the 2 belows:

> matter device factoryreset

> ot factoryreset

Best Regards,

Franck

[zzebra83]

Hi Marte,

Im just curious, is there any way to decommision a device via the matter controller?

[Marte Myrvold]

Hi,

Yes, you can use the unpair command

./chip-tool pairing unpair <node-id>

Best regards,
Marte

[zzebra83]

yes thanks that works, i can remove the device from the matter controller fabric using that command. however after unpairing it, when i try to pair the device again, it doesn't work unless i do a factory reset of the device. that defeats the purpose of unpairing it via API

[Franck-D]

Hello zzebra83,

i'm just curious about witch version of chip-tool you use

github.com/.../chip-tool

or

https://github.com/nrfconnect/sdk-connectedhomeip/tree/master/examples/chip-tool

Thanks

[zzebra83]

Hi,

im using the Python CHIP controller from connected home, that basically sends a removeFabric command to the device(nordic light bulb example). upon receipt the device succesfully clears any fabric info it has. however it is still connected to the thread network vi OTBR so it has an address and can advertise itself on the network for discovery. however like i mentioned earlier, once the device is removed from the fabric, i am unable to pair it again.

[Marte Myrvold]

Hi,

I asked the developers about this. There is no CHIP Tooll command to perform a factory reset. There is, however, a command called TestEventTrigger that allows triggering some custom behavior to the device from CHIP Tool, which can be used for debugging and testing purposes. This command is not implemented by default, so the firmware would have to be modified for this to work.

Since the device is still connected to the Thread network, you cannot pair it again using Bluetooth LE, but you can still pair it over IP. This can be done using the following CHIP Tool command:

chip-tool pairing onnetwork <node-id> <setup-pin-code>

Best regards,
Marte

[zzebra83]

i have tried that, but it seems it doesnt work if the device has been removed from fabric but not removed from thread network? the device is discoverable but pairing onnetwork doesnt work. maybe im doing something wrong, not sure yet. im using nordic light bulb example, and using the default setup pin code 20202021

[zzebra83]

Nevermind, pairing onnetwork works fine when using latest revision from connectedhome.