Beta V3.60~69 Virtual switch feedback and loss of settings on reboot

Beta testing Venus OS beta testing
,
1

I have added a virtual switch into Node RED and this works well. The only comment is you can only choose 1,2 or 3 switches or PWMs, why is 0 not an option as I do not need a PWM function.

2

Yes, just a small mistake; will be fixed asap.

And the term PWM probably needs a change as well.

PWM is a possible, and common, technology used for dimming a load. In the related hardware.

3

waiting already very long time for such a feature for RV switches. I could not find any option to change the names of nodered switch pane except headline. Talking about Output 1 ..3. and PWM Thanks Dirk

4

Go to devices, select the main switch by whatever you called it in node red, then you can drill down into the setup and rename all the individual switches.

image
image1388Ă—364 33 KB

1 Like
5

Small problem with the virtual switch set up. On my Cerbo GX I renamed the individual switches and had one of them set to “On”. When I reboot the Cerbo GX, the switch state goes to “Off” and the custom names for the individual switches revert to their default names. Need these values to persist over a reboot.

1 Like
6

Thanks found it :slight_smile:

7

same on my site. given names will not stay after reboot

1 Like
8

I love the Virtual switches! Can we add 0 to the Nr of pwms list?

One thing that I could not get to work was the new GUI switches do not respond to changes in SwitchableOutput/xx/State using a Custom Control node.

But SwitchableOutput/xx/Settings/CustomName does change the GUI switch label

The GUI switches also do not follow the Node Red (N) State value when (W) State value changes.

1 Like
9

@MiPaul I thought that I would try the switch state change from Node-RED after your post.

Note, I was testing remotely and using remote console to view the gui, not locally.

I got Node-RED to successfully control a switch state using both the Switch Control node and the Custom Control node and the switch state shown on remote console gui followed the Node-RED changes.

image
image716Ă—255 12 KB

image
image718Ă—260 12.4 KB

image
image732Ă—287 12.8 KB

However, if the switch state was changed manually in remote console gui, then it stopped following the changes in Node-RED only following changes on the remote console gui. If the browser page was refreshed after the change in state in Node-RED remote console gui then correctly showed the Node-RED change. I do not know if the same thing is happening on the local gui.

@mpvader a bit of follow up work still required here perhaps along with checking locally what happens.

1 Like
10

Thank you, that explains why it didn’t work for me. I was able to reproduce the results you found. Even with cache disabled, no change after manual input. I really like the switch feature. An LED option would be handy, or a slick way to access a NR dashboard/tile.

Just a few more additions and it will be the perfect RV interface.

11

What a great feature! (Which leads to more desires):

  • Definition of min, max and step for the pwms.
  • Visualize the current value on the pwm sliders.
  • I assume there is space for five outputs/pwms per tile (virtual device).
    Can’t we set the # of outputs/pwms from 0-5?

Cheers, luphi

12

With the help of GitHub - mc0110/inetbox2mqtt: communicate over mqtt protocol to simulate a truma inetbox , I’m now able to control my Truma heater remotely :+1: