Node red - Velbus Glasspanel button - Hue lights(SOLVED)

[Geert_Verbist]

Hi,
Might be a simple answer but I can’t get this to work.

What I want to do is use a button on a velbus glaspanel button and switch a hue light on and off with the same button.

I know how to use node red to switch on a hue light and change scenes etc. What I cannot get to work is how I use the input of the velbus button and use that as a trigger for the hue action of switching the hue light on and off. When I use the openhab item in node red and use the button as input it just does not register the pressed status of the button.

Anyone did something similar or point me in the right direction?>

Thanks

[MDAR (Stuart Hanlon, UK importer of Velbus hardware)]

I might be able to assist Mr Verbist…

Have you seen these ??

Velbus - Using NodeRed to access special / extra features

Hi all With great thanks to everyone that has inspired / guided / assisted me in my development, I have built a couple of NodeRed flows that can be used with Velbus hardware. (and are adaptable to other hardware) Please note that I haven’t or can’t test these function nodes with all the Velbus modules, as I simply don’t have them all. I’ll happily help you if you want to develop these function nodes further, but keep in mind that I am not a programmer, so any help is offered on a “best guess…

What you need is a Function node to isolate the Button Events, then query the state of your Hue Lights and act accordingly.

You can have a seperate Flow or DSL rule to change the state of the feedback LEDs dependant on the state of the HUE Thing.

Give me a shout if you need more information… (you’re the one that got me on Slack in the first place)

A pair of DSL rules might look like this

rule "Velbus button to Hue lamp"
when
Channel "velbus:vmbgp1:xxxxxxx:ch1" triggered PRESSED
then

if (Hue_Lamp_Switch.state == ON)
{ Hue_Lamp_Switch.sendCommand(OFF)
}

else

{ Hue_Lamp_Switch.sendCommand(ON)
}

end


rule "Hue Lamp to Velbus feedback"

when

Item Hue_Lamp_Switch changed

then

if (triggeringItem.state == ON)
{
VelbusGP1ButtonFeedback.sendCommand("SET_LED")
}
else

{
VelbusGP1ButtonFeedback.sendCommand("CLEAR_LED")
}

end

[Geert_Verbist]

hehehe I did. I try that. So you are saying that I need to do the actual function in Node Red and have the led on the glaspannel feedback via a rule?

I tried fiddling with the node red function. What I can’t seem to get is the state of the velbus button. When I monitor it the button just gives met NULL

[MDAR (Stuart Hanlon, UK importer of Velbus hardware)]

Hi

@Geert_Verbist

I need to do the actual function in Node Red and have the led on the glaspannel feedback via a rule?

You can do either, in either.

The DSL rule examples above deal with both the button to HUE and the HUE state back to the Feedback LEDs.

Which are you happier working in?

@Geert_Verbist

I tried fiddling with the node red function. What I can’t seem to get is the state of the velbus button

The only thing that you should need to change in the Function node is the button address

It’ll look something like

velbus:vmbgp4:xxxxxxx:ch1

If you’ve done that, the next question is…

Have you connected the input to the Function node to the openHAB2 events node, to get all the data?

[MDAR (Stuart Hanlon, UK importer of Velbus hardware)]

What’s the code for the button your are trying to detect, as shown in PaperUi?

Then edit the function node

[

    {
        "id": "bfe462be.f71a5",
        "type": "function",
        "z": "f5370db.29be5f",
        "name": "Your Velbus Button",
        "func": "var event = msg.payload.event;\nvar channel = msg.payload.channel;\nvar newMsg = { payload: msg.payload.event };\nvar button = \"velbus:vmbxxx:xxxxxxxx:xx:input#CHx\"\n\nif  (channel === button )  {\n\tif (event === \"PRESSED\") {\n\t\treturn [msg, newMsg, null, null];\n\t}\n\tif (event === \"LONG_PRESSED\") {\n\t\treturn [msg, null, newMsg, null];\n\t}\n\tif (event === \"RELEASED\") {\n\t\treturn [msg, null, null, newMsg];\n\t}\n}\nreturn null;",
        "outputs": 4,
        "noerr": 0,
        "x": 310,
        "y": 140,
        "wires": [
            [],
            [
                ""
            ],
            [
                ""
            ],
            [
                ""
            ]
        ],
        "outputLabels": [
            "Whole Msg",
            "PRESSED",
            "LONG_PRESSED",
            "RELEASED"
        ]
    }
]

[Geert_Verbist]

Got it all sorted out. Super easy actually using DSL rules. Thanks @MDAR for your continued help on velbus inside openhab…

Appreciate it