LinuxMCE Forums

General => Developers => Topic started by: hari on January 24, 2008, 02:32:22 pm

Title: ZWave API
Post by: hari on January 24, 2008, 02:32:22 pm
Hi Devs,

I try to collect all the public available ZWave information out in the wild on a wiki page: http://wiki.linuxmce.org/index.php/ZWave_API
Some manuals hold information about node types, command and device classes. And there is sample code in the "HomeDaemon" project. Maybe we can pull enough information together to create an open api header file.

best regards,
Hari

Title: Re: ZWave API
Post by: cyr on January 26, 2008, 11:47:35 am
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...

Title: Re: ZWave API
Post by: hari on January 26, 2008, 12:13:54 pm
It couldn't have been written without access to information under NDA with Zensys right?
not without big reverse engineering.
Quote
Further more, some of the header files still have Zensys copyright notices...
that problem was identified a few days ago. The actual driver is now removed from the trunk until that issue is resolved. I did some scripting to get the used defines from our code. Without the Zensys headers there are at about 50 defines needed for the lmce ZWave driver to compile.

It would be great if you could add valuable _public available_/reverse engineered information to the wiki page.

best regards,
Hari
Title: Re: ZWave API
Post by: cyr on January 27, 2008, 01:53:29 pm
Well, I've thrown together a document with some of my sniffer logs and analysis of them.

http://area26.no-ip.org/linked/zw_analysis.rtf
Title: Re: ZWave API
Post by: 1audio on January 27, 2008, 04:34:24 pm
This document may give you insight into a lot of the ZWave API  http://www.leviton.com/OA_HTML/ibcGetAttachment.jsp?cItemId=iCJMZBqYpY17c3GhTCP72w&label=IBE&appName=IBE (http://www.leviton.com/OA_HTML/ibcGetAttachment.jsp?cItemId=iCJMZBqYpY17c3GhTCP72w&label=IBE&appName=IBE)
There are a few Leviton specific commands but most commands are supported by all ZWave products. There are some commands etc. not listed on the document but it should be enough to get started.
Title: Re: ZWave API
Post by: hari on January 27, 2008, 05:53:38 pm
Well, I've thrown together a document with some of my sniffer logs and analysis of them.

http://area26.no-ip.org/linked/zw_analysis.rtf


great work! congrats for your working interface software, too ;)

best regards,
Hari
Title: Re: ZWave API
Post by: hari on January 27, 2008, 05:57:42 pm
This document may give you insight into a lot of the ZWave API  http://www.leviton.com/OA_HTML/ibcGetAttachment.jsp?cItemId=iCJMZBqYpY17c3GhTCP72w&label=IBE&appName=IBE (http://www.leviton.com/OA_HTML/ibcGetAttachment.jsp?cItemId=iCJMZBqYpY17c3GhTCP72w&label=IBE&appName=IBE)
There are a few Leviton specific commands but most commands are supported by all ZWave products. There are some commands etc. not listed on the document but it should be enough to get started.
ty, have seen that already. Still missing hex values for many classes.

best regards,
Hari
Title: Re: ZWave API
Post by: 1audio on January 27, 2008, 06:36:52 pm
I'm pushing my contacts on getting more public info on ZWave. Its sometimes hard to get commercial interests to see the value in making some of the internals public.

This week I can go through the datasheets I have to see if there are any other useful nuggets hidden in them.
Title: Re: ZWave API
Post by: hari on January 27, 2008, 06:59:02 pm
I'm pushing my contacts on getting more public info on ZWave. Its sometimes hard to get commercial interests to see the value in making some of the internals public.

This week I can go through the datasheets I have to see if there are any other useful nuggets hidden in them.
that would be very helpful!

Best regards,
Hari
Title: Re: ZWave API
Post by: aaron.b on February 13, 2008, 06:37:36 pm
We're doing testing for the 0710 release and trying to be sure it works with the ACT ZCU101 (the pyramid shaped zwave usb) because this is the model currently sold, and the only zwave dongle in 0704 doesn't work.  I know some new kernel modules were added by Hari, I believe, and now the ZCU101 is detected, and gets a ttyUSB interface.  However the ZWave software still can't talk to it.  Has anybody had any success with it?
Title: Re: ZWave API
Post by: hari on February 13, 2008, 06:50:16 pm
We're doing testing for the 0710 release and trying to be sure it works with the ACT ZCU101 (the pyramid shaped zwave usb) because this is the model currently sold, and the only zwave dongle in 0704 doesn't work.  I know some new kernel modules were added by Hari, I believe, and now the ZCU101 is detected, and gets a ttyUSB interface.  However the ZWave software still can't talk to it.  Has anybody had any success with it?
cyr has successfully sent commands to the device with his own software and the new driver:
http://forum.linuxmce.org/index.php?topic=3665.msg23011#msg23011

could you provide me with the device log? Does it initialize? Where is your exact problem? At the download configuration command?

best regards,
Hari
Title: Re: ZWave API
Post by: aaron.b on February 13, 2008, 07:50:23 pm
>> 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

My logs show this (this has the new kernel module for ttyUSB, but uses the existing ZWave software)

35      02/13/08 7:09:48.826            ++++++++++++ ZWave is connected <0x2b66ed2f1b40>
36      02/13/08 7:09:48.826            ### Run Current Job  <0x41802950>
36      02/13/08 7:09:48.882            SerialConnection::send lock serial mutex <0x41802950>
35      02/13/08 7:09:48.882            SerialConnection::send len = 2 buf = 0x00 0x15  <0x41802950>
36      02/13/08 7:09:48.882            SerialConnection::send unlock serial mutex <0x41802950>
05      02/13/08 7:09:53.026            ### Go to timeout queue <0x41802950>
05      02/13/08 7:09:53.026            ### execute the next job from timeout queue <0x41802950>
05      02/13/08 7:09:53.026            ZWJobInitialize::timeoutHandler <0x41802950>
36      02/13/08 7:09:53.082            SerialConnection::send lock serial mutex <0x41802950>
35      02/13/08 7:09:53.082            SerialConnection::send len = 2 buf = 0x00 0x15  <0x41802950>
36      02/13/08 7:09:53.082            SerialConnection::send unlock serial mutex <0x41802950>
05      02/13/08 7:09:58.010            ### Go to timeout queue <0x41802950>
05      02/13/08 7:09:58.010            ### execute the next job from timeout queue <0x41802950>
05      02/13/08 7:09:58.010            ZWJobInitialize::timeoutHandler <0x41802950>
36      02/13/08 7:09:58.066            SerialConnection::send lock serial mutex <0x41802950>
35      02/13/08 7:09:58.066            SerialConnection::send len = 2 buf = 0x00 0x15  <0x41802950>
36      02/13/08 7:09:58.066            SerialConnection::send unlock serial mutex <0x41802950>
35      02/13/08 7:09:58.290            size too small 1 <0x41802950>

....  repeats ....
35      02/13/08 7:10:03.050            size too small 1 <0x41802950>
05      02/13/08 7:10:03.050            ### Go to timeout queue <0x41802950>
05      02/13/08 7:10:03.050            ### skip the next job from timeout queue <0x41802950>
35      02/13/08 7:10:03.050            ----- INIT ---- 1 <0x41802950>
35      02/13/08 7:10:03.050            ----- INIT ---- 2 <0x41802950>
35      02/13/08 7:10:03.050            -------- 3 <0x2b66ed2f1b40>
35      02/13/08 7:10:03.050            SerialConnection ------------- asa 1 <0x2b66ed2f1b40>
35      02/13/08 7:10:03.154            SerialConnection ------------- asa 2 <0x2b66ed2f1b40>
36      02/13/08 7:10:03.154            waiting for thread to finish <0x2b66ed2f1b40>
35      02/13/08 7:10:03.154            exit receiveFunction : nr. of reads 47 <0x41001950>
36      02/13/08 7:10:03.167            thread finished <0x2b66ed2f1b40>
35      02/13/08 7:10:03.167            SerialConnection ------------- asa 3 <0x2b66ed2f1b40>
35      02/13/08 7:10:03.167            SerialConnection ------------- asa 4 <0x2b66ed2f1b40>
35      02/13/08 7:10:03.167            -------- 4 <0x2b66ed2f1b40>
10      02/13/08 7:10:03.168            Socket::SendMessage type 5 id 37 from 63 to -1000 <0x2b66ed2f1b40>
10      02/13/08 7:10:03.196            TranslateSerialUSB found /sys/devices/pci0000:00/0000:00:04.0/usb2/2-1/2-1:1.0/ttyUSB1/ttyUSB1, returning /dev/ttyUSB1 <0x2b66ed2f1b40>
36      02/13/08 7:10:03.196            Using serial port: ttyUSB1. <0x2b66ed2f1b40>
36      02/13/08 7:10:03.207            SerialConnection::connect init serial mutex <0x2b66ed2f1b40>

Title: Re: ZWave API
Post by: hari on February 13, 2008, 08:21:33 pm
>> 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 ttyUSBX 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?
thats also my understanding. I did the same approach for the Seluxit Dongle. It also uses a new chip (>2.xx) and works perfect.

Quote
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.

Quote
My logs show this (this has the new kernel module for ttyUSB, but uses the existing ZWave software)

35      02/13/08 7:09:48.826            ++++++++++++ ZWave is connected <0x2b66ed2f1b40>
36      02/13/08 7:09:48.826            ### Run Current Job  <0x41802950>
36      02/13/08 7:09:48.882            SerialConnection::send lock serial mutex <0x41802950>
35      02/13/08 7:09:48.882            SerialConnection::send len = 2 buf = 0x00 0x15  <0x41802950>
36      02/13/08 7:09:48.882            SerialConnection::send unlock serial mutex <0x41802950>
05      02/13/08 7:09:53.026            ### Go to timeout queue <0x41802950>
05      02/13/08 7:09:53.026            ### execute the next job from timeout queue <0x41802950>
05      02/13/08 7:09:53.026            ZWJobInitialize::timeoutHandler <0x41802950>
36      02/13/08 7:09:53.082            SerialConnection::send lock serial mutex <0x41802950>
35      02/13/08 7:09:53.082            SerialConnection::send len = 2 buf = 0x00 0x15  <0x41802950>
36      02/13/08 7:09:53.082            SerialConnection::send unlock serial mutex <0x41802950>
05      02/13/08 7:09:58.010            ### Go to timeout queue <0x41802950>
05      02/13/08 7:09:58.010            ### execute the next job from timeout queue <0x41802950>
05      02/13/08 7:09:58.010            ZWJobInitialize::timeoutHandler <0x41802950>
36      02/13/08 7:09:58.066            SerialConnection::send lock serial mutex <0x41802950>
35      02/13/08 7:09:58.066            SerialConnection::send len = 2 buf = 0x00 0x15  <0x41802950>
36      02/13/08 7:09:58.066            SerialConnection::send unlock serial mutex <0x41802950>
35      02/13/08 7:09:58.290            size too small 1 <0x41802950>

....  repeats ....
35      02/13/08 7:10:03.050            size too small 1 <0x41802950>
05      02/13/08 7:10:03.050            ### Go to timeout queue <0x41802950>
05      02/13/08 7:10:03.050            ### skip the next job from timeout queue <0x41802950>
35      02/13/08 7:10:03.050            ----- INIT ---- 1 <0x41802950>
35      02/13/08 7:10:03.050            ----- INIT ---- 2 <0x41802950>
35      02/13/08 7:10:03.050            -------- 3 <0x2b66ed2f1b40>
35      02/13/08 7:10:03.050            SerialConnection ------------- asa 1 <0x2b66ed2f1b40>
35      02/13/08 7:10:03.154            SerialConnection ------------- asa 2 <0x2b66ed2f1b40>
36      02/13/08 7:10:03.154            waiting for thread to finish <0x2b66ed2f1b40>
35      02/13/08 7:10:03.154            exit receiveFunction : nr. of reads 47 <0x41001950>
36      02/13/08 7:10:03.167            thread finished <0x2b66ed2f1b40>
35      02/13/08 7:10:03.167            SerialConnection ------------- asa 3 <0x2b66ed2f1b40>
35      02/13/08 7:10:03.167            SerialConnection ------------- asa 4 <0x2b66ed2f1b40>
35      02/13/08 7:10:03.167            -------- 4 <0x2b66ed2f1b40>
10      02/13/08 7:10:03.168            Socket::SendMessage type 5 id 37 from 63 to -1000 <0x2b66ed2f1b40>
10      02/13/08 7:10:03.196            TranslateSerialUSB found /sys/devices/pci0000:00/0000:00:04.0/usb2/2-1/2-1:1.0/ttyUSB1/ttyUSB1, returning /dev/ttyUSB1 <0x2b66ed2f1b40>
36      02/13/08 7:10:03.196            Using serial port: ttyUSB1. <0x2b66ed2f1b40>
36      02/13/08 7:10:03.207            SerialConnection::connect init serial mutex <0x2b66ed2f1b40>



could you please try again with revision 1494 of the spcp8x5 driver?

best regards,
Hari
Title: Re: ZWave API
Post by: totallymaxed on February 13, 2008, 10:30:45 pm
We're doing testing for the 0710 release and trying to be sure it works with the ACT ZCU101 (the pyramid shaped zwave usb) because this is the model currently sold, and the only zwave dongle in 0704 doesn't work.  I know some new kernel modules were added by Hari, I believe, and now the ZCU101 is detected, and gets a ttyUSB interface.  However the ZWave software still can't talk to it.  Has anybody had any success with it?

Aaron thats the ZCU201

Andrew
Title: Re: ZWave API
Post by: totallymaxed on February 13, 2008, 10:33:03 pm
>> 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.


My logs show this (this has the new kernel module for ttyUSB, but uses the existing ZWave software)

35      02/13/08 7:09:48.826            ++++++++++++ ZWave is connected <0x2b66ed2f1b40>
36      02/13/08 7:09:48.826            ### Run Current Job  <0x41802950>
36      02/13/08 7:09:48.882            SerialConnection::send lock serial mutex <0x41802950>
35      02/13/08 7:09:48.882            SerialConnection::send len = 2 buf = 0x00 0x15  <0x41802950>
36      02/13/08 7:09:48.882            SerialConnection::send unlock serial mutex <0x41802950>
05      02/13/08 7:09:53.026            ### Go to timeout queue <0x41802950>
05      02/13/08 7:09:53.026            ### execute the next job from timeout queue <0x41802950>
05      02/13/08 7:09:53.026            ZWJobInitialize::timeoutHandler <0x41802950>
36      02/13/08 7:09:53.082            SerialConnection::send lock serial mutex <0x41802950>
35      02/13/08 7:09:53.082            SerialConnection::send len = 2 buf = 0x00 0x15  <0x41802950>
36      02/13/08 7:09:53.082            SerialConnection::send unlock serial mutex <0x41802950>
05      02/13/08 7:09:58.010            ### Go to timeout queue <0x41802950>
05      02/13/08 7:09:58.010            ### execute the next job from timeout queue <0x41802950>
05      02/13/08 7:09:58.010            ZWJobInitialize::timeoutHandler <0x41802950>
36      02/13/08 7:09:58.066            SerialConnection::send lock serial mutex <0x41802950>
35      02/13/08 7:09:58.066            SerialConnection::send len = 2 buf = 0x00 0x15  <0x41802950>
36      02/13/08 7:09:58.066            SerialConnection::send unlock serial mutex <0x41802950>
35      02/13/08 7:09:58.290            size too small 1 <0x41802950>

....  repeats ....
35      02/13/08 7:10:03.050            size too small 1 <0x41802950>
05      02/13/08 7:10:03.050            ### Go to timeout queue <0x41802950>
05      02/13/08 7:10:03.050            ### skip the next job from timeout queue <0x41802950>
35      02/13/08 7:10:03.050            ----- INIT ---- 1 <0x41802950>
35      02/13/08 7:10:03.050            ----- INIT ---- 2 <0x41802950>
35      02/13/08 7:10:03.050            -------- 3 <0x2b66ed2f1b40>
35      02/13/08 7:10:03.050            SerialConnection ------------- asa 1 <0x2b66ed2f1b40>
35      02/13/08 7:10:03.154            SerialConnection ------------- asa 2 <0x2b66ed2f1b40>
36      02/13/08 7:10:03.154            waiting for thread to finish <0x2b66ed2f1b40>
35      02/13/08 7:10:03.154            exit receiveFunction : nr. of reads 47 <0x41001950>
36      02/13/08 7:10:03.167            thread finished <0x2b66ed2f1b40>
35      02/13/08 7:10:03.167            SerialConnection ------------- asa 3 <0x2b66ed2f1b40>
35      02/13/08 7:10:03.167            SerialConnection ------------- asa 4 <0x2b66ed2f1b40>
35      02/13/08 7:10:03.167            -------- 4 <0x2b66ed2f1b40>
10      02/13/08 7:10:03.168            Socket::SendMessage type 5 id 37 from 63 to -1000 <0x2b66ed2f1b40>
10      02/13/08 7:10:03.196            TranslateSerialUSB found /sys/devices/pci0000:00/0000:00:04.0/usb2/2-1/2-1:1.0/ttyUSB1/ttyUSB1, returning /dev/ttyUSB1 <0x2b66ed2f1b40>
36      02/13/08 7:10:03.196            Using serial port: ttyUSB1. <0x2b66ed2f1b40>
36      02/13/08 7:10:03.207            SerialConnection::connect init serial mutex <0x2b66ed2f1b40>



Hi Aaron,

We have already committed to providing Hari with a ZCU201 if this helps.

Andrew
Title: Re: ZWave API
Post by: hari on February 13, 2008, 10:42:09 pm
Aaron thats the ZCU201
aaron refers to the us version. It's the ZCU101.

best regards,
Hari
Title: Re: ZWave API
Post by: hari on February 13, 2008, 10:43:56 pm
We have already committed to providing Hari with a ZCU201 if this helps.
yes that would help as I don't have access to the device atm.

best regards,
Hari
Title: Re: ZWave API
Post by: totallymaxed on February 13, 2008, 10:53:27 pm
Aaron thats the ZCU201
aaron refers to the us version. It's the ZCU101.

best regards,
Hari

Yep your right! ;-)
Title: Re: ZWave API
Post by: caiman on April 02, 2008, 06:13:51 pm
I've read in some thread that Seluxit was thinking of building a wrapper around the zensys code in order to expose a clear and open API. Do you guys know more about the status ?

It would be really nice to use this to query some infos from the modules, like routing table and signal strength, and build a tool like Z-Seer, which unfortunately only works with their controller -> US only.
http://store.homeseer.com/store/Z-Seer-Diagnostics-Software-for-Z-Wave-P235C68.aspx (http://store.homeseer.com/store/Z-Seer-Diagnostics-Software-for-Z-Wave-P235C68.aspx)

Sam
Title: Re: ZWave API
Post by: nite_man on April 02, 2008, 08:22:39 pm
It'd be great! But think ZigBee is better. It uses open protocol.
Title: Re: ZWave API
Post by: totallymaxed on April 02, 2008, 08:55:44 pm
It'd be great! But think ZigBee is better. It uses open protocol.

We have a discussion going on about this with Zensys... no promises at all but this whole area is under discussion.

Andrew
Title: Re: ZWave API
Post by: hari on April 02, 2008, 09:21:19 pm
It'd be great! But think ZigBee is better. It uses open protocol.
the open protocol is a very important factor. But the lower frequency of Z-Wave is better for building penetration and you can buy many products now. I'm still waiting to see ZigBee HA-Devices.

I'm awaiting more devices at the moment (thanks to the support from Seluxit, Danfoss and Pluto) and try to use the available Z-Wave information with the existing code to get an overview of the protocol. There are many documents that leak information about class names/numbers and such. The article "riding on the Zwave" even shows frame specifications. If that information and a bit of probing is not sufficient we could usb snoop the homeseer stuff. But i wonder if it uses some modified firmware or monitor mode. Time will tell..

best regards,
Hari
Title: Re: ZWave API
Post by: 1audio on April 03, 2008, 07:38:45 am
ZigBee is an open standard thats not very standard. Control4 uses it. So does Crestron. And their products do not interoperate. And neither have the in depth background or experience in lighting that Leviton, Cooper and even Intermatic have. Outside of the US the story will be different but ZigBee is still a ways off for product we can use.

There is a lot of leaked info on ZWave. Also all BUT the Leviton serial module will talk the same codes from my experience testing on Windows. There are some proprietary codes but most are common to all devices in a device class. Unfortunately some of the device classes have been majorly revised in the last two years, and the newest stuff runs much faster over the network.
Title: Re: ZWave API
Post by: hari on April 03, 2008, 08:23:31 am
ZigBee is an open standard thats not very standard. Control4 uses it. So does Crestron. And their products do not interoperate. And neither have the in depth background or experience in lighting that Leviton, Cooper and even Intermatic have. Outside of the US the story will be different but ZigBee is still a ways off for product we can use.
i totally agree. ZigBee misses some class/command definitions for HA like ZWave..

Quote
There is a lot of leaked info on ZWave. Also all BUT the Leviton serial module will talk the same codes from my experience testing on Windows. There are some proprietary codes but most are common to all devices in a device class. Unfortunately some of the device classes have been majorly revised in the last two years, and the newest stuff runs much faster over the network.
I'm really happy with the speed of the 40kbit ZWave.

best regards,
Hari
Title: Re: ZWave API
Post by: caiman on April 06, 2008, 11:47:53 am
OMG...

When receiving network info at initialization time, the pluto driver inspects a bitmap of 4 bytes -> 32 possible possible devices. But Zwave should support up to 232 nodes. Maybe I am misreading something ?

And it could indeed be that my problems http://mantis.linuxmce.org/view.php?id=3614 (http://mantis.linuxmce.org/view.php?id=3614) of zwave devices being dropped started when I reached node ID 33 in my network.

Code: [Select]
                        for(int i = 5; i < 9; i++)        // that's only 4 bytes !
                        {
                                for(int j = 0; j < 8; j++)
                                {
                                        node_index++;

                                        if( (1 << j) & buffer[i])
                                        {
                                                handler()->insertNode(new ZWaveNode(handler()->homeID(), node_index));
                                        }
                                }
                        }

Another interesting thing I have noticed by decoding the received buffer is that some nodes are reported that do not exist physically.

Code: [Select]
35      04/06/08 11:01:00.510           ZWJobGetNodeProtocolInfo len = 8 buf = 0x01 0x41 0xc9 0x0c 0x00 0x04 0x10 0x00  <0xb6993b90> 04/06/08 11:01:00.510           Node[5] : BType = 0x02 GType = 0x02 SType = 0x00 Level = -1 <0xb6993b90>
36      04/06/08 11:01:00.510           Node[7] : BType = 0x02 GType = 0x02 SType = 0x00 Level = -1 <0xb6993b90>
36      04/06/08 11:01:00.510           Node[9] : BType = 0x03 GType = 0x11 SType = 0x00 Level = -1 <0xb6993b90>
36      04/06/08 11:01:00.510           Node[10] : BType = 0x03 GType = 0x10 SType = 0x00 Level = -1 <0xb6993b90>
36      04/06/08 11:01:00.510           Node[11] : BType = 0x03 GType = 0x10 SType = 0x00 Level = -1 <0xb6993b90>
36      04/06/08 11:01:00.510           Node[12] : BType = 0x03 GType = 0x10 SType = 0x00 Level = -1 <0xb6993b90>
36      04/06/08 11:01:00.510           Node[13] : BType = 0x02 GType = 0x02 SType = 0x00 Level = -1 <0xb6993b90>
36      04/06/08 11:01:00.510           Node[15] : BType = 0x02 GType = 0x02 SType = 0x00 Level = -1 <0xb6993b90>
36      04/06/08 11:01:00.510           Node[16] : BType = 0x03 GType = 0x11 SType = 0x00 Level = -1 <0xb6993b90>
36      04/06/08 11:01:00.510           Node[17] : BType = 0x02 GType = 0x02 SType = 0x00 Level = -1 <0xb6993b90>
36      04/06/08 11:01:00.510           Node[19] : BType = 0x02 GType = 0x02 SType = 0x00 Level = -1 <0xb6993b90>
36      04/06/08 11:01:00.510           Node[20] : BType = 0x02 GType = 0x02 SType = 0x00 Level = -1 <0xb6993b90>
36      04/06/08 11:01:00.510           Node[21] : BType = 0x02 GType = 0x02 SType = 0x00 Level = -1 <0xb6993b90>
36      04/06/08 11:01:00.510           Node[22] : BType = 0x04 GType = 0x10 SType = 0x00 Level = -1 <0xb6993b90>
36      04/06/08 11:01:00.510           Node[23] : BType = 0x04 GType = 0x12 SType = 0x00 Level = -1 <0xb6993b90>
36      04/06/08 11:01:00.510           Node[24] : BType = 0x02 GType = 0x02 SType = 0x00 Level = -1 <0xb6993b90>
36      04/06/08 11:01:00.511           Node[25] : BType = 0x04 GType = 0x11 SType = 0x00 Level = -1 <0xb6993b90>
36      04/06/08 11:01:00.511           Node[26] : BType = 0x04 GType = 0x10 SType = 0x00 Level = -1 <0xb6993b90>
36      04/06/08 11:01:00.511           Node[27] : BType = 0x02 GType = 0x02 SType = 0x00 Level = -1 <0xb6993b90>
36      04/06/08 11:01:00.511           Node[28] : BType = 0x02 GType = 0x02 SType = 0x00 Level = -1 <0xb6993b90>
36      04/06/08 11:01:00.511           Node[29] : BType = 0x04 GType = 0x11 SType = 0x00 Level = -1 <0xb6993b90>
36      04/06/08 11:01:00.511           Node[30] : BType = 0x04 GType = 0x10 SType = 0x00 Level = -1 <0xb6993b90>
36      04/06/08 11:01:00.511           Node[31] : BType = 0x04 GType = 0x20 SType = 0x00 Level = -1 <0xb6993b90>
36      04/06/08 11:01:00.511           Node[32] : BType = 0x00 GType = 0x00 SType = 0x00 Level = -1 <0xb6993b90>

but I only have physical nodes 9-12,16,22,25-26,29-33 on top of the remote controller and ZCU010.
Title: Re: ZWave API
Post by: hari on April 06, 2008, 03:42:24 pm
can you send me the complete log with levels 36,40,41?

best regards,
Hari
Title: Re: ZWave API
Post by: hari on April 06, 2008, 04:07:52 pm
at line 57 MAGIC_LEN is verified. Thats defined to 29. 29 * 8 = 232.

from http://www.z-wave.com/modules/xoopsfaq/index.php?cat_id=2#q26:
"A single Z-Wave network can include 232 nodes."

Coincidence? Maybe not.
please try to change "i < 9" to "i < 34".

best regards,
Hari

ps: I wish I had more Z-Wave devices for further tests. Anybody wants to buy some PLCBUS stuff?
Title: Re: ZWave API
Post by: caiman on April 06, 2008, 04:57:06 pm
Hari: good catch. It gets better.

To my knowledge, the highest device ID on my network is 33 (A PIR sensor)

Without the modification (i<9) I get  http://www.k-net.eu.org/lmce/zwave-log-i9.txt.gz (http://www.k-net.eu.org/lmce/zwave-log-i9.txt.gz)
The discovery stops at ID=32.
Still, it finds a lot of devices that don't exist.

Increasing to (i<34) I get http://www.k-net.eu.org/lmce/zwave-log-i34.txt.gz (http://www.k-net.eu.org/lmce/zwave-log-i34.txt.gz)
It finds two new devices: the PIR with ID 33  :D but also a device 37  of type 38 (light switch dimmable). The fact that the type detected is a correct one makes me believe that it is correct, but I have no idea where that device is coming from. Hey that's maybe the way for you to get new devices at no cost :-)

Sam
Title: Re: ZWave API
Post by: 1audio on April 06, 2008, 05:12:38 pm
Can you provide more details about your ZWave stuff? USB controller, primary controller and whose devices? If you get the ZTool software it will read back what your usb controller reports. I have only 17 lights but more than 28 slots taken. The ZWave protocol does not reuse device ID's (without some specific efforts) so when you delete a device the number is still taken. Also controllers don't show up on the LMCE side.
Title: Re: ZWave API
Post by: caiman on April 06, 2008, 06:06:50 pm
Hi 1audio,

Code: [Select]
9                       38              Light_Switch_dimmable
10                      37              Light_Switch_onoff
11                      37              Light_Switch_onoff
12                      37              Light_Switch_onoff
16                      38              Light_Switch_dimmable
22                      37              Light_Switch_onoff
25                      38              Light_Switch_dimmable
26                      37              Light_Switch_onoff
29                      38              Light_Switch_dimmable
30                      37              Light_Switch_onoff
31                      1813            Generic_Sensor
32                      37              Light_Switch_onoff
33                      1813            Generic_Sensor
37                      38              Light_Switch_dimmable

the main controller is ZTH200 and usb device is ZCU010. Hari and I believe unit 37 is the ZCU010, when got a new ID after I have sent a "Reset" command to it.

With the modification above, I have reloaded router a couple of time and even rebooted the core, it seems devices are not disappearing any more. Time will tell, I'll report back later on.

Sam
Title: Re: ZWave API
Post by: 1audio on April 07, 2008, 03:02:56 am
You have a Homepro Primary controller. I have used it myself and its OK. It uses a pretty early version of the ZWave library and may not support some of the newer devices correctly. I also found it was not real good with setting up routing. But it should not be a roadblock to success. Tyhe controllers do not show up on the LMCE side for some reason. They should be identified as controllers if they do come across.
You can download a trial of ZTool here http://www.homeseer.com/products/software/Z-Tool.htm (http://www.homeseer.com/products/software/Z-Tool.htm) and it will tell you what is in the USB stick. It will work with the EU stuff. And it should support all of the latest stuff.
Title: Re: ZWave API
Post by: caiman on April 07, 2008, 02:31:17 pm
Thanks 1audio. I have installed Z-tool and will try tonight.

I have filed a mantis for the limitation to 32 Zwave ID, and the associated code fix.
http://mantis.linuxmce.org/view.php?id=4154

I hope the seluxit dongle I have ordered will offer more debugging functionality. Anyone knows about the software that comes with it ? Can it be used as a master controller, or SUC ?

Sam
Title: Re: ZWave API
Post by: hari on April 07, 2008, 09:09:46 pm
all controllers i know of have the same zensys chip in there (differing only in hw and sw revisions)

best regards,
Hari
Title: Re: ZWave API
Post by: totallymaxed on April 13, 2008, 12:06:13 pm
Thanks 1audio. I have installed Z-tool and will try tonight.

I have filed a mantis for the limitation to 32 Zwave ID, and the associated code fix.
http://mantis.linuxmce.org/view.php?id=4154

I hope the seluxit dongle I have ordered will offer more debugging functionality. Anyone knows about the software that comes with it ? Can it be used as a master controller, or SUC ?

Sam


The software for the Seluxit Home Controller is Windows XP based. I think the hardware can be config'd as a MC or a SUC... but Hari may well be able to answer that for sure.
Title: Re: ZWave API
Post by: 1audio on April 13, 2008, 09:45:42 pm
There are three revisions of the ZWave chip and 5 or 6 major revisions to the firmware. If the controller libraries are installed in the chip at manufacturing (this changes depending on whether the chip is in a light switch, door lock, controller etc.) then the chip will support the controller functions. A handheld controller has different functions that a "static" controller. This has to do with the routing tables. A handheld cannot count on routing since its moving. A static controller can support a routing table fully. All of the recent controller libraries have those functions. All of the computer interface controllers seem to give full access to the basic library, except the Leviton serial controller.

Hari is doing great work on fixing the ZWave stuff.
Title: Re: ZWave API
Post by: hari on July 13, 2008, 09:17:15 pm
Hi devs,

I've made some proof of concept code available: http://svn.linuxmce.org/pluto/branches/charon-merge/src/ZWave/

It's still dirty in many places and I have still to figure out some Z-Wave details, but this is what's working for now:

* Light control (binary, dimmable)
* Floorplan feedback from local operations and from ALL ON/OFF commands
* Lighting wizard integration
* Busy handling for newer chips
* PIR support in alarm and sensor mode
* Binary sensor support
* Basic wake-up handling (queue is still missing)

What's coming soon:
* Download configuration
* Multi command handling
* RA-plus-w setback schedule thermostat support
* Merten Dongle support
* Multilevel sensor support


best regards,
Hari
Title: Re: ZWave API
Post by: caiman on July 24, 2008, 01:24:57 pm
Hi Hari,

I just wanted to confirm that after about one week of using your new ZWave code (rev 21253), I confirm it is working great!

What works great:
- PIR sensor
- normal control of switches and dimmers (I use ACT homepro)
- update on the floorplan when using "all on" or "all off" on the zwave remote

Having the possibility to poll the status of the devices on request or on a regular basis would be extremely useful, so we could get floorplan updates also when individual devices are switched on/off locally. As you suggested, the driver could generate an event to notify DCE about the status of the device polled. Even if there's a delay it's not a big deal. It would allow the floorplan to show accurate status most of the time.

For those who want to test it, you need to have a small wrapper for the ZWave binary to force it to use the freshly compiled libraries, or it will segfault

Code: [Select]
~$ cat /usr/pluto/bin/ZWave
#!/bin/bash
export LD_LIBRARY_PATH=/home/me/src/lmce-source/charon-merge/src/lib
/usr/pluto/bin/ZWave.hari $@


Once again Hari, THANK YOU for this great piece of work !
Sam
Title: Re: ZWave API
Post by: hari on July 24, 2008, 02:41:51 pm
I just wanted to confirm that after about one week of using your new ZWave code (rev 21253), I confirm it is working great!
that is great to hear..

could you trigger that bug from the old driver where your devices got out of order and disappeared? It never happened for me with the original pluto driver..

Quote
What works great:
- PIR sensor
- normal control of switches and dimmers (I use ACT homepro)
- update on the floorplan when using "all on" or "all off" on the zwave remote

Having the possibility to poll the status of the devices on request or on a regular basis would be extremely useful, so we could get floorplan updates also when individual devices are switched on/off locally. As you suggested, the driver could generate an event to notify DCE about the status of the device polled. Even if there's a delay it's not a big deal. It would allow the floorplan to show accurate status most of the time.
that is in the works.

Quote
Once again Hari, THANK YOU for this great piece of work !

you are welcome!

best regards,
Hari
Title: Re: ZWave API
Post by: caiman on July 25, 2008, 10:52:41 am
could you trigger that bug from the old driver where your devices got out of order and disappeared? It never happened for me with the original pluto driver..

I have reloaded the router a couple of times, and rebooted the core, and the last two devices did not get a new plutoID assigned, they kept the same. So it seems to be fixed  :)
Now as soon as the "download configuration" feature is available, I will test it and see if this still stands.

Sam
Title: Re: ZWave API
Post by: hari on July 26, 2008, 05:23:25 pm
Now as soon as the "download configuration" feature is available, I will test it and see if this still stands.
commited to rev 21258. Works for me, but I did only limited testing. Please report if it is fine for you.

best regards,
Hari
Title: Re: ZWave API
Post by: caiman on July 30, 2008, 09:11:43 pm
Hari,

the download configuration functionality seems to be working great. It took some time (about 30 sec) between the moment the primary controller said "sent successfully" and the moment when the ZWave driver showed any logs, but they were all there.
Btw the logs are nice, you can get a good idea of what's going on behind the scenes.

I had one of the switches that stopped responding for a while (it would work once or twice after router reload, then stop responding) but now it started working again so I'm not sure what happened. All seems ok now.

Great work!
Sam
Title: Re: ZWave API
Post by: hari on July 30, 2008, 10:08:00 pm
the download configuration functionality seems to be working great. It took some time (about 30 sec) between the moment the primary controller said "sent successfully" and the moment when the ZWave driver showed any logs, but they were all there.

Btw the logs are nice, you can get a good idea of what's going on behind the scenes.
it just enables the replication mode for 60 seconds. I need a more advanced timer that gets extended when we receive stuff. And it would be a good idea to postpone other operations until we are done.

There are three loglevels, LV_ZWAVE, LV_RECEIVE_DATA and LV_SEND_DATA. You can adjust the LogLevels value (36,40,41) in /etc/pluto.conf.

Quote
I had one of the switches that stopped responding for a while (it would work once or twice after router reload, then stop responding) but now it started working again so I'm not sure what happened. All seems ok now.
hu? do you have a log for that?

Quote
Great work!
hehe, it still is a bit of a hack for now :-)

best regards,
Hari
Title: Re: ZWave API
Post by: hari on August 01, 2008, 05:56:39 pm
short update:
Playing with LMCE being the primary controller and SIS mode (Node id server). I already can add slave devices and controllers to the network with the dongle. Ideally all remote controllers should work as inclusion controllers in this scenario. Sadly enough the ZTH100/200 does not seem to support the inclusion controller mode and only is working as secondary controller for now (Zaerc suggested a long usb extension cord to be able to add all my devices :-) )

I'm trying to get hold of a Tricklestar remote, they state SIS support on the page and it uses newer library versions. And it should be available in Europe (868Mhz)

The SIS mode seems to be the best choice for a Z-Wave network. Some devices like the RA-Plus-W only work in a network with SIS. And we get the node information frame at the time of inclusion, so we can catch battery powered devices that don't send out a broadcast wake up event.

best regards,
Hari
Title: Re: ZWave API
Post by: thoweiss on August 04, 2008, 01:10:33 pm
Doe's anybody tried the http://www.tricklestar.eu/html/s02_article/article_view.asp?art_id=133&nav_cat_id=128&nav_top_id=56 (http://www.tricklestar.eu/html/s02_article/article_view.asp?art_id=133&nav_cat_id=128&nav_top_id=56) with lmce?

The datasheet looks good for me it supports the Zwave Serial API.

Maybe it will be an alternative Z-Wave controller.

Btw, does anybody now where to buy tricklestar devices in Germany?

Regards,

Thorsten.
Title: Re: ZWave API
Post by: hari on August 04, 2008, 01:13:48 pm
I will receive a usb dongle and the remote in about two weeks. I'll keep you posted on the details.

best regards,
Hari
Title: Re: ZWave API
Post by: Domodude on August 04, 2008, 04:00:20 pm
I will receive a usb dongle and the remote in about two weeks. I'll keep you posted on the details.

Excellent! Great work, it seems everytime I log in there is good news from the Zwave department  8)
I am happy that Z-wave is catching on so well in Europe, with new products added frequently. Hopefully that will also do good things with the pricing level of most z-wave devices at this moment.
Mark
Title: Re: ZWave API
Post by: totallymaxed on August 14, 2008, 01:27:32 am
Hi devs,

I've made some proof of concept code available: http://svn.linuxmce.org/pluto/branches/charon-merge/src/ZWave/

It's still dirty in many places and I have still to figure out some Z-Wave details, but this is what's working for now:

* Light control (binary, dimmable)
* Floorplan feedback from local operations and from ALL ON/OFF commands
* Lighting wizard integration
* Busy handling for newer chips
* PIR support in alarm and sensor mode
* Binary sensor support
* Basic wake-up handling (queue is still missing)

What's coming soon:
* Download configuration
* Multi command handling
* RA-plus-w setback schedule thermostat support
* Merten Dongle support
* Multilevel sensor support


best regards,
Hari


Hi Hari,

We tested grabbed the current code in the svn this afternoon and built/installed it. As far as we can tell so far... we cant tell the difference between your new code and the RC2 z-wave binary... which is very nice indeed!

We have tested 'All on' and 'All off' from the ACT remote and the state change for all devices was correctly reflected in the DB and on the floorplan... also very nice :-)

We have some ACT wall switches that we use to control the state of other load controlling z-wave modules. If we use these wall switches to change the state of the controlled load controlling z-wave modules we do not see this change reflected in the DB or the floorplan. Is there some specific way we need to pair the wall switches to the load baring modules or is it just the case that currently this capability is not implemented?

In terms of the unimplemented features listed above in your post from the 13 July can you update us on what is now working?

Great work by the way...we have 10 devices in our test z-wave network (all lights currently...will try an ACT PIR tomorrow) and the performance excellent and stability was 100% :-)

All the best

Andrew
Title: Re: ZWave API
Post by: hari on August 14, 2008, 11:21:49 am
We tested grabbed the current code in the svn this afternoon and built/installed it. As far as we can tell so far... we cant tell the difference between your new code and the RC2 z-wave binary... which is very nice indeed!

Yeah, the drop in replacement capability is one of my requirements :-)

Quote
We have some ACT wall switches that we use to control the state of other load controlling z-wave modules. If we use these wall switches to change the state of the controlled load controlling z-wave modules we do not see this change reflected in the DB or the floorplan. Is there some specific way we need to pair the wall switches to the load baring modules or is it just the case that currently this capability is not implemented?

The older plugs from ACT supported associations in group 1 for that. The newer ones don't support that. But they send an unsolicited node information frame _sometimes_ when operated locally. If the dongle receives that it queries the level and state from the device. I'm still investigating why they don't send it all the time.

After spending a bit on the homeseer and other forums, it depends on the switch type if they work "bidi". It is not a protocol issue. The vendor has to send a node information or support associations to allow bidi.

Quote
In terms of the unimplemented features listed above in your post from the 13 July can you update us on what is now working?

* Basic wake-up handling (queue is still missing)

- queue is implemented: if you send a command to a sleeping device (like a PIR), it is queued until the device sends a wake-up notification. The commands are then moved to the send queue, and it sends a wake-up-no-more-information as last command to make the device fall asleep again.

There is one problem with that at the moment, the Z-Wave spec is a bit problematic: there can be sleeping devices that have the "listening" bit set in the node-protocol-info response. So we don't know which are sleeping devices until we get a wake-up notification from a device.

* Download configuration

- implemented. For now it has a hard-coded 60s time slot where the controller replication is enabled. It works best if you start the replication on the primary remote first, and then send the download config command to lmce.

* Multi command handling

- basic bits are there for the ra-plus-w. But there is another challenge. If there are more than one commands on the wake-up queue for a device, they should be concatenated into a single multi command.

* RA-plus-w setback schedule thermostat support

- talking to the device works. I'm just thinking about some final implementation decisions. It will only work in SIS mode. If we are not the primary or SIS we don't see the specific type when fetching device info from the chip. So there is no way to know it is a setback schedule thermostat (that needs multi-command and wake-up settings). This is no real problem as SIS will be supported soon and this is the recommended mode from danfoss. Should work ootb with automatic configuration in a week or two.

* Merten Dongle support

- I must know which usb/rs232 chipset is in there. My best guess was some ezusb stuff. But trying to load usbserial or the ftdi driver with the proper usb ids did not work (the usbserial created 6 ttyusb devices, all not working :-)

* Multilevel sensor support

- I'm awaiting a test sample from Seluxit. This should be a quick one.

* new stuff not listed in the old post:

- Primary mode with AddNodeToNetwork and RemoveNodeFromNetwork implementation. You can also add a ZTH (or other controller) as secondary. Run the AddNode command and do a replication in receive mode on the ZTH. I do not transfer any group information atm (was thinking about automatically grouping lights by rooms), but it is included and you can set up groups on the remote manually.
There is also a new "high power" mode (reported in the homeseer forum), where you don't have to be close to the devices when adding them (in direct reach, of course no routing). That would be nice for small homes as you don't need a remote. Unfortunately only brand new devices from some manufacturers support it and I have no information about that mode, so this is postponed at the moment. Without that mode and a static controller (and all "regular" [read: non-ztrollers whatever] usb dongles are static controllers) the primary mode has limited usage as you can't test-bench z-wave and the distances are too high in a regular flat for low power adding :-)

- SIS (node id server) mode with inclusion controllers. Code is there. Sadly enough the ACT ZTH remotes don't support "inclusion mode" as their library version is too old. They work as secondary remotes in SIS mode. I'm awaiting a Tricklestar remote with a brand new chipset. That should work as inclusion controller. No need to do download configuration any more in that mode. And we have the best possibilities to automatically configure the devices at inclusion, as we get the complete node information frame and the device is awake (if battery powered).

- Implemented proper callback handling. If we don't get confirmation on zw-send (from the device itself, not the z-wave stack on the dongle), it times out after 3 seconds and tries three retries to prevent stalling. Needs a bit of fixing (for other commands than zw-send), but works great for a first try.


Quote
Great work by the way...we have 10 devices in our test z-wave network (all lights currently...will try an ACT PIR tomorrow) and the performance excellent and stability was 100% :-)

I've sent over 20 thousand commands with the new driver. I'm sure there are still bugs and some bits need to be cleaned up. But for a first try it behaves pretty stable. Be aware, only the wake-up interval of the PIR gets configured automatically. You have to do the mode setting manually (both work, sensor and binary).

best regards,
Hari
Title: Re: ZWave API
Post by: totallymaxed on August 14, 2008, 03:33:43 pm
Quote
We have some ACT wall switches that we use to control the state of other load controlling z-wave modules. If we use these wall switches to change the state of the controlled load controlling z-wave modules we do not see this change reflected in the DB or the floorplan. Is there some specific way we need to pair the wall switches to the load baring modules or is it just the case that currently this capability is not implemented?

The older plugs from ACT supported associations in group 1 for that. The newer ones don't support that. But they send an unsolicited node information frame _sometimes_ when operated locally. If the dongle receives that it queries the level and state from the device. I'm still investigating why they don't send it all the time.

After spending a bit on the homeseer and other forums, it depends on the switch type if they work "bidi". It is not a protocol issue. The vendor has to send a node information or support associations to allow bidi.

Ok some further feedback on the above issue;

After resetting the Seluxit Home Controller from Wen Admin and then downloading the device data again from the ACT remote (using your code this time... before the data was from the original RC2 binary)

We have now confirmed that if we use the button on the remote ACT slaved modules to change the state of the module this is dynamically displayed in the floor plan... :-)

But the paired wall switches do not get their state updated... for the reasons you have already explained.

Howeve we can now use the floorplan to control a ACT direct load switch successfully... :-) However if we use the waal switch to change the state this does not get reflected on the floorplan strangely. Still this is nice progress!

More later after some more testing.

All the best

Andrew
Title: Re: ZWave API
Post by: totallymaxed on August 14, 2008, 03:59:50 pm
Hari,

looking in the logs we see the following when we press 'off' on the ACT direct load wall switch;

Code: [Select]
41 08/14/08 14:47:26.911 0x1 0x14 0x0 0x49 0x84 0xf 0xe 0x4 0x10 0x1 0x25 0x27 0x85 0x73 0x70 0x86 0x72 0xef 0x20 0x26 0x50 0xfb (###I######33p#r# &P#) <0xb78dab90>
36 08/14/08 14:47:26.911 FUNC_ID_ZW_APPLICATION_UPDATE:UPDATE_STATE_NODE_INFO_RECEIVED received from node 15 - <0xb78dab90>

...and we see the following when we press 'on';

Code: [Select]
41 08/14/08 14:48:51.478 0x1 0x14 0x0 0x49 0x84 0xf 0xe 0x4 0x10 0x1 0x25 0x27 0x85 0x73 0x70 0x86 0x72 0xef 0x20 0x26 0x50 0xfb (###I######33p#r# &P#) <0xb78dab90>
36 08/14/08 14:48:51.478 FUNC_ID_ZW_APPLICATION_UPDATE:UPDATE_STATE_NODE_INFO_RECEIVED received from node 15 - <0xb78dab90>

But in each case the floorplan object does not get updated (if we control it from the floor plan then the Wall switch updates correctly).

So it looks to us like the Seluxit is getting data back from the Wall switch but its not getting handled correctly in some fashion.

Whats your view?

Andrew
Title: Re: ZWave API
Post by: hari on August 15, 2008, 01:08:46 am
oh, i should handle this :-) Will look at that. Can you mail me your complete log (or the init section with the device list)?

best regards,
Hari
Title: Re: ZWave API
Post by: hari on August 15, 2008, 01:39:50 am
Whats your view?

My bad, my code only handled basic type slaves (this is a routing slave). Fix is committed to revision 21346.

best regards,
Hari

Title: Re: ZWave API
Post by: totallymaxed on August 15, 2008, 01:09:49 pm
Whats your view?

My bad, my code only handled basic type slaves (this is a routing slave). Fix is committed to revision 21346.

best regards,
Hari



Hari we just downloaded that latest revision and built it here and the fix for the direct load wall switches work great!!!! Takes about 6-7 secs for the state of the wall switch to be reflected on the floorplan.

Cool work!

Now we are testing the wall switches that are not controlling a direct load but are paired to control other plug in dimmer modules. When we use the paired wall switch the light responds correctly but the floor plan does not update still. When we look in the logs it appears that a command class is not implemented currently...

I have attached the ZWave.log to a separate email as attachments dont seem to be working here in the forum for me at present (the last entries in the log refer to the paired switches controlling a remote plugin module by the way).

Great work by the way.

Andrew
Title: Re: ZWave API
Post by: hari on August 15, 2008, 06:19:22 pm
Hari we just downloaded that latest revision and built it here and the fix for the direct load wall switches work great!!!! Takes about 6-7 secs for the state of the wall switch to be reflected on the floorplan.
when I've fixed another issue with the callback handling this should be faster (about a second)

Quote
Now we are testing the wall switches that are not controlling a direct load but are paired to control other plug in dimmer modules. When we use the paired wall switch the light responds correctly but the floor plan does not update still. When we look in the logs it appears that a command class is not implemented currently...
Yeah. This is because we receive the info frame from the remote switch and not the controlled slaves. My plan is to either read the associations from the device and query the targets, or to associate ourself into the groups to catch the command. Btw, the double paddle remote switch only sends a node info frame when the left paddle is pressed. Nothing happens with the right paddle. So maybe the association approach is the better one..

Quote
Great work by the way.
you are welcome :-)

best regards,
Hari
Title: Re: ZWave API
Post by: totallymaxed on August 19, 2008, 12:54:21 pm
Quote
Now we are testing the wall switches that are not controlling a direct load but are paired to control other plug in dimmer modules. When we use the paired wall switch the light responds correctly but the floor plan does not update still. When we look in the logs it appears that a command class is not implemented currently...
Yeah. This is because we receive the info frame from the remote switch and not the controlled slaves. My plan is to either read the associations from the device and query the targets, or to associate ourself into the groups to catch the command. Btw, the double paddle remote switch only sends a node info frame when the left paddle is pressed. Nothing happens with the right paddle. So maybe the association approach is the better one..

Quote

Hi Hari,

We're using rev 21378 now.

We have paired our wall switches to control the ACT Dimmer Modules in our test setup as reported above. But now with rev 21378 we do not see any activity in the logs at all when we change the state of one of the controlled modules using a paired wall switch.... we see no log traffic at all related to the module turning on/off.

Any ideas?

Andrew

Title: Re: ZWave API
Post by: hari on August 19, 2008, 01:01:49 pm
is this by any chance a double paddle wall switch? The second paddle does not send that info frame.

will look at that after work,
br, Hari
Title: Re: ZWave API
Post by: totallymaxed on August 19, 2008, 02:17:12 pm
is this by any chance a double paddle wall switch? The second paddle does not send that info frame.

will look at that after work,
br, Hari

Yes it is! Right will test the left hand paddle now ;-)

Andrew
Title: Re: ZWave API
Post by: hari on August 19, 2008, 02:20:42 pm
is this by any chance a double paddle wall switch? The second paddle does not send that info frame.

will look at that after work,
br, Hari

Yes it is! Right will test the left hand paddle now ;-)

Andrew
I will play with associations tonight. I'd expect we get some frame when we associate the dongle itself in group 2 (right paddle)

best regards,
Hari
Title: Re: ZWave API
Post by: totallymaxed on August 19, 2008, 02:29:51 pm
is this by any chance a double paddle wall switch? The second paddle does not send that info frame.

will look at that after work,
br, Hari

Yes it is! Right will test the left hand paddle now ;-)

Andrew
I will play with associations tonight. I'd expect we get some frame when we associate the dongle itself in group 2 (right paddle)

best regards,
Hari

After pressing the left hand paddle we get the following in the logs;

Code: [Select]
41 08/19/08 13:19:47.387 0x1 0x16 0x0 0x49 0x84 0x10 0x10 0x4 0x12 0x0 0x87 0x25 0x26 0x27 0x85 0x73 0x70 0x86 0x72 0xef 0x20 0x26 0x50 0x5a (###I#######%&'#sp#r# &PZ) <0xb7942b90>
36 08/19/08 13:19:47.387 FUNC_ID_ZW_APPLICATION_UPDATE:UPDATE_STATE_NODE_INFO_RECEIVED received from node 16 - <0xb7942b90>
36 08/19/08 13:19:47.387 unhandled class <0xb7942b90>

We are using an ACT ZTM230 Radio Frequency Controlled, 230 VAC, European 3-way Wall Mounted Transmitter, Dual Paddle (Release 1.1) by the way.

Regards

Andrew
Title: Re: ZWave API
Post by: hari on August 19, 2008, 02:33:55 pm
Andrew,

just played with associations in my coffee break. After putting the dongle into group 2 of my ACT dual paddle remote switch, I receive the following when pressing the _right_ paddle:
41   08/19/08 14:26:35.171      0x1 0x9 0x0 0x4 0x0 0x3 0x3 0x20 0x1 0x0 0xd3 (####### ###) <0xb794cb90>
36   08/19/08 14:26:35.171      FUNC_ID_APPLICATION_COMMAND_HANDLER: <0xb794cb90>
36   08/19/08 14:26:35.171      COMMAND_CLASS_BASIC -  <0xb794cb90>

I can trigger a report that results in a floorplan update based on that frame or the other frame from your previous post (unhandled atm). I'll post a follow up tonight.

best regards,
Hari
Title: Re: ZWave API
Post by: totallymaxed on August 19, 2008, 02:57:33 pm
Andrew,

just played with associations in my coffee break. After putting the dongle into group 2 of my ACT dual paddle remote switch, I receive the following when pressing the _right_ paddle:
41   08/19/08 14:26:35.171      0x1 0x9 0x0 0x4 0x0 0x3 0x3 0x20 0x1 0x0 0xd3 (####### ###) <0xb794cb90>
36   08/19/08 14:26:35.171      FUNC_ID_APPLICATION_COMMAND_HANDLER: <0xb794cb90>
36   08/19/08 14:26:35.171      COMMAND_CLASS_BASIC -  <0xb794cb90>

I can trigger a report that results in a floorplan update based on that frame or the other frame from your previous post (unhandled atm). I'll post a follow up tonight.

best regards,
Hari


Hmmm... Weird as we get nothing from the right hand paddle... but the associated dimmer module does respond.

Andrew
Title: Re: ZWave API
Post by: hari on August 19, 2008, 03:16:38 pm
Hmmm... Weird as we get nothing from the right hand paddle... but the associated dimmer module does respond.
are you sure the dongle's node-id is associated to group 2?
Interesting that the dimmer module responds.. is it a ZDP200? Can you show me that response in the log? I could not trigger it from the ones I'm using here..
That would be ideal, if the load itself gives the feedback, so we don't have to traverse the association list from the remote switch..

best regards,
Hari
Title: Re: ZWave API, basic RA-PLUS-W support, high power inclusion
Post by: hari on August 19, 2008, 06:55:05 pm
hi devs,

just commited and tested the latest svn revision: I can include the Danfoss RA-PLUS-W Setback Schedule Radiator Thermostat in primary mode with high power inclusion now (with a Seluxit dongle). Wake-up is set to 15mins, On/Off via DCE works (on==normal, off==setback).

I'm sure there are some bugs left, but it's getting in shape..

best regards,
Hari
Title: Re: ZWave API
Post by: totallymaxed on August 20, 2008, 07:09:06 am
Hmmm... Weird as we get nothing from the right hand paddle... but the associated dimmer module does respond.
are you sure the dongle's node-id is associated to group 2?
Interesting that the dimmer module responds.. is it a ZDP200? Can you show me that response in the log? I could not trigger it from the ones I'm using here..
That would be ideal, if the load itself gives the feedback, so we don't have to traverse the association list from the remote switch..

best regards,
Hari


Hari I am out of the office today... but i will ask Radu to send you the additional log responses from the log. Yes the dimmer module is a ZDP200.

When you say 'dongle' I guess your referring to the Seluxit?

Andrew
Title: Re: ZWave API
Post by: totallymaxed on August 21, 2008, 01:25:41 pm
Hmmm... Weird as we get nothing from the right hand paddle... but the associated dimmer module does respond.
are you sure the dongle's node-id is associated to group 2?
Interesting that the dimmer module responds.. is it a ZDP200? Can you show me that response in the log? I could not trigger it from the ones I'm using here..
That would be ideal, if the load itself gives the feedback, so we don't have to traverse the association list from the remote switch..

best regards,
Hari


Hari,

I am setting up a new Core with a Seluxit, ZTM230 & ZDP210 to test make sure we have not got a config problem on the other Core we have been testing the new driver on.

Can you take me through 'step by step' the procedure you use to add and pair the ZDP210 to the ZTM230 please... so that I can make sure we have identical setup procedures?

All the best

Andrew
Title: Re: ZWave API
Post by: hari on August 21, 2008, 01:33:18 pm
I am setting up a new Core with a Seluxit, ZTM230 & ZDP210 to test make sure we have not got a config problem on the other Core we have been testing the new driver on.

Can you take me through 'step by step' the procedure you use to add and pair the ZDP210 to the ZTM230 please... so that I can make sure we have identical setup procedures?
Are you using a remote? If yes, make sure you include the dongle as first device. If it does not support inclusion mode, you have to re-replicate the controller after adding the other two devices.

Basically add both to the network, then associate the ZDP to group 2 of the ZTM. Then press the right paddle on the ZTM and see if you get any response from either the ZTM or the ZDP in the logs.

If you see nothing, send a command to the ZWave interface, Set association, destination should be the ZTM, data is the dongles node-id, group 2.

Try again and report.

best regards,
Hari
Title: Re: ZWave API
Post by: totallymaxed on August 21, 2008, 02:00:30 pm
I am setting up a new Core with a Seluxit, ZTM230 & ZDP210 to test make sure we have not got a config problem on the other Core we have been testing the new driver on.

Can you take me through 'step by step' the procedure you use to add and pair the ZDP210 to the ZTM230 please... so that I can make sure we have identical setup procedures?
Are you using a remote? If yes, make sure you include the dongle as first device. If it does not support inclusion mode, you have to re-replicate the controller after adding the other two devices.

Basically add both to the network, then associate the ZDP to group 2 of the ZTM. Then press the right paddle on the ZTM and see if you get any response from either the ZTM or the ZDP in the logs.

If you see nothing, send a command to the ZWave interface, Set association, destination should be the ZTM, data is the dongles node-id, group 2.

Try again and report.

best regards,
Hari

Yes we're using the ZTH200 remote currently.

How do I include the Seluxit... we never do this normally. We use the lighting wizard to add the plugin dimmers then we manually pair the ZDM230/ZDP210's

Andrew
Title: Re: ZWave API
Post by: hari on August 21, 2008, 02:06:12 pm
How do I include the Seluxit... we never do this normally. We use the lighting wizard to add the plugin dimmers then we manually pair the ZDM230/ZDP210's

* ok, reset your primary controller for a fresh start, replicate configuration to linuxmce (download configuration from the wizard)
* add the two devices with the remote and do the associations
* download the configuration again (wizard)

best regards,
Hari
Title: Re: ZWave API
Post by: totallymaxed on August 21, 2008, 02:19:33 pm
How do I include the Seluxit... we never do this normally. We use the lighting wizard to add the plugin dimmers then we manually pair the ZDM230/ZDP210's

* ok, reset your primary controller for a fresh start, replicate configuration to linuxmce (download configuration from the wizard)
* add the two devices with the remote and do the associations
* download the configuration again (wizard)

best regards,
Hari

Right! Got it ;-)
Title: Re: ZWave API
Post by: totallymaxed on August 21, 2008, 06:37:03 pm
How do I include the Seluxit... we never do this normally. We use the lighting wizard to add the plugin dimmers then we manually pair the ZDM230/ZDP210's

* ok, reset your primary controller for a fresh start, replicate configuration to linuxmce (download configuration from the wizard)
* add the two devices with the remote and do the associations
* download the configuration again (wizard)

best regards,
Hari

Right! Got it ;-)

Hari,

I have carried out the steps above. I reset the Seluxit from the "Send Command to device" screen. Then I used the "Send Command to device" screen from Web Admin and the selected "Download Configuration" from the pop-up and clicked "Send message". The on screen confirmation was good and the ZDP210 said the data was sent ok.

However after adding the new lights to the floor plan we still do not see any updates when we use the ZTM230 on paddle-2 two control it.

Andrew
Title: Re: ZWave API
Post by: hari on August 21, 2008, 06:49:42 pm
ok, now use the "Set Association" command of the Z-wave Interface with the following parameters:

# 239 NodeID (int)  == node id of the wall switch
# 249 Group ID (int)  == 2 (group 2 for the right paddle)
# 250 Nodes List (string) == the id of your dongle, should be 2 when you followed all steps but please verify

after that you should see log messages when you push the right paddle. I'm just working on some code to trigger the floorplan update from that.

best regards,
Hari
Title: Re: ZWave API
Post by: totallymaxed on August 21, 2008, 09:50:42 pm
ok, now use the "Set Association" command of the Z-wave Interface with the following parameters:

# 239 NodeID (int)  == node id of the wall switch
# 249 Group ID (int)  == 2 (group 2 for the right paddle)
# 250 Nodes List (string) == the id of your dongle, should be 2 when you followed all steps but please verify

after that you should see log messages when you push the right paddle. I'm just working on some code to trigger the floorplan update from that.

best regards,
Hari

I have been Adding the Association using ZDP210. So that might explain why i have had no success. I'll try the steps above tomorrow ;-)

Andrew
Title: Re: ZWave API
Post by: totallymaxed on August 22, 2008, 10:14:10 am
ok, now use the "Set Association" command of the Z-wave Interface with the following parameters:

# 239 NodeID (int)  == node id of the wall switch
# 249 Group ID (int)  == 2 (group 2 for the right paddle)
# 250 Nodes List (string) == the id of your dongle, should be 2 when you followed all steps but please verify

after that you should see log messages when you push the right paddle. I'm just working on some code to trigger the floorplan update from that.

best regards,
Hari

Hmmm... how do I get the node ID of the ZTM230 Wall Switch? When I press either paddle I get nothing in the logs at all (although the assocaited light does change state ok). Is there a command to list the Node ID's from Web Admin?

Andrew
Title: Re: ZWave API
Post by: hari on August 22, 2008, 09:21:04 pm
i've just commited a new version to svn. It supports automatic configuration of the ACT PIR now. Just include it and be patient for a few minutes..

best regards,
Hari
Title: Re: ZWave API
Post by: totallymaxed on August 22, 2008, 09:58:12 pm
i've just commited a new version to svn. It supports automatic configuration of the ACT PIR now. Just include it and be patient for a few minutes..

best regards,
Hari

Great. I'll test that tomorrow... nice ;-)

Andrew
Title: Re: ZWave API
Post by: totallymaxed on August 23, 2008, 12:10:18 pm
i've just commited a new version to svn. It supports automatic configuration of the ACT PIR now. Just include it and be patient for a few minutes..

best regards,
Hari

Ok... i have added the latest ZWave binary to my home Core and added a Seluxit, reset it and then downloaded and 'empty' configuration from the ZTH200. No problem. Next I reset the PIR and then added it to Group 2 in the ZTM200... no problem. Now I downloaded the configuration from the ZTH200 again... no problem. Then did a reload and Generic Sensor 12 appeared under the Zwave Embedded Security Interface in the Device tree. I waited about 5 mins but did not see any changes in the system... you say the PIR will be automatically configured... should i see some indication of that?

So I therefore did the following;

I then did a Set Configuration with the following parameters;

# 48 Value (int) = 17
# 239 NodeID (int) = 34 **Node ID for the Zwave Interface
# 248 Parameter ID (int) = 1 **ALARM Mode

The above Set Configuration command was accepted OK. I then added the PIR to a room and placed it on the security floorplan. Then i set the 'house' to ARMED mode... waited about 10 mins and then caused the PIR to be triggered (onboard LED lit up as expected) but I got no alerts in the Orbiters and 34_ZWave.log shows no events from the triggering of the PIR.

All the best

Andrew
Title: Re: ZWave API
Post by: hari on August 23, 2008, 12:23:28 pm
should i see some indication of that?
you should see the device setup in the logfile.

Quote
So I therefore did the following;

I then did a Set Configuration with the following parameters;

# 48 Value (int) = 17
# 239 NodeID (int) = 34 **Node ID for the Zwave Interface
# 248 Parameter ID (int) = 1 **ALARM Mode
that should all be set automatically... can you send me your logfile?

wait.. i did an additional step.. I used the ZTH200 (Setup->Reset unit) to reset the PIR before inclusion. Maybe that is needed to erase any existing wake-up settings on the device. We listen for the unsolicited wake-up frame to trigger device configuration. They only get sent when no wake-up interval is set.

best regards,
Hari
Title: Re: ZWave API
Post by: totallymaxed on August 23, 2008, 12:33:22 pm
should i see some indication of that?
you should see the device setup in the logfile.

Quote
So I therefore did the following;

I then did a Set Configuration with the following parameters;

# 48 Value (int) = 17
# 239 NodeID (int) = 34 **Node ID for the Zwave Interface
# 248 Parameter ID (int) = 1 **ALARM Mode
that should all be set automatically... can you send me your logfile?

wait.. i did an additional step.. I used the ZTH200 (Setup->Reset unit) to reset the PIR before inclusion. Maybe that is needed to erase any existing wake-up settings on the device. We listen for the unsolicited wake-up frame to trigger device configuration. They only get sent when no wake-up interval is set.

best regards,
Hari

Hari I just sent my 34_ZWave.log to you on email. I did a Setup -> reset unit on the PIR before I began to add it. Maybe I should have done a back to factory reset on the ZTH200 though... as i see some devices in the tree (dimmer modules) which I do not have here at home... I only brought the PIR home with me and the ZTH200 had been used before at the office for some tests. Maybe this is causing the problem?

Andrew
Title: Re: ZWave API
Post by: hari on August 23, 2008, 12:35:02 pm
yeah, please factory reset the controller, too

best regards,
Hari
Title: Re: ZWave API
Post by: hari on August 24, 2008, 11:36:04 am
latest svn rev supports polling for light states now. I'm still playing with the timers and wonder about the impact in very big networks. It polls after 30sec of idleness at the moment. Feedback appreciated.

best regards,
Hari
Title: Re: ZWave API
Post by: Domodude on August 24, 2008, 12:13:54 pm
latest svn rev supports polling for light states now. I'm still playing with the timers and wonder about the impact in very big networks. It polls after 30sec of idleness at the moment. Feedback appreciated.

best regards,
Hari

Got it to compile! I know what to do with the binary, but where should the library go? There is currently no zwave.so in /usr/pluto/lib. Also, should I reboot or is a depmod -a enough?
Thanks
Mark
Title: Re: ZWave API
Post by: hari on August 24, 2008, 12:25:39 pm
latest svn rev supports polling for light states now. I'm still playing with the timers and wonder about the impact in very big networks. It polls after 30sec of idleness at the moment. Feedback appreciated.

best regards,
Hari

Got it to compile! I know what to do with the binary, but where should the library go? There is currently no zwave.so in /usr/pluto/lib. Also, should I reboot or is a depmod -a enough?
Thanks
Mark


ignore the .so file.. you only need the binary. No depmod/reboot needed (no kernel modules here).

best regards,
Hari
Title: Re: ZWave API
Post by: totallymaxed on August 24, 2008, 12:52:06 pm
latest svn rev supports polling for light states now. I'm still playing with the timers and wonder about the impact in very big networks. It polls after 30sec of idleness at the moment. Feedback appreciated.

best regards,
Hari

I don't have any lighting module here at home with me otherwise I test that today. Its a public holiday here on Monday... so I will test the latest revision then for sure.

I know you were planning to do some work on this aspect this weekend so I was wondering...Will this revision get the non-load remote switches working with the floorplan ie will they update the floorplan when I change a dimmer modules state using the associated wall switch... and will the remote wall switches LED pickup changes in the associated dimmers state when driven from the floorplan?

Thanks for all the hard work.

Andrew

Title: Re: ZWave API
Post by: hari on August 24, 2008, 12:57:05 pm
I know you were planning to do some work on this aspect this weekend so I was wondering...Will this revision get the non-load remote switches working with the floorplan ie will they update the floorplan when I change a dimmer modules state using the associated wall switch... and will the remote wall switches LED pickup changes in the associated dimmers state when driven from the floorplan?

just working on that. Regarding the LED: the switch itself polls the associated devices every two minutes.

best regards,
Hari
Title: Re: ZWave API
Post by: totallymaxed on August 24, 2008, 01:01:39 pm
I know you were planning to do some work on this aspect this weekend so I was wondering...Will this revision get the non-load remote switches working with the floorplan ie will they update the floorplan when I change a dimmer modules state using the associated wall switch... and will the remote wall switches LED pickup changes in the associated dimmers state when driven from the floorplan?

just working on that. Regarding the LED: the switch itself polls the associated devices every two minutes.

best regards,
Hari

Great :-)

I think there is a config setting for the wall switch to determine how often it polls the associated device... I'll look into that.

Andrew
Title: Re: ZWave API
Post by: hari on August 24, 2008, 01:05:11 pm
i've begun to collect device settings and procedures in the wiki..
Title: Re: ZWave API
Post by: totallymaxed on August 24, 2008, 05:50:39 pm
i've begun to collect device settings and procedures in the wiki..

Thats Great :-) Are you updating http://wiki.linuxmce.org/index.php/Z-Wave (http://wiki.linuxmce.org/index.php/Z-Wave) ?

What would be useful is a section about the use of the send 'Command to device' popup... maybe some examples for common operations etc.

Have built the latest revsion ok... but have nothing other than the PIR here at home right now.

Andrew
Title: Re: ZWave API
Post by: caiman on August 25, 2008, 02:02:29 pm
Hi Hari,

I've just compiled from svn, here are my first impressions, with a somehow larger z-wave network (a bit below 20 nodes, some at the edge of reachability).
- The polling works (thank you !), I see the devices being polled, and I could see in the logs that the first run has updated the internal status of some devices
- 30 seconds seems a bit short because with that number of devices, we are almost continuously seeing activity on the zwave device. IMHO every few minutes would be enough
- I saw only a few devices respond (7-8). I didn't get time to look carefully at which ones responded and which ones didn't
- I haven't tested changing a device manually because I'm at work, will test tonight. Back to work now :)

Sam
Title: Re: ZWave API
Post by: hari on August 25, 2008, 03:20:25 pm
- 30 seconds seems a bit short because with that number of devices, we are almost continuously seeing activity on the zwave device. IMHO every few minutes would be enough

the poll does not run every 30 seconds, it is triggered after being idle for 30 seconds. We have to figure out nice values with testing. I wondered if we never get idle for such a long time on very busy networks..

time will tell

br Hari
Title: Re: ZWave API
Post by: totallymaxed on August 28, 2008, 02:36:05 pm
I know you were planning to do some work on this aspect this weekend so I was wondering...Will this revision get the non-load remote switches working with the floorplan ie will they update the floorplan when I change a dimmer modules state using the associated wall switch... and will the remote wall switches LED pickup changes in the associated dimmers state when driven from the floorplan?

just working on that. Regarding the LED: the switch itself polls the associated devices every two minutes.

best regards,
Hari

Hari,

Any progress on the floorplan update issue when using non-load remote switches paired with dimmer modules?

Andrew
Title: Re: ZWave API
Post by: chrisbirkinshaw on August 29, 2008, 08:05:36 pm
Which switch modules with LEDs are we talking about here? Having some feedback in my system would be great. At the moment if I press an X10 switch downstairs before I go out to switch my lights off using a macro I have to look around the house to see that they have actually been switched off! Might there be a way to have a button trigger a LMCE event and then LMCE set the button colour once the macro has been completed?
Title: Re: ZWave API
Post by: hari on August 29, 2008, 09:36:29 pm
Hi Andrew,

Any progress on the floorplan update issue when using non-load remote switches paired with dimmer modules?

I was pretty busy this week, but half of the code is ready, the other half should follow this weekend.

best regards,
Hari
Title: Re: ZWave API
Post by: totallymaxed on August 29, 2008, 09:41:01 pm
Which switch modules with LEDs are we talking about here? Having some feedback in my system would be great. At the moment if I press an X10 switch downstairs before I go out to switch my lights off using a macro I have to look around the house to see that they have actually been switched off! Might there be a way to have a button trigger a LMCE event and then LMCE set the button colour once the macro has been completed?

Hmmm... well the basic problem with X10 is that you cannot be sure command was acted on... as there is no feedback from the controlled device. Before Hari's new driver this was essentially true of the 'old' ZWave driver too... the only difference was that ZWave is inherently more reliable in its communication protocol so meesages generally get through.

With Haris's new driver we have full bi-directional control :-)

The modules we are referring too earlier in this thread are ACT wall switches that have a single LED on each 'paddle' of the switch used to indicate the various 'states' that the paddle is in or in some cases the associated dimmer module that the 'paddle' is controlling. We are testing the scenario where a dimmer modules has been set to a new 'state' by LinuxMCE and therefore the assciated wall switch 'paddle' should have that new 'state' communicated to it and this 'state' should be reflected by the LED.

All the best

Andrew
Title: Re: ZWave API
Post by: totallymaxed on August 29, 2008, 09:41:44 pm
Hi Andrew,

Any progress on the floorplan update issue when using non-load remote switches paired with dimmer modules?

I was pretty busy this week, but half of the code is ready, the other half should follow this weekend.

best regards,
Hari

Great Hari... guessed you were busy ;-)

Andrew
Title: Re: ZWave API
Post by: hari on August 30, 2008, 06:15:02 pm
hi andrew,

the code for the right paddle is checked in, but not yet tested. Left one will follow.

best regards,
Hari
Title: Re: ZWave API
Post by: totallymaxed on August 30, 2008, 07:27:01 pm
hi andrew,

the code for the right paddle is checked in, but not yet tested. Left one will follow.

best regards,
Hari

Hey great Hari... I will test that first thing on Monday as I dont have the ACT hardware to test with here at home this weekend.

I will get that Zwave kit off to you early next week... sorry just did not get to it last week.

Andrew
Title: Re: ZWave API
Post by: hari on August 31, 2008, 11:59:05 am
just added code for the left paddle. The associations are fetched from the remote switch at device startup:
Code: [Select]
36 08/31/08 11:49:25.095 Nodes:  <0xb7986b90>
36 08/31/08 11:49:25.095 6 <0xb7986b90>
36 08/31/08 11:49:25.095 32 <0xb7986b90>
36 08/31/08 11:49:25.095 Built nodelist: 6,32 <0xb7986b90>

when we receive a node information frame (left paddle pressed), we request reports from the associated devices in group 1:

Code: [Select]
36 08/31/08 11:49:54.945 FUNC_ID_ZW_APPLICATION_UPDATE:UPDATE_STATE_NODE_INFO_RECEIVED received from node 3 -  <0xb7986b90>
36 08/31/08 11:49:54.945 This is a remote switch, we will traverse the association list and request reports <0xb7986b90>
36 08/31/08 11:49:54.945 Adding job: 0x80dc838 <0xb7986b90>
36 08/31/08 11:49:54.945 Setting callback type: 19 <0xb7986b90>
36 08/31/08 11:49:54.945 Adding job: 0x80dca58 <0xb7986b90>
36 08/31/08 11:49:54.945 Setting callback type: 19 <0xb7986b90>

then we receive the reports and send the events to update the state within lmce and the floorplan:

Code: [Select]
36 08/31/08 11:49:55.582 Got basic report from node 6, value: 0 <0xb7986b90>
36 08/31/08 11:49:55.582 Sending EVENT_State_Changed_CONST event from node 6, level 0 <0xb7986b90>
36 08/31/08 11:49:55.886 Got basic report from node 32, value: 0 <0xb7986b90>
36 08/31/08 11:49:55.886 Sending EVENT_State_Changed_CONST event from node 32, level 0 <0xb7986b90>

best regards,
Hari
Title: Re: ZWave API
Post by: totallymaxed on August 31, 2008, 01:19:54 pm
just added code for the left paddle. The associations are fetched from the remote switch at device startup:
Code: [Select]
36 08/31/08 11:49:25.095 Nodes:  <0xb7986b90>
36 08/31/08 11:49:25.095 6 <0xb7986b90>
36 08/31/08 11:49:25.095 32 <0xb7986b90>
36 08/31/08 11:49:25.095 Built nodelist: 6,32 <0xb7986b90>

when we receive a node information frame (left paddle pressed), we request reports from the associated devices in group 1:

Code: [Select]
36 08/31/08 11:49:54.945 FUNC_ID_ZW_APPLICATION_UPDATE:UPDATE_STATE_NODE_INFO_RECEIVED received from node 3 -  <0xb7986b90>
36 08/31/08 11:49:54.945 This is a remote switch, we will traverse the association list and request reports <0xb7986b90>
36 08/31/08 11:49:54.945 Adding job: 0x80dc838 <0xb7986b90>
36 08/31/08 11:49:54.945 Setting callback type: 19 <0xb7986b90>
36 08/31/08 11:49:54.945 Adding job: 0x80dca58 <0xb7986b90>
36 08/31/08 11:49:54.945 Setting callback type: 19 <0xb7986b90>

then we receive the reports and send the events to update the state within lmce and the floorplan:

Code: [Select]
36 08/31/08 11:49:55.582 Got basic report from node 6, value: 0 <0xb7986b90>
36 08/31/08 11:49:55.582 Sending EVENT_State_Changed_CONST event from node 6, level 0 <0xb7986b90>
36 08/31/08 11:49:55.886 Got basic report from node 32, value: 0 <0xb7986b90>
36 08/31/08 11:49:55.886 Sending EVENT_State_Changed_CONST event from node 32, level 0 <0xb7986b90>

best regards,
Hari

Hari thats great we'll test that first thing tomorrow!

Does this mean that the reverse situation will get reported correctly now too? ie we change the state of the associated dimmer using the floorplan... does that change get passed back to the appropriate paddle on the wall switch?

All the best

Andrew
Title: Re: ZWave API
Post by: hari on August 31, 2008, 01:25:38 pm
Does this mean that the reverse situation will get reported correctly now too? ie we change the state of the associated dimmer using the floorplan... does that change get passed back to the appropriate paddle on the wall switch?
No. The switch itself polls the devices every two minutes and changes the led accordingly.

best regards,
Hari

ps: btw, the ACT wall dimmer with double paddle is so loud (humming sound) that even my girlfriend noticed it in the sleeping room. I'm really looking forward to the merten units..
Title: Re: ZWave API
Post by: totallymaxed on August 31, 2008, 01:34:46 pm
Does this mean that the reverse situation will get reported correctly now too? ie we change the state of the associated dimmer using the floorplan... does that change get passed back to the appropriate paddle on the wall switch?
No. The switch itself polls the devices every two minutes and changes the led accordingly.

best regards,
Hari

ps: btw, the ACT wall dimmer with double paddle is so loud (humming sound) that even my girlfriend noticed it in the sleeping room. I'm really looking forward to the merten units..


Of course we discussed the fact that the Switch polls the associated devices every two mins by default. I forgot to check the docs on what values that polling period can be set to.

What ACT 2-paddle dimmer switch are you getting a hum from? I'll check that against one of our units to see if its a common fault!

I have sent another email to Seluxit about there multi-sensor... nothing back from them yet though.

Thanks

Andrew
Title: Re: ZWave API
Post by: hari on August 31, 2008, 01:38:43 pm
What ACT 2-paddle dimmer switch are you getting a hum from? I'll check that against one of our units to see if its a common fault!
ZDM230. The ZDP plugs also make noise if you get close..

Quote
I have sent another email to Seluxit about there multi-sensor... nothing back from them yet though.

Daniel gave me a short notice, he was on holidays. He said he will send me one in two weeks.

best regards,
Hari
Title: Re: ZWave API
Post by: totallymaxed on August 31, 2008, 01:47:37 pm
What ACT 2-paddle dimmer switch are you getting a hum from? I'll check that against one of our units to see if its a common fault!
ZDM230. The ZDP plugs also make noise if you get close..

Quote
I have sent another email to Seluxit about there multi-sensor... nothing back from them yet though.

Daniel gave me a short notice, he was on holidays. He said he will send me one in two weeks.

best regards,
Hari

I'll check our ZDM230's for 'hum'... I have noticed some very low level hum from the ZDP plugin dimmers.

Good news re multi-sensor from Daniel :-)

Andrew
Title: Re: ZWave API
Post by: Domodude on August 31, 2008, 05:55:30 pm
ps: btw, the ACT wall dimmer with double paddle is so loud (humming sound) that even my girlfriend noticed it in the sleeping room. I'm really looking forward to the merten units..

These are nearly noiseless. With your ear against a superdimmer unit, you can hear a slight hum. Same with the relais switch units (not surprising since it contains a relay).

I don't know about ACT units, but merten units have a separate transmitter and receiver in their own software. I hope this will be the case in the new zwave api, too!
Title: Re: ZWave API
Post by: totallymaxed on August 31, 2008, 06:15:22 pm
ps: btw, the ACT wall dimmer with double paddle is so loud (humming sound) that even my girlfriend noticed it in the sleeping room. I'm really looking forward to the merten units..

These are nearly noiseless. With your ear against a superdimmer unit, you can hear a slight hum. Same with the relais switch units (not surprising since it contains a relay).

I don't know about ACT units, but merten units have a separate transmitter and receiver in their own software. I hope this will be the case in the new zwave api, too!

Hari's new code is fully bi-directional by the way and is a real 'quantum leap' in capability for LinuxMCE - for first time we have a really fully capable ZWave driver thanks to Hari. Give it a try... you'll love it!

Andrew
Title: Re: ZWave API
Post by: hari on August 31, 2008, 06:18:52 pm
we still miss thermostat and multisensor support. Multisensor will come soon, but I still search somebody with a wired Z-Wave thermostat.

best regards,
Hari

btw: domodude: what do you mean with seperate receiver and transmitter?
Title: Re: ZWave API
Post by: thoweiss on September 04, 2008, 09:49:15 am
Something new about the Triklestar Products?

Does anybody know a good shop to by eropean z-Wave Products?

I would like to start in oktober november with z-wave...

Regards,

Thorsten.

[EDIT]

The z-Wave4you shop actuallay no longer online, don't know whats happend...
From the Triklestar sales i have the information that theire Product will be available in October 08....
 [/EDIT]


Title: Re: ZWave API
Post by: totallymaxed on September 04, 2008, 12:35:34 pm
Something new about the Triklestar Products?

Does anybody know a good shop to by eropean z-Wave Products?

I would like to start in oktober november with z-wave...

Regards,

Thorsten.

We have not purchased any products from this company but they seem to be very helpful and well informed too;

http://www.zwave4u.de

All the best

Andrew
Title: Re: ZWave API
Post by: Zaerc on September 04, 2008, 03:50:28 pm
Also see: http://wiki.linuxmce.org/index.php/Where_to_Buy#Europe
Title: Re: ZWave API
Post by: hari on September 08, 2008, 10:19:11 pm
added drapes support, tested with the merten blinds switch.

best regards,
Hari
Title: Re: ZWave API
Post by: Domodude on September 09, 2008, 02:56:11 pm
added drapes support, tested with the merten blinds switch.

Hari,

Excellent! That just makes me want to try your driver again, but previously I had no luck compiling it. A while ago you mentioned a package -- are you still planning this?

You have one taker, for sure!

Cheers
Mark
Title: Re: ZWave API
Post by: hari on September 09, 2008, 09:30:45 pm
A while ago you mentioned a package -- are you still planning this?
no package yet, have to dig deeper into "MakeRelease".

For now, I can provide a 32 bit binary for 0710: http://vt100.at/files/ZWave-0.0.1-0710-32bit.bz2

best regards,
Hari
Title: Re: ZWave API
Post by: Domodude on September 09, 2008, 09:45:04 pm
Does anybody know a good shop to by eropean z-Wave Products?

I have in the past mentioned voltus.de to buy Merten Connect z-wave gear. They have a low price, but their customer service (with which I unfortunately have quite a bit of experience) is abominable.... :(
Title: Re: ZWave API
Post by: hari on September 09, 2008, 10:13:33 pm
Does anybody know a good shop to by eropean z-Wave Products?

I have in the past mentioned voltus.de to buy Merten Connect z-wave gear. They have a low price, but their customer service (with which I unfortunately have quite a bit of experience) is abominable.... :(

possy ordered some Merten stuff at elektronetshop.de, took them some days (as stated in the shop) but cheaper than voltus.. (thanks possy :-) )

best regards,
Hari
Title: Re: ZWave API
Post by: Zaerc on September 09, 2008, 11:32:02 pm
Please add shops to http://wiki.linuxmce.org/index.php/Where_to_Buy along with your experience with them.
Title: Re: ZWave API
Post by: totallymaxed on September 28, 2008, 11:15:47 am
short update:
Playing with LMCE being the primary controller and SIS mode (Node id server). I already can add slave devices and controllers to the network with the dongle. Ideally all remote controllers should work as inclusion controllers in this scenario. Sadly enough the ZTH100/200 does not seem to support the inclusion controller mode and only is working as secondary controller for now (Zaerc suggested a long usb extension cord to be able to add all my devices :-) )

I'm trying to get hold of a Tricklestar remote, they state SIS support on the page and it uses newer library versions. And it should be available in Europe (868Mhz)

The SIS mode seems to be the best choice for a Z-Wave network. Some devices like the RA-Plus-W only work in a network with SIS. And we get the node information frame at the time of inclusion, so we can catch battery powered devices that don't send out a broadcast wake up event.

best regards,
Hari

Hi Hari,

I met with Bernard on Friday very briefly. He left me with a 'Golden' pre-production Tricklestar ZWave stick :-) !! What nice guy by the way and he has a mountain of ZWave experience together with years of experience in the home automation business. Anyway i will test the ZWave stick with your driver on Monday (I ran out of the office on Friday without picking up some ZWave kit to test it with!).

Bernard has Fedex'd me a Tricklestar ZWave remote... should get that Mon/Tues :-)... and I have asked him to send you a unit too.

If your available during Monday, even briefly we could test the ZWave stick on one of our test Cores... let me know if you have some time maybe at lunch?

All the best

Andrew
Title: Re: ZWave API
Post by: hari on September 28, 2008, 03:01:58 pm
Bernard has Fedex'd me a Tricklestar ZWave remote... should get that Mon/Tues :-)... and I have asked him to send you a unit too.
he promised one for me some weeks ago.

Quote
If your available during Monday, even briefly we could test the ZWave stick on one of our test Cores... let me know if you have some time maybe at lunch?
Monday will be pretty busy. But I'd assume the stick will work out of the box, if it still uses that pl2303 chipset.

best regards,
Hari
Title: Re: ZWave API
Post by: totallymaxed on September 28, 2008, 05:58:05 pm
Bernard has Fedex'd me a Tricklestar ZWave remote... should get that Mon/Tues :-)... and I have asked him to send you a unit too.
he promised one for me some weeks ago.

Quote
If your available during Monday, even briefly we could test the ZWave stick on one of our test Cores... let me know if you have some time maybe at lunch?
Monday will be pretty busy. But I'd assume the stick will work out of the box, if it still uses that pl2303 chipset.

best regards,
Hari

Hi Hari,

I think Bernard assumed the sample remote we purchased would be 'shared' with you - a simple mistake. Anyway i have ordered a unit for you and it should be with you by Wednesday/Thursday I expect.

No problem re Monday. I'll update you on the testing either here or on irc during Monday.

All the best

Andrew
Title: Re: ZWave API
Post by: thoweiss on November 07, 2008, 07:31:29 am
The triclestar Z-Wave USB-Adapter is now available in the onlinestore http://www.zwave4u.de/ (http://www.zwave4u.de/).

My question is:

Will this adapter work with the LMCE Z-Wave libary?

Regards Thorsten.
Title: Re: ZWave API
Post by: nite_man on November 07, 2008, 09:10:52 am
I'm also would like to know that. Because I found that only Seluxit viaSens 100 can work with the latest Z-Wave implementation.  Tricklestar USB Adapter looks nice and it's cheaper twice :)

I found the Seluxit Multisensor (http://www.zwave4u.com/product_info.php/info/p3_Seluxit-Multisensor.html/XTCsid/38bc4371d496cc2e10c36d75e3bffa98) which offers motion detection and light level, temperature and humidity measurements. Does somebody test it under LMCE? I suppose that it should work well with Seluxit viaSens 100 PC adapter. But not sure that it'll work with LMCE.

BTW, zwave4u (http://www.zwave4u.com/product_info.php/info/p3_Seluxit-Multisensor.html/XTCsid/38bc4371d496cc2e10c36d75e3bffa98) looks very attractive. It offers a lot Z-Wave devices with reasonable price and ships to EU.
Title: Re: ZWave API
Post by: hari on November 07, 2008, 09:30:41 am
the tricklestar works, I've tested it myself, but from what I know it is not yet available.

The Seluxit Multisensor will be supported soon, it is not yet released.

Yeah zwave4u looks good.

br, Hari
Title: Re: ZWave API
Post by: hari on November 07, 2008, 09:39:24 am
btw, that is documented in the wiki.
Title: Re: ZWave API
Post by: totallymaxed on November 07, 2008, 10:12:34 am
The triclestar Z-Wave USB-Adapter is now available in the onlinestore http://www.zwave4u.de/ (http://www.zwave4u.de/).

My question is:

Will this adapter work with the LMCE Z-Wave libary?

Regards Thorsten.

Yes is the answer to will it work... but you must us the new ZWave drive being developed by Hari and not the one shipped with LinuxMCE-0710. The Tricklestar Zwave products are very nice indeed and very well priced too... we like them a lot.

As to the Tricklestar USB stick being available... I doubt that they will have them in stock yet as I know that the first production units are only just about to arrive.

All the best

Andrew
Title: Re: ZWave API
Post by: nite_man on November 09, 2008, 03:19:45 pm
Thanks for explanation, guys. I have another question. Does somebody know is there some Z-Wave Door / Window Sensors (http://www.zwaveproducts.com/ZWAVE-HOME-MONITORING/Z-Wave-Door-Window-Sensor.html) for European standards?
Title: Re: ZWave API
Post by: totallymaxed on November 09, 2008, 03:26:53 pm
Thanks for explanation, guys. I have another question. Does somebody know is there some Z-Wave Door / Window Sensors (http://www.zwaveproducts.com/ZWAVE-HOME-MONITORING/Z-Wave-Door-Window-Sensor.html) for European standards?

See this thread... TechStyle has a Window/Door sensor available. We have one on test here and it works fine;

http://forum.linuxmce.org/index.php?topic=5820.msg34411#msg34411 (http://forum.linuxmce.org/index.php?topic=5820.msg34411#msg34411)

Andrew
Title: Re: ZWave API
Post by: hari on November 09, 2008, 03:35:31 pm
also in the wiki: http://wiki.linuxmce.org/index.php/Everspring_SM103
Title: Re: ZWave API
Post by: caiman on December 10, 2008, 11:05:47 am
Hi Hari,

In my next install I want to try SIS mode with a tricklestar inclusion remote and Danfoss thermostat (Xmas is coming fast :).
Would you mind sharing the steps required to install such a setup ? I guess I will reset my network completely and the use the MessageSend CLI to re-include all nodes and create the necessary associations, but I'm not sure which DCE commands are available, and in which order it's best to use them?

Are there commands to test the quality of a link, or to view the routing table ?

I quickly checked the wiki, but didn't find much about the DCE commands to use for this. Any pointers welcome :)

thanks,
Sam
Title: Re: ZWave API
Post by: hari on December 10, 2008, 11:59:31 am
Hi Hari,

In my next install I want to try SIS mode with a tricklestar inclusion remote and Danfoss thermostat (Xmas is coming fast :).
Would you mind sharing the steps required to install such a setup ? I guess I will reset my network completely and the use the MessageSend CLI to re-include all nodes and create the necessary associations, but I'm not sure which DCE commands are available, and in which order it's best to use them?

no need to use messagesend. You just include the dongle with the _fresh_ remote (can be done with the light wizard), and then start adding devices with the remote itself. They pop up in lmce automatically in SIS mode, no need to do further download configs...

Quote
Are there commands to test the quality of a link, or to view the routing table ?
there are some z-wave commands for that, but not yet available via DCE. As this driver is a replacement for the original one, I did not change the template to add new commands. 0810 will prolly provide some new commands for network repair and a few other things..

best regards,
Hari
Title: Re: ZWave API
Post by: Kostakis on April 08, 2009, 09:19:14 am
Hello guys,
i am trying to understand some basic things about z-wave devices from the source code (zwaveapi.h and zwaveapi.cpp).

I have a ZCS201 controller, a PIR ZIR010 binary sensor and a EVERSPRING SM103 door/window sensor bought from our friend from this forum :-)

My issue is , i cant fully understand how these sensors work, i can add them using 01 04 00 4a 01 b0   start ADD command .. follow all the process till the end of ADD mode... but then.. they seem like dead...

they go to sleep and whatever i send never wake up..

I just only to warn me when the door is open or there is movement in my room....  send me an event...


do i need to send some commands to wake them up?  is there a special command to put them in ALARM mode?

what is the process i must follow to have some events from these sensors? i am confused!

hope you can give me some clues to continue my search on the Z-Wave world... :-)

thank you very much!

Regards               
Title: Re: ZWave API
Post by: hari on April 08, 2009, 09:36:58 pm
would you mind to elaborate a bit on your project? Is it open source? Where can I download the code :-)

you need to set the wake-up interval right after inclusion. The node sending this will be the destination for wake up notifications.

br, Hari
Title: Re: ZWave API
Post by: Kostakis on April 09, 2009, 10:46:33 am
To download the source code it must be written first :-) I just want to control a PIR , a door windows and some binary switches for an alarm system i am developing.

I cant manage to work with battery powered devices...

if i understand you correctly, i will setup a wake-up interal for a sensor.... lets say... 5 mins.... and then every 5 mins the sensor will wake up... send me a signal.. and i will have some time? to send whatever command i want before it goes to sleep again?

but what about if a thief enters my house.. the sensor will wait for wake up time and then send me the event??

because whatever i do to the Door/window sensor for example... its not sending me anything only if i press the switch behind.

Is there anything like ALARM mode i must set the sensor to send me events in realtime??

thank you for your time!
Title: Re: ZWave API
Post by: hari on April 09, 2009, 10:12:46 pm
To download the source code it must be written first :-) I just want to control a PIR , a door windows and some binary switches for an alarm system i am developing.
share early, even if it is a PoC :-)

Quote
I cant manage to work with battery powered devices...
yeah, that part is a bit tricky sometimes.

Quote
if i understand you correctly, i will setup a wake-up interal for a sensor.... lets say... 5 mins.... and then every 5 mins the sensor will wake up... send me a signal.. and i will have some time? to send whatever command i want before it goes to sleep again?
5 min is quite short, that will drain your batteries fairly quick. You usually send a "wakeup_no_more_information" when the device shall go to sleep again (do that asap). Some like the HSM100 will empty their battery if you don't make them sleep again.

Quote
but what about if a thief enters my house.. the sensor will wait for wake up time and then send me the event??

because whatever i do to the Door/window sensor for example... its not sending me anything only if i press the switch behind.

Is there anything like ALARM mode i must set the sensor to send me events in realtime??
button pressing usually triggers the sending of a node information frame. The wake-up time is set so that you can reach the devices periodically to do configuration stuff or whatever. To receive "events", you have to associate the your controller into the proper groups on the device. PIRs usually use group 1 for trigger events. The Seluxit Multisensor e.g. has distinct groups for all sensor inputs.

Quote
thank you for your time!
you're welcome. Maybe you want to share your code, I think this is quite interesting and I'm working on a standalone z-wave library as I'm rewriting our stack..

br, Hari
Title: Re: ZWave API
Post by: Zaerc on April 09, 2009, 10:20:08 pm
...
Quote
thank you for your time!
you're welcome. Maybe you want to share your code, I think this is quite interesting and I'm working on a standalone z-wave library as I'm rewriting our stack..

br, Hari

Good idea, there seems to be plenty of interest from outside lmce, and that way it will be easier for other people to contribute that aren't (interested in being) a part of this project.
Title: Re: ZWave API
Post by: hari on April 09, 2009, 10:34:57 pm
...
Quote
thank you for your time!
you're welcome. Maybe you want to share your code, I think this is quite interesting and I'm working on a standalone z-wave library as I'm rewriting our stack..

br, Hari

Good idea, there seems to be plenty of interest from outside lmce, and that way it will be easier for other people to contribute that aren't (interested in being) a part of this project.
yup! The dunkkis.org guys are working on sth for the openwrt based on my code. Combined efforts on z-wave would be great as the protocol is huge.

br, Hari
Title: Re: ZWave API
Post by: Kostakis on April 10, 2009, 01:31:36 pm
i think i figure out how to control this demonic thing :-p

after i add my device with the usual way... i do a SetAssociation with the Static Controller... and the data starts to flow to my serial port :-)

my developing is based on a AVR32 microcontroller so i dont know if my code is so usefull, but when my functions will be ready i will post them to tell me your thoughts :-)
thank you very much

i will be in touch, great work!

regards, Kostas
Title: Re: ZWave API
Post by: hari on April 10, 2009, 01:55:40 pm
nice! happy hacking!

br, hari
Title: Re: ZWave API
Post by: yowl on September 23, 2009, 10:12:10 am
Hi,

I've just bought some zwave kit(AEON labs USB and HomePro socket) and am keen to see what drivers and libraries are out there.  I see there is kernel driver but I'm not sure that is required for this stick as it may present itself as a serial device with the USB serial driver?  Also I see there is a mention by Hari of a standalone library being worked, is there any more information on this?

Thanks

Scott
Title: Re: ZWave API
Post by: hari on September 24, 2009, 11:20:30 am
I'm running dcerouter, mysql and a few DCE devices like Z-Wave "standalone" on fedora and openembedded. Not much hassle, but you need to understand some of the core components. Jump into #linuxmce-devel if you need more info.

best regards,
Hari
Title: Re: ZWave API
Post by: Kooma on January 17, 2010, 10:43:04 am
also in the wiki: http://wiki.linuxmce.org/index.php/Everspring_SM103
Hi, I'm having difficulties in the installation of door/window sensor sm103 and hope to get some advice. Wiki is quite limited atm.

I included the sensor in the network with ACT HomePro ZTH200 remote. The response was 'only added to network 7'. OK. LMCE sees now the sensor (once the settings were downloaded from the remote), but sensor status is missing.

How can I get the status?

Thank you in advance.

/Kooma
Title: Re: ZWave API
Post by: hari on January 18, 2010, 02:37:34 pm
you need to do the proper group associations.

br Hari
Title: Re: ZWave API
Post by: Kooma on January 18, 2010, 06:46:17 pm
you need to do the proper group associations.

br Hari

Thank's hari. Feel like a moron to ask where/how the group association can be done?

Previously in this topic it was mentioned that this sensor can only be associated with group one. Noticed that before the installation, yet don't understand (obviously) what it actually means.

/Kooma
Title: Re: ZWave API
Post by: nite_man on March 12, 2010, 03:33:14 pm
Quote
The Seluxit Multisensor e.g. has distinct groups for all sensor inputs.

Could somebody give me more info how to do that and where, please? I expected that for each subsensor will be created a child device under the Multisensor. Similar to GC100 interface. But it seems I was wrong.

Thanks in advance.
Title: Re: ZWave API
Post by: hari on March 13, 2010, 12:30:10 pm
Quote
The Seluxit Multisensor e.g. has distinct groups for all sensor inputs.

Could somebody give me more info how to do that and where, please? I expected that for each subsensor will be created a child device under the Multisensor. Similar to GC100 interface. But it seems I was wrong.

Thanks in advance.

There are no child devices yet, sambuca is working on the multi instance features. But you can use the seluxit now, just associate the dongle into those groups. The Z-Wave driver will send DCE events when it receives new values from the sensors.

best regards,
Hari
Title: Re: ZWave API
Post by: sambuca on March 13, 2010, 12:41:39 pm
The multi-instance support is mostly finished. What could still be improved is the detection of devices. But that is another story, as it would require mapping each device to the correct multi instance device templates. I.e. the EZMotion sensor should be added as one motion detector and two multilevel sensors, but as the device reports itself as a multilevel sensor with three instances, it is currently added as three multilevel sensors.
But they are not added as child devices, but as three devices on the same level. This is because one device can contain sensors that are of different types, like the EZMotion, it has two climate sensors, that needs to be added below the climate interface, and one motion sensor, which needs to be added below the security interface.

I haven't figured out the proper way to do it, but it should be along the lines of the already existing device template system in LMCE. I'm not actively working on this, so anyone should feel free to take it on  ;)

br,
sambuca
Title: Re: ZWave API
Post by: nite_man on March 13, 2010, 07:04:47 pm
Thanks, guys, for the answers. If I understand correctly to install multi-sensor correctly separate device for each subsensor should be added via admin interface. But what ID should be used for them?
Title: Re: ZWave API
Post by: sambuca on March 13, 2010, 10:14:38 pm
You can use the EZMotion wiki article as a guide. Basically, the Port/Channel number device data should be node_id/instance id. But you would have to guess the instance IDs.

When the ZWave driver adds a new device, it should add a lmce device for each instance, so you could re-add your zwave device and see what instance IDs it adds.

br,
sambuca