OK, I released a new version:
I tried an install of 2.1.0.005-DSM6. No joy. Nothing in the log and no web server activity even after 30 minutes. So I uninstalled and reinstalled 2.0.0.001-DSM6 which always works.
The Synology software assures the Oracle Java update is correct for your CPU architecture. The key is that the user must update Java to get an Oracle version.
openHAB-2.1.0.010-syno-noarch-0.001.spk does not work 
Update: Sorry openHAB-2.1.0.010-syno-noarch-0.001.spk is only for Synology DiskStation Package for DSM <= 5.2 and i run DSM 6=<
It seems to work 
with openHAB-2.1.0.006-DSM6-syno-noarch-0.001.spk it makes the openhab2 user but i canāt see any files in ā/volume1/Public/openHAB2/confā or ā/volume1/Public/openHAB2/addonsā.
https://github.com/SchoppAx/openhab-syno-spk/releases/tag/2.1.0.006-DSM6
OK, I released a new version:
1 Like
It works.
Iām running a DS412+ on DSM 6.1.3-15152 and I can also see the folders and files in my Public conf Folder.
Iāll test tomorrow if I can add items and things manually via the public folder.
I have te sam e problems: 2.1.0.005, 2.1.0.008, 2.2.0.002 and 2.2.0.003 donĀ“t read the conf - folder. BasicUI answers:
no need to say, that in the conf - folder the file demo.sitemap exists!
@cniweb Hi Christian,
Thank you, both:
- openHAB-2.2.0.003-SNAPSHOT-syno-noarch-0.001.spk (DSM6)
- openHAB-2.1.0.008-DSM6-syno-noarch-0.001.spk
install well on my DS214 (ARM) and DSM716+II (INTEL)
1 Like
does openhab BasicUI read your conf - Folder? I tried it at the /volume1/public/openHAB2/conf and at the original folder, but basicUI says: sitemap not found! My Synology is a DS2013+ with DSM 6.1.3-15152 update1. The 2.0 Version worked fine.
Walter, I havenāt done much testing but:
The following files that I put in my ./conf & ./addons folders are being read:
- *.item files ( ./conf/items )
- demo.sitemap (./conf/sitemaps/. )
-*.jar files of a experimental binding, not in official repository yet ( ./addons/. )
I havenāt seriously used the Basic UI, just the paper UI, but the demo.sitemap is being read as well, when I copy the demo.sitemap into the folder ./conf/sitemaps/. A fresh install does not install this demo.sitemap file (afaik). I copied it into the folder from a backup to test it for you. Good luck.
Iām wondering is there might be an issue with Public and public, as Iāve noticed both being used in some of the posts above?
Iām wondering is there might be an issue with Public and public, as Iāve noticed both being used in some of the posts above?
It is (afaik) case sensitive and I use:
\volume1\public\openHAB2\conf
\volume1\public\openHAB2\addons
I deinstalled openHAB2 and made a new installation: openHAB2, 2.2.0.008 and afterwards the snapshot 2.2.0.3.
The problem was not solved. The installation did not install for example even demo.sitemap. So I think, there must be something wrong but I have no idea, what ā¦
@walter32 Did you grant read/write access to the Synology local group āusersā on the public-folder? This is a requirement.
Summary
The installation process automatically adds a user āopenhab2ā (as a member of āusersā to your system, hence the above requirement) which makes it possible for openHAB2 to make a symbolic link to these folders and access them. You can check whether the installation has succesfully added the āopenhab2ā user:
1 Like
of course I did, I tried it with the admin-group too; I also made a local folder conf, but I had no luck ā¦
on my DS214play with DSM6 Iāve just successfully installed
openHAB-2.2.0.003-SNAPSHOT-syno-noarch-0.001.spk without any problems.
And itās the first time Iāve installed a package which successfully set the softlinks to public, so thank you for the improvements Christian.
Latest Version 2.1.0.008 works for me on my DS414 with armadaxp CPU running DSM 6. There were 2 obstacles I had to overcome.
There is absolutely no install documentation about the public folder. loovanloon provided the key for me that the public folder needed read/write permission for group users. No such requirement previously existed when all files were in /volume1/@appstore, the install took care of all permissions.
Is it proper to open an issue on github about the missing documentation about public folder requirements that prevents a successful install of the software? (Item 52 could be closed after updating the documentation for Java which now directs the user to install a version of Java that will not run on DSM 6 Synology with Armada chipsets.)
I also found that my configuration files that worked on ver 2.0 failed on 2.1 because a # is not a proper comment. Once I replaced the # with //, the conf files were accepted.
Yes, open an issue on GitHub, please!
OK, I will open an issue on GitHub. I started to reflect on why I had a public folder and why OpenHAB used that folder. The reason I have a public folder is that the PCLoadbetter Java utility required that the Oracle Java file be put into the public folder. Otherwise I wouldāve never created public and I had no plans to use public. I believe the reason OpenHAB uses public for configs is to allow easy PC access to that file system for viewing and editing the conf files. Are there other reasons for the use of public?