A huge “Thank You!” to all who contributed and for the hard work.
Thanks to all community and specially to all mantainers!
Thank you all to pertmit all of these make it possibile.
Thank you guys
Great Job and thank you for your effort !! Seems that Santa’s delivered the gift early this year :))
The release planning that went into this is top notch! Thanks!
Great work done! Thank you all!
I "stumbled " only over a misunderstanding concerning the ephemeris action. Reading the docs I understood that holidays relative to eastern were not (yet) calculated. But they are!
Again, a big THANK YOU!
The only place for improvement I saw is the build system automatically posts releases. I think a manual verification test could be useful before posting to the repos. That could avoid the issue of some users installing a bad build.
Is there something unclear or incorrect in the Ephemeris docs? I wrote them so am more than willing to address any confusion and make corrections. Please open a new thread and tag me if you have any recommendations.
thanks for the great work.
Could someone please update the information on docker hub. The image is there, but the description mentions 2.5.0.M1 as the latest available tag.
If you just pull the image “openhab/openhab:2.5.0”, it works. The intermediate milestone versions are missing too.
I just have updated my system from 2.4.0 to 2.5.0.
Now both my USB devices RFXCom and Z-Wave keeps reïnitializing.
In the log I see this error:
org.openhab.binding.zwave/2.5.0 (Should be wired to: org.openhab.core.io.transport.serial/2.5.0 (through [org.openhab.binding.zwave/2.5.0] osgi.wiring.package; filter:="(osgi.wiring.package=org.eclipse.smarthome.io.transport.serial)"))
It’s not clear to me if or what I should change.
All settings in the Paper UI looks normal.
Look for invalid addons in addons.cfg and addons.config. A common one is restdocs since it moved from misc to ui.
The addons loader reloads all addons every minute trying to load the invalid ones.
Thanks, this was the issue.
The mail was moven from action to binding if I’m correct.
Would be nice, when upgrading that things like this are converted during a upgrade.
To be fair, the announcement included a link to the Release Notes. When upgrading using apt there are Warnings displayed too.
Thank you to all contributors for all the work you out in there!
Would be great if there could be a category in the forum where all the upgrade related issues can be tagged with. Would make it easier to see if there are problems effecting my setup before I run my upgrade.
That’s what the release notes are for, chapter
### Breaking Changes that Require Manual Interaction after the Upgrade
I upgraded my manual 2.4.0 installation to 2.5.0. I did all things from the release notes and I also cleared tmp and cache dirs.
At first start, it did not create all my items that are in text files, some were missing (those created in PaperUI were not affected).
At second start, all items were there, but my Nest account went offline after a few minutes.
At third start, the first 2 problems did not occur, but:
- the Homematic binding still throws an exception every few minutes (https://github.com/openhab/openhab-addons/issues/5725)
- the Unifi binding does not update the online switch of items anymore
So, sadly, I am back to 2.4.0, because the Unifi problem is a show-stopper for me. The Homematic bug was already reported for 2.4.0. The Unifi problem is already being talked about in that binding’s thread. The Nest problem was not reproduced. Nothing more that I can contribute, I guess.
I really appreciate all the hard work of all maintainers, still it’s not good that strange problems happen on first start (maybe related to empty cache). I have also seen others recommending to restart openHAB 2.5.0 again after the first start.
Why is this in the Announcements instead of its own thread?
Or, perhaps related to a complex, flexible system where developers cannot anticipate and test all of the myriads of configuration combinations. It appears that some binding developers seem to wait until release, or close to release to try and fix their bindings.
I was reporting an upgrade experience. AFAIR, the announcement thread has been used for this kind of feedback for the 2.4.0 release.
If bindings developers fix their binding AFTER the release, how are they then being updated outside of an openHAB release?
AFAIK, bindings cannot be updated “officially” from within an openHAB installation (despite manually uninstalling and copying the new JAR file and hoping that it works).
I mentioned in my post above “I will provide a couple of further infos on how to proceed with 2.x” - there will be a way to make add-on fixes available to existing 2.5 users, so please be patient for a few more days!