Command Factory - Configuration CC set - sending partial parameters - format - AEOTEC Indoor Siren

[BJ205]

I am 'playing' with node-red on my laptop before moving flows on to a raspberry pi. Node-red-contrib-zwave-js installed flawlessly and I am happy working with binary sensors, can switch power sockets on and off, happy days. Now I am working with an AEOTEC Indoor Siren, again, much success, I can play sounds, though the Siren doesn't accept the volume settings. Using Command Factory I can ask for data, for instance from Parameter 2 as in the picture, and the Siren returns four messages because there are four partial parameters.

The bit that has me stumped is how to set singly or as a group, the four partial parameters that the Siren tells me about. I read https://zwave-js.github.io/node-zwave-js/#/config-files/partial-parameters which gives an example of 7[0x01] as how to access partial parameters, and also the manual for the Siren which has an example of 0x01020304 to set the four partial parameters of a parameter. I read about the Configuration CC set command Configuration CC

SET
async set(
    options: ConfigurationCCAPISetOptions,
): Promise<SupervisionResult | undefined>;

but I can't find how to format the ConfigurationCCAPISetOptions, or any mention elsewhere about ConfigurationCCAPISetOptions. I have tried everything I can think of in the Params section of the Command Factory, but I either get error messages, or nothing, or it just reports back four unchanged Partial Parameters. Any help much appreciated.

[marcus-j-davies]

Hi @BJ205

You can use the CCAPI for that - but it will require the integer that represents all 4 bits.
you are far better using the Value API - I tend to discourage the CCAPI these days

In V9 that I am working on the ValueAPI is default.
here is how to do it via a function node

Setting a Value

let targetValueID = {
}
let someValue = someValue
let Message = {
    "payload": {
        "mode": "ValueAPI",
        "node": 12,
        "method": "setValue",
        "params": [targetValueID, someValue]
    }
}
return Message

Getting a Value

let targetValueID = {
}
let Message = {
    "payload": {
        "mode": "ValueAPI",
        "node": 12,
        "method": "getValue",
        "params": [targetValueID]
    }
}
return Message

See
https://github.com/zwave-js/node-red-contrib-zwave-js/wiki/Value-API

To get the correct valueID - In the side panel UI - double click on a property, and you will get the ValueID

[marcus-j-davies]

If you still wanted to use the CCAPI.
your params will be. (but ValueAPI is far easier)

bitMask obviously not always needed

This is a ConfigurationCCAPISetOptions payload
[ {"parameter": 2, bitMask: <BitMask>, "value": <Desired Value>, "valueSize": <Number>} ]

[BJ205]

Thank you, I told you it would be something obvious :-)
I had tried getting rid of the "meta" and "Propertyid" bits but had always left the valueId and its braces in place.
Now to try setting values on the Indoor Siren

[marcus-j-davies]

I have only included below the minimum required fields (normally)
just double clicking the value (or more accurately - the property) in the UI will hint at any special value in its ValueID

You could getValue for the targetValue property of course - but it wouldn't really make sense 😅

the CMD Node does support the ValueAPI Also

let MyVID = {
   commandClass: 37, /* Binary Switch */
   endpoint: 0, /* i.e a plug with 2 outlets */
}

/* To Set A Value */

MyVID.property = 'targetValue'

let Message = {
    "payload": {
        "mode": "ValueAPI",
        "node": 12,
        "method": "setValue",
        "params": [MyVID, true]
    }
}
return Message

/* To Get A Value */

MyVID.property = 'currentValue'

let Message = {
    "payload": {
        "mode": "ValueAPI",
        "node": 12,
        "method": "getValue",
        "params": [MyVID]
    }
}
return Message

[BJ205]

So I am just getting the hang of it, and then you show me a slightly different method. You have to understand that your brain might run at supersonic, mine only just makes ModelT :-)
I am now writing the bits to do the Setting of values for the AEOTEC Siren. It has 8 End Points with 7 different values that can be set for each End Point.
The first bits were easy to do with SoundSwitch SetConfugration in CMD Factory, that is working nicely, it sets a Default Tone and Default Volume for any End Point.
The next step is to be able to set a Light Effect for any End Point using a Function block and your information above. If you see a large amount of smoke far away on the horizon you will know that I got frustrated :-)
Thank you again, I look forward to V9 being released.

[marcus-j-davies]

You welcome 🤭

Do remember - you can set most of this in the UI (and for most Command Classes) 😁
The UI uses the Value API.

There is a feature that you might have missed.
set a value in the UI - and you will see the command, that you can then use your self as you see fit 🤓

[BJ205]

Yesterday I did spot that you can change all the settings in the UI, but thank you for pointing it out and increasing my pain 😁.
Didn't know about the ability to see the command, I shall be making use of that,
In my 'playing' I have developed a dashboard made with FlexDash, so though I could set everything in the ZWave UI, my version is easier to use, or at least I hope it will be easier to use.. And anyway, you always learn more having to do, and understand stuff, yes, I am a 'silver lining' type person 😁. All this started because the AEOTEC Siren doesn't accept the Volume level when you ask it to play a sound, not your problem, from what I can find it is a firmware issue. But it meant I wanted to be able to set the Default Volume in the 8 Endpoints that the siren has. And once I was looking at setting those, it seemed a shame not to also be able to set the Light Effects, fade up, time on, fade down, time off, and how long a sound plays, and if it repeats the sounds and if it repeats then the delay between sounds. And then you look back and realise you are down the 'rabbit hole'.