Create JSON for 3rd party addons

Add-ons Bindings
1

I want to simplify installation for the DEV build of the Shelly binding through the 3rd party adding feature.

I curated the following json

[
{
"title": "Shelly Binding (DEV)",
"uid": "org-openhab-binding-shelly",
"id" : "shelly-dev",
"type": "binding",
"version" : "4.2.0-SNAPSHOT",
"author" : "markus7017",
"maturity": "beta",
"content_type": "application/vnd.openhab.feature;type=karfile",
"url" : "https://github.com/markus7017/myfiles/blob/master/shelly/org.openhab.binding.shelly-4.3.0-SNAPSHOT.kar",
"link" : "https://github.com/markus7017/myfiles/blob/master/shelly/README.md",
"description" : "DEV Build of the Shelly Binding",
"compatible_versions" : "[4.1.0.0;4.3.999)",
}
]

Bildschirmfoto 2024-07-20 um 18.31.06
Bildschirmfoto 2024-07-20 um 18.31.061526Ă—448 58.4 KB

@J-N-K
Shouldn’t the binding show up in the Add-Ons strore?
Is the maturity “beta” valid?

2

I think the trailing comma at the last line is not allowed in JSON. And you need to use https://raw.githubusercontent.com/markus7017/myfiles/master/shelly/org-openhab-binding-shelly-4.3.0-dev.json, otherwise you won’t get the content of the file but the web view version.

3

tanks for the quick response
good catch :slight_smile:

Now I have

[
{
"title": "Shelly Binding (DEV)",
"uid": "org-markus7017-binding-shelly",
"id" : "shelly-dev",
"type": "binding",
"version" : "4.2.0-SNAPSHOT",
"author" : "markus7017",
"maturity": "unstable",
"content_type": "application/vnd.openhab.feature;type=karfile",
"url" : "https://github.com/markus7017/myfiles/blob/master/shelly/org.openhab.binding.shelly-4.3.0-SNAPSHOT.kar",
"link" : "https://github.com/markus7017/myfiles/blob/master/shelly/README.md",
"description" : "DEV Build of the Shelly Binding",
"compatible_versions" : "[4.1.0.0;4.3.999)"
}
]

and use

https://raw.githubusercontent.com/markus7017/myfiles/master/shelly/org-openhab-binding-shelly-4.3.0-dev.json

in the setting page.

Bildschirmfoto 2024-07-21 um 11.45.58
Bildschirmfoto 2024-07-21 um 11.45.581446Ă—448 51.9 KB

but if I open the Addon-Store and filter for “Shelly” I only see the official binding and the beta one, but not my DXEV build.

Is the maturity “beta” valid? or is it “unstable”?
Is “org-markus7017-binding-shelly” a valid und? or do I have to use “org-openhab-binding-shelly”

4

Works for me:

Bildschirmfoto 2024-07-21 um 11.58.33
Bildschirmfoto 2024-07-21 um 11.58.332476Ă—716 72 KB

It also shows up in the bindings section:

Bildschirmfoto 2024-07-21 um 11.56.20
Bildschirmfoto 2024-07-21 um 11.56.201722Ă—1200 276 KB

Edit: the remote JSON is only refreshed every 15 minutes or so, maybe you checked to early after changing the file?

5

Everything is valid as maturity, but everything except stable will not be shown when the switch is disabled. All UIDs are allowed, the only requirement is that they are unique within a marketplace type (i.e. no second add-on is allowed to have the same UID in all used JSON marketplaces).

1 Like
6

you are right, I restarted OH and now I see it, thx

1 Like