How I'm going to track a previous mode to return to it later, such as vacation mode - would like thoughts from others

[tgauchat (ActionTiles.com co-founder Terry @ActionTiles; GitHub: @cosmicpuppy)]

Using a Virtual Device to store a state is an excellent idea (though ST could just give us more near-global variables…).

In fact, I just posted about this… Frankly, I think we could merge the threads (and start a new Capability definition…).

Feature Request - On/Off Button Tile - why can't you install it from the ST App itself

Virtual Devices of many kinds are handy to use as “global” (Location or Account?) scoped storage. ST could just give us more near-global variables at the account, location, or hub level, but we only get location.mode. Virtual Devices are better, though as they fit in the security model, and events, etc… Perhaps a Capability “Data” or some other capability name(s) would help make their purpose and use more obvious though.