Hello, All,
I have a simple request -- I am searching for a dashboard 2.0 node, that simply shows 2 Arrows, one for "up" and one for "down" (ideally also showing a "0" position, but just optional).
Despite searching google with various keywords, I never get something like this. Most nodes come with sophisticated logic and dependencies from temperature, sun brightness etc.
What I am looking for is a simple option to steer my roller shutters up and down.
I need a "true" for up and a "false" for down.
Background: I am running a KNX environment, and additionally to the real switches at the wall, I want to drive the roller shutters by node Red. The KNX actuators do the real work, and they can be driven by "true" and "false". When sending the same level again (true or false) the actuator stops, so basically I do not need a "zero" position. That would be just "visually nice"
In Dashboard 1.0 I used the "number input" node and sent a "1" up and a "0" for down. Unfortunately, in Dashboard 2.0, this does no longer work, since they have greyed out the down arrow, as long as a "1" is visible. So, I need to delete the "1", enter a "0" and then need to send the arrow down, which is confusing for the users and not handy at all.
So, long story short, I simply need a visual "up - down" arrow, that sends a payload of "true" or "false".
Does anybody know such node? It seems nobody else needs such easy node ...
Try a button group node with three buttons, up, down and stop. You can use text or icons as labels.
You would have to find a way in code to resend 1 or 0 when the stop button is pressed.
Hello, Jbudd,
thanks for the quick reply. I didn notice this button group at first.
Now I tried that group node and yes, looks promising, but unfortunately, it seems to have the same logic: It is impossible to send the same command a second time. While "up" is activated(it shows blue) and I press "up" again, the debug node shows no activity. It seems a second trigger with the same value is not supported. Only sending "false" is possible, however, this is not, what my KNX node expects. The same happens with the "down" value - I cannot send it twice in a row. Is there an easy way to adopt this behavior?
Thank you Steve.
Yes, that works. The only drawback is, that "up" and "down" are individual nodes and therefore may re-arrange in a wrong way("down" appears above "up"), if I use a smaller screen, like a smartphone. So ideally, they would be combined in one node (as I have to replicate this for each of the 27 windows). But no prob, I think my family will like this solution more than running around and press the hardware switches for each window
you always can use the UI-Template ... there are lots of Button examples with the VU libraries .. you can define any state you want ... even multiple clicks on same button .. yes .. bit more coding work .. but thats the fun of it
Thanks @jbudd for this additional idea. I tried, but one problem is, that the "button group" seems not to offer separate outputs (I would need 3) and another issue, I cannot enter 2 x true or false (it says "value must be unique"). I will go with the separate button nodes, which works good enough. Thanks anyway!
I really don't think these are insurmountable problems with careful use of change and switch nodes, or even a function.
However, you are going with separate buttons, which should work well too.
Hello, @Steve-Mcl do you know, whether customized icons require a permanent internet connectivity? Or just for the moment of deploying the configuration? Because, I normally close the port 80 and 443 from Node Red towards the internet for security reasons and just open them for updates. -- Hoinz
If you are just entering the name of the icon on the button, it will use locally served versions (i.e. built into Dashboard / served from Node-RED).
Not entirely certain why you are doing that - your router should be always blocking inbound connections! You dont need inbound ports opened on the FW to permit Node-RED to be updated!
If the icons were served from a remote location, they would be resolved by your browser while you are visiting the dashboard - which I imagine HAS got port outbound 80/443 connectivity? - so blocking Node-red from inbound/outbound on those ports would not affect any CDNs your browser requests from the internet.
I might have put it not clearly - Inbound blocking is obvious, but I am talking about the outbound connectivity - I let NodeRed operate locally only and just from time to time I open the mentioned ports on my firewall to fetch some updates from outside.
