[Matter] Changing or adding Endpoints/Clusters to Matter-Template example with the zap tool leads to compiling errors

RE: [Matter] Changing or adding Endpoints/Clusters to Matter-Template example with the zap tool leads to compiling errors

Benny Nestler — Thu, 20 Oct 2022 09:20:15 GMT

Absolutely fixed!

zap tool starts equal to yours with preselected Matter Root Node. I'm very happy 😃

RE: [Matter] Changing or adding Endpoints/Clusters to Matter-Template example with the zap tool leads to compiling errors

Marte Myrvold — Thu, 20 Oct 2022 08:57:05 GMT

Hi,

Good to hear that you managed to get the zap tool working after reinstalling 🙂

Do you still see the same behavior with missing Matter Root Node and clusters, or does this seem to be fixed after reinstalling?

Best regards,

Marte

RE: [Matter] Changing or adding Endpoints/Clusters to Matter-Template example with the zap tool leads to compiling errors

Benny Nestler — Thu, 20 Oct 2022 08:32:09 GMT

Hi Marte Myrvold

I removed my SDK v2.1.0 with the Toolchain Manager (and manually, because the Toolchain Manager times out ("Removing ... ") and moved some files to an new Directory "toBeDeleted").

After the clearing I reinstall the SDK v2.1.0 and rebuild the zap tool with following tweaks:

- nvm v0.39.1

- node v18.11.0

- npm v8.19.2

1.) cd to /opt/nordic/ncs/v2.1.0/modules/lib/matter/

2.) bootstrap the zap tool with ./scripts/tools/zap/run_zaptool.sh

--> Error occurs due to an openSSL issue

{
  opensslErrorStack: [ 'error:03000086:digital envelope routines::initialization error' ],
  library: 'digital envelope routines',
  reason: 'unsupported',
  code: 'ERR_OSSL_EVP_UNSUPPORTED'
}

2.1) Fix the error by setting an environment variable

export NODE_OPTIONS=--openssl-legacy-provider

2.2) (again) bootstrap the zap tool with ./scripts/tools/zap/run_zaptool.sh

--> zap tool will be compiled but cannot be started because of the openssl-legacy-provider option (set before in NODE_OPTIONS)

⇝ electron: --openssl-legacy-provider is not allowed in NODE_OPTIONS

2.3) export NODE_OPTIONS=

3.) (again) bootstrap the zap tool with ./scripts/tools/zap/run_zaptool.sh

--> zap tool is compiled and will be started and crashes because of an (arm64) sqlite3 issue

3.1) cd to /opt/nordic/ncs/v2.1.0/modules/lib/matter/third_party/zap/repo

3.2) npm uninstall sqlite3

3.3) npm install sqlite3 --build-from-source --target_arch=arm64 --fallback-to-build

3.4) cd to /opt/nordic/ncs/v2.1.0/modules/lib/matter/

4.) (again) bootstrap the zap tool with ./scripts/tools/zap/run_zaptool.sh

bennynestler@MacBook-Pro-von-Benjamin(arm64) /opt/nordic/ncs/v2.1.0/modules/lib/matter % ./scripts/tools/zap/run_zaptool.sh ~/workspaces/matter/nRFConnect/template/src/template.zap
ARGS: -i /Users/bennynestler/workspaces/matter/nRFConnect/template/src/template.zap
🚀 Executing: git log -1 --format={"hash": "%H","timestamp": %ct}
🔍 Git commit: a94875d430d199ece002ab5bd971fdb78305fd4e from Fri Aug 12 2022 20:21:11 GMT+0200 (Mitteleuropäische Sommerzeit)
🔍 Current src hash: h2euTBRFmUDzrR/ddxfwDvNx4Qk=
🔍 Current src-shared hash: rF1YqWFjnJ5QZptyJBjTBuZ/z6M=
🔍 Previous src hash: h2euTBRFmUDzrR/ddxfwDvNx4Qk=
🔍 Previous src-shared hash: rF1YqWFjnJ5QZptyJBjTBuZ/z6M=
👍 There were no changes to front-end code, so we don't have to rebuild the SPA.
🚀 Executing: npx tsc --build ./tsconfig.json
🚀 Executing: npx copyfiles -V ./src-electron/**/*.sql ./dist/
unglobed path: ./src-electron/db/zap-schema.sql
copy from: ./src-electron/db/zap-schema.sql
copy to: dist/src-electron/db/zap-schema.sql
🚀 Executing: npx electron /opt/nordic/ncs/v2.1.0/modules/lib/matter/third_party/zap/repo/dist/src-electron/ui/main-ui.js --logToStdout --gen /opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/zap-templates/app-templates.json --zcl /opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/zap-templates/zcl/zcl.json -i /Users/bennynestler/workspaces/matter/nRFConnect/template/src/template.zap
🔧 Using state directory: ~/.zap
{"level":40,"time":1666253418767,"pid":41112,"hostname":"MacBook-Pro-von-Benjamin.fritz.box","name":"zap","msg":"Check type contradiction in XML metadata for ColorControlOptions with type BITMAP8"}
{"level":40,"time":1666253418768,"pid":41112,"hostname":"MacBook-Pro-von-Benjamin.fritz.box","name":"zap","msg":"Check type contradiction in XML metadata for LevelControlOptions with type BITMAP8"}
{"level":40,"time":1666253418768,"pid":41112,"hostname":"MacBook-Pro-von-Benjamin.fritz.box","name":"zap","msg":"Check type contradiction in XML metadata for BarrierControlBarrierPosition with type INT8U"}
{"level":40,"time":1666253419054,"pid":41112,"hostname":"MacBook-Pro-von-Benjamin.fritz.box","name":"zap","msg":"Attempting to insert cluster extension for a cluster which does not\n            exist. Check clusterExtension meta data in xml file.\n            Cluster Code: 0"}
{"level":50,"time":1666253419418,"pid":41112,"hostname":"MacBook-Pro-von-Benjamin.fritz.box","name":"zap","msg":"Tray not created, icon does not exist: /opt/nordic/ncs/v2.1.0/modules/lib/matter/third_party/zap/repo/dist/src-electron/icons/zap_32x32.png"}
{"level":30,"time":1666253419610,"pid":41112,"hostname":"MacBook-Pro-von-Benjamin.fritz.box","name":"zap","msg":"Init message received: WebSocket initialized handshake.. Responding."}
{"level":50,"time":1666253419635,"pid":41112,"hostname":"MacBook-Pro-von-Benjamin.fritz.box","name":"zap","msg":{}}
{"level":30,"time":1666253420230,"pid":41112,"hostname":"MacBook-Pro-von-Benjamin.fritz.box","name":"zap","msg":"Loading project(template.zap)"}
{"level":30,"time":1666253420274,"pid":41112,"hostname":"MacBook-Pro-von-Benjamin.fritz.box","name":"zap","msg":"Loaded project(template.zap) into database. RESP: {\"sessionId\":1,\"sessionKey\":\"E6YW8pebXJV1ufBKAWS7GMldpwFG8hpa\"}"}
{"level":30,"time":1666253420319,"pid":41112,"hostname":"MacBook-Pro-von-Benjamin.fritz.box","name":"zap","msg":"Init message received: WebSocket initialized handshake.. Responding."}
{"level":50,"time":1666253420330,"pid":41112,"hostname":"MacBook-Pro-von-Benjamin.fritz.box","name":"zap","msg":{}}

5.) Be happy about a working zap - tool 🙂

RE: [Matter] Changing or adding Endpoints/Clusters to Matter-Template example with the zap tool leads to compiling errors

Benny Nestler — Thu, 20 Oct 2022 06:04:50 GMT

Hi,

I've installed the SDK and the Toolchain via the nRF Connect Desktop Toolchain Manager.

I don't know where the errors come from, but they don't seem important to me.

{"level":50,"time":1666246901423,"pid":28813,"hostname":"MacBook-Pro-von-Benjamin.fritz.box","name":"zap","msg":"Error reading xml file: /Users/bennynestler/modules/lib/matter/src/app/zap-templates/zcl/zcl.json\n Error: Custom ZCL XML Error: Unknown extension file"}
{"level":50,"time":1666246901423,"pid":28813,"hostname":"MacBook-Pro-von-Benjamin.fritz.box","name":"zap","msg":"Error reading xml file: /Users/bennynestler/modules/lib/matter/src/app/zap-templates/app-templates.json\n Error: Custom ZCL XML Error: Unknown extension file"}

It looks like the zap tool look also in user directory for default json-files which are normally locate in the sdk directory. The (ZCL Extension) json-files from

/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/zap-templates/app-templates.json and

/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/zap-templates/zcl/zcl.json

will be loaded by zap tool.

I try to update my SDK and toolchain with the Toolchain Manager. But this dosen't leads to success.

Should I remove the SDK V2.1.0 and reinstall?

RE: [Matter] Changing or adding Endpoints/Clusters to Matter-Template example with the zap tool leads to compiling errors

Marte Myrvold — Wed, 19 Oct 2022 12:14:02 GMT

Hi,

If I save, close, and reopen it then it looks the same. Same amount of clusters and everything.

When comparing your output with mine I see that you get errors about reading xml files, due to unknown extension files. Did you install nRF Connect SDK manually or using Toolchain Manager? If you installed it manually, did you make sure to install all python requirements?

Best regards,

Marte

RE: [Matter] Changing or adding Endpoints/Clusters to Matter-Template example with the zap tool leads to compiling errors

Benny Nestler — Wed, 19 Oct 2022 10:09:51 GMT

What happens if you save the template.zap file, quit the zap tool and reopen the template.zap file??

But in your picture the number of enabled clusters is also wrong (you don't have 26 enabled cluster but only 15), isn't it?

I'm working on a MacBook Pro M1 Max.

Mac OS Monterey V12.6

My (terminal) zap output is following

bennynestler@MacBook-Pro-von-Benjamin(x86_64) /opt/nordic/ncs/v2.1.0/modules/lib/matter % ./scripts/tools/zap/run_zaptool.sh ~/workspaces/matter/nRFConnect/template/src/template.zap         
🚀 Executing: git log -1 --format={"hash": "%H","timestamp": %ct}
🔍 Git commit: e9277b989f1d128bc881e88ecbf7a3353c841c39 from Wed May 11 2022 16:45:40 GMT+0200 (Mitteleuropäische Sommerzeit)
🔍 Current src hash: aqrjjVB67BD5DC9iha9ORJah5zc=
🔍 Current src-shared hash: nOWlRqSeZbEDOkt+AnCdf01DNYM=
🔍 Previous src hash: aqrjjVB67BD5DC9iha9ORJah5zc=
🔍 Previous src-shared hash: nOWlRqSeZbEDOkt+AnCdf01DNYM=
👍 There were no changes to front-end code, so we don't have to rebuild the SPA.
🚀 Executing: npx tsc --build ./tsconfig.json
🚀 Executing: npx copyfiles -V ./src-electron/**/*.sql ./dist/
unglobed path: ./src-electron/db/zap-schema.sql
copy from: ./src-electron/db/zap-schema.sql
copy to: dist/src-electron/db/zap-schema.sql
🚀 Executing: npx electron /opt/nordic/ncs/v2.1.0/modules/lib/matter/third_party/zap/repo/dist/src-electron/ui/main-ui.js --logToStdout --gen /opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/zap-templates/app-templates.json --zcl /opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/zap-templates/zcl/zcl.json -i /Users/bennynestler/workspaces/matter/nRFConnect/template/src/template.zap
{"level":50,"time":1666173946831,"pid":23025,"hostname":"MacBook-Pro-von-Benjamin.local","name":"zap","msg":"Tray not created, icon does not exist: /opt/nordic/ncs/v2.1.0/modules/lib/matter/third_party/zap/repo/dist/src-electron/icons/zap_32x32.png"}
{"level":40,"time":1666173947009,"pid":23025,"hostname":"MacBook-Pro-von-Benjamin.local","name":"zap","msg":"247, /opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/zap-templates/zcl/zcl.json: Multiple toplevel zcl.properties found. Using the first one from args: 56"}
{"level":40,"time":1666173947010,"pid":23025,"hostname":"MacBook-Pro-von-Benjamin.local","name":"zap","msg":"Multiple toplevel generation template metafiles found. Using the one from args: 127"}
{"level":40,"time":1666173947010,"pid":23025,"hostname":"MacBook-Pro-von-Benjamin.local","name":"zap","msg":"247, /opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/zap-templates/zcl/zcl.json: Multiple toplevel zcl.properties found. Using the first one from args: 56"}
{"level":40,"time":1666173947010,"pid":23025,"hostname":"MacBook-Pro-von-Benjamin.local","name":"zap","msg":"Multiple toplevel generation template metafiles found. Using the one from args: 127"}
{"level":40,"time":1666173947010,"pid":23025,"hostname":"MacBook-Pro-von-Benjamin.local","name":"zap","msg":"Multiple toplevel generation template metafiles found. Using the one from args: 127"}
{"level":40,"time":1666173947010,"pid":23025,"hostname":"MacBook-Pro-von-Benjamin.local","name":"zap","msg":"247, /opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/zap-templates/zcl/zcl.json: Multiple toplevel zcl.properties found. Using the first one from args: 56"}
{"level":40,"time":1666173947012,"pid":23025,"hostname":"MacBook-Pro-von-Benjamin.local","name":"zap","msg":"247, /opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/zap-templates/zcl/zcl.json: Multiple toplevel zcl.properties found. Using the first one from args: 56"}
{"level":40,"time":1666173947012,"pid":23025,"hostname":"MacBook-Pro-von-Benjamin.local","name":"zap","msg":"Multiple toplevel generation template metafiles found. Using the one from args: 127"}
{"level":40,"time":1666173947012,"pid":23025,"hostname":"MacBook-Pro-von-Benjamin.local","name":"zap","msg":"247, /opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/zap-templates/zcl/zcl.json: Multiple toplevel zcl.properties found. Using the first one from args: 56"}
{"level":40,"time":1666173947012,"pid":23025,"hostname":"MacBook-Pro-von-Benjamin.local","name":"zap","msg":"247, /opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/zap-templates/zcl/zcl.json: Multiple toplevel zcl.properties found. Using the first one from args: 56"}
{"level":40,"time":1666173947012,"pid":23025,"hostname":"MacBook-Pro-von-Benjamin.local","name":"zap","msg":"Multiple toplevel generation template metafiles found. Using the one from args: 127"}
{"level":40,"time":1666173947012,"pid":23025,"hostname":"MacBook-Pro-von-Benjamin.local","name":"zap","msg":"Multiple toplevel generation template metafiles found. Using the one from args: 127"}
{"level":30,"time":1666173947023,"pid":23025,"hostname":"MacBook-Pro-von-Benjamin.local","name":"zap","msg":"Init message received: WebSocket initialized handshake.. Responding."}
{"level":50,"time":1666173947065,"pid":23025,"hostname":"MacBook-Pro-von-Benjamin.local","name":"zap","msg":{}}
{"level":50,"time":1666173947252,"pid":23025,"hostname":"MacBook-Pro-von-Benjamin.local","name":"zap","msg":"Error reading xml file: /Users/bennynestler/modules/lib/matter/src/app/zap-templates/zcl/zcl.json\n Error: Custom ZCL XML Error: Unknown extension file"}
{"level":50,"time":1666173947252,"pid":23025,"hostname":"MacBook-Pro-von-Benjamin.local","name":"zap","msg":"Error reading xml file: /Users/bennynestler/modules/lib/matter/src/app/zap-templates/app-templates.json\n Error: Custom ZCL XML Error: Unknown extension file"}
{"level":40,"time":1666173947252,"pid":23025,"hostname":"MacBook-Pro-von-Benjamin.local","name":"zap","msg":"None of packages exist, so using first one overall: 2."}
{"level":30,"time":1666173947374,"pid":23025,"hostname":"MacBook-Pro-von-Benjamin.local","name":"zap","msg":"Init message received: WebSocket initialized handshake.. Responding."}
{"level":50,"time":1666173947416,"pid":23025,"hostname":"MacBook-Pro-von-Benjamin.local","name":"zap","msg":{}}

And a new created matter-template leads to this view in zap tool

RE: [Matter] Changing or adding Endpoints/Clusters to Matter-Template example with the zap tool leads to compiling errors

Marte Myrvold — Wed, 19 Oct 2022 08:35:47 GMT

Hi,

When I run the zap tool endpoint 0 is automatically configured as Matter Root Node with all the same clusters as in my previous picture:

The picture above is from when I created a new application in VS Code just as you did. I did not do anything else with the application before running the zap tool, so this is what my device looks like in your step 2. I asked a colleague of mine to test as well, and they got the same as me.

I am looking into what the reason might be for why the Matter Root Node is not automatically configured for you, but I need some more time to investigate. Have you made any changes to the template sample previously? Did you install nRF Connect SDK using Toolchain Manager or manually? Can you also upload the output in the terminal from when you run the zap tool?

Best regards,

Marte

RE: [Matter] Changing or adding Endpoints/Clusters to Matter-Template example with the zap tool leads to compiling errors

Benny Nestler — Wed, 19 Oct 2022 06:59:30 GMT

Hi Marte Myrvold

yesterday I experiment a little bit with the zap tool and the matter template with following weird results:

1.) Create a new example matter-template from nRF SDK with VS Code integration plugin

2.) Open the src/template.zap file with zap-tool. Looks like this

3.) Edit Endpoint 0 and choose "Matter Root Node" from device list. Looks like this

--> Looks similar but not equal to yours Marte Myrvold ; but the right panel doesn't show 26 enabled Clusters. There are only 12! (And yes, I tried to scroll down, to the supposedly rest of 14 enabled Clusters)

4.) Save the file and quit the zap-tool.

5.) Reopen the src/template.zap file with zap-Tool. Looks like this

The numbers are changed ... !? I think that is the correct view!

6.) Add the missing Cluster in the CHIP category

- OTA Software Update Provider (0x0029) --> Choose Client

- OTA Software Update Requestor (0x002A) --> Choose Server

7.) Configure Cluster OTA Software Update Requestor

- enable all required Attributes, Attributes Reporting, Commands and Events

8.) Save the file (if possible --> I've issues with saving of files; very often my changes couldn't be saved and the zap tool don't offers the save menu entry; the only thing which helps is to restart the tool and retry in a slitly different change order )

9.) Try to configure the OTA Software Update Provider

--> This action always leads to freeze the zap -Tool

The only exit from this state, is to exit the zap tool (Menu --> Electron --> Quit Electron or Control + C in Terminal)

Marte Myrvold can you verify my steps/issues with the zap tool?

My zap-tool About window looks like following

RE: [Matter] Changing or adding Endpoints/Clusters to Matter-Template example with the zap tool leads to compiling errors

Benny Nestler — Tue, 18 Oct 2022 10:37:53 GMT

Hi Marte Myrvold

thanks for your hint. But that's only a fault/issue of the zap tool.

If you click on Endpoint 1, the left overview frame of Endpoint 0 changes as well and vice versa. But I thinks that's only a view issue.

But there was a valuable aspect in your picture, that's not described in the SDK documentation. The Endpoint 0 is not configured as "Matter root node" if I load the template.zap file from the template example.

I try to change the Endpoint 0 to the "Matter Root Node" and see what is the result.

RE: [Matter] Changing or adding Endpoints/Clusters to Matter-Template example with the zap tool leads to compiling errors

Marte Myrvold — Tue, 18 Oct 2022 09:19:31 GMT

Hi Benny,

Can you check which clusters are enabled on endpoint 0 and whether any of them are OTA? From the left side of your picture I see that endpoint 0 only has 5 clusters enabled, while when I go through the guide on my side I have 26 enabled clusters. The issue might be that you are missing some mandatory clusters for the Matter Root Node, such as OTA. This is what endpoint 0 looks like on my side:

Best regards,

Marte

RE: [Matter] Changing or adding Endpoints/Clusters to Matter-Template example with the zap tool leads to compiling errors

Benny Nestler — Tue, 18 Oct 2022 06:10:59 GMT

Hi Marte Myrvold ,

yes, I already thought that it was an OTA error.

But the error appears, since I edit the original zap-file.

The steps are the following:

1.) Create new matter-template application

2.) Build it with a configuration of your choice (I use the nRF5340DK) --> Build success

3.) Change the src/template.zap file and add endpoint 1 (Device = Matter Temperature Sensor (0x0302)).

4.) Use the generate.py script to create necessary cpp- and header- files

5.) Rebuild with the same configuration --> Build fails with the mentioned error.

[18/55] Building CXX object CMakeFiles/app.dir/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/clusters/ota-requestor/DefaultOTARequestor.cpp.obj
FAILED: CMakeFiles/app.dir/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/clusters/ota-requestor/DefaultOTARequestor.cpp.obj 
ccache /opt/nordic/ncs/toolchains/v2.1.0/opt/zephyr-sdk/arm-zephyr-eabi/bin/arm-zephyr-eabi-g++ -DCHIP_HAVE_CONFIG_H -DKERNEL -DMBEDTLS_CONFIG_FILE=\"nrf-config.h\" -DMBEDTLS_USER_CONFIG_FILE=\"nrf-config-user.h\" -DNRF5340_XXAA_APPLICATION -DNRF_802154_ACK_TIMEOUT_ENABLED=1 -DNRF_802154_ECB_PRIORITY=-1 -DNRF_802154_ENCRYPTION_ENABLED=1 -DNRF_802154_IE_WRITER_ENABLED=1 -DNRF_802154_INTERNAL_RADIO_IRQ_HANDLING=0 -DNRF_802154_PENDING_EXTENDED_ADDRESSES="" -DNRF_802154_PENDING_SHORT_ADDRESSES="" -DNRF_802154_RX_BUFFERS=16 -DNRF_802154_SECURITY_WRITER_ENABLED=1 -DNRF_802154_SWI_PRIORITY=1 -DNRF_802154_TX_STARTED_NOTIFY_ENABLED=1 -DNRF_802154_USE_RAW_API=1 -DNRF_SKIP_FICR_NS_COPY_TO_RAM -DUSE_PARTITION_MANAGER=1 -DZCBOR_ASSERT -D_FORTIFY_SOURCE=2 -D__LINUX_ERRNO_EXTENSIONS__ -D__PROGRAM_START -D__ZEPHYR__=1 -I../src -I/opt/nordic/ncs/v2.1.0/nrf/samples/matter/common/src -I/opt/nordic/ncs/v2.1.0/modules/lib/matter/third_party/nlio/repo/include -I/opt/nordic/ncs/v2.1.0/modules/lib/matter/zzz_generated/app-common -I/opt/nordic/ncs/v2.1.0/zephyr/include/zephyr -I/opt/nordic/ncs/v2.1.0/zephyr/include -Izephyr/include/generated -I/opt/nordic/ncs/v2.1.0/zephyr/soc/arm/nordic_nrf/nrf53 -I/opt/nordic/ncs/v2.1.0/zephyr/lib/libc/newlib/include -I/opt/nordic/ncs/v2.1.0/zephyr/lib/util/fnmatch/. -I/opt/nordic/ncs/v2.1.0/zephyr/soc/arm/nordic_nrf/common/. -I/opt/nordic/ncs/v2.1.0/zephyr/subsys/bluetooth -I/opt/nordic/ncs/v2.1.0/zephyr/subsys/net/lib/sockets/. -I/opt/nordic/ncs/v2.1.0/zephyr/subsys/net/lib/openthread/platform/. -I/opt/nordic/ncs/v2.1.0/zephyr/subsys/settings/include -I/opt/nordic/ncs/v2.1.0/nrf/include -I/opt/nordic/ncs/v2.1.0/modules/lib/zcbor/include -I/opt/nordic/ncs/v2.1.0/modules/hal/cmsis/CMSIS/Core/Include -I/opt/nordic/ncs/v2.1.0/modules/hal/nordic/nrfx -I/opt/nordic/ncs/v2.1.0/modules/hal/nordic/nrfx/drivers/include -I/opt/nordic/ncs/v2.1.0/modules/hal/nordic/nrfx/mdk -I/opt/nordic/ncs/v2.1.0/zephyr/modules/hal_nordic/nrfx/. -Imodules/libmetal/libmetal/lib/include -I/opt/nordic/ncs/v2.1.0/modules/lib/open-amp/open-amp/lib/include -I/opt/nordic/ncs/v2.1.0/modules/crypto/tinycrypt/lib/include -I/opt/nordic/ncs/v2.1.0/nrfxlib/openthread/include -Imodules/nrfxlib/nrfxlib/nrf_security/src/include/generated -I/opt/nordic/ncs/v2.1.0/nrfxlib/nrf_security/include -I/opt/nordic/ncs/v2.1.0/nrfxlib/nrf_security/include/mbedtls -I/opt/nordic/ncs/v2.1.0/nrfxlib/nrf_security/include/psa -I/opt/nordic/ncs/v2.1.0/mbedtls/include -I/opt/nordic/ncs/v2.1.0/mbedtls/include/mbedtls -I/opt/nordic/ncs/v2.1.0/mbedtls/include/psa -I/opt/nordic/ncs/v2.1.0/mbedtls/library -I/opt/nordic/ncs/v2.1.0/nrfxlib/nrf_security/../crypto/nrf_oberon/include -I/opt/nordic/ncs/v2.1.0/nrfxlib/nrf_security/../crypto/nrf_oberon/include/mbedtls -I/opt/nordic/ncs/v2.1.0/nrfxlib/nrf_security/../crypto/nrf_oberon/include/psa -I/opt/nordic/ncs/v2.1.0/nrfxlib/crypto/nrf_oberon/include/mbedtls -I/opt/nordic/ncs/v2.1.0/nrfxlib/crypto/nrf_oberon/include -I/opt/nordic/ncs/v2.1.0/nrfxlib/softdevice_controller/include -I/opt/nordic/ncs/v2.1.0/nrfxlib/nrf_802154/serialization/include -I/opt/nordic/ncs/v2.1.0/nrfxlib/nrf_802154/serialization/include/platform -I/opt/nordic/ncs/v2.1.0/nrfxlib/nrf_802154/serialization/include/serialization -I/opt/nordic/ncs/v2.1.0/nrfxlib/nrf_802154/serialization/include/host -I/opt/nordic/ncs/v2.1.0/zephyr/include/zephyr/posix -I/opt/nordic/ncs/v2.1.0/modules/lib/matter/src -I/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/include -I/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/lib -I/opt/nordic/ncs/v2.1.0/modules/lib/matter/third_party/nlassert/repo/include -Imodules/connectedhomeip/gen/include -isystem /opt/nordic/ncs/v2.1.0/nrfxlib/crypto/nrf_cc312_platform/include "-DCHIP_ADDRESS_RESOLVE_IMPL_INCLUDE_HEADER=<lib/address_resolve/AddressResolve_DefaultImpl.h>" -Os -fcheck-new -std=c++14 -Wno-register -fno-exceptions -fno-rtti -imacros /Users/bennynestler/workspaces/matter/nRFConnect/original_template/build/zephyr/include/generated/autoconf.h -ffreestanding -fno-common -g -gdwarf-4 -fdiagnostics-color=always -mcpu=cortex-m33 -mthumb -mabi=aapcs -mfpu=fpv5-sp-d16 -mfloat-abi=hard -mfp16-format=ieee -imacros /opt/nordic/ncs/v2.1.0/zephyr/include/zephyr/toolchain/zephyr_stdint.h -Wall -Wformat -Wformat-security -Wno-format-zero-length -Wno-main -Wpointer-arith -Wexpansion-to-defined -Wno-unused-but-set-variable -fno-asynchronous-unwind-tables -fno-pie -fno-pic -fno-reorder-functions -fno-defer-pop -fmacro-prefix-map=/Users/bennynestler/workspaces/matter/nRFConnect/original_template=CMAKE_SOURCE_DIR -fmacro-prefix-map=/opt/nordic/ncs/v2.1.0/zephyr=ZEPHYR_BASE -fmacro-prefix-map=/opt/nordic/ncs/v2.1.0=WEST_TOPDIR -ffunction-sections -fdata-sections -specs=nano.specs -std=gnu++17 -D_SYS__PTHREADTYPES_H_ -MD -MT CMakeFiles/app.dir/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/clusters/ota-requestor/DefaultOTARequestor.cpp.obj -MF CMakeFiles/app.dir/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/clusters/ota-requestor/DefaultOTARequestor.cpp.obj.d -o CMakeFiles/app.dir/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/clusters/ota-requestor/DefaultOTARequestor.cpp.obj -c /opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/clusters/ota-requestor/DefaultOTARequestor.cpp
/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/clusters/ota-requestor/DefaultOTARequestor.cpp: In member function 'CHIP_ERROR chip::DefaultOTARequestor::SendQueryImageRequest(chip::OperationalDeviceProxy&)':
/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/clusters/ota-requestor/DefaultOTARequestor.cpp:757:17: error: 'OtaSoftwareUpdateProviderCluster' is not a member of 'chip::Controller'
  757 |     Controller::OtaSoftwareUpdateProviderCluster cluster;
      |                 ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/clusters/ota-requestor/DefaultOTARequestor.cpp:757:17: note: maximum limit of 1000 namespaces searched for 'OtaSoftwareUpdateProviderCluster'
/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/clusters/ota-requestor/DefaultOTARequestor.cpp:758:5: error: 'cluster' was not declared in this scope
  758 |     cluster.Associate(&deviceProxy, mProviderLocation.Value().endpoint);
      |     ^~~~~~~
/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/clusters/ota-requestor/DefaultOTARequestor.cpp:758:5: note: maximum limit of 1000 namespaces searched for 'cluster'
/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/clusters/ota-requestor/DefaultOTARequestor.cpp: In member function 'CHIP_ERROR chip::DefaultOTARequestor::SendApplyUpdateRequest(chip::OperationalDeviceProxy&)':
/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/clusters/ota-requestor/DefaultOTARequestor.cpp:827:17: error: 'OtaSoftwareUpdateProviderCluster' is not a member of 'chip::Controller'
  827 |     Controller::OtaSoftwareUpdateProviderCluster cluster;
      |                 ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/clusters/ota-requestor/DefaultOTARequestor.cpp:827:17: note: maximum limit of 1000 namespaces searched for 'OtaSoftwareUpdateProviderCluster'
/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/clusters/ota-requestor/DefaultOTARequestor.cpp:828:5: error: 'cluster' was not declared in this scope
  828 |     cluster.Associate(&deviceProxy, mProviderLocation.Value().endpoint);
      |     ^~~~~~~
/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/clusters/ota-requestor/DefaultOTARequestor.cpp:828:5: note: maximum limit of 1000 namespaces searched for 'cluster'
/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/clusters/ota-requestor/DefaultOTARequestor.cpp: In member function 'CHIP_ERROR chip::DefaultOTARequestor::SendNotifyUpdateAppliedRequest(chip::OperationalDeviceProxy&)':
/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/clusters/ota-requestor/DefaultOTARequestor.cpp:842:17: error: 'OtaSoftwareUpdateProviderCluster' is not a member of 'chip::Controller'
  842 |     Controller::OtaSoftwareUpdateProviderCluster cluster;
      |                 ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/clusters/ota-requestor/DefaultOTARequestor.cpp:842:17: note: maximum limit of 1000 namespaces searched for 'OtaSoftwareUpdateProviderCluster'
/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/clusters/ota-requestor/DefaultOTARequestor.cpp:843:5: error: 'cluster' was not declared in this scope
  843 |     cluster.Associate(&deviceProxy, mProviderLocation.Value().endpoint);
      |     ^~~~~~~
/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/clusters/ota-requestor/DefaultOTARequestor.cpp:843:5: note: maximum limit of 1000 namespaces searched for 'cluster'
[19/55] Building CXX object CMakeFiles/app.dir/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/clusters/ota-requestor/ota-requestor-server.cpp.obj
[20/55] Building CXX object CMakeFiles/app.dir/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/clusters/thread-network-diagnostics-server/thread-network-diagnostics-server.cpp.obj
[21/55] Building CXX object CMakeFiles/app.dir/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/clusters/software-diagnostics-server/software-diagnostics-server.cpp.obj
[22/55] Building CXX object CMakeFiles/app.dir/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/clusters/time-format-localization-server/time-format-localization-server.cpp.obj
[23/55] Building CXX object CMakeFiles/app.dir/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/util/af-event.cpp.obj
[24/55] Building CXX object CMakeFiles/app.dir/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/util/attribute-table.cpp.obj
[25/55] Building CXX object CMakeFiles/app.dir/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/clusters/operational-credentials-server/operational-credentials-server.cpp.obj
[26/55] Building CXX object CMakeFiles/app.dir/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/util/attribute-storage.cpp.obj
[27/55] Building CXX object CMakeFiles/app.dir/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/util/client-api.cpp.obj
[28/55] Building CXX object CMakeFiles/app.dir/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/util/DataModelHandler.cpp.obj
[29/55] Building CXX object CMakeFiles/app.dir/opt/nordic/ncs/v2.1.0/modules/lib/matter/zzz_generated/app-common/app-common/zap-generated/attributes/Accessors.cpp.obj
ninja: build stopped: subcommand failed.
FATAL ERROR: command exited with status 1: /opt/nordic/ncs/toolchains/v2.1.0/bin/cmake --build /Users/bennynestler/workspaces/matter/nRFConnect/original_template/build

 *  The terminal process terminated with exit code: 1. 
 *  Terminal will be reused by tasks, press any key to close it.

Best regards,

Benny

RE: [Matter] Changing or adding Endpoints/Clusters to Matter-Template example with the zap tool leads to compiling errors

Marte Myrvold — Mon, 17 Oct 2022 13:35:41 GMT

Hi,

The other clusters are required clusters. Some are mandatory for all Matter devices, and others are for Temperature sensor device specifically. You can read about the required clusters for different device types in the Matter Device Library specification.

The error messages are related to OTA and not the other clusters. I am not sure why you are getting this error, but I will look into it and get back to you tomorrow.

Best regards,

Marte

RE: [Matter] Changing or adding Endpoints/Clusters to Matter-Template example with the zap tool leads to compiling errors

Benny Nestler — Mon, 17 Oct 2022 11:44:44 GMT

Hi Marte Myrvold

I've found a solution for my Issue:

The solution is described in this link https://stackoverflow.com/questions/72553650/how-to-get-node-sqlite3-working-on-mac-m1

The issue seems to be the arm64 node-sqlite3 implementation.

After solving my problem, I work on all points of the description https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/ug_matter_gs_adding_clusters.html#ug-matter-creating-accessory

But there are also errors, but different as I described in my initial post.

The errors are in the linker process:

 *  Executing task: nRF Connect: Build: original_template/build (active) 

Building original_template
west build --build-dir /Users/bennynestler/workspaces/matter/nRFConnect/original_template/build /Users/bennynestler/workspaces/matter/nRFConnect/original_template

[0/65] Performing build step for 'multiprotocol_rpmsg_subimage'
[0/5] Performing build step for 'b0n_subimage'
ninja: no work to do.
[1/59] Performing build step for 'mcuboot_subimage'
ninja: no work to do.
[2/57] Performing build step for 'chip-gn'
Generating compile_commands took 6ms
Done. Made 77 targets from 84 files in 30ms
ninja: no work to do.
[4/55] Building CXX object CMakeFiles/app.dir/src/zap-generated/callback-stub.cpp.obj
[5/55] Building CXX object CMakeFiles/app.dir/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/clusters/diagnostic-logs-server/diagnostic-logs-server.cpp.obj
[6/55] Building CXX object CMakeFiles/app.dir/src/zap-generated/IMClusterCommandHandler.cpp.obj
[7/55] Building CXX object CMakeFiles/app.dir/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/clusters/descriptor/descriptor.cpp.obj
[8/55] Building CXX object CMakeFiles/app.dir/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/clusters/localization-configuration-server/localization-configuration-server.cpp.obj
[9/55] Building CXX object CMakeFiles/app.dir/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/clusters/basic/basic.cpp.obj
[10/55] Building CXX object CMakeFiles/app.dir/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/clusters/general-diagnostics-server/general-diagnostics-server.cpp.obj
[11/55] Building CXX object CMakeFiles/app.dir/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/clusters/general-commissioning-server/general-commissioning-server.cpp.obj
[12/55] Building CXX object CMakeFiles/app.dir/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/clusters/administrator-commissioning-server/administrator-commissioning-server.cpp.obj
[13/55] Building CXX object CMakeFiles/app.dir/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/clusters/group-key-mgmt-server/group-key-mgmt-server.cpp.obj
[14/55] Building CXX object CMakeFiles/app.dir/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/clusters/network-commissioning/network-commissioning.cpp.obj
[15/55] Building CXX object CMakeFiles/app.dir/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/clusters/access-control-server/access-control-server.cpp.obj
[16/55] Building CXX object CMakeFiles/app.dir/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/util/attribute-size-util.cpp.obj
[17/55] Building CXX object CMakeFiles/app.dir/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/util/binding-table.cpp.obj
[18/55] Building CXX object CMakeFiles/app.dir/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/clusters/ota-requestor/DefaultOTARequestor.cpp.obj
FAILED: CMakeFiles/app.dir/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/clusters/ota-requestor/DefaultOTARequestor.cpp.obj 
ccache /opt/nordic/ncs/toolchains/v2.1.0/opt/zephyr-sdk/arm-zephyr-eabi/bin/arm-zephyr-eabi-g++ -DCHIP_HAVE_CONFIG_H -DKERNEL -DMBEDTLS_CONFIG_FILE=\"nrf-config.h\" -DMBEDTLS_USER_CONFIG_FILE=\"nrf-config-user.h\" -DNRF5340_XXAA_APPLICATION -DNRF_802154_ACK_TIMEOUT_ENABLED=1 -DNRF_802154_ECB_PRIORITY=-1 -DNRF_802154_ENCRYPTION_ENABLED=1 -DNRF_802154_IE_WRITER_ENABLED=1 -DNRF_802154_INTERNAL_RADIO_IRQ_HANDLING=0 -DNRF_802154_PENDING_EXTENDED_ADDRESSES="" -DNRF_802154_PENDING_SHORT_ADDRESSES="" -DNRF_802154_RX_BUFFERS=16 -DNRF_802154_SECURITY_WRITER_ENABLED=1 -DNRF_802154_SWI_PRIORITY=1 -DNRF_802154_TX_STARTED_NOTIFY_ENABLED=1 -DNRF_802154_USE_RAW_API=1 -DNRF_SKIP_FICR_NS_COPY_TO_RAM -DUSE_PARTITION_MANAGER=1 -DZCBOR_ASSERT -D_FORTIFY_SOURCE=2 -D__LINUX_ERRNO_EXTENSIONS__ -D__PROGRAM_START -D__ZEPHYR__=1 -I../src -I/opt/nordic/ncs/v2.1.0/nrf/samples/matter/common/src -I/opt/nordic/ncs/v2.1.0/modules/lib/matter/third_party/nlio/repo/include -I/opt/nordic/ncs/v2.1.0/modules/lib/matter/zzz_generated/app-common -I/opt/nordic/ncs/v2.1.0/zephyr/include/zephyr -I/opt/nordic/ncs/v2.1.0/zephyr/include -Izephyr/include/generated -I/opt/nordic/ncs/v2.1.0/zephyr/soc/arm/nordic_nrf/nrf53 -I/opt/nordic/ncs/v2.1.0/zephyr/lib/libc/newlib/include -I/opt/nordic/ncs/v2.1.0/zephyr/lib/util/fnmatch/. -I/opt/nordic/ncs/v2.1.0/zephyr/soc/arm/nordic_nrf/common/. -I/opt/nordic/ncs/v2.1.0/zephyr/subsys/bluetooth -I/opt/nordic/ncs/v2.1.0/zephyr/subsys/net/lib/sockets/. -I/opt/nordic/ncs/v2.1.0/zephyr/subsys/net/lib/openthread/platform/. -I/opt/nordic/ncs/v2.1.0/zephyr/subsys/settings/include -I/opt/nordic/ncs/v2.1.0/nrf/include -I/opt/nordic/ncs/v2.1.0/modules/lib/zcbor/include -I/opt/nordic/ncs/v2.1.0/modules/hal/cmsis/CMSIS/Core/Include -I/opt/nordic/ncs/v2.1.0/modules/hal/nordic/nrfx -I/opt/nordic/ncs/v2.1.0/modules/hal/nordic/nrfx/drivers/include -I/opt/nordic/ncs/v2.1.0/modules/hal/nordic/nrfx/mdk -I/opt/nordic/ncs/v2.1.0/zephyr/modules/hal_nordic/nrfx/. -Imodules/libmetal/libmetal/lib/include -I/opt/nordic/ncs/v2.1.0/modules/lib/open-amp/open-amp/lib/include -I/opt/nordic/ncs/v2.1.0/modules/crypto/tinycrypt/lib/include -I/opt/nordic/ncs/v2.1.0/nrfxlib/openthread/include -Imodules/nrfxlib/nrfxlib/nrf_security/src/include/generated -I/opt/nordic/ncs/v2.1.0/nrfxlib/nrf_security/include -I/opt/nordic/ncs/v2.1.0/nrfxlib/nrf_security/include/mbedtls -I/opt/nordic/ncs/v2.1.0/nrfxlib/nrf_security/include/psa -I/opt/nordic/ncs/v2.1.0/mbedtls/include -I/opt/nordic/ncs/v2.1.0/mbedtls/include/mbedtls -I/opt/nordic/ncs/v2.1.0/mbedtls/include/psa -I/opt/nordic/ncs/v2.1.0/mbedtls/library -I/opt/nordic/ncs/v2.1.0/nrfxlib/nrf_security/../crypto/nrf_oberon/include -I/opt/nordic/ncs/v2.1.0/nrfxlib/nrf_security/../crypto/nrf_oberon/include/mbedtls -I/opt/nordic/ncs/v2.1.0/nrfxlib/nrf_security/../crypto/nrf_oberon/include/psa -I/opt/nordic/ncs/v2.1.0/nrfxlib/crypto/nrf_oberon/include/mbedtls -I/opt/nordic/ncs/v2.1.0/nrfxlib/crypto/nrf_oberon/include -I/opt/nordic/ncs/v2.1.0/nrfxlib/softdevice_controller/include -I/opt/nordic/ncs/v2.1.0/nrfxlib/nrf_802154/serialization/include -I/opt/nordic/ncs/v2.1.0/nrfxlib/nrf_802154/serialization/include/platform -I/opt/nordic/ncs/v2.1.0/nrfxlib/nrf_802154/serialization/include/serialization -I/opt/nordic/ncs/v2.1.0/nrfxlib/nrf_802154/serialization/include/host -I/opt/nordic/ncs/v2.1.0/zephyr/include/zephyr/posix -I/opt/nordic/ncs/v2.1.0/modules/lib/matter/src -I/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/include -I/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/lib -I/opt/nordic/ncs/v2.1.0/modules/lib/matter/third_party/nlassert/repo/include -Imodules/connectedhomeip/gen/include -isystem /opt/nordic/ncs/v2.1.0/nrfxlib/crypto/nrf_cc312_platform/include "-DCHIP_ADDRESS_RESOLVE_IMPL_INCLUDE_HEADER=<lib/address_resolve/AddressResolve_DefaultImpl.h>" -Os -fcheck-new -std=c++14 -Wno-register -fno-exceptions -fno-rtti -imacros /Users/bennynestler/workspaces/matter/nRFConnect/original_template/build/zephyr/include/generated/autoconf.h -ffreestanding -fno-common -g -gdwarf-4 -fdiagnostics-color=always -mcpu=cortex-m33 -mthumb -mabi=aapcs -mfpu=fpv5-sp-d16 -mfloat-abi=hard -mfp16-format=ieee -imacros /opt/nordic/ncs/v2.1.0/zephyr/include/zephyr/toolchain/zephyr_stdint.h -Wall -Wformat -Wformat-security -Wno-format-zero-length -Wno-main -Wpointer-arith -Wexpansion-to-defined -Wno-unused-but-set-variable -fno-asynchronous-unwind-tables -fno-pie -fno-pic -fno-reorder-functions -fno-defer-pop -fmacro-prefix-map=/Users/bennynestler/workspaces/matter/nRFConnect/original_template=CMAKE_SOURCE_DIR -fmacro-prefix-map=/opt/nordic/ncs/v2.1.0/zephyr=ZEPHYR_BASE -fmacro-prefix-map=/opt/nordic/ncs/v2.1.0=WEST_TOPDIR -ffunction-sections -fdata-sections -specs=nano.specs -std=gnu++17 -D_SYS__PTHREADTYPES_H_ -MD -MT CMakeFiles/app.dir/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/clusters/ota-requestor/DefaultOTARequestor.cpp.obj -MF CMakeFiles/app.dir/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/clusters/ota-requestor/DefaultOTARequestor.cpp.obj.d -o CMakeFiles/app.dir/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/clusters/ota-requestor/DefaultOTARequestor.cpp.obj -c /opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/clusters/ota-requestor/DefaultOTARequestor.cpp
/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/clusters/ota-requestor/DefaultOTARequestor.cpp: In member function 'CHIP_ERROR chip::DefaultOTARequestor::SendQueryImageRequest(chip::OperationalDeviceProxy&)':
/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/clusters/ota-requestor/DefaultOTARequestor.cpp:757:17: error: 'OtaSoftwareUpdateProviderCluster' is not a member of 'chip::Controller'
  757 |     Controller::OtaSoftwareUpdateProviderCluster cluster;
      |                 ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/clusters/ota-requestor/DefaultOTARequestor.cpp:757:17: note: maximum limit of 1000 namespaces searched for 'OtaSoftwareUpdateProviderCluster'
/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/clusters/ota-requestor/DefaultOTARequestor.cpp:758:5: error: 'cluster' was not declared in this scope
  758 |     cluster.Associate(&deviceProxy, mProviderLocation.Value().endpoint);
      |     ^~~~~~~
/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/clusters/ota-requestor/DefaultOTARequestor.cpp:758:5: note: maximum limit of 1000 namespaces searched for 'cluster'
/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/clusters/ota-requestor/DefaultOTARequestor.cpp: In member function 'CHIP_ERROR chip::DefaultOTARequestor::SendApplyUpdateRequest(chip::OperationalDeviceProxy&)':
/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/clusters/ota-requestor/DefaultOTARequestor.cpp:827:17: error: 'OtaSoftwareUpdateProviderCluster' is not a member of 'chip::Controller'
  827 |     Controller::OtaSoftwareUpdateProviderCluster cluster;
      |                 ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/clusters/ota-requestor/DefaultOTARequestor.cpp:827:17: note: maximum limit of 1000 namespaces searched for 'OtaSoftwareUpdateProviderCluster'
/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/clusters/ota-requestor/DefaultOTARequestor.cpp:828:5: error: 'cluster' was not declared in this scope
  828 |     cluster.Associate(&deviceProxy, mProviderLocation.Value().endpoint);
      |     ^~~~~~~
/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/clusters/ota-requestor/DefaultOTARequestor.cpp:828:5: note: maximum limit of 1000 namespaces searched for 'cluster'
/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/clusters/ota-requestor/DefaultOTARequestor.cpp: In member function 'CHIP_ERROR chip::DefaultOTARequestor::SendNotifyUpdateAppliedRequest(chip::OperationalDeviceProxy&)':
/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/clusters/ota-requestor/DefaultOTARequestor.cpp:842:17: error: 'OtaSoftwareUpdateProviderCluster' is not a member of 'chip::Controller'
  842 |     Controller::OtaSoftwareUpdateProviderCluster cluster;
      |                 ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/clusters/ota-requestor/DefaultOTARequestor.cpp:842:17: note: maximum limit of 1000 namespaces searched for 'OtaSoftwareUpdateProviderCluster'
/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/clusters/ota-requestor/DefaultOTARequestor.cpp:843:5: error: 'cluster' was not declared in this scope
  843 |     cluster.Associate(&deviceProxy, mProviderLocation.Value().endpoint);
      |     ^~~~~~~
/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/clusters/ota-requestor/DefaultOTARequestor.cpp:843:5: note: maximum limit of 1000 namespaces searched for 'cluster'
[19/55] Building CXX object CMakeFiles/app.dir/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/clusters/ota-requestor/ota-requestor-server.cpp.obj
[20/55] Building CXX object CMakeFiles/app.dir/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/clusters/thread-network-diagnostics-server/thread-network-diagnostics-server.cpp.obj
[21/55] Building CXX object CMakeFiles/app.dir/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/clusters/software-diagnostics-server/software-diagnostics-server.cpp.obj
[22/55] Building CXX object CMakeFiles/app.dir/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/clusters/time-format-localization-server/time-format-localization-server.cpp.obj
[23/55] Building CXX object CMakeFiles/app.dir/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/util/af-event.cpp.obj
[24/55] Building CXX object CMakeFiles/app.dir/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/util/attribute-table.cpp.obj
[25/55] Building CXX object CMakeFiles/app.dir/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/clusters/operational-credentials-server/operational-credentials-server.cpp.obj
[26/55] Building CXX object CMakeFiles/app.dir/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/util/attribute-storage.cpp.obj
[27/55] Building CXX object CMakeFiles/app.dir/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/util/client-api.cpp.obj
[28/55] Building CXX object CMakeFiles/app.dir/opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/util/DataModelHandler.cpp.obj
[29/55] Building CXX object CMakeFiles/app.dir/opt/nordic/ncs/v2.1.0/modules/lib/matter/zzz_generated/app-common/app-common/zap-generated/attributes/Accessors.cpp.obj
ninja: build stopped: subcommand failed.
FATAL ERROR: command exited with status 1: /opt/nordic/ncs/toolchains/v2.1.0/bin/cmake --build /Users/bennynestler/workspaces/matter/nRFConnect/original_template/build

 *  The terminal process terminated with exit code: 1.

Seems to be that the zap - Tool enables more than the described clusters (of your guide). Should I try to deactivate some of the clusters?

What does "basic" - Cluster means in your description?

Where are more Cluster which are enabled by default!

RE: [Matter] Changing or adding Endpoints/Clusters to Matter-Template example with the zap tool leads to compiling errors

Benny Nestler — Mon, 17 Oct 2022 08:31:28 GMT

Hi Marte Myrvold

that doesn't work for me.

See the following log (same error as with the current node/npm version):

bennynestler@MBPvonBenjamin(x86_64) /opt/nordic/ncs/v2.1.0/modules/lib/matter % node -v
v15.4.0
bennynestler@MBPvonBenjamin(x86_64) /opt/nordic/ncs/v2.1.0/modules/lib/matter % npm -v
7.7.6
bennynestler@MBPvonBenjamin(x86_64) /opt/nordic/ncs/v2.1.0/modules/lib/matter % cd third_party/zap/repo 
bennynestler@MBPvonBenjamin(x86_64) /opt/nordic/ncs/v2.1.0/modules/lib/matter/third_party/zap/repo % git clean -fdx
Removing .quasar/
Removing .version.json
Removing dist/
Removing node_modules/
Removing spa/
bennynestler@MBPvonBenjamin(x86_64) /opt/nordic/ncs/v2.1.0/modules/lib/matter/third_party/zap/repo % cd ../../../     
bennynestler@MBPvonBenjamin(x86_64) /opt/nordic/ncs/v2.1.0/modules/lib/matter % ./scripts/tools/zap/run_zaptool.sh ~/workspaces/matter/nRFConnect/template/src/template.zap
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '@npmcli/fs@1.1.0',
npm WARN EBADENGINE   required: { node: '^12.13.0 || ^14.15.0 || >=16' },
npm WARN EBADENGINE   current: { node: 'v15.4.0', npm: '7.7.6' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '@voxpelli/semver-set@4.0.0',
npm WARN EBADENGINE   required: { node: '^14.18.0 || >=16.0.0' },
npm WARN EBADENGINE   current: { node: 'v15.4.0', npm: '7.7.6' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'installed-check@6.0.4',
npm WARN EBADENGINE   required: { node: '^14.18.0 || >=16.0.0' },
npm WARN EBADENGINE   current: { node: 'v15.4.0', npm: '7.7.6' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'installed-check-core@6.0.2',
npm WARN EBADENGINE   required: { node: '^14.18.0 || >=16.0.0' },
npm WARN EBADENGINE   current: { node: 'v15.4.0', npm: '7.7.6' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'chalk@5.1.2',
npm WARN EBADENGINE   required: { node: '^12.17.0 || ^14.13 || >=16.0.0' },
npm WARN EBADENGINE   current: { node: 'v15.4.0', npm: '7.7.6' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'list-installed@2.0.1',
npm WARN EBADENGINE   required: { node: '^14.18.0 || >=16.0.0' },
npm WARN EBADENGINE   current: { node: 'v15.4.0', npm: '7.7.6' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'meow@10.1.5',
npm WARN EBADENGINE   required: { node: '^12.20.0 || ^14.13.1 || >=16.0.0' },
npm WARN EBADENGINE   current: { node: 'v15.4.0', npm: '7.7.6' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'gauge@4.0.0',
npm WARN EBADENGINE   required: { node: '^12.13.0 || ^14.15.0 || >=16' },
npm WARN EBADENGINE   current: { node: 'v15.4.0', npm: '7.7.6' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'npmlog@6.0.0',
npm WARN EBADENGINE   required: { node: '^12.13.0 || ^14.15.0 || >=16' },
npm WARN EBADENGINE   current: { node: 'v15.4.0', npm: '7.7.6' }
npm WARN EBADENGINE }
npm WARN deprecated @types/anymatch@3.0.0: This is a stub types definition. anymatch provides its own type definitions, so you do not need this installed.
npm WARN deprecated stable@0.1.8: Modern JS already guarantees Array#sort() is a stable sort, so this library is deprecated. See the compatibility table on MDN: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort#browser_compatibility
npm WARN deprecated source-map-url@0.4.1: See https://github.com/lydell/source-map-url#deprecated
npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated har-validator@5.1.5: this library is no longer supported
npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated source-map-resolve@0.5.3: See https://github.com/lydell/source-map-resolve#deprecated
npm WARN deprecated w3c-hr-time@1.0.2: Use your platform's native performance.now() and performance.timeOrigin.
npm WARN deprecated sane@4.1.0: some dependency vulnerabilities fixed, support for node < 10 dropped, and newer ECMAScript syntax/features added
npm WARN deprecated fsevents@1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm WARN deprecated chokidar@2.1.8: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
npm WARN deprecated fsevents@1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm WARN deprecated chokidar@2.1.8: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
npm WARN deprecated eslint-loader@4.0.2: This loader has been deprecated. Please use eslint-webpack-plugin
npm WARN deprecated querystring@0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated babel-eslint@10.1.0: babel-eslint is now @babel/eslint-parser. This package will no longer receive updates.
npm WARN deprecated uuid@3.4.0: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated uuid@3.4.0: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated uuid@3.4.0: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated electron-osx-sign@0.4.17: Please use @electron/osx-sign moving forward. Be aware the API is slightly different
npm WARN deprecated electron-osx-sign@0.5.0: Please use @electron/osx-sign moving forward. Be aware the API is slightly different
npm WARN deprecated electron-osx-sign@0.5.0: Please use @electron/osx-sign moving forward. Be aware the API is slightly different
npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated @npmcli/fs@1.1.0: this version had an improper engines field added, update to 1.1.1
npm WARN deprecated node-pre-gyp@0.11.0: Please upgrade to @mapbox/node-pre-gyp: the non-scoped node-pre-gyp package is deprecated and only the @mapbox scoped package will recieve updates in the future
npm WARN deprecated node-pre-gyp@0.17.0: Please upgrade to @mapbox/node-pre-gyp: the non-scoped node-pre-gyp package is deprecated and only the @mapbox scoped package will recieve updates in the future
npm WARN deprecated svgo@1.3.2: This SVGO version is no longer supported. Upgrade to v2.x.x.
npm WARN deprecated highlight.js@9.18.5: Support has ended for 9.x series. Upgrade to @latest
npm WARN deprecated core-js@2.6.12: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
npm WARN deprecated core-js@2.6.12: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
npm WARN deprecated core-js@3.21.1: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.

added 3075 packages, and audited 3076 packages in 17s

199 packages are looking for funding
  run `npm fund` for details

37 vulnerabilities (1 low, 14 moderate, 17 high, 5 critical)

To address issues that do not require attention, run:
  npm audit fix

To address all issues possible (including breaking changes), run:
  npm audit fix --force

Some issues need review, and may require choosing
a different dependency.

Run `npm audit` for details.
npm notice 
npm notice New major version of npm available! 7.7.6 -> 8.19.2
npm notice Changelog: https://github.com/npm/cli/releases/tag/v8.19.2
npm notice Run npm install -g npm@8.19.2 to update!
npm notice 
🚀 Executing: git log -1 --format={"hash": "%H","timestamp": %ct}
🔍 Git commit: e9277b989f1d128bc881e88ecbf7a3353c841c39 from Wed May 11 2022 16:45:40 GMT+0200 (Mitteleuropäische Sommerzeit)
🔍 Current src hash: aqrjjVB67BD5DC9iha9ORJah5zc=
🔍 Current src-shared hash: nOWlRqSeZbEDOkt+AnCdf01DNYM=
👎 Error reading old hash file: /opt/nordic/ncs/v2.1.0/modules/lib/matter/third_party/zap/repo/spa/hash.json
🐝 Front-end code changed, so we need to rebuild SPA.
🚀 Executing: npx quasar build

 Build mode........ spa
 Pkg quasar........ v1.17.1
 Pkg @quasar/app... v2.2.11
 Debugging......... no
 Publishing........ no

⇝ Browserslist: caniuse-lite is outdated. Please run:
  npx browserslist@latest --update-db
  Why you should do it regularly: https://github.com/browserslist/browserslist#browsers-data-updating
 Configured browser support (at least 45.26% of global marketshare):
 · Chrome for Android >= 96
 · Firefox for Android >= 95
 · QQ for Android >= 10.4
 · UC for Android >= 12.12
 · Android >= 96
 · Baidu >= 7.12
 · Chrome >= 97
 · Edge >= 97
 · Firefox >= 95
 · IE >= 11
 · iOS >= 15.2
 · Kaios >= 2.5
 · Opera Mini >= all
 · Opera Mobile >= 64
 · Opera >= 82
 · Safari >= 15.2
 · Samsung >= 15.0

 App · Running "@quasar/testing" Quasar App Extension...
 App · Running "@quasar/testing-unit-jest" Quasar App Extension...
 App · Running "@quasar/testing-e2e-cypress" Quasar App Extension...
 App · Reading quasar.conf.js
 App · Extension(@quasar/testing-e2e-cypress): Extending quasar.conf...
 App · Transpiling JS (Babel active) - includes IE11 support
 App · Extending SPA Webpack config
 App · Cleaned build artifact: "/opt/nordic/ncs/v2.1.0/modules/lib/matter/third_party/zap/repo/spa"
 App · Generating Webpack entry point
 App · Compiling with Webpack...
Starting type checking service...
 App · Compiling SPA...
 App · Compiled SPA done in 18157 ms
 App · Added build artifact "/opt/nordic/ncs/v2.1.0/modules/lib/matter/third_party/zap/repo/spa"

 Build summary for css/js/json (the rest are omitted):
 ╔═════════════════════╤═══════════╤═══════════╗
 ║               Asset │      Size │   Gzipped ║
 ╟─────────────────────┼───────────┼───────────╢
 ║      1.8ce39149.css │   0.48 KB │   0.28 KB ║
 ║      3.d57d983c.css │   0.11 KB │   0.11 KB ║
 ║    app.674ffe40.css │   0.77 KB │   0.28 KB ║
 ║ vendor.c6e57c02.css │ 415.08 KB │  71.23 KB ║
 ╟─────────────────────┼───────────┼───────────╢
 ║       1.8a969588.js │  56.43 KB │  13.27 KB ║
 ║       3.c3bcbf14.js │  38.07 KB │   7.21 KB ║
 ║       4.b0d2a606.js │   7.29 KB │   2.61 KB ║
 ║       5.a885112d.js │   1.49 KB │   0.81 KB ║
 ║       6.4326c2f9.js │  12.10 KB │   3.86 KB ║
 ║       7.0e860913.js │   7.02 KB │   2.32 KB ║
 ║     app.5da6689e.js │  54.10 KB │  13.86 KB ║
 ║  vendor.dbd8f6a2.js │ 655.43 KB │ 207.66 KB ║
 ╚═════════════════════╧═══════════╧═══════════╝
 
 Build succeeded

 Build mode........ spa
 Pkg quasar........ v1.17.1
 Pkg @quasar/app... v2.2.11
 Debugging......... no
 Publishing........ no
 Transpiled JS..... yes (Babel) - includes IE11 support
 ==================
 Output folder..... /opt/nordic/ncs/v2.1.0/modules/lib/matter/third_party/zap/repo/spa

 Tip: Built files are meant to be served over an HTTP server
      Opening index.html over file:// won't work

 Tip: You can use "$ quasar serve" command to create a web server,
      both for testing or production. Type "$ quasar serve -h" for
      parameters. Also, an npm script (usually named "start") can
      be added for deployment environments.
      If you're using Vue Router "history" mode, don't forget to
      specify the "--history" parameter: "$ quasar serve --history"

⇝ npm⇝  notice 
npm notice New major version of npm available! 7.7.6 -> 8.19.2
npm notice Changelog: <https://github.com/npm/cli/releases/tag/v8.19.2>
npm notice Run `npm install -g npm@8.19.2` to update!
npm notice 
✍ Writing out new hash file.
🚀 Executing: npx tsc --build ./tsconfig.json
⇝ npm⇝  notice 
npm notice New major version of npm available! 7.7.6 -> 8.19.2
npm notice Changelog: <https://github.com/npm/cli/releases/tag/v8.19.2>
npm notice Run `npm install -g npm@8.19.2` to update!
npm notice 
🚀 Executing: npx copyfiles -V ./src-electron/**/*.sql ./dist/
unglobed path: ./src-electron/db/zap-schema.sql
copy from: ./src-electron/db/zap-schema.sql
copy to: dist/src-electron/db/zap-schema.sql
⇝ npm⇝  notice 
npm notice⇝  New major version of npm available! 7.7.6 -> 8.19.2
npm ⇝ notice Changelog: <https://github.com/npm/cli/releases/tag/v8.19.2>
npm ⇝ notice Run `npm install -g npm@8.19.2` to update!
npm notice⇝  
🚀 Executing: npx electron /opt/nordic/ncs/v2.1.0/modules/lib/matter/third_party/zap/repo/dist/src-electron/ui/main-ui.js --logToStdout --gen /opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/zap-templates/app-templates.json --zcl /opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/zap-templates/zcl/zcl.json -i /Users/bennynestler/workspaces/matter/nRFConnect/template/src/template.zap
⇝ App threw an error during load
⇝ Error: Cannot find module '/opt/nordic/ncs/v2.1.0/modules/lib/matter/third_party/zap/repo/node_modules/sqlite3/lib/binding/napi-v6-darwin-unknown-arm64/node_sqlite3.node'
Require stack:
- /opt/nordic/ncs/v2.1.0/modules/lib/matter/third_party/zap/repo/node_modules/sqlite3/lib/sqlite3-binding.js
- /opt/nordic/ncs/v2.1.0/modules/lib/matter/third_party/zap/repo/node_modules/sqlite3/lib/sqlite3.js
- /opt/nordic/ncs/v2.1.0/modules/lib/matter/third_party/zap/repo/dist/src-electron/db/db-api.js
- /opt/nordic/ncs/v2.1.0/modules/lib/matter/third_party/zap/repo/dist/src-electron/db/query-package.js
- /opt/nordic/ncs/v2.1.0/modules/lib/matter/third_party/zap/repo/dist/src-electron/util/util.js
- /opt/nordic/ncs/v2.1.0/modules/lib/matter/third_party/zap/repo/dist/src-electron/ui/ui-util.js
- /opt/nordic/ncs/v2.1.0/modules/lib/matter/third_party/zap/repo/dist/src-electron/ui/menu.js
- /opt/nordic/ncs/v2.1.0/modules/lib/matter/third_party/zap/repo/dist/src-electron/ui/window.js
- /opt/nordic/ncs/v2.1.0/modules/lib/matter/third_party/zap/repo/dist/src-electron/ui/main-ui.js
- /opt/nordic/ncs/v2.1.0/modules/lib/matter/third_party/zap/repo/node_modules/electron/dist/Electron.app/Contents/Resources/default_app.asar/main.js
- 
    at Module._resolveFilename (node:internal/modules/cjs/loader:940:15)
    at Function.n._resolveFilename (node:electron/js2c/browser_init:249:1105)
    at Module._load (node:internal/modules/cjs/loader:785:27)
    at Function.c._load (node:electron/js2c/asar_bundle:5:13331)
    at Module.require (node:internal/modules/cjs/loader:1012:19)
    at require (node:internal/modules/cjs/helpers:102:18)
    at Object.<anonymous> (/opt/nordic/ncs/v2.1.0/modules/lib/matter/third_party/zap/repo/node_modules/sqlite3/lib/sqlite3-binding.js:4:15)
    at Module._compile (node:internal/modules/cjs/loader:1116:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1169:10)
    at Module.load (node:internal/modules/cjs/loader:988:32)
⇝ npm⇝  notice  
npm notice New major version of npm available! 7.7.6 -> 8.19.2
npm notice Changelog: <https://github.com/npm/cli/releases/tag/v8.19.2>
npm ⇝ notice Run `npm install -g npm@8.19.2` to update!
npm notice 
😎 All done: 416s 768ms.

Any other ideas?

Best regards,

Benny

RE: [Matter] Changing or adding Endpoints/Clusters to Matter-Template example with the zap tool leads to compiling errors

Benny Nestler — Mon, 17 Oct 2022 08:17:28 GMT

Hi Marte Myrvold ,

I've try to downgrade with nvm-tool to your mentioned versions. The error is still the same.

Here is the whole output

bennynestler@MBPvonBenjamin(x86_64) /opt/nordic/ncs/v2.1.0/modules/lib/matter/third_party/zap/repo % git clean -fdx
Removing .quasar/
Removing .version.json
Removing dist/
Removing node_modules/
Removing spa/
bennynestler@MBPvonBenjamin(x86_64) /opt/nordic/ncs/v2.1.0/modules/lib/matter/third_party/zap/repo % cd ../../../     
bennynestler@MBPvonBenjamin(x86_64) /opt/nordic/ncs/v2.1.0/modules/lib/matter % ./scripts/tools/zap/run_zaptool.sh ~/workspaces/matter/nRFConnect/template/src/template.zap
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '@npmcli/fs@1.1.0',
npm WARN EBADENGINE   required: { node: '^12.13.0 || ^14.15.0 || >=16' },
npm WARN EBADENGINE   current: { node: 'v15.4.0', npm: '7.7.6' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '@voxpelli/semver-set@4.0.0',
npm WARN EBADENGINE   required: { node: '^14.18.0 || >=16.0.0' },
npm WARN EBADENGINE   current: { node: 'v15.4.0', npm: '7.7.6' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'installed-check@6.0.4',
npm WARN EBADENGINE   required: { node: '^14.18.0 || >=16.0.0' },
npm WARN EBADENGINE   current: { node: 'v15.4.0', npm: '7.7.6' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'installed-check-core@6.0.2',
npm WARN EBADENGINE   required: { node: '^14.18.0 || >=16.0.0' },
npm WARN EBADENGINE   current: { node: 'v15.4.0', npm: '7.7.6' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'chalk@5.1.2',
npm WARN EBADENGINE   required: { node: '^12.17.0 || ^14.13 || >=16.0.0' },
npm WARN EBADENGINE   current: { node: 'v15.4.0', npm: '7.7.6' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'list-installed@2.0.1',
npm WARN EBADENGINE   required: { node: '^14.18.0 || >=16.0.0' },
npm WARN EBADENGINE   current: { node: 'v15.4.0', npm: '7.7.6' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'meow@10.1.5',
npm WARN EBADENGINE   required: { node: '^12.20.0 || ^14.13.1 || >=16.0.0' },
npm WARN EBADENGINE   current: { node: 'v15.4.0', npm: '7.7.6' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'gauge@4.0.0',
npm WARN EBADENGINE   required: { node: '^12.13.0 || ^14.15.0 || >=16' },
npm WARN EBADENGINE   current: { node: 'v15.4.0', npm: '7.7.6' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'npmlog@6.0.0',
npm WARN EBADENGINE   required: { node: '^12.13.0 || ^14.15.0 || >=16' },
npm WARN EBADENGINE   current: { node: 'v15.4.0', npm: '7.7.6' }
npm WARN EBADENGINE }
npm WARN deprecated @types/anymatch@3.0.0: This is a stub types definition. anymatch provides its own type definitions, so you do not need this installed.
npm WARN deprecated stable@0.1.8: Modern JS already guarantees Array#sort() is a stable sort, so this library is deprecated. See the compatibility table on MDN: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort#browser_compatibility
npm WARN deprecated source-map-url@0.4.1: See https://github.com/lydell/source-map-url#deprecated
npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated har-validator@5.1.5: this library is no longer supported
npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated source-map-resolve@0.5.3: See https://github.com/lydell/source-map-resolve#deprecated
npm WARN deprecated w3c-hr-time@1.0.2: Use your platform's native performance.now() and performance.timeOrigin.
npm WARN deprecated sane@4.1.0: some dependency vulnerabilities fixed, support for node < 10 dropped, and newer ECMAScript syntax/features added
npm WARN deprecated fsevents@1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm WARN deprecated chokidar@2.1.8: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
npm WARN deprecated fsevents@1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm WARN deprecated chokidar@2.1.8: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
npm WARN deprecated eslint-loader@4.0.2: This loader has been deprecated. Please use eslint-webpack-plugin
npm WARN deprecated querystring@0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated babel-eslint@10.1.0: babel-eslint is now @babel/eslint-parser. This package will no longer receive updates.
npm WARN deprecated uuid@3.4.0: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated uuid@3.4.0: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated uuid@3.4.0: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated electron-osx-sign@0.4.17: Please use @electron/osx-sign moving forward. Be aware the API is slightly different
npm WARN deprecated electron-osx-sign@0.5.0: Please use @electron/osx-sign moving forward. Be aware the API is slightly different
npm WARN deprecated electron-osx-sign@0.5.0: Please use @electron/osx-sign moving forward. Be aware the API is slightly different
npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated @npmcli/fs@1.1.0: this version had an improper engines field added, update to 1.1.1
npm WARN deprecated node-pre-gyp@0.11.0: Please upgrade to @mapbox/node-pre-gyp: the non-scoped node-pre-gyp package is deprecated and only the @mapbox scoped package will recieve updates in the future
npm WARN deprecated node-pre-gyp@0.17.0: Please upgrade to @mapbox/node-pre-gyp: the non-scoped node-pre-gyp package is deprecated and only the @mapbox scoped package will recieve updates in the future
npm WARN deprecated svgo@1.3.2: This SVGO version is no longer supported. Upgrade to v2.x.x.
npm WARN deprecated highlight.js@9.18.5: Support has ended for 9.x series. Upgrade to @latest
npm WARN deprecated core-js@2.6.12: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
npm WARN deprecated core-js@2.6.12: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
npm WARN deprecated core-js@3.21.1: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.

added 3075 packages, and audited 3076 packages in 17s

199 packages are looking for funding
  run `npm fund` for details

37 vulnerabilities (1 low, 14 moderate, 17 high, 5 critical)

To address issues that do not require attention, run:
  npm audit fix

To address all issues possible (including breaking changes), run:
  npm audit fix --force

Some issues need review, and may require choosing
a different dependency.

Run `npm audit` for details.
npm notice 
npm notice New major version of npm available! 7.7.6 -> 8.19.2
npm notice Changelog: https://github.com/npm/cli/releases/tag/v8.19.2
npm notice Run npm install -g npm@8.19.2 to update!
npm notice 
🚀 Executing: git log -1 --format={"hash": "%H","timestamp": %ct}
🔍 Git commit: e9277b989f1d128bc881e88ecbf7a3353c841c39 from Wed May 11 2022 16:45:40 GMT+0200 (Mitteleuropäische Sommerzeit)
🔍 Current src hash: aqrjjVB67BD5DC9iha9ORJah5zc=
🔍 Current src-shared hash: nOWlRqSeZbEDOkt+AnCdf01DNYM=
👎 Error reading old hash file: /opt/nordic/ncs/v2.1.0/modules/lib/matter/third_party/zap/repo/spa/hash.json
🐝 Front-end code changed, so we need to rebuild SPA.
🚀 Executing: npx quasar build

 Build mode........ spa
 Pkg quasar........ v1.17.1
 Pkg @quasar/app... v2.2.11
 Debugging......... no
 Publishing........ no

⇝ Browserslist: caniuse-lite is outdated. Please run:
  npx browserslist@latest --update-db
  Why you should do it regularly: https://github.com/browserslist/browserslist#browsers-data-updating
 Configured browser support (at least 45.26% of global marketshare):
 · Chrome for Android >= 96
 · Firefox for Android >= 95
 · QQ for Android >= 10.4
 · UC for Android >= 12.12
 · Android >= 96
 · Baidu >= 7.12
 · Chrome >= 97
 · Edge >= 97
 · Firefox >= 95
 · IE >= 11
 · iOS >= 15.2
 · Kaios >= 2.5
 · Opera Mini >= all
 · Opera Mobile >= 64
 · Opera >= 82
 · Safari >= 15.2
 · Samsung >= 15.0

 App · Running "@quasar/testing" Quasar App Extension...
 App · Running "@quasar/testing-unit-jest" Quasar App Extension...
 App · Running "@quasar/testing-e2e-cypress" Quasar App Extension...
 App · Reading quasar.conf.js
 App · Extension(@quasar/testing-e2e-cypress): Extending quasar.conf...
 App · Transpiling JS (Babel active) - includes IE11 support
 App · Extending SPA Webpack config
 App · Cleaned build artifact: "/opt/nordic/ncs/v2.1.0/modules/lib/matter/third_party/zap/repo/spa"
 App · Generating Webpack entry point
 App · Compiling with Webpack...
Starting type checking service...
 App · Compiling SPA...
 App · Compiled SPA done in 18157 ms
 App · Added build artifact "/opt/nordic/ncs/v2.1.0/modules/lib/matter/third_party/zap/repo/spa"

 Build summary for css/js/json (the rest are omitted):
 ╔═════════════════════╤═══════════╤═══════════╗
 ║               Asset │      Size │   Gzipped ║
 ╟─────────────────────┼───────────┼───────────╢
 ║      1.8ce39149.css │   0.48 KB │   0.28 KB ║
 ║      3.d57d983c.css │   0.11 KB │   0.11 KB ║
 ║    app.674ffe40.css │   0.77 KB │   0.28 KB ║
 ║ vendor.c6e57c02.css │ 415.08 KB │  71.23 KB ║
 ╟─────────────────────┼───────────┼───────────╢
 ║       1.8a969588.js │  56.43 KB │  13.27 KB ║
 ║       3.c3bcbf14.js │  38.07 KB │   7.21 KB ║
 ║       4.b0d2a606.js │   7.29 KB │   2.61 KB ║
 ║       5.a885112d.js │   1.49 KB │   0.81 KB ║
 ║       6.4326c2f9.js │  12.10 KB │   3.86 KB ║
 ║       7.0e860913.js │   7.02 KB │   2.32 KB ║
 ║     app.5da6689e.js │  54.10 KB │  13.86 KB ║
 ║  vendor.dbd8f6a2.js │ 655.43 KB │ 207.66 KB ║
 ╚═════════════════════╧═══════════╧═══════════╝
 
 Build succeeded

 Build mode........ spa
 Pkg quasar........ v1.17.1
 Pkg @quasar/app... v2.2.11
 Debugging......... no
 Publishing........ no
 Transpiled JS..... yes (Babel) - includes IE11 support
 ==================
 Output folder..... /opt/nordic/ncs/v2.1.0/modules/lib/matter/third_party/zap/repo/spa

 Tip: Built files are meant to be served over an HTTP server
      Opening index.html over file:// won't work

 Tip: You can use "$ quasar serve" command to create a web server,
      both for testing or production. Type "$ quasar serve -h" for
      parameters. Also, an npm script (usually named "start") can
      be added for deployment environments.
      If you're using Vue Router "history" mode, don't forget to
      specify the "--history" parameter: "$ quasar serve --history"

⇝ npm⇝  notice 
npm notice New major version of npm available! 7.7.6 -> 8.19.2
npm notice Changelog: <https://github.com/npm/cli/releases/tag/v8.19.2>
npm notice Run `npm install -g npm@8.19.2` to update!
npm notice 
✍ Writing out new hash file.
🚀 Executing: npx tsc --build ./tsconfig.json
⇝ npm⇝  notice 
npm notice New major version of npm available! 7.7.6 -> 8.19.2
npm notice Changelog: <https://github.com/npm/cli/releases/tag/v8.19.2>
npm notice Run `npm install -g npm@8.19.2` to update!
npm notice 
🚀 Executing: npx copyfiles -V ./src-electron/**/*.sql ./dist/
unglobed path: ./src-electron/db/zap-schema.sql
copy from: ./src-electron/db/zap-schema.sql
copy to: dist/src-electron/db/zap-schema.sql
⇝ npm⇝  notice 
npm notice⇝  New major version of npm available! 7.7.6 -> 8.19.2
npm ⇝ notice Changelog: <https://github.com/npm/cli/releases/tag/v8.19.2>
npm ⇝ notice Run `npm install -g npm@8.19.2` to update!
npm notice⇝  
🚀 Executing: npx electron /opt/nordic/ncs/v2.1.0/modules/lib/matter/third_party/zap/repo/dist/src-electron/ui/main-ui.js --logToStdout --gen /opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/zap-templates/app-templates.json --zcl /opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/zap-templates/zcl/zcl.json -i /Users/bennynestler/workspaces/matter/nRFConnect/template/src/template.zap
⇝ App threw an error during load
⇝ Error: Cannot find module '/opt/nordic/ncs/v2.1.0/modules/lib/matter/third_party/zap/repo/node_modules/sqlite3/lib/binding/napi-v6-darwin-unknown-arm64/node_sqlite3.node'
Require stack:
- /opt/nordic/ncs/v2.1.0/modules/lib/matter/third_party/zap/repo/node_modules/sqlite3/lib/sqlite3-binding.js
- /opt/nordic/ncs/v2.1.0/modules/lib/matter/third_party/zap/repo/node_modules/sqlite3/lib/sqlite3.js
- /opt/nordic/ncs/v2.1.0/modules/lib/matter/third_party/zap/repo/dist/src-electron/db/db-api.js
- /opt/nordic/ncs/v2.1.0/modules/lib/matter/third_party/zap/repo/dist/src-electron/db/query-package.js
- /opt/nordic/ncs/v2.1.0/modules/lib/matter/third_party/zap/repo/dist/src-electron/util/util.js
- /opt/nordic/ncs/v2.1.0/modules/lib/matter/third_party/zap/repo/dist/src-electron/ui/ui-util.js
- /opt/nordic/ncs/v2.1.0/modules/lib/matter/third_party/zap/repo/dist/src-electron/ui/menu.js
- /opt/nordic/ncs/v2.1.0/modules/lib/matter/third_party/zap/repo/dist/src-electron/ui/window.js
- /opt/nordic/ncs/v2.1.0/modules/lib/matter/third_party/zap/repo/dist/src-electron/ui/main-ui.js
- /opt/nordic/ncs/v2.1.0/modules/lib/matter/third_party/zap/repo/node_modules/electron/dist/Electron.app/Contents/Resources/default_app.asar/main.js
- 
    at Module._resolveFilename (node:internal/modules/cjs/loader:940:15)
    at Function.n._resolveFilename (node:electron/js2c/browser_init:249:1105)
    at Module._load (node:internal/modules/cjs/loader:785:27)
    at Function.c._load (node:electron/js2c/asar_bundle:5:13331)
    at Module.require (node:internal/modules/cjs/loader:1012:19)
    at require (node:internal/modules/cjs/helpers:102:18)
    at Object.<anonymous> (/opt/nordic/ncs/v2.1.0/modules/lib/matter/third_party/zap/repo/node_modules/sqlite3/lib/sqlite3-binding.js:4:15)
    at Module._compile (node:internal/modules/cjs/loader:1116:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1169:10)
    at Module.load (node:internal/modules/cjs/loader:988:32)

RE: [Matter] Changing or adding Endpoints/Clusters to Matter-Template example with the zap tool leads to compiling errors

Marte Myrvold — Mon, 17 Oct 2022 06:45:17 GMT

Hi,

Can you try downgrading to node v15.4.0 and npm v7.7.6? These are the versions I downgraded to after having similar issues with node v18, and it is working with these versions on my side.

Best regards,

Marte

RE: [Matter] Changing or adding Endpoints/Clusters to Matter-Template example with the zap tool leads to compiling errors

Benny Nestler — Mon, 17 Oct 2022 06:25:54 GMT

Hi Marte Myrvold ,

same error appears after doing the git clean -fdx command.

My versions are:

npm = 8.19.2

node = 18.4.0

RE: [Matter] Changing or adding Endpoints/Clusters to Matter-Template example with the zap tool leads to compiling errors

Marte Myrvold — Mon, 17 Oct 2022 06:05:27 GMT

Hi,

Which version of node and npm are you using? I get errors when using a version that is too new.

Can you try the following:

Go to ncs-dir/modules/lib/matter/third_party/zap/repo
Run git clean -fdx to remove all local file changes in the repo
Run zap-tool as described in the instruction again.

Best regards,

Marte

RE: [Matter] Changing or adding Endpoints/Clusters to Matter-Template example with the zap tool leads to compiling errors

Benny Nestler — Fri, 14 Oct 2022 08:10:56 GMT

I try this today without success.

The problem today is to (run and) build the zap-tool.

Uncaught Exception:
Error: Cannot find module '/opt/nordic/ncs/v2.1.0/modules/lib/matter/third_party/zap/repo/node_modules/sqlite3/lib/binding/napi-v6-darwin-unknown-arm64/node_sqlite3.node'
Require stack:
- /opt/nordic/ncs/v2.1.0/modules/lib/matter/third_party/zap/repo/node_modules/sqlite3/lib/sqlite3-binding.js
- /opt/nordic/ncs/v2.1.0/modules/lib/matter/third_party/zap/repo/node_modules/sqlite3/lib/sqlite3.js
- /opt/nordic/ncs/v2.1.0/modules/lib/matter/third_party/zap/repo/dist/src-electron/db/db-api.js
- /opt/nordic/ncs/v2.1.0/modules/lib/matter/third_party/zap/repo/dist/src-electron/db/query-package.js
- /opt/nordic/ncs/v2.1.0/modules/lib/matter/third_party/zap/repo/dist/src-electron/util/util.js
- /opt/nordic/ncs/v2.1.0/modules/lib/matter/third_party/zap/repo/dist/src-electron/ui/ui-util.js
- /opt/nordic/ncs/v2.1.0/modules/lib/matter/third_party/zap/repo/dist/src-electron/ui/menu.js
- /opt/nordic/ncs/v2.1.0/modules/lib/matter/third_party/zap/repo/dist/src-electron/ui/window.js
- /opt/nordic/ncs/v2.1.0/modules/lib/matter/third_party/zap/repo/dist/src-electron/ui/main-ui.js
- /opt/nordic/ncs/v2.1.0/modules/lib/matter/third_party/zap/repo/node_modules/electron/dist/Electron.app/Contents/Resources/default_app.asar/main.js
- 
at Module._resolveFilename (node:internal/modules/cjs/loader:940:15)
at Function.n._resolveFilename (node:electron/js2c/browser_init:249:1105)
at Module._load (node:internal/modules/cjs/loader:785:27)
at Function.c._load (node:electron/js2c/asar_bundle:5:13331)
at Module.require (node:internal/modules/cjs/loader:1012:19)
at require (node:internal/modules/cjs/helpers:102:18)
at Object.<anonymous> (/opt/nordic/ncs/v2.1.0/modules/lib/matter/third_party/zap/repo/node_modules/sqlite3/lib/sqlite3-binding.js:4:15)
at Module._compile (node:internal/modules/cjs/loader:1116:14)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1169:10)
at Module.load (node:internal/modules/cjs/loader:988:32)

RE: [Matter] Changing or adding Endpoints/Clusters to Matter-Template example with the zap tool leads to compiling errors

Benny Nestler — Fri, 14 Oct 2022 08:01:25 GMT

I think I use the correct zap-file (src/template.zap).

RE: [Matter] Changing or adding Endpoints/Clusters to Matter-Template example with the zap tool leads to compiling errors

rosc — Wed, 12 Oct 2022 13:02:15 GMT

I have seen the same errors, though my issues originated using a wrong ZAP-file with the generated files. Maybe this is causing the problem?

RE: [Matter] Changing or adding Endpoints/Clusters to Matter-Template example with the zap tool leads to compiling errors

Marte Myrvold — Wed, 12 Oct 2022 12:29:06 GMT

Hi,

Did you add any other endpoints, clusters, and/or attributes than the ones in the guide? Did you follow all the steps in the guide, that is, editing the main loop, creating a callback, and adding source files to CMakeLists.txt as well? If so, make sure that you are looking at the correct version of the documentation. The version you are linking to is the latest version, which is documentation for the main branch, and these steps differ between the main branch and v2.0.2.

I am not able to reproduce your issue when testing with nRF Connect SDK v2.1.0. Can you test with v2.1.0 and see if you get the same issue there?

Best regards,

Marte