Templated addon?

[5iver (Scott Rushworth)]

@CDriver

This is exactly what is needed
It needs to be, to “install” and use, almost as simple as adding a new addon. Something along the lines of "drop this zip file into the “install” director and something magic happens.

This is what I was describing as currently available through the Eclipse IoT Marketplace ExtensionService. One specific for OH will be setup too.

@CDriver

Your idea of improving the collaboration needs to include setting up the things, items, rules etc

I think that will come in a much later phase. Creating Items, Things, dependencies on bindings, even specific system configurations, etc. through a template is all very complex. We need to start small and get in some iterations.

However, this is possible now using the Jython HLs. The OWM script creates the Items for you. I will be adding a PR for a core.things module that can be used for creating Things and includes functionality similar to Simple Mode, where the Items can be created for all of the Channels of the Thing.

The ability to export a template from an existing rule does not exist yet, but it’s pretty easy to do by hand. I may have posted about how to do this already, but I also have a draft tutorial post on how to use templates that will go out one of these days. My plan is to release several rule templates after the Jython bundle PR is approved.

From another topic…

@5iver

The HL repo has examples of how to write custom scripts and the use of the libraries. Looking to the future, a fraction of users will use this information. A smaller fraction will develop rule templates that contain scripts using custom libraries. However, these rule templates will be shared through an ExtensionService and used by the vast majority of OH users in their UI rules.