I use this device which works well.

http://www.amazon.com/gp/product/B007UZH7B8?keywords=aeon%20labs&qid=1450238294&ref_=sr_1_3&sr=8-3

hi! so, I got nearly the same setup a couple weeks ago (main components being the rpi2 & z-stick gen5). I first got an Aeon Labs z-wave smart switch to start with .

here's my wall of text that will serve more as moral support rather than technical support. There's also a chance that reading my wall of text will make things worse... I hope not, but it does at least demonstrate my messy experience with openhab thus far.

I went through tutorials and whatnot and it never really clicked. I figured I'd have this knocked out in a single evening, and that didn't happen for me. Everybody says the learning curve is steep, and knowing this fact is what kept me going (basically knowing I wasn't alone).

Using basic troubleshooting logic, I simplified the setup - no more attacking it full force with all the ideas of how I would customize this to suit my needs. Start embarrassingly simple and go from there.

For me, this is how I started moving forward. Stuck the z-stick into my Windows PC, placed the demo files where they belong, added the z-wave 1.8 binding file to the addons directory, put the HABmin files in the right place, opened the openhab-designer program and started looking at what was going on. Opening the HABmin interface is what gave me insight into what was going on with the z-wave controller. At first I tried this without the demo files (I thought the demo files would clutter up the experience), but although most of the demo stuff didn't apply to my setup, it gave me something to reverse engineer.

Change "demo.sitemap" to "default.sitemap" - that means you don't have to specify the sitemap in the URL... http://127.0.0.1:8080/ - default place to look at the default sitemap (sitemap file defines the pages, on-screen switches, etc...)

In Windows, you run openHAB by running the "start.bat" file in the runtime folder. The command prompt window will stay open and also serve as a window into what's going on with the server. Helpful debugging stuff maybe. You can run this in the background somehow, but for now, I want to see all the stuff happening so I let it do its thing. (Don't close this window - it's doing all the background stuff.)

So, each device in your z-wave network is a "node". When you pair (aka "include") a z-wave device to the z-stick, the node is assigned a number and saved in the stick itself (I think, which is something I didn't expect to be the case...). Easy to include new nodes with the z-stick, which btw has a battery inside: take the z-stick OUT of the computer, bring it to your plugged in z-wave switch, press the button on the z-stick and it slowly flashes blue, then press the button on the z-wave device. the new node is created in the z-stick and becomes available to reference via openhab when connected to the computer again)

demo.items file defines the actual items that your sitemap can reference. my z-wave item for that switch looks like this (all one line):

Switch MyPlug1 "My First Test Plug" (All) {zwave="2:command=switch_binary"}

In the sitemap, you'd reference this switch with its name, MyPlug1.

The "2" is the node. It's what points to the specific hardware device you want to reference. The commands available depend on the type of device you have, but I haven't investigated those options much.

I used HABmin to find the node. It's like a browser-based GUI admin page for openHAB. Download HABmin and put the files in the webapps directory within the openHAB runtime folder.

Here's some random screenshots that may or may not be a helpful reference: http://imgur.com/a/otbtD

It gets better. When I'm happy with it, I will move the install back over to the rpi2 (it's all text files, after all, so easy-ish transition) So far I have a motion sensor (from monoprice) that will turn on a light for one minute when triggered. (I can't seem to turn off that rule, but it at least works. ) I also replaced an in-wall switch for an outdoor light with a z-wave switch, so I can turn on the outdoor light from my phone. That's nice. It's all still a bit scrambled and messy, but it's starting to make more sense the more I tinker with it. The best thing I did was to understand that this will take time, and to accept that brute-forcing my way through learning this was not the path for me. :)

I hope I didn't screw up your project with all this nonsense. If you have any "ah ha!" moments / revelations, please share!