matter binding switch+light bulb

[maheswara]

As per my understanding once both switch bulb are bound,  The switch on/off should work irrespective of the open thread border router state

But What I observe is things work fine for some time  and stops working after some time  when otbr is switched off.

logs messages are given below, Appreciate if you can help with this behaviour

Thanks,

Mahesh

I: Button has been pressed, keep in this state for at least 500 ms to change light sensitivity of binded lighting devices.

I: Notify Bounded Cluster | endpoint: 1 cluster: 6

I: 687418 [DIS]Found an existing secure session to [1:0000000000000008]!

D: 687424 [DIS]OperationalSessionSetup[1:0000000000000008]: State change 1 --> 5

I: 687433 [EM]<<< [E:39665i S:25179 M:52943474] (S) Msg TX to 1:0000000000000008 [AF60] --- Type 0001:08 (IM:InvokeCommandRequest)

I: 687444 [IN](S) Sending msg 52943474 on secure session with LSID: 25179

I: 687452 [DL]OpenThread SED interval is 200ms

I: 687674 [EM]>>> [E:39665i S:25179 M:110482160 (Ack:52943474)] (S) Msg RX from 1:0000000000000008 [AF60] --- Type 0001:09 (IM:InvokeCommandResponse)

I: 687688 [DMG]Received Command Response Status for Endpoint=1 Cluster=0x0000_0006 Command=0x0000_0002 Status=0x0

D: Binding command applied successfully!

I: 687702 [DL]OpenThread SED interval is 1000ms

I: 687707 [EM]<<< [E:39665i S:25179 M:52943475 (Ack:110482160)] (S) Msg TX to 1:0000000000000008 [AF60] --- Type 0000:10 (SecureChannel:StandaloneAck)

I: 687720 [IN](S) Sending msg 52943475 on secure session with LSID: 25179

I: 788678 [DL]SRP Client was stopped, because current server is no longer detected.

D: 788686 [DL]OpenThread State Changed (Flags: 0x00000200)

D: 788694 [DL]OpenThread State Changed (Flags: 0x00000002)

D: 788701 [DL] Thread Unicast Addresses:

D: 788705 [DL] fd96:eaa2:e33:dfc8:0:ff:fe00:9401/64 valid rloc

D: 788713 [DL] fd96:eaa2:e33:dfc8:db04:da11:5efa:ad40/64 valid

D: 788720 [DL] fe80::74b0:2e3e:7ed1:64ce/64 valid preferred

^CD: 1088815 [DL]OpenThread State Changed (Flags: 0x00000200)

uart:~$ I: Button has been pressed, keep in this state for at least 500 ms to change light sensitivity of binded lighting devices.

I: Notify Bounded Cluster | endpoint: 1 cluster: 6

I: 1128150 [DIS]Found an existing secure session to [1:0000000000000008]!

D: 1128156 [DIS]OperationalSessionSetup[1:0000000000000008]: State change 1 --> 5

I: 1128165 [EM]<<< [E:39666i S:25179 M:52943476] (S) Msg TX to 1:0000000000000008 [AF60] --- Type 0001:08 (IM:InvokeCommandRequest)

I: 1128176 [IN](S) Sending msg 52943476 on secure session with LSID: 25179

I: 1128184 [DL]OpenThread SED interval is 200ms

I: 1130078 [IN](S) Sending msg 52943476 on secure session with LSID: 25179

I: 1132035 [IN](S) Sending msg 52943476 on secure session with LSID: 25179

I: 1134922 [IN](S) Sending msg 52943476 on secure session with LSID: 25179

I: 1138873 [IN](S) Sending msg 52943476 on secure session with LSID: 25179

E: 1144135 [EM]Failed to Send CHIP MessageCounter:52943476 on exchange 39666i sendCount: 4 max retries: 4

D: 1147751 [IN]SecureSession[0x20003438]: MarkAsDefunct Type:2 LSID:25179

I: 1147757 [SC]SecureSession[0x20003438]: Moving from state 'kActive' --> 'kDefunct'

I: 1147765 [DMG]Time out! failed to receive invoke command response from Exchange: 39666i

I: Response timeout for invoked command, trying to recover CASE session.

D: 1147779 [DIS]OperationalSessionSetup[1:0000000000000008]: State change 1 --> 2

I: 1147787 [DIS]Resolving 138B5D26E49FAF60:0000000000000008 ...

I: 1147794 [DL]OpenThread SED interval is 1000ms

I: 1147987 [DIS]Checking node lookup status after 201 ms

[AHaug]

Hi,

I can understand why you would expect that this should work without an OTBR, as you can draw parallels to how it works in a pure Thread network with a full Thread device and End device relation, but thats not quite how it works in a Matter over Thread network.

The short version is that the Matter devices does not work without an OTBR because they don't act as SRP servers. It is possible to enable SRP server on the Matter devices. Note however that pre-build OpenThread librariese do not include this functionality.

 To enable it, you need to enable :

CONFIG_OPENTHREAD_SRP_SERVER=y

CONFIG_OPENTHREAD_SOURCES=y

For more details refer to:

 - https://github.com/openthread/openthread/blob/main/src/cli/cli_srp_server.cpp

 - https://github.com/openthread/openthread/blob/main/src/cli/README_SRP_SERVER.md

However, note that Thread Border Router still seems to be important piece of the network as it allows communication with external networks like Wi-Fi, so it is a useful device to have in your Matter network regardless

Kind regards,
Andreas

[maheswara]

Thanks  Andreas for quick and useful information.

I understand the importance of the  Border router, But If whatever reason the border router is down, there is no way to control the devices which is not good, atleast weshould be able to control the devices locally irrespective of the Border router status.

I will try your suggestions 

Thanks,

Mahesh

[AHaug]

Hi,

maheswara said:

I understand the importance of the  Border router, But If whatever reason the border router is down, there is no way to control the devices which is not good, atleast weshould be able to control the devices locally irrespective of the Border router status.

Yes, this is what the controller and third party commercial hubs would ensure would not happen in combination with adding the SRP servers role to the devices

maheswara said:

I will try your suggestions 

Great, let me know if you have any related follow up questions to this topic

Kind regards,
Andreas