chip-tool cluster commands failing all the time

pabl40
Posts: 15
Joined: Thu May 02, 2024 11:12 am

chip-tool cluster commands failing all the time

Postby pabl40 » Tue May 14, 2024 1:47 pm

I have an ESP32-C6-DevKitM-1. I have flashed this with the Matter light example from the esp-matter SDK.

I then commission my device as follows :

Code: Select all

 chip-tool pairing ble-wifi 0x7283 'My Network' 123456789 20202021 3840
This all works fine. My device connects to my local network and and I can ping its IP address etc.

I don't know, why but I am unable then to turn on or off the light or send any cluster command using the chip tool for example :

Code: Select all

chip-tool onoff toggle 0x7283 0x01
I get the following below. Am I missing something? :

Code: Select all

[1715694336.819940][4472:4472] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_tool_kvs
[1715694336.821260][4472:4472] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_kvs
[1715694336.821301][4472:4472] CHIP:DL: ChipLinuxStorage::Init: Attempt to re-initialize with KVS config file: /tmp/chip_kvs
[1715694336.822772][4472:4472] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_factory.ini
[1715694336.822880][4472:4472] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_config.ini
[1715694336.822947][4472:4472] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_counters.ini
[1715694336.823209][4472:4472] CHIP:DL: writing settings to file (/tmp/chip_counters.ini-WSN4ht)
[1715694336.823563][4472:4472] CHIP:DL: renamed tmp file to file (/tmp/chip_counters.ini)
[1715694336.823929][4472:4472] CHIP:DL: NVS set: chip-counters/reboot-count = 17 (0x11)
[1715694336.824140][4472:4472] CHIP:DL: Got Ethernet interface: enp0s3
[1715694336.824322][4472:4472] CHIP:DL: Found the primary Ethernet interface:enp0s3
[1715694336.824621][4472:4472] CHIP:DL: Failed to get WiFi interface
[1715694336.824671][4472:4472] CHIP:DL: Failed to reset WiFi statistic counts
[1715694336.824715][4472:4472] CHIP:IN: UDP::Init bind&listen port=0
[1715694336.824781][4472:4472] CHIP:IN: UDP::Init bound to port=46740
[1715694336.824798][4472:4472] CHIP:IN: BLEBase::Init - setting/overriding transport
[1715694336.824813][4472:4472] CHIP:IN: TransportMgr initialized
[1715694336.824873][4472:4472] CHIP:FP: Initializing FabricTable from persistent storage
[1715694336.824918][4472:4472] CHIP:TS: Last Known Good Time: 2023-10-14T01:16:48
[1715694336.825519][4472:4472] CHIP:FP: Fabric index 0x1 was retrieved from storage. Compressed FabricId 0x35CFE666CE838CD1, FabricId 0x0000000000000001, NodeId 0x000000000001B669, VendorId 0xFFF1
[1715694336.826572][4472:4472] CHIP:ZCL: Using ZAP configuration...
[1715694336.827095][4472:4472] CHIP:CTL: System State Initialized...
[1715694336.827193][4472:4472] CHIP:CTL: Setting attestation nonce to random value
[1715694336.827270][4472:4472] CHIP:CTL: Setting CSR nonce to random value
[1715694336.827431][4472:4474] CHIP:DL: CHIP task running
[1715694336.827562][4472:4474] CHIP:DL: HandlePlatformSpecificBLEEvent 32786
[1715694336.827676][4472:4474] CHIP:CTL: Setting attestation nonce to random value
[1715694336.827716][4472:4474] CHIP:CTL: Setting CSR nonce to random value
[1715694336.827934][4472:4474] CHIP:CTL: Generating NOC
[1715694336.828143][4472:4474] CHIP:FP: Validating NOC chain
[1715694336.828544][4472:4474] CHIP:FP: NOC chain validation successful
[1715694336.828586][4472:4474] CHIP:FP: Updated fabric at index: 0x1, Node ID: 0x000000000001B669
[1715694336.828602][4472:4474] CHIP:TS: Last Known Good Time: 2023-10-14T01:16:48
[1715694336.828617][4472:4474] CHIP:TS: New proposed Last Known Good Time: 2021-01-01T00:00:00
[1715694336.828631][4472:4474] CHIP:TS: Retaining current Last Known Good Time
[1715694336.829780][4472:4474] CHIP:FP: Metadata for Fabric 0x1 persisted to storage.
[1715694336.835566][4472:4474] CHIP:TS: Committing Last Known Good Time to storage: 2023-10-14T01:16:48
[1715694336.845253][4472:4474] CHIP:CTL: Joined the fabric at index 1. Fabric ID is 0x0000000000000001 (Compressed Fabric ID: 35CFE666CE838CD1)
[1715694336.859605][4472:4474] CHIP:TOO: Sending command to node 0x7283
[1715694336.860118][4472:4474] CHIP:CSM: FindOrEstablishSession: PeerId = [1:0000000000007283]
[1715694336.860377][4472:4474] CHIP:CSM: FindOrEstablishSession: No existing OperationalSessionSetup instance found
[1715694336.860615][4472:4474] CHIP:DIS: OperationalSessionSetup[1:0000000000007283]: State change 1 --> 2
[1715694337.063755][4472:4474] CHIP:DIS: Checking node lookup status after 203 ms
[1715694356.834065][4472:4472] CHIP:CTL: Shutting down the commissione
[1715694356.834211][4472:4472] CHIP:CTL: Shutting down the controller
[1715694356.834268][4472:4472] CHIP:DIS: OperationalSessionSetup[1:0000000000007283]: Cancelling incomplete address resolution as device is being deleted.
[1715694356.834350][4472:4472] CHIP:IN: Expiring all sessions for fabric 0x1!!
[1715694356.834384][4472:4472] CHIP:FP: Forgetting fabric 0x1
[1715694356.834424][4472:4472] CHIP:TS: Pending Last Known Good Time: 2023-10-14T01:16:48
[1715694356.834519][4472:4472] CHIP:TS: Previous Last Known Good Time: 2023-10-14T01:16:48
[1715694356.835051][4472:4472] CHIP:TS: Reverted Last Known Good Time to previous value
[1715694356.835101][4472:4472] CHIP:CTL: Shutting down the commissioner
[1715694356.835134][4472:4472] CHIP:CTL: Shutting down the controller
[1715694356.835167][4472:4472] CHIP:CTL: Shutting down the System State, this will teardown the CHIP Stack
[1715694356.835263][4472:4472] CHIP:DMG: All ReadHandler-s are clean, clear GlobalDirtySet
[1715694356.835397][4472:4472] CHIP:FP: Shutting down FabricTable
[1715694356.835434][4472:4472] CHIP:TS: Pending Last Known Good Time: 2023-10-14T01:16:48
[1715694356.835502][4472:4472] CHIP:TS: Previous Last Known Good Time: 2023-10-14T01:16:48
[1715694356.835605][4472:4472] CHIP:TS: Reverted Last Known Good Time to previous value
[1715694356.836108][4472:4472] CHIP:DL: writing settings to file (/tmp/chip_counters.ini-sI6X0o)
[1715694356.836685][4472:4472] CHIP:DL: renamed tmp file to file (/tmp/chip_counters.ini)
[1715694356.837441][4472:4472] CHIP:DL: NVS set: chip-counters/total-operational-hours = 0 (0x0)
[1715694356.837514][4472:4472] CHIP:DL: Inet Layer shutdown
[1715694356.837539][4472:4472] CHIP:DL: BLE shutdown
[1715694356.837595][4472:4472] CHIP:DL: System Layer shutdown
[1715694356.837755][4472:4472] CHIP:TOO: Run command failure: examples/chip-tool/commands/common/CHIPCommand.cpp:617: CHIP Error 0x00000032: Timeout
Last edited by pabl40 on Tue May 14, 2024 4:41 pm, edited 1 time in total.

liaifat85
Posts: 200
Joined: Wed Dec 06, 2023 2:46 pm

Re: chip-tool cluster commands failing all the time

Postby liaifat85 » Tue May 14, 2024 2:36 pm

Here is a github thread regarding the run command failure.
https://github.com/project-chip/connect ... sues/23081

pabl40
Posts: 15
Joined: Thu May 02, 2024 11:12 am

Re: chip-tool cluster commands failing all the time

Postby pabl40 » Tue May 14, 2024 4:42 pm

liaifat85 wrote:
Tue May 14, 2024 2:36 pm
Here is a github thread regarding the run command failure.
https://github.com/project-chip/connect ... sues/23081
Thanks for your reply. I did see this before posting. It is still unsolved however.

Who is online

Users browsing this forum: Majestic-12 [Bot] and 106 guests