The issue reported here and here is still present in 3.70~78. Relay control is not available in Node Red.
Interestingly, reading relay state is available. But strangely, one can choose a SmartShunt, which doesn’t even have a relay. Perhaps it’s the alarm state, but that’s available in the Battery Monitor node.
Tested with Venus OS v3.70~78
I just tested the new virtual device node “Switch/Numeric input”
I tested it against “*Switch/Temperature setpoint”
*
When sending a msg.payload { “/SwitchableOutput/output_1/Dimming”: $number(payload) }.
“Switch/Numeric input” ==> The new value is not updated to the Venus OS UI
“Switch/Temperature setpoint” ==> The new value is correctly updated to the Venus OS UI
Also, the “Switch/Numeric input” has a State output. However, sending a msg.payload to this
{ “/SwitchableOutput/output_1/State”: $number(payload) } does not change anything in the UI.
I guess the implementation of this virtual node is not yet completed.
Here are some screenshots of the UI and MQTT data:
I updated from version 3.70-61 to 3.70-78. I’m using virtual switches and digital outputs on the IO Extender 150. When I use them as momentary switches, they no longer trigger any function. They work as toggles, as expected. They also worked normally in version 3.70-61. Setup: Cerbo mk2, GX Touch70, IO Extender 150, GX Tank 140, MP 12/1600, Startcraft LIT200WP via VE.CAN. Is there a solution?
I’m curious how the temperature slider is working for you?
I was just came in here to report a bug that no matter how I configure it I only get one or two steps on the slider, and sometimes only one temperature. For example, I have one slider set min -10, max 0, step 1. On my Cerbo it shows up at 14-32 F (that part is expected as my system is set to F) and it only shows 14 until the slider hits the max and then shows 32. Changing my system to C gives the same result, just different numbers of course.
Hi all
I just tried to use the virtual switch / momentary switch, and it doesn’t fire in node red.
To make sure, I did no mistake I simply connected a momentary switch with two debug nodes, one for each output, set the output of the debug nodes to all data.
while it shows up in the remote console of GUIv2 and I can press it (while pressed the button shows “On”, it doesn’t fire anything in node red, so the debug nodes show nothing.
I have this behaviour only with the momentary switch, the on off switches work as intended.
Anybody else having this behaviour?
thank you
Hi @wolferl
I tried to reproduce what you are describing:
In my understanding this means:
I will create a Github issue for the first output.
Concerning the “state” output: Can you please double check if you get that output? From your description it sounds as if you get no output at all, which is different to what I’m seeing. If you still cannot see anything on the second output, please share your flow.
Best,
Chris
Thank you Chris.
I have exactly the same setup, see the pic. I don’t get an output at all at 3.70~83 but as well on 3.70~81
I´m running a cerbogx with about 30 virtuel switches on nodered and another one with 20. On both system happens the same . Even on v3.70-81 the switches has been separated from devices categorie all virtuel switches are working but adding a new switch it destroys all existing switch assignments. This happens on Version v3.70-81 and 83 as well. Maybe you can look into this.
Can you explain what you mean with “destroys all existing switch assignments”?
Note that the name and group are taken from the Node-RED configuration. If you adjust those later on via the console, these values get lost and overwritten with the values from the Node-RED configuration on reboot or when updating the firmware.
Background is that there can be only one source of truth for these values, which is the Node-RED configuration. This used to behave slightly differently.
Marking your issue as resolved. Via DM’s between @wolferl and @chris9 we found the underlying problem being:
deactivated the 3rd relay in gpio_list and now the momentary switches work as well.
I believe we fixed this in v3.70~79. Please confirm if so, or ping me otherwise.
This is a gui bug, not Node-RED and has been reported to the gui developers. Should be picked up and fixed shortly.
Thanks for reporting.
Hi, just in case this is still open: for me it was still there in 3.70~83
Thanks
wolferl
I have the same bug and made a separate post about it. Switching Cerbo Settings from Fahrenheit to Celsius fixed it for me. I’m on 3.70 and it shows build date/time of 202602224155852. @dfaber is v3.70~79 on the Beta channel? I’m on the official release currently.
no v3.70~79 is older than v3.70.
