Can't connect to nRF52840-DK with Python CHIP Controller

RE: Can't connect to nRF52840-DK with Python CHIP Controller

user106736 — Wed, 08 Jun 2022 13:42:57 GMT

Yes, I think you always need to use a Matter Controller to control(get info from device) over the Matter network.

If you want to know if Matter supports other ways for communicationg with devices, I suggest that you have a look at the Matter Specification.

Regards,
Sigurd Hellesvik

RE: Can't connect to nRF52840-DK with Python CHIP Controller

user114952 — Wed, 08 Jun 2022 11:55:08 GMT

Hello,

You were right, the command you sent me works. Also, I see your point on WiFi - Thread communication. However, from what I understand, I always require to use the CHIP controller to get info from the device, am I right?

RE: Can't connect to nRF52840-DK with Python CHIP Controller

user106736 — Wed, 01 Jun 2022 13:01:28 GMT

For step 7, try "zclread Basic ProductName 1234 0 0" instead. It seems that the documentation is wrong here, and the basic cluster is on endpoint 0, and not endpoint 1.

[quote user="mihnea17cristian"]Now, I don't normally require this, I would like to commission the device to my thread network and after that, control it from a WiFi network... How can achieve this?[/quote]

When you use the zclread commands, the command goes through Wi-Fi from your PC to the Border Router and then to your Matter device over the Thread network.

Do you want something else than this?

Regards,
Sigurd Hellesvik

RE: Can't connect to nRF52840-DK with Python CHIP Controller

user114952 — Wed, 01 Jun 2022 08:44:30 GMT

Actually no, after installing it like this and going through the instructions available here: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/1.9.1/matter/python_chip_controller_building.html (which you send it to me), I am able to connect to the device by ble and also send commands (turn the ligh bulb on/off), which is Step 6 from the link.

However, at Step 7, when I try to get ProductName with the command " zclread Basic ProductName 1234 1 0 ", I receive the following error:

chip-device-ctrl > zclread Basic ProductName 1234 1 0
Using PASE connection
[1654072284.640471][271108:271114] CHIP:IN: Prepared secure message 0x7f7a5fce18 to 0x00000000000004D2 (1)  of type 0x2 and protocolId (0, 1) on exchange 33810i with MessageCounter:2809441.
[1654072284.640541][271108:271114] CHIP:IN: Sending encrypted msg 0x7f7a5fce18 with MessageCounter:2809441 to 0x00000000000004D2 (1) at monotonic time: 773705553 msec
[1654072284.752556][271108:271114] CHIP:EM: Received message of type 0x5 with protocolId (0, 1) and MessageCounter:15675771 on exchange 33810i
2022-06-01 10:31:24,753 root         ERROR    For path: Endpoint = 1, Attribute = <class 'chip.clusters.Objects.Basic.Attributes.ProductName'>, got IM Error: InteractionModelError: UnsupportedAttribute (0x86)
AttributeReadResult(path=AttributePath(nodeId=1234, endpointId=1, clusterId=40, attributeId=3), status=0, value=ValueDecodeFailure(TLVValue=None, Reason=InteractionModelError(<Status.UnsupportedAttribute: 134>)))

Now, I don't normally require this, I would like to commission the device to my thread network and after that, control it from a WiFi network... How can achieve this?

Thank you,

Mihnea Cristian Marin

RE: Can't connect to nRF52840-DK with Python CHIP Controller

user106736 — Mon, 30 May 2022 06:20:14 GMT

Do you get the same errors if you use the chip-device-ctrl installed from https://github.com/nrfconnect/sdk-connectedhomeip/releases/tag/v1.9.1?

Regards,
Sigurd Hellesvik

RE: Can't connect to nRF52840-DK with Python CHIP Controller

user114952 — Wed, 25 May 2022 15:36:11 GMT

Okay,

So after I consulted the page https://developer.nordicsemi.com/nRF_Connect_SDK/doc/1.9.1/matter/python_chip_controller_building.html I have the following issues:

1. After installing the CHIP controller when I try the BLE interface I get the following:

sudo out/python_env/bin/chip-device-ctrl --bluetooth-adapter=hci2
CHIP:DIS: Init admin pairing table with server storage.
CHIP:IN: local node id is 0x000000000001b669
CHIP:DL: MDNS failed to join multicast group on eth0 for address type IPv4: Inet Error 1016 (0x000003F8): Address not found
CHIP:DL: MDNS failed to join multicast group on rndis0 for address type IPv4: Inet Error 1016 (0x000003F8): Address not found
CHIP:DL: MDNS failed to join multicast group on usb0 for address type IPv4: Inet Error 1016 (0x000003F8): Address not found
CHIP:ZCL: Using ZAP configuration...
CHIP:ZCL: deactivate report event
CHIP:CTL: Getting operational keys
CHIP:CTL: Generating operational certificate for the controller
CHIP:CTL: Getting root certificate for the controller from the issuer
CHIP:CTL: Generating credentials
CHIP:CTL: Loaded credentials successfully
CHIP:DL: Platform main loop started.
2022-05-25 17:29:25,177 ChipBLEMgr   INFO     adapter hci2 cannot be found, expect the ble mac address
Traceback (most recent call last):
  File "out/python_env/bin/chip-device-ctrl", line 789, in <module>
    main()
  File "out/python_env/bin/chip-device-ctrl", line 769, in main
    devMgrCmd = DeviceMgrCmd(rendezvousAddr=options.rendezvousAddr,
  File "out/python_env/bin/chip-device-ctrl", line 155, in __init__
    self.bleMgr.ble_adapter_select("hci{}".format(bluetoothAdapter))
  File "/home/iotlab/connectedhomeip/out/python_env/lib/python3.8/site-packages/chip/ChipBluezMgr.py", line 829, in ble_adapter_select
    self.adapter.adapter_register_signal()
AttributeError: 'NoneType' object has no attribute 'adapter_register_signal'

2. And so, I run the following command, which works:

sudo out/python_env/bin/chip-device-ctrl

3. After that, when I try to set the previously obtained Active Operational Dataset I get:

set-pairing-thread-credential 0e080000000000010000000300000f35060004001fffe0020811111111222222220708fde7466588be63af051000112233445566778899aabbccddeeff030e4f70656e54687265616444656d6f010212340410445f2b5ca6f2a93a55ce570a70efeecb0c0402a0fff8
Pairing Thread Credential is nolonger available, use NetworkCommissioning cluster instead.

4. And finally, if I try to Commission the Matter accessory device over Bluetooth LE I get:

connect -ble 3840 20202021 1234
Device is assigned with nodeid = 1234
CHIP:BLE: BLE removing known devices.
CHIP:BLE: BLE initiating scan.
CHIP:BLE: New device scanned: E9:1C:51:27:C0:68
CHIP:BLE: Device discriminator match. Attempting to connect.
CHIP:BLE: Scan complete notification without an active scan.
CHIP:DL: Bluez notify CHIPoBluez connection disconnected
CHIP:IN: Failed to establish BLE connection: Ble Error 6012 (0x0000177C): Remote device closed BLE connection
CHIP:BLE: no endpoint for sub complete
Failed to establish secure session to device: 4050
CHIP:BLE: PASESession timed out while waiting for a response from the peer. Expected message type was 33
Failed to establish secure session to device: 4050
CHIP Error 4050 (0x00000FD2): Timeout

RE: Can't connect to nRF52840-DK with Python CHIP Controller

user106736 — Wed, 25 May 2022 06:47:59 GMT

When I suggested that you use chip-tool some time ago, I were a bit premature. Our developers say that this will not be ready for use until nRF Connect SDK v1.9.1.
I suggested this due to a misunderstanding on my part, sorry about that.

chip-device-ctrl should work fine with v1.9.1, and you had gotten quite some way with that earlier in this case.
Does it work for you to go back to chip-device-ctrl, so we know we are working with something stable?

If so, have a look at Working with Python CHIP Controller, specifically the section on "Using Python CHIP Controller for Matter accessory testing". For the chip-device-ctrl, you already downloaded it from releases, right?

Regards,
Sigurd Hellesvik

RE: Can't connect to nRF52840-DK with Python CHIP Controller

user114952 — Tue, 24 May 2022 14:11:18 GMT

This is the result of trying what you suggest:

./chip_tool/chip-tool pairing ble-thread hex:0e080000000000010000000300000f35060004001fffe0020811111111222222220708fde7466588be63af051000112233445566778899aabbccddeeff030e4f70656e54687265616444656d6f010212340410445f2b5ca6f2a93a55ce570a70efeecb0c0402a0fff8 1 20202021 3840  
CHIP:CTL: Init failure! Operational Cred Issuer: Error 4175 (0x0000104F)
CHIP:TOO: Run command failure: Error 4175 (0x0000104F)

RE: Can't connect to nRF52840-DK with Python CHIP Controller

user106736 — Tue, 24 May 2022 14:00:32 GMT

I am talking to our developers about this, and they think "fabric-id" might be a misprint.

I will let you know when they find out, but in the meantime, what happens if you try to use "node-id" instead?
Just choose a number, which will be the node-id you assign to the device.

Regards,
Sigurd Hellesvik

RE: Can't connect to nRF52840-DK with Python CHIP Controller

user114952 — Mon, 23 May 2022 13:05:46 GMT

No, I didn't forget about the node-id. As I was telling you in the message, I checkout to commit 762a204b04049dac01c7ecf8f695ddd58f085c29, where the command structure is:

./chip_tool/chip-tool pairing ble-thread operationalDataset fabric-id setup-pin-code discriminator

And this is why I asked you about the fabric-id...

RE: Can't connect to nRF52840-DK with Python CHIP Controller

user106736 — Mon, 23 May 2022 11:06:18 GMT

The guide on how to use chip-tool can be found at https://github.com/project-chip/connectedhomeip/blob/master/docs/guides/chip_tool_guide.md.

[quote user="mihnea17cristian"]After some digging and finding this post https://github.com/project-chip/connectedhomeip/issues/6951, if I checkout to commit 762a204b04049dac01c7ecf8f695ddd58f085c29 I would get this error[/quote]

After a second look at this, it looks like you forgot node-id. Try to do something like:

./chip_tool/chip-tool pairing ble-thread 1 hex:0e080000000000010000000300000f35060004001fffe0020811111111222222220708fde7466588be63af051000112233445566778899aabbccddeeff030e4f70656e54687265616444656d6f010212340410445f2b5ca6f2a93a55ce570a70efeecb0c0402a0fff8 20202021 3840

where 1 is a nodeid assigned to the commissionee.

Regards,
Sigurd Hellesvik

RE: Can't connect to nRF52840-DK with Python CHIP Controller

user114952 — Mon, 23 May 2022 09:25:05 GMT

Hello,

Can you please give me a link to a full tutorial that you use for installing and running the CHIP tool? Because I think the board is flashed accordingly and also the border router seems to working okay.

Thank you,

Mihnea Cristian Marin

RE: Can't connect to nRF52840-DK with Python CHIP Controller

user114952 — Thu, 19 May 2022 15:03:10 GMT

Yes, its value is 2.

Regards,

Mihnea Marin

RE: Can't connect to nRF52840-DK with Python CHIP Controller

user106736 — Wed, 18 May 2022 13:18:08 GMT

Bluetooth Low Energy is only used to initiate the commissioning.
As a part of the commissioning, the Matter device is connecting to the thread network and the OTBR.

If the OTBR is not configured correctly, this may impact the commissioning.

Did you check net.ipv6.conf.wlan0.accept_ra as well?

Regards,
Sigurd Hellesvik

RE: Can't connect to nRF52840-DK with Python CHIP Controller

user114952 — Mon, 16 May 2022 08:12:12 GMT

Hello

Yes, the 'ot-ctl br enable' command returned 'Done', but I don't see why this helps right now considering my issues are when I try to connect to a device using BLE, in order to connect it after to the thread network.

Regards,

Mihnea Cristian

RE: Can't connect to nRF52840-DK with Python CHIP Controller

user106736 — Wed, 11 May 2022 15:12:04 GMT

Have you enabled Router Advertisement on your OTBR, as explained in https://openthread.io/codelabs/openthread-border-router#6?

Regards,
Sigurd Hellesvik

RE: Can't connect to nRF52840-DK with Python CHIP Controller

user106736 — Fri, 06 May 2022 12:11:19 GMT

A Fabric is a logical collection of communicating Nodes, sharing a common root of trust,
and a common distributed configuration state.
To read more about it, see the Matter Specification.

The Specification is still not public, so you will have to contact the Matter Group if you need access to it.

I have installed both the python chip controller and the chip-tool on my computer and is testing the commissioning myself as well now.
Do not know if it is what you want to hear, but I am facing some issues myself.

When I get it to work successfully, I will share my experience with you.

Regards,
Sigurd Hellesvik

RE: Can't connect to nRF52840-DK with Python CHIP Controller

user114952 — Wed, 04 May 2022 15:40:52 GMT

I managed to install Matter and the chip tool on a bigger sd card (on the same nvidia jetson). However, by git cloning the repo and installing the chip tool, when I try to commision the device, I receive the same error from the first post on this ticket.

After some digging and finding this post https://github.com/project-chip/connectedhomeip/issues/6951, if I checkout to commit 762a204b04049dac01c7ecf8f695ddd58f085c29 I would get this error:

./chip_tool/chip-tool pairing ble-thread hex:0e080000000000010000000300000f35060004001fffe0020811111111222222220708fde7466588be63af051000112233445566778899aabbccddeeff030e4f70656e54687265616444656d6f010212340410445f2b5ca6f2a93a55ce570a70efeecb0c0402a0fff8 20202021 3840
[1651678493.027787][52926:52926] CHIP:CTL: Read local id 0x000000000001B669, remote id 0x0000000000BC5C01
[1651678493.037072][52926:52926] CHIP:IN: UDP::Init bind&listen port=5541
[1651678493.037151][52926:52926] CHIP:IN: UDP::Init bind&listen port=5541
[1651678493.037203][52926:52926] CHIP:IN: TransportMgr initialized
[1651678493.037221][52926:52926] CHIP:DIS: Init fabric pairing table with server storage
[1651678493.038040][52926:52926] CHIP:IN: Loading certs from KVS
[1651678493.038069][52926:52926] CHIP:IN: local node id is 0x000000000001B669
[1651678493.039022][52926:52926] CHIP:DL: MDNS failed to join multicast group on eth0 for address type IPv4: ../examples/chip-tool/third_party/connectedhomeip/src/inet/IPEndPointBasis.cpp:259: Inet Error 0x00000110: Address not found
[1651678493.039723][52926:52926] CHIP:DL: MDNS failed to join multicast group on rndis0 for address type IPv4: ../examples/chip-tool/third_party/connectedhomeip/src/inet/IPEndPointBasis.cpp:259: Inet Error 0x00000110: Address not found
[1651678493.040110][52926:52926] CHIP:DL: MDNS failed to join multicast group on usb0 for address type IPv4: ../examples/chip-tool/third_party/connectedhomeip/src/inet/IPEndPointBasis.cpp:259: Inet Error 0x00000110: Address not found
[1651678493.040409][52926:52926] CHIP:ZCL: Using ZAP configuration...
[1651678493.040486][52926:52926] CHIP:ZCL: deactivate report event
[1651678493.040511][52926:52926] CHIP:CTL: Getting operational keys
[1651678493.040525][52926:52926] CHIP:CTL: Generating credentials
[1651678493.040948][52926:52926] CHIP:CTL: Loaded credentials successfully
[1651678493.041282][52926:52931] CHIP:DL: CHIP task running
[1651678493.041332][52926:52926] CHIP:TOO: InitArgs: Wrong arguments number: 3 instead of 4
Usage:
  ./chip_tool/chip-tool pairing ble-thread operationalDataset fabric-id setup-pin-code discriminator
[1651678493.041431][52926:52926] CHIP:TOO: Run command failure: ../examples/chip-tool/commands/common/Commands.cpp:183: CHIP Error 0x0000002F: Invalid argument
[1651678493.041614][52926:52926] CHIP:CTL: Shutting down the commissioner
[1651678493.041656][52926:52926] CHIP:CTL: Shutting down the controller
[1651678493.041717][52926:52926] CHIP:DL: Inet Layer shutdown
[1651678493.041872][52926:52926] CHIP:DL: BLE layer shutdown
[1651678493.041887][52926:52926] CHIP:DL: System Layer shutdown

However, if I checkout to 8dc938d63504e0e44d204eca505cc893fbc4d690, the command asks me for fabric_id. What is that?

Regards,

Mihnea Cristian Marin

RE: Can't connect to nRF52840-DK with Python CHIP Controller

user114952 — Thu, 21 Apr 2022 11:26:51 GMT

I would follow the steps on the last link you sent me, but right now I don't have enough space on the device...Once I manage to clean it and install the chip-tool, I will send you may status.

Regards,

Mihnea Cristian Marin

RE: Can't connect to nRF52840-DK with Python CHIP Controller

user106736 — Wed, 20 Apr 2022 12:05:46 GMT

I were unable to find the size and python version of chip-tool.
I suggest you make an issue on https://github.com/project-chip/connectedhomeip asking for this if you want to know.

From your past issue with the python chip controller, I found this issue, having a very similar log to your issue.
Maybe you are able to solve it from the discussion in that issue?

Regards,
Sigurd Hellesvik

RE: Can't connect to nRF52840-DK with Python CHIP Controller

user114952 — Wed, 13 Apr 2022 14:09:50 GMT

So first, I checked the poste you shared with me, but it's the same as closing the ble connection and then running the resolve command, right? Which is exactly what I was doing...

Second, can you please tell me what python version I need to have to be able to run the chip-tool, and also how much free disk space is needed?

Thank you,
Mihnea Cristian Marin

RE: Can't connect to nRF52840-DK with Python CHIP Controller

user106736 — Wed, 13 Apr 2022 13:22:42 GMT

This error looks like the one in case 84317.

Try to follow the advise from Charlie in the case; Does it fix your issue?

Regards,
Sigurd Hellesvik

RE: Can't connect to nRF52840-DK with Python CHIP Controller

user114952 — Wed, 13 Apr 2022 11:07:19 GMT

This is the output

chip-device-ctrl > resolve 1
[1649847790.257041][4145696:4145702] CHIP:DL: Re-trying resolve
[1649847795.260521][4145696:4145702] CHIP:DL: Re-trying resolve
[1649847800.263969][4145696:4145702] CHIP:DL: Re-trying resolve
[1649847805.268085][4145696:4145702] CHIP:DL: Avahi resolve failed
[1649847805.268174][4145696:4145702] CHIP:CTL: Error resolving node id: ../../src/platform/Linux/DnssdImpl.cpp:714: CHIP Error 0x000000AC: Internal error
[1649847805.268202][4145696:4145702] CHIP:CTL: Error resolving node id: ../../src/platform/Linux/DnssdImpl.cpp:714: CHIP Error 0x000000AC: Internal error
Failed to update node address: 172
[1649847805.268606][4145696:4145702] CHIP:CTL: Error resolving node id: ../../src/lib/dnssd/Discovery_ImplPlatform.cpp:90: CHIP Error 0x000000A6: Unknown resource ID
[1649847805.268834][4145696:4145702] CHIP:CTL: Error resolving node id: ../../src/lib/dnssd/Discovery_ImplPlatform.cpp:90: CHIP Error 0x000000A6: Unknown resource ID
Failed to update node address: 166
Bus error (core dumped)

RE: Can't connect to nRF52840-DK with Python CHIP Controller

user106736 — Wed, 13 Apr 2022 08:33:07 GMT

I do not think there are any other command doing the same as the resolve command.
Do you get any error message from the resolve command?

Just so you know: As an alternative to the Python Chip Controller, you could try the chip-tool for Linux of MacOS.

Regards,
Sigurd Hellesvik

RE: Can't connect to nRF52840-DK with Python CHIP Controller

user114952 — Wed, 13 Apr 2022 08:04:07 GMT

I used it and it works, also used the "ConnectNetwork" instead of "EnableNetwork". However, when I try to run the "resolve" command (only with nodeid as parameter), it doesn't do anything other than quitting the chip-device-ctrl.... Is there a substitute for the resolve command also?

Thank you,

Mihnea Marin