For the lights to stop flashing, add the following at the end of the rule:
Wait for event: tilt sensor closed
Off: Big Chair, Dining Room
(You can select both lights together with the action - doesn’t need to be separate commands.)
Note that using the flash command, if the bulb doesn’t support flashing, will have the hub send an on then an off command continuously. This can cause the hub to flood the Z-Wave or Zigbee network on which the bulb or switch is connected. It will also slow down the hub when multiple devices are selected, though I suspect only 2 might not be a problem.
What I have done to remedy this is either use a color bulb and set it to a color that I only use for this, or use the Inovelli switch’s LED to show a specific pattern.
I expect what @Sebastien is referring to is how HE (or the developer of any custom driver) needs to implement the flash command. I.e. just because the flash command is shown in the screen does not indicate how it is implemented "under the hood". The driver may support it, but how it does, I am assuming, may differ.
Whether it supports it can be checked by calling the command, either within the rule you have setup or simply on the Device Details page. As to @Sebastien 's point about how it is achieved.... that I am not sure how to determine. Any ideas @Sebastien ?
That’s a good question. I suspect that if all logging is enabled, the logs might show on/off events, as @Slate mentions.
I would say that if you see issues with the lights blinking at uneven speeds or other commands slowing down, then the driver or device doesn’t support flashing and just sends on/off commands. If everything works as expected when flashing, then all is good.