You really do work fast !!!
Is it too hot to go outside today ?
We’re thinking even easier than that.
msg.payload = channel/s as HEX, so multiply channels can be triggered
If no Topic, use the command as set in the Send Raw Bytes node
If a Topic exists as a single Hex value, use that as the Command
(Although I do like how you’ve got it accepting a name string, so maybe that for clarity?)
Having the command from the topic and/or having the databytes from the payload for sure will make the node easier to use for dynamic input. I also like the Mustache input as it is quite readable once you are familiar using it. But there’s a learning curve…
So you got me thinking 
Bottom line: it should be easier to use! Usability is key here!
Here is a new mock-up on how a screen might look like:
I think this will make the node both easier to use for static and dynamic input.
What do you all think? Would this be easier?
All input is welcome 
And now I will enjoy the sun … respecting social distancing! 
Oh I say!! 
I think that’s brilliant.
That probably covers a lot of use cases 
Labour before pleasure, no sign of ‘stille zaterdag’ here.
Hard to keep up with the updates, not to mention the efforts @GertSt does to push them out! 
Like the dynamic idea for the combined message; does not put you in a ‘locked down’ position of choice in the flow.
So I did some UX refactoring on the Send Raw Bytes node.
Version 0.2.06 is now published.
Changes:
–Enjoy.
Got this message:
node-red-contrib-velbus
0.2.6
- Error: Cannot find module ‘mustache’ (line:4)
After installing:
node-red-contrib-viseo-mustache
Restarted Node-Red and now the testing can begin!
Oops! I have a look and fix asap! Glad you could temporary fix by yourself
Sorry, I made a mistake in the dependencies of version 0.2.6.
So I just pushed an update 0.2.7 to fix this.
If you have difficulties upgrading using the Palette Manager, due to the error in 0.2.6, I recommend to remove the module manually using the command line:
cd ./.node-red (or another path where you installed node-red)npm uninstall node-red-contrib-velbusnpm install node-red-contrib-velbusHi Gert
As an edge use case example for your nodes, I tried to set the Ambient edge light colours of a VMBEL2 yesterday by using Command 0xD4 (which appears twice in the protocol document)
Nothing I tried in VelbusLink or your NodeRed nodes worked.
When I used the Module configuration in VelbusLink to set the edge lights, I saw in the log that the memory map was being directly addressed, with no reference to a 0xD4 command.
The Data Bytes format was easy enough to follow, so maybe this is an example of how a table of commands would be useful, or a specific node for this type of command.
I tried it myself, both using the Send raw bytes node as from within Velbuslink (using the Send a Packet window), but it did not work here either.
The required databytes should have a specific binary combination and the documentation is not too clear to me. So I probably feed it with the wrong bits 
An example from Velbus would be helpful here …
Did my run for 0xD4 and…
Succeded: the trick was in the last byte!
Code for upper button ambient color: 0xD4 0x01 0x02 0x6y
should be for fix light with highest priority 0bx11yyyyy, x=1 is for blink and y are color bits
You nailed it!
Looking at error prone binary data like this, it would be so cool to have a user-friendly interface to rule all those commands!
That’s why we need a well structured, detailed JSON file! At least, that would be the first small step
The place where bits join and become bytes… but a lot trail and error
It will be very hard to have this (and other) stuff detailed on bit level.
Hi
Can you help the programatically challenged?
I’m trying to repeat your work and it’s just not working for me.
I’m getting a little confused… (maybe I’m hungry?)
Reading this (Page 23), it looks like I need to send
Command = 0xD4
To module address = 0xE2
To apply to background lights = 0x01
To apply to all 4 side = 0x0F
To apply Colour pallet no 28 to background without blinking = 0x1C
Like this
But nothing happens 
Priority = LOW
You should add 0x60 + your color dec 28 in hex = 0x1C => 0x7C as 4th byte
0x01 0x0F 0x7C
Okay…
I think I see…
I’ll give it a try tomorrow and report back.
I’ve just released a new version 0.2.08.
We now have a dimmer and a relay node.
Easy to set or get the brightness of a dimmer or to switch a relay on or off.
I’m using it to write dimmer and relay states to InfluxDB and visualizing it with Grafana.
Set it up on a Pi and an hour later you have some nice usage logs of all your Velbus relays and dimmers.
Gert
I am very interested in the node-red integration, but isn’t the Signum going to host node-red (or node-red alike) ?
That’s a very good question - I’m looking forward to have at least a little bit of info about Signum asap!
May be @VEL524 can help us out?
