The matter zap tool opens a. zap file, is error

RE: The matter zap tool opens a. zap file, is error

Amanda Hsieh — Thu, 07 Sep 2023 12:49:43 GMT

Hi,

[quote user="DoubleAmaing"]I am using a customer board,[/quote]

Is it your custom board or your customer's board? Is the schematic reviewed by our support team? If not, please create a new support case to review the board.

I would suggest you use the nRF52840DK or nRF52840 dongle to test if you just want to know how to work with Matter.

[quote user="DoubleAmaing"]I really can't find the problem, so I used the Bluetooth example to test the Bluetooth connection, but the connection failed[/quote]

Please create a new support case for the connection failed issue which is far away from the original scope.

-Amanda H.

RE: The matter zap tool opens a. zap file, is error

DoubleAmaing — Thu, 07 Sep 2023 02:25:41 GMT

Complete prompt：

SEGGER J-Link V7.88j - Real time terminal output
SEGGER J-Link V10.1, SN=600105955
Process: JLinkExe
*** Booting Zephyr OS build v3.3.99-ncs1-1 ***
Starting Bluetooth Peripheral Status example
I: 8 Sectors of 4096 bytes
I: alloc wra: 0, ea0
I: data wra: 0, 11c
I: SoftDevice Controller build revision: 
I: e0 7e 2e c1 5e 05 85 23 |.~..^..#
I: 46 15 dc fa 8e 29 7d 70 |F....)}p
I: 10 93 a5 fc             |....    
I: HW Platform: Nordic Semiconductor (0x0002)
I: HW Variant: nRF52x (0x0002)
I: Firmware: Standard Bluetooth controller (0x00) Version 224.11902 Build 2231721665
I: No ID address. App must call settings_load()
Bluetooth initialized
I: Identity: CC:68:EF:6F:CF:85 (random)
I: HCI: version 5.4 (0x0d) revision 0x1077, manufacturer 0x0059
I: LMP: version 5.4 (0x0d) subver 0x1077
Advertising successfully started
Connected
Disconnected (reason 62)

RE: The matter zap tool opens a. zap file, is error

DoubleAmaing — Thu, 07 Sep 2023 02:18:07 GMT

Hello,

I am using a customer board,

I really can't find the problem, so I used the Bluetooth example to test the Bluetooth connection, but the connection failed, as follows:

Tools: nRF connect for Mobile, Bluetooth: Peripheral Status, Customer Board (52840)

1. VS Code Open "Bluetooth: Peripheral Status', prjconf adds enable RTT instruction.

2. 'Build Configuration'

3. Flash and “Connect RTT”，Then, connect to 'Nordic_Status' through 'nRF Connect for mobile'

I: HW Platform: Nordic Semiconductor (0x0002)
I: HW Variant: nRF52x (0x0002)
I: Firmware: Standard Bluetooth controller (0x00) Version 224.11902 Build 2231721665
I: No ID address. App must call settings_load()
Bluetooth initialized
I: Identity: CC:68:EF:6F:CF:85 (random)
I: HCI: version 5.4 (0x0d) revision 0x1077, manufacturer 0x0059
I: LMP: version 5.4 (0x0d) subver 0x1077
Advertising successfully started
Connected
Disconnected (reason 62)

RE: The matter zap tool opens a. zap file, is error

Amanda Hsieh — Wed, 06 Sep 2023 13:12:36 GMT

Hi,

It looks like a problem with BLE connectivity. The device handling it like bluetooth card or USB HCI. Not sure what device was used, could be the one built in "ThinkPad-E470". In case of those errors, it is worth checking the system logs for bluetooth errors.

What instructions do you follow? Could you provide the link?

-Amanda H.

RE: The matter zap tool opens a. zap file, is error

DoubleAmaing — Mon, 04 Sep 2023 07:45:21 GMT

This problem has been bothering me for a week, please help me, thank you.

Environment:

Raspberry Pie (Border Router)

router

Ubuntu 20.04(Linux Host)

Board (Light_Blub)

Chih TooL:

Using pre compiled, version 2.4.1

Releases · nrfconnect/sdk-connectedhomeip (github.com)

I can see the device 'matterLight' on my computer

yida@yida-ThinkPad-E470:~$ ./chip-tool-debug pairing ble-thread 1 hex:0e080000000000010000000300000d35060004001fffe00208ee7e4a2d48cdfd7e0708fd131483b543b1000510253bf95c157a90fe0984c54686572c74030f4f70656e5468726561642d643666370102d6f70410e2b8eaa64e39fc95ac12cc7b8757bd410c0402a0f7f8 20202021 3840
[1693455991.857097][4839:4839] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_kvs
[1693455991.857259][4839:4839] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_factory.ini
[1693455991.857292][4839:4839] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_config.ini
[1693455991.857312][4839:4839] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_counters.ini
[1693455991.857419][4839:4839] CHIP:DL: writing settings to file (/tmp/chip_counters.ini-GRdMES)
[1693455991.857580][4839:4839] CHIP:DL: renamed tmp file to file (/tmp/chip_counters.ini)
[1693455991.857592][4839:4839] CHIP:DL: NVS set: chip-counters/reboot-count = 4 (0x4)
[1693455991.857767][4839:4839] CHIP:DL: Got Ethernet interface: enp4s0
[1693455991.857872][4839:4839] CHIP:DL: Found the primary Ethernet interface:enp4s0
[1693455991.857981][4839:4839] CHIP:DL: Got WiFi interface: wlp5s0
[1693455991.858096][4839:4839] CHIP:DL: Found the primary WiFi interface:wlp5s0
[1693455991.858111][4839:4839] CHIP:IN: UDP::Init bind&listen port=0
[1693455991.858167][4839:4839] CHIP:IN: UDP::Init bound to port=35531
[1693455991.858173][4839:4839] CHIP:IN: UDP::Init bind&listen port=0
[1693455991.858190][4839:4839] CHIP:IN: UDP::Init bound to port=60013
[1693455991.858194][4839:4839] CHIP:IN: BLEBase::Init - setting/overriding transport
[1693455991.858198][4839:4839] CHIP:IN: TransportMgr initialized
[1693455991.858210][4839:4839] CHIP:FP: Initializing FabricTable from persistent storage
[1693455991.858251][4839:4839] CHIP:TS: Last Known Good Time: 2023-07-11T07:53:58
[1693455991.858390][4839:4839] CHIP:FP: Fabric index 0x1 was retrieved from storage. Compressed FabricId 0x9E45793F71B1363E, FabricId 0x0000000000000001, NodeId 0x000000000001B669, VendorId 0xFFF1
[1693455991.858814][4839:4839] CHIP:ZCL: Using ZAP configuration...
[1693455991.860751][4839:4839] CHIP:DL: Avahi client registered
[1693455991.861340][4839:4839] CHIP:CTL: System State Initialized...
[1693455991.861376][4839:4839] CHIP:CTL: Stopping commissioning discovery over DNS-SD
[1693455991.861388][4839:4839] CHIP:CTL: Setting attestation nonce to random value
[1693455991.861395][4839:4839] CHIP:CTL: Setting CSR nonce to random value
[1693455991.861515][4839:4841] CHIP:DL: CHIP task running
[1693455991.861566][4839:4841] CHIP:DL: HandlePlatformSpecificBLEEvent 32784
[1693455991.861642][4839:4841] CHIP:CTL: Stopping commissioning discovery over DNS-SD
[1693455991.861651][4839:4841] CHIP:CTL: Setting attestation nonce to random value
[1693455991.861656][4839:4841] CHIP:CTL: Setting CSR nonce to random value
[1693455991.865085][4839:4841] CHIP:CTL: Generating NOC
[1693455991.868697][4839:4841] CHIP:FP: Validating NOC chain
[1693455991.884270][4839:4841] CHIP:FP: NOC chain validation successful
[1693455991.884290][4839:4841] CHIP:FP: Updated fabric at index: 0x1, Node ID: 0x000000000001B669
[1693455991.884297][4839:4841] CHIP:TS: Last Known Good Time: 2023-07-11T07:53:58
[1693455991.884301][4839:4841] CHIP:TS: New proposed Last Known Good Time: 2021-01-01T00:00:00
[1693455991.884305][4839:4841] CHIP:TS: Retaining current Last Known Good Time
[1693455991.884814][4839:4841] CHIP:FP: Metadata for Fabric 0x1 persisted to storage.
[1693455991.885274][4839:4841] CHIP:TS: Committing Last Known Good Time to storage: 2023-07-11T07:53:58
[1693455991.885681][4839:4841] CHIP:CTL: Joined the fabric at index 1. Fabric ID is 0x0000000000000001 (Compressed Fabric ID: 9E45793F71B1363E)
[1693455991.889681][4839:4841] CHIP:CTL: Setting thread operational dataset from parameters
[1693455991.889689][4839:4841] CHIP:CTL: Setting attestation nonce to random value
[1693455991.889695][4839:4841] CHIP:CTL: Setting CSR nonce to random value
[1693455991.889701][4839:4841] CHIP:CTL: Commission called for node ID 0x0000000000000001
[1693455991.891513][4839:4840] CHIP:DL: TRACE: Bus acquired for name C-12e7
[1693455991.895595][4839:4841] CHIP:DL: PlatformBlueZInit init success
[1693455991.897811][4839:4840] CHIP:BLE: BLE removing known devices.
[1693455991.898425][4839:4840] CHIP:BLE: BLE initiating scan.
[1693455992.016874][4839:4841] CHIP:DL: Long dispatch time: 127 ms, for event type 2
[1693455992.136968][4839:4840] CHIP:BLE: Device 43:64:47:98:B2:6A does not look like a CHIP device.
[1693455992.139170][4839:4840] CHIP:BLE: Device 55:10:7D:B1:6C:94 does not look like a CHIP device.
[1693455992.144187][4839:4840] CHIP:BLE: Device 77:F8:C2:66:E0:EE does not look like a CHIP device.
[1693455992.190893][4839:4840] CHIP:BLE: Device 52:B6:FE:0D:52:8E does not look like a CHIP device.
[1693455992.192647][4839:4840] CHIP:BLE: Device 7B:3E:E8:FB:B9:E5 does not look like a CHIP device.
[1693455992.198519][4839:4840] CHIP:BLE: Device 4F:42:CC:FF:9D:AD does not look like a CHIP device.
[1693455992.237858][4839:4840] CHIP:BLE: Device 4A:97:7C:F4:F4:F1 does not look like a CHIP device.
[1693455992.244527][4839:4840] CHIP:BLE: Device D5:5B:3D:14:B3:8F does not look like a CHIP device.
[1693455992.302090][4839:4840] CHIP:BLE: Device 5E:1F:73:F2:C2:3F does not look like a CHIP device.
[1693455992.315487][4839:4840] CHIP:BLE: Device 35:29:5E:75:6B:ED does not look like a CHIP device.
[1693455992.385728][4839:4840] CHIP:BLE: Device 5A:92:DF:03:CE:2E does not look like a CHIP device.
[1693455992.447875][4839:4840] CHIP:BLE: Device 55:10:7D:B1:6C:94 does not look like a CHIP device.
[1693455992.461133][4839:4840] CHIP:BLE: Device 52:B6:FE:0D:52:8E does not look like a CHIP device.
[1693455992.476969][4839:4840] CHIP:BLE: Device 5F:03:20:5A:24:C4 does not look like a CHIP device.
[1693455992.535754][4839:4840] CHIP:BLE: Device 55:10:7D:B1:6C:94 does not look like a CHIP device.
[1693455992.562439][4839:4840] CHIP:BLE: Device 77:F8:C2:66:E0:EE does not look like a CHIP device.
[1693455992.657832][4839:4840] CHIP:BLE: Device 5A:92:DF:03:CE:2E does not look like a CHIP device.
[1693455992.675837][4839:4840] CHIP:BLE: Device C3:45:FB:8C:1A:33 does not look like a CHIP device.
[1693455992.739873][4839:4840] CHIP:BLE: Device 7B:3E:E8:FB:B9:E5 does not look like a CHIP device.
[1693455992.774767][4839:4840] CHIP:BLE: Device 4A:97:7C:F4:F4:F1 does not look like a CHIP device.
[1693455992.834091][4839:4840] CHIP:BLE: Device D5:F2:EA:48:13:47 does not look like a CHIP device.
[1693455992.886850][4839:4840] CHIP:BLE: Device 43:64:47:98:B2:6A does not look like a CHIP device.
[1693455992.930633][4839:4840] CHIP:BLE: Device 35:29:5E:75:6B:ED does not look like a CHIP device.
[1693455992.949098][4839:4840] CHIP:BLE: Device DB:9C:17:45:91:C0 does not look like a CHIP device.
[1693455992.983643][4839:4840] CHIP:BLE: Device 77:F8:C2:66:E0:EE does not look like a CHIP device.
[1693455993.034911][4839:4840] CHIP:BLE: Device 35:29:5E:75:6B:ED does not look like a CHIP device.
[1693455993.223787][4839:4840] CHIP:BLE: Device 47:D0:1D:75:59:8C does not look like a CHIP device.
[1693455993.233188][4839:4840] CHIP:BLE: Device E9:D8:C3:FF:DB:BE does not look like a CHIP device.
[1693455993.260438][4839:4840] CHIP:BLE: Device 52:B6:FE:0D:52:8E does not look like a CHIP device.
[1693455993.295423][4839:4840] CHIP:BLE: Device 7B:3E:E8:FB:B9:E5 does not look like a CHIP device.
[1693455993.305372][4839:4840] CHIP:BLE: Device 77:F8:C2:66:E0:EE does not look like a CHIP device.
[1693455993.321427][4839:4840] CHIP:BLE: Device 4A:97:7C:F4:F4:F1 does not look like a CHIP device.
[1693455993.428689][4839:4840] CHIP:BLE: Device 43:64:47:98:B2:6A does not look like a CHIP device.
[1693455993.483470][4839:4840] CHIP:BLE: Device 5A:92:DF:03:CE:2E does not look like a CHIP device.
[1693455993.560753][4839:4840] CHIP:BLE: Device 35:29:5E:75:6B:ED does not look like a CHIP device.
[1693455993.567996][4839:4840] CHIP:BLE: Device 4F:42:CC:FF:9D:AD does not look like a CHIP device.
[1693455993.749640][4839:4840] CHIP:BLE: Device D9:B1:89:CD:26:BC does not look like a CHIP device.
[1693455993.948121][4839:4840] CHIP:BLE: Device D2:D6:AF:FC:48:F7 does not look like a CHIP device.
[1693455993.948480][4839:4840] CHIP:BLE: Device F3:3D:4D:DB:DC:EE does not look like a CHIP device.
[1693455993.995691][4839:4840] CHIP:BLE: Device 35:29:5E:75:6B:ED does not look like a CHIP device.
[1693455994.125540][4839:4840] CHIP:BLE: Device 5A:92:DF:03:CE:2E does not look like a CHIP device.
[1693455994.193786][4839:4840] CHIP:BLE: Device 52:B6:FE:0D:52:8E does not look like a CHIP device.
[1693455994.308404][4839:4840] CHIP:BLE: Device 4F:42:CC:FF:9D:AD does not look like a CHIP device.
[1693455994.309306][4839:4840] CHIP:BLE: Device 5A:92:DF:03:CE:2E does not look like a CHIP device.
[1693455994.398003][4839:4840] CHIP:BLE: Device 4F:42:CC:FF:9D:AD does not look like a CHIP device.
[1693455994.677452][4839:4840] CHIP:BLE: Device C3:45:FB:8C:1A:33 does not look like a CHIP device.
[1693455994.837861][4839:4840] CHIP:BLE: Device D5:F2:EA:48:13:47 does not look like a CHIP device.
[1693455995.176084][4839:4840] CHIP:BLE: Device 77:F8:C2:66:E0:EE does not look like a CHIP device.
[1693455995.187870][4839:4840] CHIP:BLE: Device 02:67:D8:9B:04:BD does not look like a CHIP device.
[1693455995.227377][4839:4840] CHIP:BLE: Device 7B:3E:E8:FB:B9:E5 does not look like a CHIP device.
[1693455995.754318][4839:4840] CHIP:BLE: Device 52:B6:FE:0D:52:8E does not look like a CHIP device.
[1693455995.755287][4839:4840] CHIP:BLE: Device D9:B1:89:CD:26:BC does not look like a CHIP device.
[1693455995.761597][4839:4840] CHIP:BLE: Device CF:AD:81:30:E7:BB does not look like a CHIP device.
[1693455995.770820][4839:4840] CHIP:BLE: Device 4F:42:CC:FF:9D:AD does not look like a CHIP device.
[1693455995.802829][4839:4840] CHIP:BLE: Device 7B:3E:E8:FB:B9:E5 does not look like a CHIP device.
[1693455995.803547][4839:4840] CHIP:BLE: Device 77:F8:C2:66:E0:EE does not look like a CHIP device.
[1693455995.810845][4839:4840] CHIP:BLE: Device 02:67:D8:9B:04:BD does not look like a CHIP device.
[1693455996.677254][4839:4840] CHIP:BLE: Device 52:B6:FE:0D:52:8E does not look like a CHIP device.
[1693455996.678400][4839:4840] CHIP:BLE: Device C3:45:FB:8C:1A:33 does not look like a CHIP device.
[1693455997.478034][4839:4840] CHIP:BLE: Device E2:13:C2:7B:C0:70 does not look like a CHIP device.
[1693455998.197236][4839:4840] CHIP:BLE: Device 52:B6:FE:0D:52:8E does not look like a CHIP device.
[1693455998.446706][4839:4840] CHIP:BLE: Device 5A:92:DF:03:CE:2E does not look like a CHIP device.
[1693455998.625719][4839:4840] CHIP:BLE: Device 48:5F:74:67:2F:30 does not look like a CHIP device.
[1693455998.680855][4839:4840] CHIP:BLE: Device C3:45:FB:8C:1A:33 does not look like a CHIP device.
[1693455998.723092][4839:4840] CHIP:BLE: Device 5A:92:DF:03:CE:2E does not look like a CHIP device.
[1693455998.782864][4839:4840] CHIP:BLE: Device 52:B6:FE:0D:52:8E does not look like a CHIP device.
[1693455998.844840][4839:4840] CHIP:BLE: Device 4A:97:7C:F4:F4:F1 does not look like a CHIP device.
[1693455998.845869][4839:4840] CHIP:BLE: Device D5:F2:EA:48:13:47 does not look like a CHIP device.
[1693455999.001215][4839:4840] CHIP:BLE: New device scanned: CC:5E:B5:42:C3:48
[1693455999.001263][4839:4840] CHIP:BLE: Device discriminator match. Attempting to connect.
[1693456002.027697][4839:4841] CHIP:BLE: BLE scan error: src/platform/Linux/bluez/ChipDeviceScanner.cpp:154: CHIP Error 0x00000032: Timeout
[1693456009.009391][4839:4841] CHIP:DL: HandlePlatformSpecificBLEEvent 16386
[1693456009.009445][4839:4841] CHIP:DIS: Closing all BLE connections
[1693456009.009636][4839:4840] CHIP:DL: FAIL: ConnectDevice : Operation was cancelled (19)
[1693456009.009853][4839:4841] CHIP:DL: HandlePlatformSpecificBLEEvent 16386
[1693456111.861977][4839:4839] CHIP:CTL: Shutting down the commissioner
[1693456111.862036][4839:4839] CHIP:CTL: Stopping commissioning discovery over DNS-SD
[1693456111.862062][4839:4839] CHIP:CTL: Shutting down the controller
[1693456111.862097][4839:4839] CHIP:IN: Expiring all sessions for fabric 0x1!!
[1693456111.862125][4839:4839] CHIP:FP: Forgetting fabric 0x1
[1693456111.862163][4839:4839] CHIP:TS: Pending Last Known Good Time: 2023-07-11T07:53:58
[1693456111.862398][4839:4839] CHIP:TS: Previous Last Known Good Time: 2023-07-11T07:53:58
[1693456111.862427][4839:4839] CHIP:TS: Reverted Last Known Good Time to previous value
[1693456111.862470][4839:4839] CHIP:CTL: Shutting down the commissioner
[1693456111.862498][4839:4839] CHIP:CTL: Stopping commissioning discovery over DNS-SD
[1693456111.862522][4839:4839] CHIP:CTL: Shutting down the controller
[1693456111.862541][4839:4839] CHIP:CTL: Shutting down the System State, this will teardown the CHIP Stack
[1693456111.863739][4839:4839] CHIP:DMG: All ReadHandler-s are clean, clear GlobalDirtySet
[1693456111.863833][4839:4839] CHIP:BLE: BleConnectionDelegate::CancelConnection is not implemented.
[1693456111.863882][4839:4839] CHIP:FP: Shutting down FabricTable
[1693456111.863918][4839:4839] CHIP:TS: Pending Last Known Good Time: 2023-07-11T07:53:58
[1693456111.864103][4839:4839] CHIP:TS: Previous Last Known Good Time: 2023-07-11T07:53:58
[1693456111.864126][4839:4839] CHIP:TS: Reverted Last Known Good Time to previous value
[1693456111.864355][4839:4839] CHIP:DL: writing settings to file (/tmp/chip_counters.ini-v57lyA)
[1693456111.865010][4839:4839] CHIP:DL: renamed tmp file to file (/tmp/chip_counters.ini)
[1693456111.865071][4839:4839] CHIP:DL: NVS set: chip-counters/total-operational-hours = 0 (0x0)
[1693456111.865095][4839:4839] CHIP:DL: Inet Layer shutdown
[1693456111.865114][4839:4839] CHIP:DL: BLE shutdown
[1693456111.865685][4839:4839] CHIP:DL: System Layer shutdown
[1693456111.866303][4839:4839] CHIP:TOO: Run command failure: examples/chip-tool/commands/common/CHIPCommand.cpp:537: CHIP Error 0x00000032: Timeout

RE: The matter zap tool opens a. zap file, is error

Amanda Hsieh — Mon, 28 Aug 2023 15:07:02 GMT

Hi,

Check out the Working with the CHIP Tool doc.

-Amanda H.

RE: The matter zap tool opens a. zap file, is error

DoubleAmaing — Mon, 28 Aug 2023 07:59:06 GMT

thank you!

I still have some questions. Could you please help me。

Link for "

Configure the CHIP Tool for Linux or macOS 

"Matter over Thread: Configuring Border Router and Linux/macOS controller on separate devices — nRF Connect SDK 2.4.99 documentation (nordicsemi.com)

I am in China and I am unable to download 'Connectedhomeip';

But I need to build a controller to control the End device（Light device）,

I want to use ' light_bulb' to debug；

I use this method to build the controller "Matter nRF Connect releases GitHub page"；

See the figure below：

After download is complete：

I don't know how to "Bulid" or "Run" binary files,

Please consult me, thank you

RE: The matter zap tool opens a. zap file, is error

Amanda Hsieh — Fri, 25 Aug 2023 03:07:15 GMT

Hi,

You run the wrong command instead of `pip install clang-format`.

After running `pip install clang-format`, I don't get any errors.

-Amanda H.

RE: The matter zap tool opens a. zap file, is error

DoubleAmaing — Fri, 25 Aug 2023 01:14:55 GMT

thank you.

I have installed clang format and updated it to the latest version, but it still prompts this error.

May I ask if this error has an impact on adding a cluster? Will it affect the operation of the program?

RE: The matter zap tool opens a. zap file, is error

Amanda Hsieh — Thu, 24 Aug 2023 19:09:11 GMT

Hi,

[quote user="DoubleAmaing"]clang-format error: [WinError 2] 系统找不到指定的文件。[/quote]

Please run the command `pip install clang-format` to fix the error.

[quote user="DoubleAmaing"]I can't find MatterPostAttributeChangeCallback() in the file src/zap generated/callback stub. cpp ；why?[/quote]

Thanks for the report. We will fix it. You can refer to the example for the implementation.

-Amanda H.

RE: The matter zap tool opens a. zap file, is error

DoubleAmaing — Thu, 24 Aug 2023 06:45:34 GMT

Hi,

I can't find MatterPostAttributeChangeCallback() in the file src/zap generated/callback stub. cpp ；why?

Adding clusters to Matter application — nRF Connect SDK 2.4.99 documentation (nordicsemi.com)

I searched globally for this function and found that it was in another file

RE: The matter zap tool opens a. zap file, is error

DoubleAmaing — Thu, 24 Aug 2023 04:43:37 GMT

Hi，

links:

Adding clusters to Matter application — nRF Connect SDK 2.4.99 documentation (nordicsemi.com)

Matter tools — nRF Connect SDK 2.4.99 documentation (nordicsemi.com)

I downloaded the 2.4.1 SDK through nRF connect for desktop;

Open the. zap file according to the link above;

Then, I use light_ Switch. zap to perform zap compilation, I did not perform any changes to the light_Switch.zap.

RE: The matter zap tool opens a. zap file, is error

Amanda Hsieh — Wed, 23 Aug 2023 14:01:10 GMT

Hi,

[quote user="DoubleAmaing"]According to the guidelines, I enabled on/off and temperature cluster[/quote]

Which guidelines are you using? Could you provide the links?

[quote user="DoubleAmaing"]

But there is an error:

clang-format error: [WinError 2] 系统找不到指定的文件。

[/quote]

You said you are using light_ Bulb's .zap in the original post, but seems you are building another sample in the log.

Could you elaborate in more detail to help me reproduce the issue?

-Amanda H.

RE: The matter zap tool opens a. zap file, is error

DoubleAmaing — Wed, 23 Aug 2023 03:11:58 GMT

thanks you.

Yes, I have followed ZAP according to the official guidelines；

“'Error: Unable to find cluster extension by component.';”： The "notifications" in the screenshot below(I'm not sure if this prompt will affect anything)

but Endpoint 1 can be edited without any warnings;

According to the guidelines, I enabled on/off and temperature cluster

And I compiled according to the process, as follows:

But there is an error:

clang-format error: [WinError 2] 系统找不到指定的文件。

RE: The matter zap tool opens a. zap file, is error

Amanda Hsieh — Tue, 22 Aug 2023 15:21:32 GMT

Hi,

[quote user="DoubleAmaing"]The main interface of Zap has the following prompt[/quote]

Do you install the ZAP tool by following the instructions in Matter tools -> Installing the ZAP tool?

[quote user=""]Some clusters have warnings, may I ask what is missing from these?[/quote]

You can ignore them which are implemented in endpoint-1.

[quote user=""]there is an error message stating 'Error: Unable to find cluster extension by component.';[/quote]

How do you get the error? What did you modify? I could not reproduce it.

Regards,
Amanda H.

RE: The matter zap tool opens a. zap file, is error

DoubleAmaing — Tue, 22 Aug 2023 09:16:45 GMT

The main interface of Zap has the following prompt

Check type contradiction in XML metadata for ColorControlOptions with type BITMAP8
Check type contradiction in XML metadata for BarrierControlBarrierPosition with type INT8U

The matter zap tool opens a. zap file, is error

RE: The matter zap tool opens a. zap file, is error

RE: The matter zap tool opens a. zap file, is error

RE: The matter zap tool opens a. zap file, is error

RE: The matter zap tool opens a. zap file, is error

RE: The matter zap tool opens a. zap file, is error

RE: The matter zap tool opens a. zap file, is error

RE: The matter zap tool opens a. zap file, is error

Configure the CHIP Tool for Linux or macOS

RE: The matter zap tool opens a. zap file, is error

RE: The matter zap tool opens a. zap file, is error

RE: The matter zap tool opens a. zap file, is error

RE: The matter zap tool opens a. zap file, is error

RE: The matter zap tool opens a. zap file, is error

RE: The matter zap tool opens a. zap file, is error

RE: The matter zap tool opens a. zap file, is error

RE: The matter zap tool opens a. zap file, is error

RE: The matter zap tool opens a. zap file, is error

Configure the CHIP Tool for Linux or macOS 