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.
It's easy to test this for yourself by installing the node and using the example flow which is provided by the node, and see if it works.
If it does not work, then either raise an issue with the node author, or posting a request here in the forum.
Thank you you right. I'ma a beginner with node red & github
I will.
How ever, when reconsidering my need, I will try to formulate it in a new forum subject.
When I use HomeKit Bridge Node than there always has to be a JSON input like {"On":true} and {"On":false}
So it would be easy if the output is JSON I think.
Ok, then we will need to add an extra option in the TypedInput of the "value" column, so you can send javascript objects in the output messages (to avoid having to use an extra Change node). We will put that on our TODO list, and implement it when I'm back into business. Until then you will need to add that Change node...