[SOLVED] How to check and restart Bindings

I’m using OH2 on a ubunut server, my hue rules stops working after 2 days.
Maybe it’s the binding that has stopped? I don’t know!
Whats the command to check the binding via karaff and start again, I havent found anything to do so on karaff console.
Thanks guys

List all bundles

bundle:list 
 ID │ State    │ Lvl │ Version                │ Name
────┼──────────┼─────┼────────────────────────┼─────────────────────────────────────────────────────────────────────────────────────────
 20 │ Active   │  80 │ 5.3.1.201602281253     │ OSGi JAX-RS Connector
bundle:status 20
Active
Logging in as openhab

                          __  _____    ____
  ____  ____  ___  ____  / / / /   |  / __ )
 / __ \/ __ \/ _ \/ __ \/ /_/ / /| | / __  |
/ /_/ / /_/ /  __/ / / / __  / ___ |/ /_/ /
\____/ .___/\___/_/ /_/_/ /_/_/  |_/_____/
    /_/                        2.4.0
                               Release Build

Hit '<tab>' for a list of available commands
and '[cmd] --help' for help on a specific command.
Hit '<ctrl-d>' or type 'system:shutdown' or 'logout' to shutdown openHAB.

openhab> bundle:
bundle:id                                                (Gets the bundle ID)
bundle:diag      (Displays diagnostic information why a bundle is not Active)
bundle:info                (Displays detailed information of a given bundles)
bundle:list                                     (Lists all installed bundles)
bundle:stop                                                    (Stop bundles)
bundle:start                                                 (Starts bundles)
bundle:watch                                    (Watches and updates bundles)
bundle:status                                 (Get the bundle current status)
bundle:update                                                 (Update bundle)
bundle:classes (Displays a list of classes/resources contained in the bundle)
bundle:headers                     (Displays OSGi headers of a given bundles)
bundle:install                                 (Installs one or more bundles)
bundle:refresh                                              (Refresh bundles)
bundle:resolve                                              (Resolve bundles)
bundle:restart                                             (Restarts bundles)
bundle:services                              (Lists OSGi services per Bundle)
bundle:load-test                                 (Load test bundle lifecycle)
bundle:tree-show  (Shows the tree of bundles based on the wiring information)
bundle:uninstall                                          (Uninstall bundles)
bundle:find-class          (Locates a specified class in any deployed bundle)
bundle:start-level                 (Gets or sets the start level of a bundle)
bundle:capabilities           (Displays OSGi capabilities of a given bundles)
bundle:requirements           (Displays OSGi requirements of a given bundles)
bundle:dynamic-import    (Enables/disables dynamic-import for a given bundle)

thanks @BrutalBirdie for the quick reply

Glad I could help :slight_smile:

LOL Typo for the win! :joy:

1 Like

yeah :sunglasses: typo of the day

2 Likes

I did not even realize this. But the UBUNUT-Server is a good name to be honest :smiley:

1 Like

I uninstalled a binding with bundle:unistall from 3.1.0.M5 to test another jar which I put in /usr/share/openhab/addons
After the test I wanted to reinstall the original bundle.
I managed to bundle:install with the URL searched in github. Now bundle:list shows
3.1.0.202106020341
instead of 3.1.0.5 as version number for the bundle.
Is there a way to use go back to the original M5-bundle?

Remove the file from the addons folder & reinstall the binding.

1 Like

I did that. To reinstall I used


bundle:install https://ci.openhab.org/job/openHAB-Addons/lastSuccessfulBuild/artifact/bundles/org.openhab.binding.fronius/target/org.openhab.binding.fronius-3.1.0-SNAPSHOT.jar

and get
253 â Installed â 80 â 3.1.0.202106090459
instead of 3.1.0.M5

So I didn’t get the original version but an updated one. Is that a problem?

That looks like you got a newer snapshot version. Tha t should work with M5 assuming no new bugs :wink: