installed 2.5M2 yesterday and after some initial difficulties it now runs smooth. I had to restart openHAB several times before most of the exceptions in the log disappeared. I have two remaining issues, maybe it is useful for someone else:
To resolve exceptions by the org.openhab.core.ephemeris binding (still have to check out, what this is for) could only be resolved by creating services/ephemeris.cfg, as stated somewhere else on this forum :
Setting these parameters in PaperUI was not enough, but I prefer config files anyway. I could not find any documentation regarding valid region codes, so I am not really sure, what I configured
The KNX2 binding throws the following exception on every start, but it seems to work OK anyhow:
2019-08-12 00:41:25.572 [WARN ] [mmon.WrappedScheduledExecutorService] - Scheduled runnable ended with an exception:
java.lang.NullPointerException: null
at org.openhab.binding.knx.internal.client.AbstractKNXClient.readNextQueuedDatapoint(AbstractKNXClient.java:283) ~[?:?]
at org.openhab.binding.knx.internal.client.AbstractKNXClient.lambda$1(AbstractKNXClient.java:199) ~[?:?]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) ~[?:?]
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) ~[?:?]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) ~[?:?]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) ~[?:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:?]
at java.lang.Thread.run(Thread.java:748) [?:?]
after upgrading my Docker Installation I get the tollowing error in my Docker Terminal:
Launching the openHAB runtime...
Error installing bundle listed in startup.properties with url: mvn:org.apache.karaf.features/org.apache.karaf.features.extension/4.2.2 and startlevel: 1
After a complete deletion of all configs, 2.5.0.M2 won’t start either …
Kind regards
Niklas
Edit: Looks like the Docker container are still referencing to the startup.properties of 2.5.0.M1
After the start of the container my startup.properties is overwritten by 2.5.0.M1 file …
Edit2:
After a recreation of the container from scratch, everything works as expected.
I just did M2 upgrade today. Initially I had constant warnings about items not existing (even though they did). Clean-cache / reboots didn’t help. Ended up doing an uninstall and reinstall. (not purge - I kept my config files and everything else untouched)
After the reinstall everything started up correctly.
With a cleared cache, 2.5M2 logs a bunch of errors and usually warnings about missing Items. The cache should be cleared in the upgrade, so this happens on first start. After a few minutes and the logs are calm, restart OH again and the errors will be gone.
So, after clearing the cache, restart twice. I thought there was an issue for this already in GH (I can’t search for it ATM), but there may not be.
I just upgraded from 2.5 M1, and I am now having trouble with my embeded MQTT broker. I’m using the MQTT binding and the internal MQTT broker. My MQTT broker Thing now shows up as offline. I see that the name has changed on the broker since the upgrade.
I have deleted my MQTT broker as a thing, reinstalled the broker but then nothing appears in my inbox anymore. Is this a known issue? Or have I just missed something here? I’m leaning toward the latter.
Right, unless you need an entry in addon.cfg for a snapshot jar file or something you can safely comment everything out of the addon.cfg or even just delete the file and OpenHAB will recreate a new one on startup. Upon it doing so, if you look at it, every line will be commented out
It seems we are back on track with monthly milestone releases and it is great to see the huge activity from so many contributors. Big thanks to everyone involved!
A question that comes up more frequently now is when to expect the final 2.5 release, so let me briefly comment on that. Due to the long-running build refactoring that was underway many months after the 2.4 release, we did not follow the bi-yearly release cycle anymore and preferred to first come back with regular milestone builds. We will most likely do 2 or 3 more of them, but definitely want to get 2.5 out of the door this year, likely around early December. No dates are set yet, but that’s roughly the timeline to expect. As some might have noticed already, the focus is currently to get the PR queue for new bindings done and merged - so if you are one of the contributors, who is waiting since a long time for a review, now is a good moment to ping us on your PR to get the well-deserved attention .
As always: Enjoy Milestone 3 and if you encounter bugs, please directly report them on Github - thanks!
Is the openhab2-addons-legacy package supposed to be available, too ?
[11:57:24] root@openhabianpi:/home/openhabian/openhabian# apt-get install openhab2 openhab2-addons openhab2-addons-legacy
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen.... Fertig
Die folgenden Pakete werden aktualisiert (Upgrade):
openhab2 openhab2-addons openhab2-addons-legacy
3 aktualisiert, 0 neu installiert, 0 zu entfernen und 76 nicht aktualisiert.
Es müssen 271 MB an Archiven heruntergeladen werden.
Nach dieser Operation werden 921 kB Plattenplatz freigegeben.
Holen:1 https://openhab.jfrog.io/openhab/openhab-linuxpkg testing/main armhf openhab2 all 2.5.0~M3-1 [76,2 MB]
Holen:2 https://openhab.jfrog.io/openhab/openhab-linuxpkg testing/main armhf openhab2-addons all 2.5.0~M3-1 [182 MB]
Fehl:3 https://openhab.jfrog.io/openhab/openhab-linuxpkg testing/main armhf openhab2-addons-legacy all 2.5.0~M3-1
503 Service Temporarily Unavailable [IP: 35.231.52.82 443]
Es wurden 259 MB in 45 s geholt (5.726 kB/s).
E: Fehlschlag beim Holen von https://openhab.jfrog.io/openhab/openhab-linuxpkg/pool/main/2.5.0~M3/openhab2-addons-legacy_2.5.0~M3-1_all.deb 503 Service Temporarily Unavailable [IP: 35.231.52.82 443]
E: Einige Archive konnten nicht heruntergeladen werden; vielleicht »apt-get update« ausführen oder mit »--fix-missing« probieren?
.