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

[Benny Nestler]

Hi Nordic Guys,

hope you can help following issue (I think the issue is still mentioned in Ticket https://devzone.nordicsemi.com/f/nordic-q-a/87410/corrupt-matter-zcl-file-generation-matter-template-project, Case ID: 288305).

I try to extend the matter-template example from the nRF SDK. Out off the box the example compiles, build and links The application can be copied to the nRF5340DK board and works.

If I add a new endpoint, like it is described in https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/ug_matter_gs_adding_clusters.html#ug-matter-creating-accessory and let the generator.py script do its work, the result is an unbuild-able application.

See the following build-output:

/Users/bennynestler/workspaces/matter/nRFConnect/matter-template/src/zap-generated/endpoint_config.h:570:3: error: conversion from '<brace-enclosed initializer list>' to 'EmberAfDefaultOrMinMaxAttributeValue' is ambiguous
  570 |   }
      |   ^
/opt/nordic/ncs/v2.0.2/modules/lib/matter/src/app/util/attribute-storage.cpp:102:71: note: in expansion of macro 'GENERATED_ATTRIBUTES'
  102 | constexpr const EmberAfAttributeMetadata generatedAttributes[]      = GENERATED_ATTRIBUTES;
      |                                                                       ^~~~~~~~~~~~~~~~~~~~
In file included from /opt/nordic/ncs/v2.0.2/modules/lib/matter/src/app/util/af-types.h:58,
                 from /opt/nordic/ncs/v2.0.2/modules/lib/matter/src/app/util/af.h:69,
                 from /opt/nordic/ncs/v2.0.2/modules/lib/matter/src/app/util/common.h:45,
                 from /opt/nordic/ncs/v2.0.2/modules/lib/matter/src/app/util/attribute-storage.cpp:42:
/opt/nordic/ncs/v2.0.2/modules/lib/matter/src/app/util/attribute-metadata.h:104:15: note: candidate: 'constexpr EmberAfDefaultOrMinMaxAttributeValue::EmberAfDefaultOrMinMaxAttributeValue(const EmberAfAttributeMinMaxValue*)'
  104 |     constexpr EmberAfDefaultOrMinMaxAttributeValue(const EmberAfAttributeMinMaxValue * ptr) : ptrToMinMaxValue(ptr) {}
      |               ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/opt/nordic/ncs/v2.0.2/modules/lib/matter/src/app/util/attribute-metadata.h:103:15: note: candidate: 'constexpr EmberAfDefaultOrMinMaxAttributeValue::EmberAfDefaultOrMinMaxAttributeValue(uint16_t)'
  103 |     constexpr EmberAfDefaultOrMinMaxAttributeValue(uint16_t val) : defaultValue(val) {}
      |               ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/opt/nordic/ncs/v2.0.2/modules/lib/matter/src/app/util/attribute-metadata.h:102:15: note: candidate: 'constexpr EmberAfDefaultOrMinMaxAttributeValue::EmberAfDefaultOrMinMaxAttributeValue(const uint8_t*)'
  102 |     constexpr EmberAfDefaultOrMinMaxAttributeValue(const uint8_t * ptr) : ptrToDefaultValue(ptr) {}
      |               ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/opt/nordic/ncs/v2.0.2/modules/lib/matter/src/app/util/attribute-metadata.h:100:7: note: candidate: 'constexpr EmberAfDefaultOrMinMaxAttributeValue::EmberAfDefaultOrMinMaxAttributeValue(const EmberAfDefaultOrMinMaxAttributeValue&)'
  100 | union EmberAfDefaultOrMinMaxAttributeValue
      |       ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/opt/nordic/ncs/v2.0.2/modules/lib/matter/src/app/util/attribute-metadata.h:100:7: note: candidate: 'constexpr EmberAfDefaultOrMinMaxAttributeValue::EmberAfDefaultOrMinMaxAttributeValue(EmberAfDefaultOrMinMaxAttributeValue&&)'
In file included from /opt/nordic/ncs/v2.0.2/modules/lib/matter/src/app/util/config.h:83,
                 from /opt/nordic/ncs/v2.0.2/modules/lib/matter/src/app/util/af.h:56,
                 from /opt/nordic/ncs/v2.0.2/modules/lib/matter/src/app/util/common.h:45,
                 from /opt/nordic/ncs/v2.0.2/modules/lib/matter/src/app/util/attribute-storage.cpp:42:

The error repeats several times as result of the inclusion of header files.

[Benny Nestler]

Hi Marte Myrvold ,

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

My versions are:

npm = 8.19.2

node = 18.4.0

[Marte Myrvold]

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

[Benny Nestler]

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/[email protected]',
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/[email protected]',
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: '[email protected]',
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: '[email protected]',
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: '[email protected]',
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: '[email protected]',
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: '[email protected]',
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: '[email protected]',
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: '[email protected]',
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/[email protected]: This is a stub types definition. anymatch provides its own type definitions, so you do not need this installed.
npm WARN deprecated [email protected]: 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 [email protected]: See https://github.com/lydell/source-map-url#deprecated
npm WARN deprecated [email protected]: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated [email protected]: this library is no longer supported
npm WARN deprecated [email protected]: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated [email protected]: See https://github.com/lydell/source-map-resolve#deprecated
npm WARN deprecated [email protected]: Use your platform's native performance.now() and performance.timeOrigin.
npm WARN deprecated [email protected]: some dependency vulnerabilities fixed, support for node < 10 dropped, and newer ECMAScript syntax/features added
npm WARN deprecated [email protected]: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm WARN deprecated [email protected]: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
npm WARN deprecated [email protected]: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm WARN deprecated [email protected]: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
npm WARN deprecated [email protected]: This loader has been deprecated. Please use eslint-webpack-plugin
npm WARN deprecated [email protected]: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated [email protected]: babel-eslint is now @babel/eslint-parser. This package will no longer receive updates.
npm WARN deprecated [email protected]: 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 [email protected]: 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 [email protected]: 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 [email protected]: Please use @electron/osx-sign moving forward. Be aware the API is slightly different
npm WARN deprecated [email protected]: Please use @electron/osx-sign moving forward. Be aware the API is slightly different
npm WARN deprecated [email protected]: Please use @electron/osx-sign moving forward. Be aware the API is slightly different
npm WARN deprecated [email protected]: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated @npmcli/[email protected]: this version had an improper engines field added, update to 1.1.1
npm WARN deprecated [email protected]: 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 [email protected]: 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 [email protected]: This SVGO version is no longer supported. Upgrade to v2.x.x.
npm WARN deprecated [email protected]: Support has ended for 9.x series. Upgrade to @latest
npm WARN deprecated [email protected]: 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 [email protected]: 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 [email protected]: 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 [email protected] 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 [email protected]` 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 [email protected]` 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 [email protected]` 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)