Tokenized, discrete message topics

[i8beef]

A thought I had... I don't really need this right now, but I might introduce something like this in some of my other projects soon, and thought it would be a good fit for the project... I use the same topic format that you do by default here, but there are some proposed standards like the mqtt-smarthome projects, etc. that look to use other standards like "device/status/all/the/rest" and "device/set/all/the/rest", etc. While I prefer the topic structure you use, it might open up some options for people trying to follow those proposals if they had more options for configuring topics.

So I propose a tokenized message topic option, where someone could setup the entire topic pattern as desired using tokens. Each of your topic options then would become a full topic string like "zway/{room}/{device}/set", or maybe I want to do "mySillyName/set/{room}/{device}", etc.

Tokenizing would allow for a lot of options here for people. I'm not sure what an upgrade path looks like for that for those of us already running the module though, i.e., could you take the existing settings and generate the defaults for these fields easily?

[i8beef]

To be clear, I'm saying replace the existing three suffix options with a separate field for status, query and command.