Distributing bindings through the IoT Marketplace

(John Doe) #101

Thank you, wasn´t aware that it´s only working from 2.1 up, I was running 2.0…

(Dries) #102

Last weekend, I install my first binding trough the marketplace (Denon/Marantz binding).

Today I upgraded my OH snapshot to a newer release. And I noticed this binding got uninstalled. I guess it happened by clearing the cache/tmp folders. I had to reinstall the binding via PaperUI.

Is that normal/expected behaviour?

(Jürgen Baginski) #103

Yes, that is the normal behaviour.

(TKoe) #104

Hi guys.

Does anyone know if the marketplace down?
Snip from my openHAB2 log:

==> /var/log/openhab2/openhab.log <==
2018-01-22 16:54:38.792 [WARN ] [arketplace.internal.MarketplaceProxy] - Failed downloading Marketplace entries:  : marketplace.eclipse.org
2018-01-22 16:54:38.799 [WARN ] [arketplace.internal.MarketplaceProxy] - Retrying again in a minute

(Michael) #105

Hi everybody,
might be that I’m doing anything wrong. Everytime I upgrade openhab 2 I need to reinstall my Xiaomi Mi IO Binding, which is from the marketplace. Isn’t there a better way to install it automatically? It’s quite uncomfortable if you have lots of marketplace bindings, isn’t it?


(Ssalonen) #106

I think you are not doing anything wrong – actually, this very thing mentioned in the opening post:

Note 2: The jars are installed in the OSGi cache - which means that they are lost upon an openHAB distro upgrade (which cleans the cache) - you will have to manually re-install then from the marketplace. As the main use case for the start will be for testing pre-releases, I think this is acceptable. For the future, I also plan an improved mechanism, which would download the jars to the addons folder (or something similar), so that they are kept over an upgrade as well.

Unfortunately, I don’t have an answer for you – let’s see what others come up with.

(Jürgen Baginski) #107

The "comfortable"way is the build-in way. However that is limited for the bindings that went through the complete process to be accepted into a stable build.
The marketplace way to install bindings before that process is completed has been established in order to let experienced users install such bindings in an earlier state., knowing that for such users the “installation” of such binding would be no hassle ( dropping into addons folder).
IMHO this setup makes sense.

(Skinah) #108

Great feature that I have not used yet but wanting peoples feedback on what to do with my binding found here:

Currently this binding is a double up of sorts with another binding which is already merged. Add to this that a user wanting to use my binding has to build hardware first, this will cause the number of users to be in the lower number. So what to do with a binding like this?

  1. Do I still create a PR for the binding to be merged or listed so others can find the code on github easier? I am very new to github so not sure what options there are for what could be an low used binding and not worth building into Openhab 2.
  2. Do I just keep offering the JAR directly as I am now?
  3. I built the binding with the skeleton create binding script and choose “openhab” as the namespace? when the script was building. Does that mean it is not eclipse smarthome compatible and I should not upload it to the Maketplace as it is openhab2 only?

Any advice would be great as I have 2 more bindings on the way and still getting a feel for what the process is, done so much reading and learning to get to this point so I apologise if I have missed something.