Thanks for the feedback.
I will give some more specifics to help target the discussion.
I am currently working on bring support for a protocol to the russound binding. Russound amps provide whole home audio amps which power multi zones of speakers. You end up with any number of speaker zones (I have 8, no idea of what an average install would be).
You could easily have 6 channels linked to items and want Alexa support for each zone. ie. power, volume, source, mute, etc.
I found setting up Alexa support via the current gui is quite a bit of work, and quite monotonous as things are now. It also requires the end user spends significant time reading the Alexa binding documentation to figure out how to set up a speaker.
I was thinking when adding the bridge to the system, there would be a config flag something like ‘Generate Alexa metadata automatically’. Even if the Alexa metadata is generated, this does not mean Alexa would automatically have access. The end user would still have to go over to the Alexa smart device section and initiate a scan to detect smart devices within their system.
In looking at the recent binding dev documentation, I haven’t found mention of how to access the metadata registry, getting reference to it, etc.
The binding obviously has intimate knowledge of the things it is creating so it seemed reasonable to add the necessary information into openhab to allow a much simpler experience for end users to get support.
that is where I am coming from, and was looking for feedback on if this feature is a good idea in general, and if so, if others with more experience with bindings, especially with the newer apis related to version 3 had tackled something like this.