Creating Open Thread Network with nRF52840 DK Board as RCP failed

[jparekh68]

Hi, 

1. otbr-agent service is successfully running on raspberrypi. See below.

Fullscreen 8664.otbr_agent_status.txt Download

● otbr-agent.service - OpenThread Border Router Agent
     Loaded: loaded (/lib/systemd/system/otbr-agent.service; enabled; vendor preset: enabled)
     Active: activating (auto-restart) (Result: exit-code) since Tue 2023-01-31 22:58:12 GMT; 3s ago
    Process: 1469 ExecStartPre=service mdns start (code=exited, status=0/SUCCESS)
    Process: 1475 ExecStart=/usr/sbin/otbr-agent $OTBR_AGENT_OPTS (code=exited, status=2)
   Main PID: 1475 (code=exited, status=2)
        CPU: 73ms
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
lines 1-7/7 (END)

2. RCP Firmware successfully flashed on nRF52840 DK Board. See below:

3. We are not able to figure out next steps from the Documentation. Our objective is to form a Thread Network and run example "Lock" using Android Chiptool.

4. Our RCP Board(nRF52840 DK) is now connected to Raspberrypi and status check is as below: 

Fullscreen otbr_agent_status_1.txt Download

pi@raspberrypi:~ $ cd ot-br-posix
pi@raspberrypi:~/ot-br-posix $ sudo service otbr-agent status
● otbr-agent.service - OpenThread Border Router Agent
     Loaded: loaded (/lib/systemd/system/otbr-agent.service; enabled; vendor pr>
     Active: active (running) since Thu 2023-02-02 23:38:43 GMT; 5s ago
    Process: 1462 ExecStartPre=service mdns start (code=exited, status=0/SUCCES>
   Main PID: 1468 (otbr-agent)
      Tasks: 1 (limit: 4915)
        CPU: 72ms
     CGroup: /system.slice/otbr-agent.service
             └─1468 /usr/sbin/otbr-agent -I wpan0 -B eth0 spinel+hdlc+uart:///d>

Feb 02 23:38:43 raspberrypi otbr-agent[1468]: [NOTE]-AGENT---: Backbone interfa>
Feb 02 23:38:43 raspberrypi otbr-agent[1468]: [NOTE]-AGENT---: Running 0.3.0-08>
Feb 02 23:38:43 raspberrypi otbr-agent[1468]: [NOTE]-AGENT---: Thread version: >
Feb 02 23:38:43 raspberrypi otbr-agent[1468]: [NOTE]-AGENT---: Thread interface>
Feb 02 23:38:43 raspberrypi otbr-agent[1468]: [NOTE]-AGENT---: Radio URL: spine>
Feb 02 23:38:43 raspberrypi otbr-agent[1468]: [NOTE]-AGENT---: Radio URL: trel:>
Feb 02 23:38:43 raspberrypi otbr-agent[1468]: [NOTE]-ILS-----: Infra link selec>
Feb 02 23:38:43 raspberrypi otbr-agent[1468]: [INFO]-NCP-----: OpenThread log l>
Feb 02 23:38:45 raspberrypi otbr-agent[1468]: 49d.17:06:14.146 [W] Platform---->
Feb 02 23:38:45 raspberrypi otbr-agent[1468]: 49d.17:06:14.146 [C] Platform---->
lines 1-20/20 (END)...skipping...
● otbr-agent.service - OpenThread Border Router Agent
     Loaded: loaded (/lib/systemd/system/otbr-agent.service; enabled; vendor preset: enabled)
     Active: active (running) since Thu 2023-02-02 23:38:43 GMT; 5s ago
    Process: 1462 ExecStartPre=service mdns start (code=exited, status=0/SUCCESS)
   Main PID: 1468 (otbr-agent)
      Tasks: 1 (limit: 4915)
        CPU: 72ms
     CGroup: /system.slice/otbr-agent.service
             └─1468 /usr/sbin/otbr-agent -I wpan0 -B eth0 spinel+hdlc+uart:///dev/ttyACM0 trel://eth0

 

5. I also refer to your webinar of October 15, 2021 https://webinars.nordicsemi.com/developing-matter-products-with-nrf-4. Video duration 21:50 to 23:07

FORM Open Thread network is failed.

Please help us resolve the issue. We know if once Open Thread Network is formed,  Android Chiptool will automatically identify the "Lock" device which is flashed on the other nRF52840 DK Board.

Regards.

Jogen

[Charlie]

Hi Jogen,

FORM Open Thread network is failed.

How does it failed? Did you try to form with the web UI?

There is no "lock" device you can test with the thread network directly.

Are you playing with Matter device? Apple Homekit and Google Smart Home already have support on Matter now, so you can use their infrastructure to do Matter device test directly.

Best regards,

Charlie

[jparekh68]

Hi,

"How does it failed? Did you try to form with the web UI?"

Yes. 

If I understand this correctly then if a thread network is formed with RaspberryPi + RCP(in this case nRF52840DK) I should be able to connect and play with any matter device by scanning its QR code and using either of these 3 a. Apple HomeKit b. Google Smart Home c. Android Chip Tool.(This tool currently provides functionality of only Lock and Dimmable Light.).

If above is true then I would like to form a Thread Network using RaspberryPi + RCP(in this case nRF52840DK). and connect a matter device. But I am stuck after running otbr-agent successfully. 

"Are you playing with Matter device? Apple Homekit and Google Smart Home already have support on Matter now, so you can use their infrastructure to do Matter device test directly."

Even to do the above I have to create a Thrread Border Router. Correct?? 

Regards. 

Jogen

[Charlie]

Hi Jogen,

Good to hear OTBR works, you can only test it with Android Chip Tool. For how to add Matter device to other smart home systems, please refers to (+) Matter: Testing the nRF Connect platform with Apple, Google and Samsung ecosystems - Blogs - Nordic Blog - Nordic DevZone (nordicsemi.com).

Best regards,

Charlie

[jparekh68]

Hi,

Thanks.

Commissioning matter device looks pretty straight forward from below blog.

devzone.nordicsemi.com/.../matter-testing-nrf-connect-sdk-platform-with-apple-google-and-samsung-ecosystems-218911247

Howvwer, a certain portion of my question still remains under confusion. Maybe I did not draft the question correctly.

I will make one more attempt to draft the question correctly as below:

From the above blog it is clear that it is possible to commission 'Matter Light Bulb" using any of the ecosystem i.e. Apple Home Kit, Google Nest, Samsung Smart Things.

How about the following:

If I want to create:

1. nRF52840 DK - Light Bulb

2. nRF52840 DK - RCP

3. Thread Border Router - Raspberrypi

4. Android Chip Tool(Android Phone App) to commission the above light bulb. 

I tried above with 1. being a 'Lock" device and you mentioned that it is not possible to commission a Lock Device.

I am stuck at "FORM open thread networkhas failed". However, otbr-agent is successfully running on Raspberry pi.

Hope I have drafted the question correctly now for you to get a better grasp.

Regards.

Jogen 

[Charlie]

Hi Jogen,

Ok, I think I understand you better now.

1) OTBR and Android Chip Tool are initially developed for Matter developers when there was no commercial TBR(like homepod min, next hub) in the market, so developers can use them for development and test purpose. Android Chip Tool is only a sample to show how to develop your own Chip Tool on mobile phones.

2) 

jparekh68 said:

I tried above with 1. being a 'Lock" device and you mentioned that it is not possible to commission a Lock Device.

It is possible to provision a Lock Device with Android Chip Tool and you can try to control it with CLUSTER INTERACTION TOOL, but it does not provide a direct interface for Lock device like LIGHT ON/OFF &LEVEL CLUSTER. With the formal release of Matter1.0, I see less and less maintenance effort on Android Chip Tool by CSA, because developers can test on other commercial smart ecosystems now.

3)

jparekh68 said:

I am stuck at "FORM open thread networkhas failed". However, otbr-agent is successfully running on Raspberry pi.

Sorry, I misunderstood your meaning. Let's continue to debug this issue. I have tested OTBR several weeks ago, but I am not sure if there are some changes recently. Let me try the OTBR setup procedure again and I will feedback to you later.

Best regards,

Charlie