And also having that switch as input has another problem. Whenever the status is reported the On/Off action is executed. Creating nasty either race condition or bouncing with on and off states indefinitely. That sucks. Looks like only reasonable approach would be having two switches. One for status ...

Unless you have an input to read the outcome from the switch, I guess, feedback I have the switch as an input as well. But that does not solve the problem of the device being i.e. offline/down. With that I can guess only based on Last Seen . Which is clunky as well. One solution I can think of is ...

Hello, I have an ON/Off action on a virtual switch. But no matter whether the URL exists or not, returns 2xx status code or not etc. the switch is turned on/off when I click on it. Is there a way to configure some confirmation (i.e. the request succeeded)? Or at least wait for the state from the ...