I’m playing with a 3-way virtual switch. Should the “Auto” selection also generate a msg event like ON/OFF does?
I don’t see anything from either output from Auto, a bug or the way it was intended to operate?
V3.70~60
The Auto button doesn’t affect /SwitchableOutput/output_1/State, but is available via /SwitchableOutput/output_1/Auto.
Thanks, I hoped it would have been an event msg instead.
Can anyone share an example of how to set up a function in Node-RED that evaluates the value in /SwitchableOutput/output_1/Auto ?
I can’t find enough documentation to teach me how to evaluate data that is not in a message payload. I’ve never really dealt with finding node data from paths. I’m probably using the wrong terms or perspective to search for answers.
I use the Victron custom input node set to the device & auto path set to returns a value on change, same with the state value. Add a topic with a change node.
I locally save the values on complex logic by the incoming topic using context variables. It also makes it easier to see the values without a bunch of debugs. Not sure if that’s proper or not, but it does work well.
2 VS msg values, plus 2 Shelly relay msgs output the logic. I find adding more outputs to the function instead of handling return msg topics to be easier.
The status path has some nice visual indicators too. The switch disable (value:32) and external control (128) are my favorites.
Thanks, How do you set the Switch node to the Auto path?
(EDIT) I realized what you were suggesting after I asked.
I added the “custom input” node and was able to set it to send the state of the Auto component. I now have the Switch node reporting On/Off and the Custom Input node reporting Auto/Manual. This gets me back on track for using the 3-state button info in functions, and/or setting them as context data, etc.
Thanks again!
1 Like
It’s in the custom input node setup. I’m using v3.80~8 which is a beta version. Older beta or production versions might not have full virtual switch support. It’s a fairly recent evolution. Looks like v3.71 might be the latest production.
I use input nodes to watch changes from a switch, not the switch node itself.
I use the switch node input only for changes to the switch (state, status, and auto)
Recent VS update has 3 outputs on a 3 state switch. The bottom output has the auto changes, middle is state changes.
1 Like
Hi,
I tried the 3.8 version and in fact the Third output appears. But now the second output does not work anymore…
I had to use a custom one to get the state of the manual on /off.
Is it working on yours?
I don’t use the switch outputs, but custom input node like you. Only because I have all Victron I/O in a separate flow for clarity & OCD.
Quick look, it appears to operate properly. Top is pass-through from input, middle is state, bottom is auto. beta v3.80~14