I have a running OH1 installation (RPi3, raspbian, Aeon Gen5 Zwave stick with half a dozen devices included).
Now I am eager to migrate to OH2 and searching for “the right path”. I would prefer to keep it simple and use openHABian on a new SD card. After the installation I would try to migrate my configuration to the new OH2 installation.
At least this ensures a way back, if I am not happy with perhaps the stability of OH2 beta.
Or is it better to install OH2 on my current OH1 SD card? Maybe this includes some kind of automatic migration?
I’m primarily concerned about my zwave devices. What happens when I do a new, clean installation of OH2 and then install my AEON zwave stick? Are all my current devices stored on the stick, so that the new OH2 installation recognizes them automatically? Or do I have to include all of them again?
The migration part of the wiki documentation doesn’t give me any answers for this.
You will be just fine swapping your Zwave stick between your OH1 and OH2 installation as all your Zwave inclusions are stored on the Zwave stick and not in Openhab.
So once you plug in you Zwave stick into OH2 and have installed the Zwave binding in OH2 it will find all the previously included zwave nodes.
Hello @jaydee73,
I have no experience with zwave but regarding the migration: There is no migration procedure in place, hence I agree with your first thought. Start off with a fresh (openHABian) installation and add your configuration step by step. If you want to stay with the file based configuration you already have:
have a close look at the logs throughout the whole migration process (in openHABian, there is the alias command openhablog for that)
On a side note: We are always looking for volunteers to write short tutorials. It would be amazing if you (or whoever reads this) could find the time to write a short text on Migrating from OH1 to OH2 and post it under Tutorials & Examples. A summary twice the size of my previous answer is probably enough.
Absolutely. I just thought that @jaydee73 may find it easier to contribute something here in the forum. You (Stefan) are of course also welcome to create a pull request for the migration article.
So I guess what I’m saying is: Content first!
I know how big of a step it is to start contributing to a new project and ANYTHING is already amazing. If someone finds the time to write a short tutorial, I’ll be sure to take my time to transfer it into the docs.
Since I’m having some small issues with new zwave sensors (see Floodsensor) that should be no issues in OH2, I’m also on the point to (maybe) migrate from OH1 to OH2.
Don’t know if a procedure is now fully in place (or needed)? Else I would like to attribute to this.
Personally, I’m having some questions like:
What with my server-migration? Can I run 2 servers/applications at the same, or one-shot upgrade, or…?
What with my hardware (zwave, knx…)?
What with my items/sitemap files (just copy and go?)?
What with my rules/scripts (again just copy and go?)?
Will my add-ons like pushover work…?
Certainly all questions that will be answered when I start to dig in to them. But maybe better for everybody to organize this a bit? Since English is not my native language, I guess it would be nice if somebody else can help to (re)write the procedure?
OH2 is the successor to OH1. Yes there are a lot differences but most things will of course work as before.
Regarding the upgrade process: I would recommend making a backup of your OH1 installation and then making a clean switch. Habmin2 will take care of your zwave devices. Items, sitemaps and rules can be reused with a few slight modifications. Most addons (like pushover) are working as expected. To be safe, check the list of tested addons and have a quick search for obvious problems with e.g. knx here in the forum.
Please have a look at the Migration Tutorial and if you are working with a Raspberry Pi, consider using openHABian.
To elaborate just a bit on Thom’s answer, the reason it is best to make a clean switch is that there are conflicts when trying to run two instances of OH at the same time. In your case the big problem will be only one can access the zwave controller at a time.
Hardware setup for zwave is a little different with the 2.0 zwave binding, but the procedure is documented in the readme.
Items will be slightly different. 2.0 bindings use the new concepts of Things and Channels. These replace the configuration parameters you used to put in the “{ }” on your Items. Now, instead of a config that looks like {zwave="6:command=switch_binary,respond_to_basic=true"} it will look like {channel="zwave:device:528f7aca:node6:switch_binary" } which is the Channel ID which you can find in PaperUI, Habmin, or the Karaf console.
Sitemap, rules, scripts, and persistence should all work unchanged.
If it is a supported 1.9 binding, it should work just fine. If it is a 2.0 version of that binding it may work differently.
Let me know if the Migration Tutorial is not adequate for your needs and I’ll edit it to address the deficiencies.
KNX was running out of the box, just updated knx.cfg.
zwave binding was something else. the file zwave.cfg wasn’t created automatically, and I needed to copy the jar file 1.9 under addons. But after this…
And with copying the old items, sitemaps, rules, scripts… OH2 started to live.
I just needed to updated the _default sitemap to default to get my ‘old’ sitemap to show up.
And copy the icons so my old sitemap was
It all took about 2 hours, so to be honest, it wasn’t that big of deal.
Next step, trying to secure the server a bit more, OH1 was nicely/simply done for access internally/externally. But now, I feel a bit naked.
Afterwards, check if all rules/scripts/pushover… are working as they supposed to do. I guess step 6 in the migration procedure (btw you’ve got 2x times step 6 in the procedure)?
Afterwards, update to OH2 bindings and testing the zwave devices.
The config file will only be generated if you “install” the binding through the console or PaperUI. If you are using PaperUI, you need to configure the System to “Include Legacy 1.x Bindings” and the 1.9 zwave binding will now appear in the list. I’m not sure how to do it from the console.
I followed the steps, (option include legacy…) all through paperUI. But somewhere, the file wasn’t created. I’ve created it manually, and it was working.
But now, I’m running the 2.0 binding. Jiepie!
All none-powered zwave devices are still in state ‘unknown’ in things. But guess I’ll just need to have a little bit of patience. The powered once are in, and I can switch on a light with a simple relay. So it looks promising.
Tomorrow I’ll have a look if the devices have communicated a bit more information.
I’ve added nginx for security. Is working smoothly for the android app. I just have a small issue with habmin and google chrome. But in firefox it’s working. So for the moment, I’m not naked anymore.
Glad you got it working. You may have to manually wake up some of your battery powered devices. The binding may need multiple contacts with the device to get all the info it needs. If your device only reports very infrequently (e.g. I have smoke alarms that report once a week, if that) it could take weeks or months before the binding recognizes the device. Some devices, like Minimotes, don’t report at all without being woken up.
Also, I would caution you to at least consider using my.openhab to get at your OH remotely. Ngnix is pretty awesome and a solid project but any time you expose your LAN to the Internet you are taking on the responsibility to monitor, audit, and update your connections to ensure your home network is and remains protected.
For example, I have port 22 (ssh) exposed over my router. In the last week I’ve banned over 2100 IP addresses who are trying to hack into my network through that port. Before switching to OH 2 and I had 443 exposed I saw a similar number of attacks a week on that port.
If you are unaware that these sorts of attacks can take place and/or are unaware how to find out if these attacks are taking place on your network I cannot recommend using NGINX as your protection mechanism and highly recommend my.openhab instead.
Not yet unfortunately. However, you can run on OH 2 with the 1.9 SNAPSHOT binding or an alternatively compiled binding (i.e. whatever you are using now) until it is.
I’ve got another firewall (opnsense) in front of everything that does a first layer of security. And mostly, I work over vpn, but I’m very intresting how openhab2 solve these things. Professional deformation as network engineer.
A very nice feature of openhab is the internal/external connection with the android app. With this, it’s not needed to explain my family about private/public use. They just use it…
No devices have been properly added.
I see a lot of log entries like below. Looks like it keep on counting up?
2016-10-05 18:33:29.142 [ItemStateChangedEvent ] - zwave_serial_zstick_1578e7a83ee_serial_sof changed from 8958 to 8959
2016-10-05 18:33:29.290 [ItemStateChangedEvent ] - zwave_serial_zstick_1578e7a83ee_serial_sof changed from 8959 to 8960
2016-10-05 18:33:29.441 [ItemStateChangedEvent ] - zwave_serial_zstick_1578e7a83ee_serial_sof changed from 8960 to 8961
I’ve triggerd a Philio 3in1 sensor several time (open/close, tampered the switch…). But to me, it seems that it’s not sending data anymore. Or at least, it’s not being seen in the logs.
I’ve got about 20 of these sensors, and before, they’re sending every 2 hours data like temperature/battery/lux… But till now, not one sensor was reconigzed in OH2.
logs/openhab.log:2016-10-05 12:20:24.223 [ERROR] [l.serialmessage.SendDataMessageClass] - NODE 31: Sent Data was not placed on stack due to error 0.
logs/openhab.log:2016-10-05 12:20:29.570 [WARN ] [ocol.ZWaveController$ZWaveSendThread] - NODE 31: Too many retries. Discarding message: Message: class=SendData[0x13], type=Request[0x00], priority=Poll, dest=31, callback=222, payload=1F 01 00
logs/openhab.log:2016-10-05 16:37:58.564 [INFO ] [mmandclass.ZWaveSecurityCommandClass] - NODE 31: setupNetworkKey useSchemeZero=false
logs/openhab.log:2016-10-05 16:38:04.929 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 31: Timeout while sending message. Requeueing - 2 attempts left!
logs/openhab.log:2016-10-05 16:39:12.017 [INFO ] [mmandclass.ZWaveSecurityCommandClass] - NODE 31: setupNetworkKey useSchemeZero=false
logs/openhab.log:2016-10-05 16:39:13.030 [INFO ] [ommandclass.ZWaveVersionCommandClass] - NODE 31: Command Class BASIC has version 0!
logs/openhab.log:2016-10-05 16:39:13.083 [INFO ] [ommandclass.ZWaveVersionCommandClass] - NODE 31: Command Class BASIC has version 0!
logs/openhab.log:2016-10-05 16:39:13.871 [ERROR] [curityCommandClassWithInitialization] - NODE 31: SECURITY_ERROR Invalid state! Secure inclusion has not completed and we are not in inclusion mode. Aborting
logs/openhab.log:2016-10-05 16:39:14.260 [ERROR] [curityCommandClassWithInitialization] - NODE 31: SECURITY_ERROR Invalid state! Secure inclusion has not completed and we are not in inclusion mode. Aborting
logs/openhab.log:2016-10-05 16:39:14.745 [ERROR] [curityCommandClassWithInitialization] - NODE 31: SECURITY_ERROR Invalid state! Secure inclusion has not completed and we are not in inclusion mode. Aborting
logs/openhab.log:2016-10-05 16:39:20.732 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 31: Timeout while sending message. Requeueing - 2 attempts left!
logs/openhab.log:2016-10-05 16:39:44.444 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 31: Timeout while sending message. Requeueing - 2 attempts left!
logs/openhab.log:2016-10-05 16:39:53.868 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 31: Timeout while sending message. Requeueing - 2 attempts left!
logs/openhab.log:2016-10-05 16:39:59.924 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 31: Timeout while sending message. Requeueing - 1 attempts left!
logs/openhab.log:2016-10-05 17:09:32.178 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 31: Timeout while sending message. Requeueing - 2 attempts left!
Almost 5 days, and still no devices that are properly recognized.
After I run around and tampered all devices, things were starting to look like it should be.
…