Having a feature to do not send command if the device state is the same value than the command?
Technically
- This palette doesn't keep device state for all of devices. Each device node keep its own state. I would require to copy the same init logic as the device node
- You can set the
deviceIddynamically with the input message to the command node.- if we want to continue to support it: we need to keep state of all devices in NR (and if we need to initiate cache for all devices (slow process), I think some of us will hate you
) - if we make this feature incompatible with the other, than it add some complexity for the user
- if we want to continue to support it: we need to keep state of all devices in NR (and if we need to initiate cache for all devices (slow process), I think some of us will hate you
Conceptually:
- We already mention it in this thread (lol but I don't know where
), but a node should do one and only one thing. - I don't like the idea of half-mixing concept of device node with command node. Otherwise we will end up with one big node to do everything
- Since it's a good practice to check the device state before sending command. On most scenarios it doesn't do anything to send multi time the same command
Summary
It's technically not an easy process (but possible) and conceptually not an idea that I'm convinced 
