What the advantage trying the 2.0 binding in OH2

Until now I have been avoiding the 2.0 binding as far as possible.
Also Paper UI is hardly ever used. Everything is defined in related .things and .conf files.
This behavior still comes from the past where the data base was mapdb and not json.

I was therefore wondering what the user benefit is switching to the 2.0 bindings instead of staying on using the old 1.x binding?

Because in v2.0 of the bindings you’ve got some extended features like for example Auto Discovery that can help you to very quickly setup new things/channels. Another good reason is that now that many bindings are ported to v2.0, I doubt that former v1.x versions will be maintained in the future (at least for myself, it’s too much work maintaining two versions in two environments).

1 Like