matter over thread OTBR issue

RE: matter over thread OTBR issue

AHaug — Thu, 06 Jul 2023 14:15:27 GMT

No worries.

[quote user="gautam_joshi"] get after 2-3 minute later when i remove the OTBR,[/quote]

Could you elaborate on why you want to remove the OTBR from the network? What is the purpose of your project?

I see that no one has provided you with this list of links yet, but please see the following links which I've provided to https://devzone.nordicsemi.com/f/nordic-q-a/101292/matter-over-wi-fi-solution and devzone.nordicsemi.com/.../control-matter-device-remotely

Together with https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/protocols/matter/index.html I recommend you to start with the Matter samples and configure them for use over Wifi as described in the sample doc

Go through the Matter overview subpage, watch the Matter webinar and familiarize yourself with the concepts
Go through the getting started with Matter subpage which contains another webinar regarding how to test Matter samples in nRF Connect SDK and how finishes with how to test with commercial Matter ecosystems
- Testing Matter in the nRF Connect SDK also has its own link to how to configure CHIP Tool for Linux or macOS when using Matter over Wifi
Lastly go through how to create Matter end product

I don't believe you've followed the setup properly and that causes the binding issues that you see. If you've seen these links before, please revisit them, watch and follow the webinars to learn how to add custom clusters, bindings and to add features to your Matter devices

Kind regards,
Andreas

RE: matter over thread OTBR issue

gautam_joshi — Thu, 06 Jul 2023 10:41:37 GMT

hello,

sorry for late reply,

i don't get anything so i again try to do binding and then i try to remove OTBR but this time also i get same error but i have notice in matter switch logs which i get after 2-3 minute later when i remove the OTBR,

 632825 [DL]SRP Client was stopped, because current server is no longer detected.
D: 632834 [DL]OpenThread State Changed (Flags: 0x00000280)
D: 632840 [DL]   Partition Id: 0x65C2623A
D: 632846 [DL]OpenThread State Changed (Flags: 0x00000002)
D: 632851 [DL]   Thread Unicast Addresses:
D: 632855 [DL]        fd2d:b5c7:7093:108c:0:ff:fe00:3c01/64 valid rloc
D: 632862 [DL]        fd2d:b5c7:7093:108c:f269:d542:dcda:4553/64 valid
D: 632868 [DL]        fe80::c09f:594b:5e64:2d0c/64 valid preferred
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: 646174 [DIS]Found an existing secure session to [1:000000000000000F]!
D: 646181 [DIS]OperationalSessionSetup[1:000000000000000F]: State change 1 --> 5
I: 646189 [EM]<<< [E:40761i S:57243 M:40843356] (S) Msg TX to 1:000000000000000F [62B8] --- Type 0001:08 (IM:InvokeCommandRequest)
I: 646201 [IN](S) Sending msg 40843356 on secure session with LSID: 57243
I: 646208 [DL]OpenThread SED interval is 200ms
I: 648134 [IN](S) Sending msg 40843356 on secure session with LSID: 57243
I: 649940 [IN](S) Sending msg 40843356 on secure session with LSID: 57243
I: 652532 [IN](S) Sending msg 40843356 on secure session with LSID: 57243
I: 656097 [IN](S) Sending msg 40843356 on secure session with LSID: 57243
E: 662050 [EM]Failed to Send CHIP MessageCounter:40843356 on exchange 40761i sendCount: 4 max retries: 4
D: 665775 [IN]SecureSession[0x20003618]: MarkAsDefunct Type:2 LSID:57243
I: 665782 [SC]SecureSession[0x20003618]: Moving from state 'kActive' --> 'kDefunct'
I: 665789 [DMG]Time out! failed to receive invoke command response from Exchange: 40761i
I: Response timeout for invoked command, trying to recover CASE session.
D: 665804 [DIS]OperationalSessionSetup[1:000000000000000F]: State change 1 --> 2
I: 665811 [DIS]Resolving 233F0C7456E562B8:000000000000000F ...
I: 665818 [DL]OpenThread SED interval is 1000ms
I: 666011 [DIS]Checking node lookup status after 200 ms

and i also see that once i start the OTBR again my binding works perfectly.

./chip-tool binding read binding <node_id> <ep_id>

and i also try this command this works perfectly for switch but not for bulb.

so i am very confused that is this issue of my device or anything else.

Your help will be greatly appreciated.

RE: matter over thread OTBR issue

AHaug — Fri, 23 Jun 2023 11:53:42 GMT

Hi,

Initial thoughts:

Switch without otbr: It looks like the binding has not happened properly due to

I: 626405 [DMG]Time out! failed to receive invoke command response from Exchange: 63478i
E: Binding command was not applied! Reason: 32

But on the other hand, you get

I: 460083 [DMG]Received Command Response Status for Endpoint=1 Cluster=0x0000_0006 Command=0x0000_0002 Status=0x0
D: Binding command applied successfully!

A few lines over that.

Could you explain what you did at those points in time?
Could you look up reason 32 and see if that gives you any hint?
Could you send a read attribute command from chip-tool to both the bulb and switch to read the binding attribute in the binding cluster to check if the devices actually are bounded?
1. ./chip-tool binding read binding <node_id> <ep_id>

Let me know about this when you get that far!

Kind regards,
Andreas

RE: matter over thread OTBR issue

gautam_joshi — Wed, 21 Jun 2023 12:50:35 GMT

hello,

yes here are the logs.

devzone.nordicsemi.com/.../SWITCH_5F00_without_5F00_otbr.TXT

devzone.nordicsemi.com/.../SWITCH_5F00_with_5F00_otbr.TXT

devzone.nordicsemi.com/.../bulb_5F00_without_5F00_otbr.TXT

devzone.nordicsemi.com/.../bulb_5F00_with_5F00_otbr.TXT

RE: matter over thread OTBR issue

AHaug — Wed, 21 Jun 2023 12:30:35 GMT

Hi,

Could you get us some device logs for what happens throughout the procedure from start (commissioning and binding the devices with the OTBR in the network) to finish (after having removed the OTBR and attempting to communicate between the devices?

Initial thoughts is that the devices should be able to communicate with each other over Thread as long as they have been bounded.

Kind regards,
Andreas