Thanks to both. This is nice.
But I have a question: if I use inject node to change the state, it does change the state in ui, but do not send anything through to debug node from it’s output. Only if I change the state by clicking the control directly the debug node shows the new state. Am I doing something wrong?
Yes, the developers are aware, and that feature will be added in the future.
There is a ongoing discussion about how it will be implemented, but no decision has been made yet.
This is a great addition for my dashboard, Thanks.
I'd like to change the color or hide the border and have tried a CSS template using .multistate-switch-wrapper without luck:
This is fine if you are end-user.
If you create something for wide use, and you find yourself to be forced to use the !important flag, it just shows that something went wrong. Back to drawing board ...
The border around the buttons makes the "switch-like" look for widget. But technically it is nav-bar or menu. So it is highly possible to get much better results if to use dedicated components
Perhaps as a wish for the next version: I miss the opportunity to influence the topic of the outgoing message. My use case is that I transfer the value as a payload and use the Topic to determine the source for a value. Of course I can do this with an additional change node after the node, but it would be nice to be able to influence this in the node itself as the other UI nodes have such a possibility.