Second real trial of oh2 b5 after having used oh1 for years
Did manual installation in expert mode though
Started with paper UI - really impressing, but⦠as an experienced user it would be much faster for me to do a copy&paste in the config files as in oh1; however instead of doing a clone of my current (running) oh1.8 system I want to do a setup oh2 from scratch. Therefore have started with hue as the easiest one, installed binding, identified bridge and after bridge got my 86 things (lamps). Have started creating items for first 2 lamps under paper ui I wanted to move now into config files and continue with changes.
However surprise: I do not find any things and items under ./conf/things ./conf/items which I had created under paper ui. Actually my perception was that all the configuration I do via paper ui on oh2 would be written into the config files and vice versa.
Can someone throw more light into this whether my understanding is wrong and if so, where do I find the config of all the staff created with paper ui and whether both paper ui conf and manual conf at same time would work.
This perception is wrong, at least a little bit. If you do your configuration using PaperUI, all the data is stored in files, but not the mentioned ./conf/* files. PaperUI writes the data in a JSONDB, which can be found under userdata/jsondb. And yes, this file is editable.
And also yes that you can use the PaperUI based json-files and manually created conf-files at the same time.
Many thanks for fast reply. Now I got a better understand. Just had a look at those config files under jsondb. You are right it is editable but nomenklatur is completely different from previous config files and not very manual editor friendly.
So one more question: What is the configuration for at .conf/*files ?
Is is only interim for those who want to upgrade from oh1.x to oh2 or will this remain longer and is another way how to configure oh2 with old oh1.x configuration nomenklatur?
Sorry for those questions but I want to find out of what is the (for me as coming from oh1) easiest way to configure oh2 without loosing all the advantages oh2 brings.
Yes, I think the json-files are not intended to be edited on a more frequent basis. At least not as we did it with the OH1 files.
The conf-files I think are still there because of the OH1 -> OH2 migrations. A lot of the (a little more experienced) users who come from OH1 do it this way: Let the things be discovered automatically using PaperUI (and therefore stored in json db) and do everything else manually with conf-files (items, sitemaps, rules etc.). Especially if they are migrating an existing and possibly very complex OH1 configuration and therfore donβt want to start from scratch.
PaperUI for sure will remain. Wether the conf-files do remain or not, I donβt know. On the short run Iβm sure they also will remain.
Would it be possible to make a main thread/page for custom rules of people. I have some rules for rollershutters and echo usage which i would like to share with you.
Hey Phill,
sure thing. Thatβs what the whole Tutorials and Examples category is for. Just create a new thread named βRollershutter Automationβ and throw your rules in there See other examples in the category to get an idea.
Guys, please update this FAQ.
When a new file is put to OpenHAB /addons folder, one must change the file permissions. Otherwise it will be invisible or maybe just inaccessible to OpenHAB.
Something like that:
chown openhab:openhab org.openhab.binding.enigma2_2.1.0.SNAPSHOT.jar
@sihui I will recheck the samba config on my PI3 openhabian, but on my system, downloaded and installed less than month ago, the behavior is different. And Iβm sure I didnβt changed the samba config just because Iβm not a Linux expert.
A moment ago I tried to copy some OpenHAB 2.3.0 JAR file using a samba share and checked after that the file permissions on the PI3 system. The owner of the file is openhabian user, not openhab. Also the file doesnβt have an executable flag, but Iβm not sure itβs required for OpenHAB2 JAR files.
So, as I can see, Raspberry PI users must change permissions for files copied to /addons folder, otherwise they will be invisible or inaccessible for the OpenHAB software. Also files may be put not only via samba share. I copied a file via SSE using MC. Unfortunately I just followed the FAQ and didnβt imagined to take care about permissions.
ITβs not the big deal to update the FAQ topic. But I mentioned above that Iβm not a Linux expert. So itβs better to discuss firstly, than write incorrect changes. My opinion that itβs enough to add something like βPlease check the file permissions, the file owner should be βopenhabβ. Use chown openhab:openhab to change permissionsβ.
Also the steps 4) and 5) are incorrect, at least for OpenHAB 2.2. When some binding is uninstalled in Paper UI, it doesnβt appears in the Karaf bundle:list -s output and cannot be uninstalled using bundle:uninstall.
I can assure you that on a linux manual installed system following the steps in the docs there are no permission issues.
I never tried openHABian, so if there are permission problems with that installation method, it is not recommended to change the FAQ (because that one is general), but to open an issue for openHABian.
Whatβs wrong with it on your system?
openhab> bundle:list -s
START LEVEL 100 , List Threshold: 50
ID β State β Lvl β Version β Symbolic name
βββββΌβββββββββββΌββββββΌβββββββββββββββββββββββββΌβββββββββββββββββββββββββββββββββ
...
228 β Active β 80 β 1.12.0.201801160209 β org.openhab.action.mail
229 β Active β 80 β 1.12.0.201801160209 β org.openhab.action.pushover
234 β Active β 80 β 0.10.0.201801152239 β org.eclipse.smarthome.binding.a
237 β Active β 80 β 1.12.0.201801160209 β org.openhab.binding.caldav-comm
239 β Active β 80 β 1.12.0.201801160209 β org.openhab.io.caldav
240 β Active β 80 β 1.12.0.201801160209 β org.openhab.binding.expire
242 β Active β 80 β 2.3.0.201801141430 β org.openhab.binding.harmonyhub
244 β Active β 80 β 1.12.0.201801160209 β org.openhab.binding.http
245 β Active β 80 β 0.10.0.201801152239 β org.eclipse.smarthome.binding.h
246 β Active β 80 β 0.10.0.201801152239 β org.eclipse.smarthome.config.di
247 β Active β 80 β 0.10.0.201801152239 β org.eclipse.smarthome.io.transp
248 β Active β 80 β 2.3.0.201801141430 β org.openhab.binding.amazondashb
249 β Active β 80 β 1.12.0.201801160209 β org.openhab.binding.mqtt
250 β Active β 80 β 1.12.0.201801160209 β org.openhab.io.transport.mqtt
251 β Active β 80 β 2.3.0.201801141430 β org.openhab.binding.network
252 β Active β 80 β 1.12.0.201801160209 β org.openhab.binding.tinkerforge
253 β Active β 80 β 2.3.0.201801141430 β org.openhab.binding.mihome
254 β Active β 80 β 0.10.0.201801152239 β org.eclipse.smarthome.extension
255 β Active β 80 β 2.3.0.201801141430 β org.openhab.io.openhabcloud
256 β Active β 80 β 1.12.0.201801160209 β org.openhab.persistence.influxdb
257 β Active β 80 β 1.12.0.201801160209 β org.openhab.persistence.mapdb
264 β Active β 80 β 2.3.0.201801201844 β org.openhab.binding.zwave
I havenβt tested this, but in theory, as long as the (*.jar) file can be read by any user (chmod xx4), it should work (the manually deployed binding will be loaded)
β¦maybe execute is also needed?.. not sure
@sihui Whatβs wrong with it on my system? Donβt know, is it wrong or just different - again, Iβm not a Linux or OpenHAB expert to say is it wrong or not.
What says FAQ on this page? 1) Uninstall the addon in Paper UI. <steps 2-4 are skipped to not waste the time> 5) Execute bundle:uninstall β¦
On my system, official openhabian on Raspberry PI3, OpenHAB 2.2 stable, when step 1) is performed, the bundle disappears from the Karaf console. At least it became invisible by bundle:list -s output and indeed it cannot be uninstalled using bundle:uninstall command.
Itβs not the big deal, because newest bundle JAR with right permissions, placed to the /addons folder, became automatically visible in Karaf console and OpenHAB automatically uses it like it was installed in Paper UI. I only want to notice that FAQ on this page sometimes is different, maybe incorrect, than real working system. It may be confusing for newbies.
OK, I believe someone who will read this FAQ page, will also read our discussion and keep in mind that itβs better also to recheck the file permissions.
As @rlkoshak said before, the FAQ is a wiki page and should allow everyone to add improved answers easily. I was a bit sad to see a longer discussion but not a single edit in the wiki itself. I have just done a few improvements of the FAQ and believe it is now much clearer and makes clear that some steps might be optional or depend on other things. Hope it helps.