I've been thinking about how involved it is to set up new Shims devices, so I'm trying to do something about it. There's a new branch of the plugin on GitHub: https://github.com/FlyingDiver/Indigo-S ... /templates
This version of the plugin can create new devices (and optionally the associated Broker trigger) based on template files. The files are in YAML format, and there's a couple samples included in the plugin wrapper. There's also an external (to the plugin) directory that will also be searched for template files. You can specify the name for that directory in the plugin config.
There's two plugin menu commands - one writes the YAML for a selected plugin to the Indigo log. The other opens a dialog box for picking a template, a broker, and a UniqueID, and then creates a Shim device from that. You can pretty much copy the lines from the log directly to a template file. I think I may have done some edits, but I don't recall the details.
The format of the template file is still a work in progress. Right now, there's redundant data in there which needs to be fixed. But if you take one of the existing files and copy it, you can try to create your own. My intention is to bundle as many templates into the plugin as possible. But since my supply of MQTT generating devices is very limited, most of them will need to come from the community.
I'm probably going to have to enhance the file picker to support sub-directories of templates, as I think the template list could get out of hand otherwise.
The trigger creation code need works too. I'd like to be able to determine if there's already a trigger for this device, and get rid of the option checkbox. Not sure if that'll be possible or not.
If you want to play with this version, go ahead. Just be aware that I'm leaving at oh-dark-thirty Friday morning for almost a month, so expect long delays if you have questions about it.
Also, please create GitHub issues for actual bugs or enhancement requests. I don't want them to get lost in the noise.