esp-matter using factory dac

[nublos]

I use esp-idf v5.4.1 with esp-matter v1.4 with target esp32c3
When switching to factory dac provider I end up in wrong commissioning mode 0, dac credentials do not get loaded:

I (1343) chip[DMG]: AccessControl: initializing
I (1353) chip[DMG]: Examples::AccessControlDelegate::Init
I (1353) chip[DMG]: AccessControl: setting
I (1353) chip[DMG]: DefaultAclStorage: initializing
I (1363) chip[DMG]: DefaultAclStorage: 0 entries loaded
I (1363) chip[SVR]: WARNING: mTestEventTriggerDelegate is null
I (1373) chip[ZCL]: Using ZAP configuration...
I (1383) esp_matter_cluster: Cluster plugin init common callback
I (1383) chip[DMG]: AccessControlCluster: initializing
I (1383) chip[ZCL]: WRITE ERR: ep 0 clus 0x0000_0030 attr 0x0000_0000 not supported
I (1393) chip[ZCL]: Initiating Admin Commissioning cluster.
I (1403) chip[DIS]: Updating services using commissioning mode 0
I (1403) chip[DIS]: CHIP minimal mDNS started advertising.
E (1413) chip[SVR]: ERROR setting up transport: 201

My factory image.bin is at the right offset. Flag and namespace are correct. Is there a way to enable more specific logging to see what is happening in the dac provider?

These are relevant sdkconfig-defaults I use:

CONFIG_ESP_SECURE_CERT_DS_PERIPHERAL=n

CONFIG_ENABLE_ESP32_FACTORY_DATA_PROVIDER=y
CONFIG_ENABLE_ESP32_DEVICE_INSTANCE_INFO_PROVIDER=y
CONFIG_CHIP_FACTORY_NAMESPACE_PARTITION_LABEL="fctry"
CONFIG_CHIP_FACTORY_NAMESPACE_PARTITION_NAME="chip-factory"
CONFIG_FACTORY_DEVICE_INSTANCE_INFO_PROVIDER=
CONFIG_ESP_MATTER_NVS_USE_COMPACT_ATTR_STORAGE=y

[nublos]

After switching from "nvs_partition_gen.py" to "generate_esp32_chip_factory_bin.py" it worked.
I used the Test Certs like described in "https://project-chip.github.io/connecte ... _data.html"

I set these sdkconfig.defaults:
CONFIG_ENABLE_ESP32_FACTORY_DATA_PROVIDER=y
CONFIG_ENABLE_ESP32_DEVICE_INSTANCE_INFO_PROVIDER=y
CONFIG_ENABLE_TEST_SETUP_PARAMS=n
CONFIG_FACTORY_DAC_PROVIDER=y
CONFIG_CHIP_FACTORY_NAMESPACE_PARTITION_LABEL="fctry"