@Nadahar I read here that you need a kar file with a complete feature definition.
You can use python scripting next
It also contains a correct /OH-INF/addon/addons.xml and a additional /OH-INF/config/config.xml which is used via config-description-ref and contains the binding config description.
The official binding works without problems including the binding configuration.
The only difference to the marketplace kar file is that the marketplace version has a different feature name. The feature name there is prefixed with “next-” to avoid auto uninstalling the binding.
So, if you put the marketplace kar file into the addon folder, it is recognized and installed. The binding itself works, but has two issues.
- The Add-on Configuration defined in
/OH-INF/config/config.xmlis not available - The Add-on is not visible in the Add-on overview
If I install the Add-on via Marketplace Store it works too and is visible in The Add-on store, but there are still problems with the Configuration UI.