Found Amanda for backup… sounds complicated (but very effective).
Found openHABian-config and upgraded to 2.2.0 I’ll have to figure out what the other options do.
Still can’t find addons directory.
It’s possible that you did not upgrade correctly (there is a configuration for logging that has changed, the upgrade will by default use the old configuration, which is wrong). See here:
I guess that’s the problem. It would have been nice to have known that I should not have accepted the defaults for those files. Perhaps some instructions somewhere.
I’ll see if I can patch it up.
You might think “that’s well hidden!” but from the perspective of a developer, this (release information document) is the one and only place to give detailed informations. Why repeating informations over and over again, when you can simply set a link to it?
I don’t want to be too hard on the good people here since I really appreciate everything they do but I do think the upgrade instructions could be improved to avoid the difficulty I (and others) have encountered.
The upgrade instructions are:
If you are working with an openHABian setup, the upgrade is quite easy. Regardless of if you are currently using the openHAB 2.1 stable release or one of the latest 2.2 SNAPSHOT builds, switching to openHAB 2.2.0 stable is done in just a few steps:
Connect to the SSH command line and execute: sudo openhabian-config
Select the "Update" option
Wait for the openHABian update to finish, reenter the openHABian configuration tool
Select the "openHAB 2.2.0 stable" option
It would be good to include instructions here to NOT accept the default reply to the messages which appear during the upgrade for certain files. The default option keeps the old configuration and this is not the correct response for some of the files. (It would be useful to know which files should use the old configuration and which the new.)
The “Breaking Changes” section talks about what to do if you have made changes to the configuration file but should also include the above advice about upgrading to NOT accept the default response to that file which is to keep the old file. It should instruct to use the new file.
Again, I really appreciate all of the effort everyone has put into this project and my intention is to improve it, not criticize.
That’s the Thing. Wenn can’t publish such Infos online from a developers view, if the System is going to be used by other people than developers too.
Ich would consider myself as a geek, tech interested human and since i am working with different programming languages for years i would consider myself as a kind of developer too.
Guss what: i had the logging problem too and checked that file after updating.
Things like this should be improved if we want openHAB to be used by a wider range in the future.
Oh, I had this Issue, too. But I don’t complain, because I found the needed information at once by reading the release notes (which I should have done before updating!)
Release notes are never optional that’s no “we are very proud to present, and hey, thank god it’s Friday” document, but essential information about new functions, bug fixes, changes …
And home automation is no job for “let’s click the install button and all will work automagically”.
In fact, at least in Germany, we home automation enthusiasts are always called nerds
I need some advice for moving the configuration files to a mounted nfs folder located on a NAS.
It seems as if the configuration folder is hard-linked to at least two places:
/etc/openhab2/
/srv/openhab2-conf/
What’s the reason for that? Could there be a problem with replacing them with symlinks to an nfs-mounted folder?
I also consider moving /srv/openhab2-userdata as well, could there be a problem with that?
See /etc/fstab. The first column is the real location. The second is a directory loopback mount of the same dir to allow for Samba to easily share it (you can remove it from /etc/fstab if you don’t want it, also IIRC it’s a reversible config option in openHABian). So no, you do not want to move /srv/.
I have a NAS, too, and chose to mount logs (var/log/openhab2) and /var/lib/openhab2 (to contain persistence data etc). I chose to however NOT mount /etc/openhab2 so in case of trouble with the NAS or connection openhab still has access to the config.
Thank you @mstormi for this detailed information and for sharing your experience about using a NAS.
Before my update to openhabian, the entire (manual) openhab installation was located on a mounted nfs folder. But the setup is completely different now. I think I will now also keep everything on the sd card and make regular backups instead (maybe even executed by rules via the exec binding).
I’d still strongly suggest to put logs and persistence data on the NAS mount. They account for the vast majority of writes, and once you move these, you’ll be ‘reasonably’ safe from SD card corruption.
You’ll still have to do backups, of course. Check out the Amanda backup system install option in openHABian.
I raised this topic/problem on the beginners forum:-
and have been advised to move it here.as it seems to be a problem with openhab setup. The same Pi with raspbian stretch works fine, so the problem is not the hardware.
I have tried a number of times now to get the wireless working, each time the result is the same, the pi no longer boots and I have to reflash the card.
Any help/advice/solutions would be gratefully received- as I stated in the beginners forum, using wired on my home network is not an option for me except for testing.
After being unsuccessful to install OpenhabianPi 1.4.1 on my new RBP3+ through WiFi, I was able to install OH through Ethernet.
Then I wanted to make WiFi active using openhabian-config, but the I got this message:
┌────────────┤ Incompatible Hardware Detected ├────────────┐
│ │
│ Wifi setup: This option is for the Pi3, Pi0W or the Pine │
│ A64 system only. │
│ │
│ │
│ │
│ <Ok> │
│ │
└──────────────────────────────────────────────────────────┘
Should I wait for an update that includes WiFi support?