I'm working on my own code to talk to a Z-wave controller (ZCU201), the result will hopefully be a small C library with some documentation. I'm using a combination of the LMCE code, the Zensys docs you have also found, and some reverse engineering to figure things out. One thing I'm curious about is the actual legal status of the Z-wave code in LMCE. It couldn't have been written without access to information under NDA with Zensys right? Further more, some of the header files still have Zensys copyright notices. >>sent commands to the device with his own software and the new driver I had been making the assumption that the 'new driver/software' was basically just for the usb->rs232 chip, so the kernel would see the dongle and add it as a ttyUSB • entry, but that once that happened, the serial protocol to talk to the device was the same and the existing ZWave binary would be used.

Introduction to OpenZWave. OpenZWave is an open-source, cross-platform library designed to enable anyone to add support for Z-Wave. API (Application Programming Interface) mode is a frame-based method for sending and receiving data to and from a radio's serial UART. The API is an alternative to.

Is that a misunderstanding? Have you and cyr been developing your own replacement for the existing ZWave binary? Maybe the 3 of us (4 if we get Daniel in) could talk about this on Skype or something.

This is relevant for us since the programmer at Pluto who wrote the ZWave module originally is not with us anymore, and there's some new ZWave features we need implemented, and maybe we can get you guys some equipment if you're working on ZWave drivers. Cyr works on a seperate project but seems to make good progress without the Zensys SDK. I stared at the DCE ZWave code for some days and have coarse understanding.

My next steps will be implementing multilevel sensor support after receiving the multisensor sample from Seluxit and improving bidirectional support. What holds me back for now is the 'unknown state' of the lmce/pluto code atm. It got removed because of the Zensys headers. I did some code parsing and came up with ~50 #defines needed to get rid of the both zensys files.

If Zensys is happy with that I can continue to improve the code. >>sent commands to the device with his own software and the new driver I had been making the assumption that the 'new driver/software' was basically just for the usb->rs232 chip, so the kernel would see the dongle and add it as a ttyUSB • entry, but that once that happened, the serial protocol to talk to the device was the same and the existing ZWave binary would be used. Is that a misunderstanding? Have you and cyr been developing your own replacement for the existing ZWave binary? Maybe the 3 of us (4 if we get Daniel in) could talk about this on Skype or something. This is relevant for us since the programmer at Pluto who wrote the ZWave module originally is not with us anymore, and there's some new ZWave features we need implemented, and maybe we can get you guys some equipment if you're working on ZWave drivers.

Z-Wave is a protocol for wireless communication with home appliances e.g. Lamps and sensors. Z-Wave can be used for switching on, switching off, monitoring etc. It is possible to learn more about Z-Wave by reading one of the (in Danish) on this site. It is easy to get started with Z-Wave programming.

One important note here is that the specifications aren’t publicly available. The example in this article can be used for switching a lamp on or off. A Z-Wave USB stick from is required for running the example in this article. It can be bought. The driver makes the Z-Wave unit available as a seriel port for the operating system.

The serial port communication protocol is specified. Several other Z-Wave USB sticks utilize the same approach. Similar units from other manufacturers will most likely be compatible with the example in this article. The Aeon Labs Z-Wave USB stick is by the way the same unit as the one bundled with the master. A switch or dimmer unit is also needede.g. The Innovus SmartPower, but any switch unit will work.

A number of requirements needs to be fulfilled in order to be able to run the example from this article. Write (message, 0, message. Length ); sp. Close ( ); As the above example shows then it is relatively simple to get started with Z-Wave development in C#. Alternatives to making the implementation from scratch exist e.g.

The development platform from ‘ or the from. In the upcoming article about Z-Wave programming in C# the program will be modified in order to allow it to switch the unit on and then off.

The modified example will require some additional insights to the signalling at the serial port. The source code can be downloaded via this.

You are free to use the code in any manner you like. Install Oracle 10g Xe On Centos Version Check there.

Your Vera purchase includes a Z-Wave dongle, which must remain plugged into the back of Vera for her Z-Wave functions to work. You do not need to do anything for the dongle to work with Vera.

If you want to use the dongle separately from Vera, or purchased an extra dongle on its own, you will need the appropriate CP210x USB-RS232 drivers for your operating system. They are available here: 1. Download the Windows drivers for the Zwave Stick: 2.1. Download [b]VCP Driver Kit [/b] 2.3. If you don't have an unzip program (a program to extrac the zip archive) grab 7zip from here: 2.3.1.

Download [b]7-Zip 4.65 [/b] 2.4. Extract the CP210x_VCP_Win2K_XP_S2K3.zip archive and run CP210x_VCP_Win2K_XP_S2K3.exe 2.4.1. Install the Drivers. Plug the black Zwave dongle in your PC USB PORT Once the drivers are installed, the dongle should show up as a COM port or serial device.

Then any software designed to work with the Z-Wave serial API, such as ControlThink, HomeSeer, etc., should work fine. Windows users may need to edit the port settings and set them as follows: Bits per second: 115200 Data bits: 8 Parity: None Stop bits: 1 Flow Control: none To add devices to the dongle, tap the button so the blue light is blinking slowly. Then activate your nearby Z-Wave devices. To remove devices, press and hold the button until it blinks quickly, then activate your nearby Z-Wave devices. You can also add/remove devices while the dongle is attached to the PC's USB interface using your Z-Wave software's add/remove device function.

Use your Z-Wave software to replicate the Z-Wave network. Z-Wave Dongle Versions: • 2.40 = Zensys Firmware 4.27; • 2.48 = Zensys Firmware 5.02; • 2.60 = Zensys Firmware 5.02 Service Pack 2; • 2.78 = Zensys Firmware 5.02 Service Pack 3. You can determine the dongle version looking at the Version: line on the More Z-Wave Options page (Devices ->Z-Wave ->More Z-Wave Options).