Upgraded OH from 2.3.001 to 2.5m1 on a Synology:
I first wanted to thank the folks that helped me put this list together in this thread (@waspie & @Dennis1108 @ github )
Over all impression in the last 12 hours is the stability and consistency of 2.5m1. The logging has really improved in the events log. CPU usage has been reduced by 50%.
My Synology OH Setup:
Two DS716 setup in a HA cluster configuration (active/passive)
* RAID-1 drives in both units
* One USB SSD drive hanging off one of the DS716 units to backup OH to
* Two AEOTec USB zWave controllers (which are copies of each other)
* Using OH v2.3.001 from the Package Center (never updated to v2.3.005)
* I’m using these bindings:
- zWave v2.5, HUE, Sonos, WeMo, Onkyo, Amazon Echo, Unifi, MQTT, Open Weather Map, Mail, Air Quality, IP Camera, Nest, Network, Samsung TV, Synology Surveillance Station, Climacons, HUE Emulation, CalDAV
* Majority of my OH configuration has been done with single configuration files for things, items and rules. I have around 15k lines of code in the rules file since starting in June 2018.
* I'm running HABPanel on three Samsung tablets on walls
Steps I Followed:
1. Backup the entire \homes\openHab directory to another machine (do it twice, just in case)
2. Stop OH via the Package Center
3. Reboot the Synology to insure all OH hooks are disconnected
4. Uninstall OH v2.3.001 from the Synology via Package Center
5. Rename \openHAB\openhab public folder that contains the installation files \openHAB\openhab to \openHAB\openhab2.3 to insure there isn’t any conflict during this upgrade process
6. Download OH2.4 for Synology (PKG & ZIP)
a. https://github.com/openhab/openhab-syno-spk/releases
b. Unzip a copy of the of the ZIP on a PC for later review and copying over to the Synology
7. Copy openHAB-2.4.0.001-syno-noarch-0.001.spk over to \openHAB public folder (not the \homes\openhab directory)
8. ** Package Center, Manual Install, look for openHAB-2.4.0.001-syno-noarch-0.001.spk on your local PC
a. Choose 3rd destination /var/services/homes/openhab
b. I did NOT choose to install tmpfs or zWave options. I get the latest zWave binding (JAR) from the latest build online since it changes every week with new updates to it (Thanks @chris !)
i. If you had zWave running natively on v2.3; you’ll need to completely reset up zWave devices from scratch, there was a complete rewrite done (lucky for me; I did this on 2.3 prior to this upgrade)
9. Reboot the Synology
10. OH should auto start after the reboot, take a look at the log files to see what errors could be coming up. Mine was multiple IPs bound to interfaces.
2019-04-05 17:09:05.041 [WARN ] [g.eclipse.smarthome.core.net.NetUtil] - Found multiple local interfaces - ignoring 169.254.171.42
2019-04-05 17:09:05.063 [WARN ] [g.eclipse.smarthome.core.net.NetUtil] - Found multiple local interfaces - ignoring 192.168.0.230 <--
2019-04-05 17:09:05.065 [WARN ] [g.eclipse.smarthome.core.net.NetUtil] - Found multiple local interfaces - ignoring 192.168.0.210
You can resolve this from either the GUI Paper, System, Network setting or adding this line item in the runtime.cfg file
org.eclipse.smarthome.core.net.NetUtil:primaryAddress=192.168.0.230/24
11. Wait for OH 2.4 to completely start up; look at the openhab.log to verify complete startup
12. Stop OH 2.4 via Package Center
13. Download v2.5m1
a. https://www.openhab.org/download/
i. Select Linux - apt - milestone
ii. Scroll down to manual installation and then click the big unmissable download link
iii.Download OH 2.5m1 runtime and openhab-addons-2.5.0.M1.kar files
b. Modify your /etc/hosts to point to the main domain URL in the openHAB-2.4.0.001-syno-noarch-0.001.spk file to localhost. You’ll need to SSH into your system and go into super user mode in order to modify this file
i. 127.0.0.1 bintray.com
if you have a HA cluster; make sure to add it to both device hosts file)
ii. This will make it fail downloading the openHAB distribution files from the Internet and fallback to openhab-2.4.0.zip held in your \openHAB public folder (not your \homes\openhab folder)
c. Download and rename the openhab-2.5.0.M1.zip file to openhab-2.4.0.zip as seen in the /scripts/installer.sh file within .SPK file.
d. Copy over the newly renamed openhab-2.4.0.zip to /openHAB/ public folder (not your \homes\openhab folder) from your PC
e. Copy over openhab-addons-2.5.0.M1.kar to the /addon’s directory; this will be used to pull the bindings from since the bintray.com domain host entry points to your localhost now
14. Blow away and recreate the /userdata/tmp and /userdata/cache directories as a precaution.
15. Startup OH via Package Center (which will still show v2.4), review the logs to insure it starts up fine
16. Stop OH via Package Center
17. The main restore points would be your entire /conf folder, /userdata folder, and “some” of /addons JAR’s.
a. /userdata you probably only need/want:
i. uuid (file)
ii. openhabcloud (folder)
iii.jsondb (folder)
b. /config/org/openhab/ (there are files in here you may want like habpanel.config, the others are rebuilt)
c. Copy/paste entries from your copy of your /userdata/etc/org.ops4j.pax.logging.cfg into the new logging file which is different than v2.3 so don’t overwrite the entire logging file
18. Once v2.5m1 is running stable; start adding addon’s via the GUI slowly. You will see a system performance issues when adding a lot of bindings semi-quickly.
a. Insure this file is in the /addon’s directory you downloaded previously --> openhab-addons-2.5.0.M1.kar
b. You’ll want to use the GUI for all addon’s that exist in your installation vs. dropping them into the addon’s directory (one at a time to insure each work).
c. The only addon’s I dropped into the directory where ones that were NOT part of the GUI selections (one off bindings)
d. You will see duplicate binding entries in the GUI binding area 1.13 and 1.14 along with 2.4 and 2.5m1, choose the 2.5m1 options
e. Modify your addon’s.cfg file for binding entries to insure the bindings load the next time you clear cache/tmp directories
The ONLY major issues I encounter was:
1. Sitemaps, all my slider items had to be committed out – https://community.openhab.org/t/oh-v2-5m1-sitemap-slider-entries/71861
2. Having some duplicate bindings running from 2.4 and 2.5m1 that I had to manually stop and uninstall
3. Changing some startup rule logic - I'm guessing 2.5m1 is a bit more strict on item states
** Possible Hurdles for Some OH Synology Installations (I did NOT have to do this):
a. Remove the user in the Synology web UI
b. Reboot Synology
c. Following instructions from @Dennis1108
i. https://github.com/openhab/openhab-syno-spk/issues/148
ii. I did NOT have to do this step but here’s what mine looked like:
root@ds716cluster:~# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/md0 2.3G 1.2G 1.1G 53% /
none 3.9G 0 3.9G 0% /dev
/tmp 3.9G 23M 3.9G 1% /tmp
/run 3.9G 4.0M 3.9G 1% /run
/dev/shm 3.9G 4.0K 3.9G 1% /dev/shm
none 4.0K 0 4.0K 0% /sys/fs/cgroup
cgmfs 100K 0 100K 0% /run/cgmanager/fs
/dev/drbd-md2 3.5T 2.1T 1.5T 60% /volume1
/dev/sdq1 470G 73M 470G 1% /volumeUSB1/usbshare
Best, Jay