Enjoy the new release and keep coding for 2.3 now!
P.S.: If you come across any issues, please directly files bug reports in the corresponding issue trackers - this will make it easier to follow-up than using this topic here.
Thanks a lot to everyone being involved in OH.
I really appreciate all your efforts enabling me with my limited coding capabilities to create a very satisfying smart home.
Will prepare a post with HomeBuilder presentation shortly, so everyone can enjoy it and kickstart their automation
Just to let you know real quick - if you have any ideas on how to improve HomeBuilder, feel free to submit an issue and CC my github handle (same as here).
Note that the upgrade process with Docker is not as smooth as it should be. I use the following process:
Backup and delete the contents of userdata
Run the new Image
Wait for OH to come up. Notice that userdata has been repopulated.
Stop the container
Restore userdata/jsondb and any modified config files in userdata/etc that you may have modified. It is probably best to reedit those files rather than blindly copying them.
We have a concept that might work to automate this but I haven’t had a chance to work on it to prove it out. The concept is to modify entrypoint.sh to check userdata/etc/version.properties and if the default version is different from the one mapped into the container then essentially do the same steps as Benjy’s script/apt-get/yum upgrade process. I know it is all theoretically possible but my Bash scripting skills are not all that great these days.
No, this is something we want to work out after christmas. But yes, the rough plan is to have 2.2 branches from which such releases would then be built. We do not have those branches yet (only the 2.2.0 tags), so PRs cannot be created against it. Note that only really critical fixes should make it in there. I’d suggest to add a “critical” label to the according issues/PR, but this is up to the maintainer - once the branches are created, those commits can be cherry-picked to it.
Leave us now a few days to relax, the past weeks (and night) were pretty tough
Unless I have missed something, in looking at the upgrade instructions for Windows I can see there has not been a change since 2.0 stable came out.
If you are upgrading from one stable version to another there is an issue when following those instructions in regards to the new logger. If you do not remove/delete the current logging file and add in the new one your log files will be blank.
Fantastic! Another great milestone for home automation enthusiasts and users.
Congratulations and thanks a lot to all who have made this possible especially just before Christmas!
I was able to upgrade to 2.2 on my RPi3, but because I had to install Oracle JDK version of Java to get it to work with openHAB cloud, I’m now getting errors when running “sudo apt-get upgrade” where it’s wanting me to install or use the JRE or JDK that contains missing components… Anyone else have this issue?
I’ve upgraded v2.1 on a raspberry Pi3 using apt get. The installation went well and all appears to be working with the exception on a blank log file.
Having read the link below about a windows installation I stopped OH, deleted the log files and restarted. OH created openhab.log but it is still blank.
Below is the log list in case it might provide some insight. Any idea what I have done wrong?
When you did the upgrade did it ask if you want to keep or use the new version of any config files? The logging config changed between versions and if you don’t have the new one your logger will be broken.
Is someone still working on that? 
