Ah, sorry ! I just meant the excerpt from the logfile that you already pasted here in your initial post.
The gibberish with all the lines starting with “at” is what in Java is called a stacktrace - it tells us which places in the code it ran through when the error happened.
Same error here on OH 2.1 stable release. For what it’s worth, I’ve upgraded from 2.0 to 2.1.
For those of you unfamiliar with the commands, you can restart the bundle by first “START ID” number using the bundle:list command. Then, use that number to stop and start the astro bundle using the bundle:stop and bundle:start commands, respectively.
Maybe a dumb question, but is it still possible in OH2 (as it was with OH1) to just to exchange the JAR file of the astro binding to update this particular binding to the most recent one, without upgrading the entire OH2.1 system to an unstable release?
Yes, you can do that, but… The last ESH stable release was June 26, which does not include the astro binding fix (the astro binding recently was moved from the OH2 addons code base to the ESH code base). Therefore, I don’t think the fix for this bug will be available in a snapshot (unstable) OH2 build until @Kai builds the next ESH stable release.
Sorry again for my lack of knowledge, but what does ESH stand for please?
Does this mean, that there is no chance to have a workaround to update the Astrobinding to a working version until Kai releases this ESH? (I am guessing ESH is the stable release ?)
Cool, thanks a lot. Kind of obvious but wasn’t stil that clear to me Too many acronyms in IT…
So again for my understanding: For the time being it is not possible to replace the jar until Kai has released a STABLE ESH version? In other words, before the STABLE release of 2.2 there is no chance to have a fixed astrobinding.jar?
extract zip, find org.eclipse.smarthome.binding.astro_0.9.0.xyz.jar
install manually (don’t forget to uninstall the existing astro binding first)
Maybe it won’t work since there are additional changes in the ESH distro in other jars also.
Moving to snapshot is really not something to worry about. It is as stable as the release build.
You can always revert back to 2.1 stable from snapshot if you don’t like 2.2 snap