Is your feature request related to a problem? Please describe.
When using the node with other services I tend to get infinite looping because when the TP-Link node receives a message to change the state, it outputs the result (when startPowerEvents is active).
Describe the solution you'd like
Ideally I could see power state change output only when the device is directly controlled (button on it or via the Kasa app). That would update my flows when it changes but not cause loops when the input changes the state.
Many other nodes have this functionality or some other method to prevent passing input to output.
Describe alternatives you've considered
I haven't figured out a robust solution yet, but it probably involves a trigger node.
Is your feature request related to a problem? Please describe. When using the node with other services I tend to get infinite looping because when the TP-Link node receives a message to change the state, it outputs the result (when startPowerEvents is active).
Describe the solution you'd like Ideally I could see power state change output only when the device is directly controlled (button on it or via the Kasa app). That would update my flows when it changes but not cause loops when the input changes the state.
Many other nodes have this functionality or some other method to prevent passing input to output.
Describe alternatives you've considered I haven't figured out a robust solution yet, but it probably involves a trigger node.