Not quite. There was a serious bug identified with 2.5.1 release core. This has been fixed and a new release, 2.5.1 will occur on the release repo. After that the core of OH will remain at version 2.5.1. However, developers can continue to make updates to bindings and other add-ons. These updates will be released as 2.5.2+ versions of the bindings. These updates to bindings will run on the 2.5.1 core.
There is nothing you need to do differently to install openHAB so I’m not sure what updates you want to be made to the installation docs.
What we don’t know yet (see my post above) is how we will install the 2.5.2+ versions of the add-ons. At such time as we know that, we (probably I) will update the docs if appropriate.
I forgot to answer this. There will be an addons Kar file distributed via the way openHAB is always distributed. Users will be able to upgrade the addons part. I don’t know the specifics. Previous updates were for the whole system, while this only updates one part, the addons. This is new and the reason the update of the distribution is needed.
The issue being foxed is when you perform a new install of openhab2 and openhab2-addons the initial dashboard either does not show or only shows for about a minute before it is uninstalled. They added the initial dashboard to the addons kar file, I believe.
Hello everyone! Is this right place to post suggestions for OH 3 ?
Introduce channel dependencies in binding XML. I mean when a channel is visible or not according to a setting on another channel. I know it can be configured in sitemap, but would be nice to have it in binding’s XML as a template. Or use disabled state instead of invisible. I think it would make controls more consistent. For instance, some devices have master on/off switch, and in OFF state other controls are ineffective, so it’s quite logical to have them in disabled state.
Add some parameters (properties) for manual discovery. This would be very handy in some cases, where you need to use something like one-time password in order to perform initial connection to a device.
My 2 cents regarding the new UI: I don’t think that typescript would put off contributions or that it has a learning curve (unless you start abusing it). But it does make refactoring easier and moving forward way faster and saves you a lot in the long run.
im just getting started with openHab for my Connected-Bus-Project… but I see the Serial binding which I very much need is a 1.x.x… does that mean I need to give up on OH already and go find a different setup? that there will be no more Serial Support in OH3 when it releases??
No. I suspect that there will be a 2.x/3.x version of the serial binding created. Much of the hard work is already done (that serial service that Bruce mentions which is shared by several bindings). All that needs to be done is create a binding that exposes the serial binding so users can more easily create and configure Things (a la MQTT 2 binding).
Should my expectations not pan out and a serial binding does not get developed before 3.0 comes out, there is almost certainly going to be a way to easily run a stripped down version of OH 1 and use a federation capability to connect that to an OH 3 instance. Obviously this would be a stop gap plan b type of approach but it would get you by if the binding doesn’t get released before OH 3.
You can also stick to OH 2.5 (or any earlier version of OH).
You can also look into possibly providing some help to create a 2.x version for the serial binding. This is not the only v1 binding that is kind of important. TCP and HTTP also do not have v2 bindings yet (HTTP one is definitely in work).
I done an upgrade on my qnap and it broke openhab, not found error for paperui. Done a fresh install still the same, then checked the console and features were not installed.
Added paperui and configured addons.cfg and all working