Compilation not possible with Occupancy cluster enabled (Matter)

[rwahidi]

Hi,

I am working with the Matter Light Bulb sample. I have come across a problem where I can not compile my firmware if I implement the occupancy sensor cluster using the ZAP-Tool.

When I toggle this option to enabled, the compilation fails.

This is the error I receive:

/home/install/ncs/toolchains/7795df4459/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd: app/libapp.a(util.cpp.obj): in function `emberAfInit()':
/home/install/ncs/v2.5.0/modules/lib/matter/src/app/util/util.cpp:111: undefined reference to `MatterOccupancySensingPluginServerInitCallback()'
collect2: error: ld returned 1 exit status
ninja: build stopped: subcommand failed.
FATAL ERROR: command exited with status 1: /home/install/ncs/toolchains/7795df4459/usr/local/bin/cmake --build /home/install/nrf_apps/light_bulb_2.5.0/build

For me this error was reproducible on both the 2.5.0 and the 2.6.0 SDK in the same way, even after reinstalling. I am building for a nrf52840-DK

Do I need to implement any callbacks before I can compile this cluster? I tried with the temperature cluster and it compiled without any problems.

I appreciate the help.

[Amanda Hsieh]

Hi, 

Please be aware that each NCS has its corresponding supported ZAP-Tool version and make sure you use the correct ZAP-Tool version.  

See Installing the ZAP tool.  

Regards,
Amanda H.

[rwahidi]

You were right, for some reason it always ran the wrong version of the ZAP-Tool.
However it seems to have changed some files permanently, because I cannot fix this error by making a pristine build or by removing the cluster again using the ZAP-Tool.

So even if the Occupancy Cluster is completely disabled ,or when I remove the entire endpoint, the problem remains.

Do you have any suggestions? Else I might just try reinstalling the sdk.

[Amanda Hsieh]

You can check the environment variable and update it or Try to search on your PC to find the other version ZAP-Tool and replace it with the corresponding version. 

[rwahidi]

I removed the version I did not need, and that problem is fixed. However the ZAP-Tool version does not make a difference in my original issue, I again receive the same error.

The only difference I see now, is that I can successfully compile again after removing the occupancy cluster in the ZAP-Tool. I am not sure what exactly changed.

Edit: I created a new build of the light bulb sample in a different location, and it does compile with the occupancy sensor enabled.

[Amanda Hsieh]

Delete the build folder and build again. 

[rwahidi]

I tried and still get the same behaviour

[rwahidi]

I think I have found what caused most of the problems. Whenever I would install a new version of the toolchain or SDK, it would install the toolchain and for some reason set the path to the old SDK without installing the newer one. So even when it showed as v2.5.0 it was actually some older version.

This was the same for VS Code and when using the nRF Connect for desktop app to install other versions. The only fix I found so far ist completely getting rid of any other SDK's, because just changing the directory did not help.