So a timeout doesn't change %device% anymore?

[bertabcd1234]

device should get set to "timeout" with or without a triggering device as long as the wait timed out, which is the issue here -- not whether it's set to the name of the triggering device, which indeed does require a "real" trigger.

This was reported on 2.3.2 a while back and I'm not sure it was ever addressed:

%device% time out

Hello, In some of my automations, I exploit %device%, local variables, and the timeout feature to ask a question if an action should be performed. I parse the variable to see if it has the word “timeout” in it. If the device triggers before timeout, then the actions continue. This has worked perfectly for me, but since 2.3.2, timeout will not set in the variable and my rules perform actions they should not. Here is a screen grab if my rule [image]

Tagging @bravenel to take a look, assuming this wasn't an intentional change or that there isn't a "new" way to do this.