Sending messages is hard :)

[lurendrejer]

Well, just saying 'hi' - had a great time moving my SH-setup from my current controller to NR with zwave-js.
I got everything going where something had to react to z-wave commands (turning on conbee lights, etc).

When I came to the part where i had to change states of z-wave devices themselves - I hit a wall.
Thermostats, binary switches, etc. - I tried and tried (https://github-wiki-see.page/m/zwave-js/node-red-contrib-zwave-js/wiki/CC-API)

I'm super impressed by how effecient zwave-js and node-red in itself is, but having to create z-wave messages manually is just too much for me.

If you ever consider creating some sort of function node, where one can select commands (multi, switch, whatever) - I'll be all over this thing.

Great work, thank you!

[lurendrejer]

oh, and the association-interface has a bug.
If i try to associate a multichannel device, with another i get this:
For instance: 31.1 [group 6] with 1.1 [controller]

I typed 1 and 1 into the interface.
It works if i associate with 1.0 (non multichannel) - but then the status updates doesn't work. They have to reach endpoint 1.1.

[lurendrejer]

Oh, neat - thank you :)
I'm going to bed - I'm way behind on that.

I'll try it out after work tomorrow.

How do I update?

[marcus-j-davies]

No... Thank you.

I found the bug, and I am fixing it now - I will be publishing an update in the next hour (I will ping you when its up)
Once again - thanks for spotting that one.

#111

when its up - you will see it in the NR palette as an available update.

[crxporter]

Did you say bug 🐞

[marcus-j-davies]

Indeed!

when creating Multi Channel Associations I am taking the HTML element its self as the value - and not the value of the HTML Element.

🙈

[marcus-j-davies]

@lurendrejer.

6.1.1 has now been released, this fixes the multi channel association bug you found (again Thank you).

This should appear in the palette as an update.
Will be grateful if you can let me know if you can now add Multi Channel associations (I don't have any devices that make use of them)

[marcus-j-davies]

Hi @lurendrejer ,

lets take a look.

To turn on a Binary Switch.
https://github.com/zwave-js/node-red-contrib-zwave-js/wiki/CC-API#examples

let Message = {
    payload: {
        mode: "CCAPI",
        node: 2,
        cc: "Binary Switch",
        method: "set",
        params: [true]
    }
}
return Message

[marcus-j-davies]

To adjust a Thermostat Set point

let Message = {
    payload: {
        mode: "CCAPI",
        node: 2,
        cc: "Thermostat Setpoint",
        method: "set",
        enums: {0:"ThermostatSetpointType"},
        params: ["Heating", value, scale]
    }
}
return Message

[lurendrejer]

This is that I tried:
let Message = {
payload: {
mode: "CCAPI",
node: 31,
cc: "Binary Switch",
endpoint: 2,
method: "set",
params: [true]
}
}

does the return Message -part actually 'send' the command?

[marcus-j-davies]

does it change when using the UI?

[lurendrejer]

Theres a ui? - sorry I completely missed that part.

[marcus-j-davies]

[lurendrejer]

Oooh I just thought that was a tool to look up the commands... doh!

[marcus-j-davies]

if it works here - let me know

[lurendrejer]

And how would i go about leaving 'node' empty, since i'm routing it to a specific z-wave node in my flow?

[marcus-j-davies]

just removing the node property from your message, will be enough.

[marcus-j-davies]

Just to re-cap 😆

• endpoints are integers (1,2,3,4)
• let me know if the UI works (it might just be a funny set up with the device)

I would also use the real wiki address.
https://github.com/zwave-js/node-red-contrib-zwave-js/wiki/getting-started

[lurendrejer]

How do i send the command from the UI?
Am i really that stupid?

[lurendrejer]

It does work :)
I'll get the message sorted tomorrow, I'm pretty sure of it.

Thank you for everything up until now, I'll be sure to update with my findings - if i find out the rest by myself, I might even be able to remember it -!

I was missing a crucial part - that I cound test-send messages and capture those.

Thank you, thank you, thank you!!

[marcus-j-davies]

double click current value....

send me screen shot

[lurendrejer]

[marcus-j-davies]

based on that

let Message = {
    payload: {
        mode: "CCAPI",
        node: <your node id>, 
        endpoint: 3,
        cc: "Binary Switch",
        method: "set",
        params: [true]
    }
}
return Message

[marcus-j-davies]

the CC API does not update the UI.
so it will affect the device - but may not update the UI.

the CCAPI - is very low level,
the ValueAPI - whilst a little more advanced - updates the UI

[lurendrejer]

I'll be re-enabling my homeseer -> nodered -> conbee flow for the rest of the day, I think.

And look into the native zwave-js -> nodered -> conbee later.

After that, I'll start the zwave-js -> nodered -> native zigbee -project.

[lurendrejer]

Right now, I have too many layers of abstraction.

[lurendrejer]

And again, thank you so much for you time!

[marcus-j-davies]

OK,

Double clicking current value will show you the endpoint ID, and you can use that to correct the message.

Based on that.

in a function node -> Controller or zwave-device node

let Message = {
    payload: {
        mode: "CCAPI",
        node: <your node id>, /* not needed for some modes on device-node /*
        endpoint: #,
        cc: "Binary Switch",
        method: "set",
        params: [true]
    }
}
return Message

if endpoint is 0 - you can omit endpoint from your message.

[lurendrejer]

I just omit the node: -part too? - if i'm sending it to a specific z-wave node-type-node.

[marcus-j-davies]

correct.
if set to Specific Device or Multiple Device

[marcus-j-davies]

Be sure to checkout the wiki in all its glory - it has examples for most things

[lurendrejer]

I will, and i thought i had.
Again, doh!

[marcus-j-davies]

Oh and welcome to z-wave for node red 😁

@crxporter,
Is also part of the team

[lurendrejer]

It actually does seem to work... thank you.
But man it's a bit more tough than using the conbee-like interfaces in node-red.

[lurendrejer]

Since I have something working now, I think i'll create a subflow - that handles the basic, endpoint, etc. parts.
Like i did for the Central Scene commands.

[marcus-j-davies]

Nice!

The device-node has the ability to use variables if inside a subflow.
and the one pot of gold for you will be the event-filter node.

you can send each different type of value update through a different output pin - i.e splitting the values out to different paths,

VERY handy for motion sensors with temp and lux sensing for an example.

do holla, if you want to know how.

[lurendrejer]

This is what i ended up with - it does the legwork :)

[marcus-j-davies]

Looking good.

Here is the type of events to expect from the module.

https://github.com/zwave-js/node-red-contrib-zwave-js/wiki/Payload-Messaging-Format#event-table
Scroll slightly up, to see how they are delivered.

[lurendrejer]

My simple test - triggered by a zigbee device, is working.
I'll look into what I can do with some advanced functionality (Basic, multilevel, Temperature etc.) tomorrow

once again, thank you!!

[marcus-j-davies]

Lastley,
feel free to join us on discord. 👍 .
we have a few deconz users here also

https://discord.gg/QD2Uu2cT

[crxporter]

If the original request here was "make commands easier" ... we are working on some ideas at #113

[lurendrejer]

Updating seems to fail:
2021-09-29T17:44:09.983Z Install : node-red-contrib-zwave-js 6.1.1

2021-09-29T17:44:09.738Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --production --engine-strict [email protected]
2021-09-29T17:44:18.978Z [err] npm ERR! code 1
2021-09-29T17:44:18.978Z [err] npm ERR! path /root/.node-red/node_modules/node-red-contrib-zwave-js
2021-09-29T17:44:18.979Z [err] npm
2021-09-29T17:44:18.980Z [err] ERR! command failed
2021-09-29T17:44:18.980Z [err] npm ERR! command sh -c npm install --build-from-source --production @serialport/[email protected] && npm install --build-from-source --production [email protected]
2021-09-29T17:44:18.980Z [err] npm ERR! npm WARN npm npm does not support Node.js v16.10.0
2021-09-29T17:44:18.980Z [err] npm ERR! npm WARN npm You should probably upgrade to a newer version of node as we
2021-09-29T17:44:18.980Z [err] npm ERR! npm WARN npm can't make any promises that npm will work with this version.
2021-09-29T17:44:18.980Z [err] npm ERR! npm WARN npm Supported releases of Node.js are the latest release of 4, 6, 7, 8, 9, 10.
2021-09-29T17:44:18.980Z [err] npm ERR! npm WARN npm You can find the latest version at https://nodejs.org/
2021-09-29T17:44:18.980Z [err] npm ERR! npm ERR! cb.apply is not a function
2021-09-29T17:44:18.980Z [err] npm ERR!
2021-09-29T17:44:18.980Z [err] npm ERR! npm ERR! A complete log of this run can be found in:
2021-09-29T17:44:18.980Z [err] npm ERR! npm ERR! /root/.npm/_logs/2021-09-29T17_44_18_543Z-debug.log
2021-09-29T17:44:18.987Z [err]
2021-09-29T17:44:18.987Z [err] npm ERR! A complete log of this run can be found in:
2021-09-29T17:44:18.987Z [err] npm
2021-09-29T17:44:18.987Z [err] ERR! /root/.npm/_logs/2021-09-29T17_44_18_981Z-debug.log

[lurendrejer]

it's fixed - sorry.
Before i ran the --ignore-scripts and restarted nodered afterwards.

I tried stopping node-red, running --ignore-scripts and starting node-red - it shows 6.1.1 now

[marcus-j-davies]

yay!

looks like the serialport guys changed something (I'll get onto them about that)

in the mean time you now have a fixed Association Management UI.
Fancy a test (like you did yesterday before shooting off?) - adding a Multi Channel Association

[lurendrejer]

yes, will do - right away

[lurendrejer]

It accepts the values and the UI starts updating for a binary switch.
I can delete, add, delete, add - and everything happens as it should.

Thank you of the quick fix :)

[marcus-j-davies]

We have a node being developed 'cmd-factory' which removes the need to manually write commands 👍

[lurendrejer]

This is giving me headaches...

I've tried sending commands via the gui, but the debugger doesn't show them - maybe because it's a battery device and the get queued.

Is this correct?

let Message = {
payload: {
mode: "CCAPI",
cc: "Thermostat Setpoint",
method: "set",
enums: {0:"ThermostatSetpointType"},
params: ["Heating", 20, celsius]
}
}
return Message

[marcus-j-davies]

OK @lurendrejer
"Celsius" matches into this file

https://github.com/zwave-js/node-zwave-js/blob/6282534a933217dc8241326e24655c5aaf33c07e/packages/config/config/scales.json

so you could in theory use 0, 0x00 (not sure how strict it is) - and it will still use Celsius

[lurendrejer]

aah!
i'll stick with celsius, but thank you for investigating :)

[marcus-j-davies]

@lurendrejer,

I decided to test this (it was bugging me), and it seems you do indeed need a number.
I think Celsius is being used by default - so it looks like it works (and it does but technically using Celsius as default)

using 'celsius'

2021-09-29T21:34:45.980Z DRIVER » [Node 002] [REQ] [SendData]
                                  │ transmit options: 0x25
                                  │ callback id:      6
                                  └─[ThermostatSetpointCCSet]
                                      setpoint type: Heating
                                      value:         15 undefined

using 0x00 (For celsius on that scales lookup)

2021-09-29T21:35:16.757Z DRIVER » [Node 002] [REQ] [SendData]
                                  │ transmit options: 0x25
                                  │ callback id:      7
                                  └─[ThermostatSetpointCCSet]
                                      setpoint type: Heating
                                      value:         15 °C

thought you should know - but then if it works anyway (albeit using a default because of a mismatch) - I guess its ok 😄
but notice the undefined in the log

[lurendrejer]

Bugger, i'll straighten my course - one day, someone will update a driver and BAM, thankyou - again :)

[marcus-j-davies]

Anytime - if not already detected, I like to help new users to the point of getting up and running.

[marcus-j-davies]

@lurendrejer,

Can you confirm you currently have a functional setup (I.e no issues) with zwave in node-red?

I am going to switch my focus to the new cmd-factory node (allows to create commands with low code from the user end)
This has been asked by others - so I better do it 😁

But want to make sure you are at a stage of exploration as opposed to dealing with teething issues?
of course, do holla if you need help with anything.

and I really do suggest joining our discord server for real time discussion, lots of Node-red users, who use the zwave plug-in, apple Homekit plug-in, unify plug-in, deconz and more.

👍

[lurendrejer]

Everything is working as expected!