need help! how to set EnergyEvseMode cluster attribute SupportedModes?

[colddownz]

when i try to Initialize a EnergyEvseMode cluster attrubute SupportedModes,
Caused by: Validating node0.socket.energyEvseMode.state.supportedModes.0.modeTags.0.value: Value "0" is not defined in enum (135), i have no idea to deal it,

my code:

const supportModes =  [
    {
        label: "Auto",
        mode:0,
        modeTags:[{
            value: 0
        }],
        
    },
    {
        label: "Quick",
        mode:1,
        modeTags:[{
            value: 1
        }]
    },

]
// Define the endpoint for the device.  This is the "thing/device" that will appear on the network.
const measuredSocketEndpoint = new Endpoint(MeasuredSocket, {
    id: "socket",
    electricalPowerMeasurement: {
        powerMode: ElectricalPowerMeasurement.PowerMode.Ac,
        // We simulate that we can measure the following values.
        accuracy: [
            {
                measurementType: MeasurementType.ActivePower, // mW
                ...fakedAccuracyDetails,
            },
            {
                measurementType: MeasurementType.ActiveCurrent, // mA
                ...fakedAccuracyDetails,
            },
            {
                measurementType: MeasurementType.Voltage, // mV
                ...fakedAccuracyDetails,
            },
            {
                measurementType: MeasurementType.Frequency, // mHz
                ...fakedAccuracyDetails,
            },
        ],
        numberOfMeasurementTypes: 4,
    },
    electricalEnergyMeasurement: {
        accuracy: {
            measurementType: MeasurementType.ElectricalEnergy, // mWh
            ...fakedAccuracyDetails,
        },

        // cumulativeEnergyReset:{

        //     importedResetTimestamp: 0,
        //     exportedResetTimestamp: 1,
        //     importedResetSystime: 2,
        //     exportedResetSystime: 3,

        // }
        cumulativeEnergyReset: null

    },

    energyEvseMode:{
        currentMode: 16384,
        startUpMode: 16385,
        supportedModes: supportModes
    }

});

error infomation:

OnOffPlugInUnitAgent {}
2024-11-27 10:11:20.340 DEBUG Transaction Transaction initialize<node0.socket>#9 locked node0.socket.descriptor.state
2024-11-27 10:11:20.341 DEBUG Transaction Transaction reactor<node0.descriptor.#updatePartsList>#a locked node0.descriptor.state
2024-11-27 10:11:20.341 DEBUG Transaction Transaction reactor<node0.descriptor.#updatePartsList>#a committed and unlocked 1 resource
2024-11-27 10:11:20.342 ERROR Transaction Rolling back initialize<node0.socket>#9 due to error: Behaviors have errors
2024-11-27 10:11:20.342 DEBUG Transaction Transaction initialize<node0.socket>#9 rolled back and unlocked 6 resources
2024-11-27 10:11:20.344 FATAL Logger Unhandled error detected: Behaviors have errors
at (/home/xuliangwang/chipTools/matter.js/packages/node/src/endpoint/properties/Behaviors.ts:173:27)
at all (/home/xuliangwang/chipTools/matter.js/packages/general/src/util/Construction.ts:699:25)
at (/home/xuliangwang/chipTools/matter.js/packages/general/src/util/Construction.ts:689:17)
Cause #0: Error initializing node0.socket.energyEvseMode
at crash (/home/xuliangwang/chipTools/matter.js/packages/node/src/behavior/internal/BehaviorBacking.ts:69:19)
at ClusterServerBacking.[construct] (/home/xuliangwang/chipTools/matter.js/packages/node/src/behavior/internal/BehaviorBacking.ts:83:13)
at initializer (/home/xuliangwang/chipTools/matter.js/packages/general/src/util/Construction.ts:275:80)
at invokeInitializer (/home/xuliangwang/chipTools/matter.js/packages/general/src/util/Construction.ts:572:30)
at AsyncConstruction.start (/home/xuliangwang/chipTools/matter.js/packages/general/src/util/Construction.ts:276:17)
at Behaviors.#createBacking (/home/xuliangwang/chipTools/matter.js/packages/node/src/endpoint/properties/Behaviors.ts:536:30)
at Behaviors.activate (/home/xuliangwang/chipTools/matter.js/packages/node/src/endpoint/properties/Behaviors.ts:327:28)
at initializeBehaviors (/home/xuliangwang/chipTools/matter.js/packages/node/src/endpoint/properties/Behaviors.ts:159:26)
at actOffline (/home/xuliangwang/chipTools/matter.js/packages/node/src/behavior/context/server/OfflineContext.ts:49:20)
at Transaction.act (/home/xuliangwang/chipTools/matter.js/packages/node/src/behavior/state/transaction/Tx.ts:98:29)
Caused by: Validating node0.socket.energyEvseMode.state.supportedModes.0.modeTags.0.value: Value "0" is not defined in enum (135)
at (/home/xuliangwang/chipTools/matter.js/packages/node/src/behavior/state/validation/ValueValidator.ts:136:19)
at Object.value (/home/xuliangwang/chipTools/matter.js/packages/node/src/behavior/state/validation/conformance.ts:32:13)
at validateStruct (/home/xuliangwang/chipTools/matter.js/packages/node/src/behavior/state/validation/ValueValidator.ts:251:28)
at (/home/xuliangwang/chipTools/matter.js/packages/node/src/behavior/state/validation/conformance.ts:32:13)
at validateEntries (/home/xuliangwang/chipTools/matter.js/packages/node/src/behavior/state/validation/ValueValidator.ts:305:21)
at (/home/xuliangwang/chipTools/matter.js/packages/node/src/behavior/state/validation/ValueValidator.ts:318:9)
at Object.modeTags (/home/xuliangwang/chipTools/matter.js/packages/node/src/behavior/state/validation/conformance.ts:32:13)
at validateStruct (/home/xuliangwang/chipTools/matter.js/packages/node/src/behavior/state/validation/ValueValidator.ts:251:28)
at (/home/xuliangwang/chipTools/matter.js/packages/node/src/behavior/state/validation/conformance.ts:32:13)
at validateEntries (/home/xuliangwang/chipTools/matter.js/packages/node/src/behavior/state/validation/ValueValidator.ts:305:21)
/home/xuliangwang/chipTools/matter.js/packages/node/src/endpoint/properties/Behaviors.ts:173
causes => new EndpointBehaviorsError(causes),

[Apollon77]

Mode Tags is usage specific.If you check the specification about EvseModeBase cluster you find:

... these are the allowed standard modes. And so the error says that value 0 or 1 are no allowed mode tags in this case because only 0x4000-0x4002 is allowed

[colddownz]

Thank you for your help,  I have modified the modTags as follows: but the error still exists, Let me calm down and find out where I went wrong.

const supportModes =  [
    {
        label: "Manual",
        mode: 0,
        modeTags:[
            {
                value: 0x4000
        },
    ],
        
    },
    {
        label: "TimeOfUse",
        mode:1,
        modeTags:[{
            value:0x4001
        }]
    },

Cause #0: Error initializing node0.socket.energyEvseMode
at crash (/home/xuliangwang/chipTools/matter.js/packages/node/src/behavior/internal/BehaviorBacking.ts:69:19)
at ClusterServerBacking.[construct] (/home/xuliangwang/chipTools/matter.js/packages/node/src/behavior/internal/BehaviorBacking.ts:83:13)
at initializer (/home/xuliangwang/chipTools/matter.js/packages/general/src/util/Construction.ts:275:80)
at invokeInitializer (/home/xuliangwang/chipTools/matter.js/packages/general/src/util/Construction.ts:572:30)
at AsyncConstruction.start (/home/xuliangwang/chipTools/matter.js/packages/general/src/util/Construction.ts:276:17)
at Behaviors.#createBacking (/home/xuliangwang/chipTools/matter.js/packages/node/src/endpoint/properties/Behaviors.ts:536:30)
at Behaviors.activate (/home/xuliangwang/chipTools/matter.js/packages/node/src/endpoint/properties/Behaviors.ts:327:28)
at initializeBehaviors (/home/xuliangwang/chipTools/matter.js/packages/node/src/endpoint/properties/Behaviors.ts:159:26)
at actOffline (/home/xuliangwang/chipTools/matter.js/packages/node/src/behavior/context/server/OfflineContext.ts:49:20)
at Transaction.act (/home/xuliangwang/chipTools/matter.js/packages/node/src/behavior/state/transaction/Tx.ts:98:29)
Caused by: Validating node0.socket.energyEvseMode.state.supportedModes.0.modeTags.0.value: Value "16384" is not defined in enum (135)

[Apollon77]

Ok, I was able to reproduce and will check. it is basically the first time a Modecluster is used.

But for my understanding:
What is "MeasuredSocket"?
In fact even with Matter 1.4 specs the only device type that should get an "energy evse mode" cluster added is an EnergyEvse device ...

[colddownz]

I used the C++version of chip-all-cluster-chip-tools to simulate devices for testing. This week I found that matter.js is more convenient and efficient. MeasureSocket doesn't exist, it's just an exercise for me to learn how to use matter.js
thanks again!

[Apollon77]

Ok, I openend #1455 to fix the validation issue. Please retry after the fix