So now I got the USB controller and the two attached devices was discovered - I also managed to link to a switch using the paper-ui. I have some stupid questions though:
Thanks for the great work!
Great work @chris 
First I installed the latest OH2-snapshot #133 from cloudbees on OS X El Capitain, Version 10.11.3 (15D21)
First problem was to set the serial port /dev/tty.SLAB_USBtoUART of my AEON Labs Z-Stick S2 USB Controller (DSA02203) in habmin with Safari, it wasn’t possible to enter the value into the field - changed to Firefox it works. After restarting openHAB my AEON Labs Z-Wave stick works 
AEON Labs 4 in 1 Sensor (DSB05) was discovered and could be configured, works fine
Fibaro RGBW Controller (FGBRGBW) was discovered and could be configured, works fine
Fibaro Double Relay Switch 2x1.5kW (FGS211) was discovered as unknown, maybe i got a version >=1.9 marked as information required in the database
Fibaro Motion Sensor (FGMS001) was discovered as unknown, because database status is “This device is awaiting review following updates.”?
Thank you very much for your hard work on this OH2-Z-Wave-Binding!
Hi to everybody.
Seems to work nice on my setup. My OH Alpha2 is running on an Ubuntu-VM which switches from host to host. So I use a RaspPi as Gateway with Virualhere.
Now everytime I lose connection or unplug/plug my Aeonstick S2 I have to restart OH2 or at least to modify the Port-Setting (ttyUSB0 to ttyUSB0 to reboot binding). Is there any possibility to implement some sort of Watchdog?
I’d like to upload an XML (1 for now [Aeon Labs.DSC27,Micro Illuminator G2], further coming) to your DB, i’m already registered.
Thank you for your great work!
Thanks Marvin. I’ve uploaded your files - there’s maybe some work to do with the color button device (which looks kind of cool actually) to define the channels so we’ll need to look at that, but at least the devices have a start…
This device also needs some thought as to how to handle this in the database (well, not just the database, but within OH2).
It shouldn’t, but if you (or the binding!) ends up going into include mode and including the device multiple times, then this could happen. I need to relook at the logic around discovery mode to make sure the binding isn’t causing this sort of thing since a few people have made similar comments…
Maybe this requires a broader discussion and you should take up with ESH since this is defined in the ESH docs. @kai what’s the ruling here? I understand from the docs, and previous discussions that item types need to be set to those listed in the ESH docs?
Correct - this is something that is still ongoing within ESH.
I think you should be able to delete the sample files, but I’m not 100% sure that nothing gets generated into the mapdb database so you might also need to delete that as well (in the userdata/mapdb folder). If this doesn’t help, I’d suggest starting a separate thread on this (but do a quick search first since I think I saw a similar thread recently).
I’ve processed these two. I’ll generate a new version later tonight…
I’ve given you access - thanks 
I’ve updated the binding with the latest devices (8 more added tonight).
Note that this doesn’t include all devices that people have added/updated today since some of them are still missing data so we’ll need to look at this at some stage, but I’ve tried to get everything that’s ready into the system…
[quote=“chris, post:125, topic:7522, full:true”]
I’ve updated the binding with the latest devices (8 more added tonight).[/Quote]
Thanks for that, @Chris!
For me node 2, 5 ans 8 is working now. The RGB-LED-Simmer/ Switch (PSR04) isn’t supported yet, but as you said we have to take a closer look at this device. The Roller Shutter and the Smart Switch I don’t get them to send anything. Maybe they aren’t working correctly.
A log might be useful for the roller shutter since that looks ok in the database.
For the smart switch, I guess that’s the [Aeotec Micro Switch G2] ( http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/822)? This device still needs an XML file loading - if you can add one, or put it in your OneDrive, that would be great…
Hi all
Myabe it’s trivial question.
I have aoeon usb z-stick. Shuld I crate file zwave.cfg in /conf/services similar to openhab.cfg ?
Regards
Tomek
No - you dont need this file. Just follow the instructions above and ad the Z-Wave Serial Controller thing - this is a proxy for the z-stick.
Ok
I set up OH2
I go to habmin select Configuration-> Thing Configuration -> + next Add new Thing Wizard was showed with three steps
The Database seems to be crached (synology? :p)
Isn’t this the device I updated with an XML this morning (MEZ)?
Edit: Sorry, my XML was for the DSC27, Micro Illuminator G2
There is a bug here in the UI, but are you sure the thing is not being created? Look in the thing configuration to see if it’s there…
It seems ok here at the moment. One point is that you need to have the www in front, otherwise Synology can get upset.
I’m not sure what you’re referring to - sorry… I think you modified 3 devices this morning - ZMNHBA, DSC27, and the Z-Stick. I’ve created a new binding with the first 2 added already - the zstick isn’t really needed…
Thank you @chris 
Fibaro Motion Sensor (FGMS001) was discovered and could be configured
Fibaro Double Relay Switch 2x1.5kW (FGS211) remains still as unknown, maybe i got a version >=1.9
Tested with fresh installed OH2-snapshot #134 from cloudbees on OS X El Capitain, Version 10.11.3 (15D21)
Regards
Heiko
The FGS211 in the database has no version constraint so it should work. Can you attach your XML file for this node - or post the type/id that is being reported?
hope this XML from openhab/userdata/zwave is the thing you need for diagnostic:
node7.xml (6.1 KB)
what of this information from Paper UI is the type/id?
Unknown
Node 7 (010F:0200:100A:2.1)
zwave:unknown:200539d5:node7
sorry, at this early step in OH2 beta i don’t understand very much about the configuration.
Erm I’ve got a small but frustrating issue that’s popped up.
All ZWave parameters have disappeared from PaperUI. They’re available in HabMIN and yesterday or the day before they were in PaperUI, now nothing.
There’s no problems in the log and I’ve tried blasting browser cache.
Any ideas?
That’s perfect - thanks. I’ve updated the database and will generate a new version later, so hopefully it will be fixed then
I don’t use PaperUI so havent noticed this. I did see some PRs going through where there were updates to the config screens so maybe there’s some sort of incompatability now. I’ll try and look at this over the next couple of days…
Thank you for that, i’ll try it out - maybe with the next OH2-snapshot from cloudbees
Don’t worry about that, too much is changing at this time - with the latest cloudbees snapshot in PaperUI i have much problems to configure other things then testing the Z-Wave binding 
Hi @chris,
A couple of things I’ve noticed…
Following on from my earlier question on Contact item vs Switch item for the motion sensor, I’ve bound the channel to a Switch item to see if I can get it working. Unfortunately I don’t seem to ever get an update. I’ve seen SENSOR_MULTILEVEL (i.e. temperature, humidity etc) reports being received but none from the motion sensor. Funnily enough I’m getting the anti-tamper/vibration reports too.
I seem to get errors in my log when trying to change the device parameters. Here’s an example:
2016-02-17 22:03:12.159 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Got an event from Z-Wave network: ZWaveConfigurationParameterEvent
2016-02-17 22:03:12.161 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Got a value event from Z-Wave network, endpoint = 0, command class = CONFIGURATION, value = org.openhab.binding.zwave.internal.protocol.ZWaveConfigurationParameter@53187b
2016-02-17 22:03:12.162 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Update CONFIGURATION 5/1 to 2
2016-02-17 22:03:12.162 [INFO ] [marthome.event.ItemStateChangedEvent] - zwave_serial_zstick_152e6d93f03_serial_sof changed from 211 to 212
2016-02-17 22:03:12.166 [ERROR] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Sub-parameter config_201_1 is 00000002
2016-02-17 22:03:12.166 [ERROR] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Sub-parameter config_201_1 is 2
2016-02-17 22:03:12.168 [ERROR] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Sub-parameter config_202_1 is 00000002
2016-02-17 22:03:12.169 [ERROR] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Sub-parameter config_202_1 is 2
2016-02-17 22:03:12.172 [ERROR] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Size error 2<>1 from config_203_2
2016-02-17 22:03:12.173 [ERROR] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Sub-parameter config_204_1 is 00000002
2016-02-17 22:03:12.174 [ERROR] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Sub-parameter config_204_1 is 2
2016-02-17 22:03:12.175 [ERROR] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Sub-parameter config_110_1 is 00000002
2016-02-17 22:03:12.176 [ERROR] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Sub-parameter config_110_1 is 2
2016-02-17 22:03:12.177 [ERROR] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Size error 4<>1 from config_112_4
2016-02-17 22:03:12.178 [ERROR] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Sub-parameter config_39_1 is 00000002
2016-02-17 22:03:12.179 [ERROR] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Sub-parameter config_39_1 is 2
2016-02-17 22:03:12.180 [ERROR] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Size error 4<>1 from config_113_4
2016-02-17 22:03:12.181 [ERROR] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Size error 4<>1 from config_111_4
2016-02-17 22:03:12.182 [ERROR] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Size error 2<>1 from config_41_2
2016-02-17 22:03:12.183 [ERROR] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Sub-parameter config_42_1 is 00000002
2016-02-17 22:03:12.184 [ERROR] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Sub-parameter config_42_1 is 2
2016-02-17 22:03:12.185 [ERROR] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Size error 2<>1 from config_43_2
2016-02-17 22:03:12.186 [ERROR] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Sub-parameter config_40_1 is 00000002
2016-02-17 22:03:12.187 [ERROR] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Sub-parameter config_40_1 is 2
2016-02-17 22:03:12.188 [ERROR] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Sub-parameter config_252_1 is 00000002
2016-02-17 22:03:12.189 [ERROR] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Sub-parameter config_252_1 is 2
2016-02-17 22:03:12.190 [ERROR] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Size error 4<>1 from config_255_4
2016-02-17 22:03:12.191 [ERROR] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Sub-parameter config_2_1 is 00000002
2016-02-17 22:03:12.192 [ERROR] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Sub-parameter config_2_1 is 2
2016-02-17 22:03:12.193 [ERROR] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Sub-parameter config_100_1 is 00000002
2016-02-17 22:03:12.194 [ERROR] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Sub-parameter config_100_1 is 2
2016-02-17 22:03:12.195 [ERROR] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Size error 4<>1 from config_101_4
Maybe these are linked - I’m not sure if the parameters for the motion sensor are correct but it errors when I try and change them.
I’ve already turned on debug for the binding - any others tips for trying to pin point the issues?