LinuxMCE Forums

General => Developers => Topic started by: totallymaxed on January 04, 2008, 12:59:34 am

Title: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: totallymaxed on January 04, 2008, 12:59:34 am
The new ACT Solutions ZCU201 USB Z-wave Interface uses the SPCP825A USB to UART Controller chip

http://w3.sunplus.com/ShowFeature.asp?body=SPCP825A-001B (http://w3.sunplus.com/ShowFeature.asp?body=SPCP825A-001B)

The SPCP825A currently has no USB driver support for Linux and therefore the ZCU201 is not detected when attached to a USB port. ACT Solutions have kindly provided me with the source to an Open driver for the SPCP825A to enable a working driver to be developed. As tar as I know this source is working but not fully debugged.

If anyone in the Developer forum would be interested in looking at this driver source to see if a working driver could be put together please get in touch and I will make it available to you.

Let me know if your interested in working on this?

Andrew
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: ddamron on January 04, 2008, 02:59:36 am
Would if I could, but can't so I won't.  :-\
(I don't know C++ well enough)

Dan
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: eloy on January 04, 2008, 05:53:36 am
Would if I could, but can't so I won't.  :-\
(I don't know C++ well enough)

I bet the sample driver is written in C, not C++. You know C? ;-)
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: tschak909 on January 04, 2008, 05:58:54 am
totallymaxed, gimme. :-)

-Thom
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: totallymaxed on January 04, 2008, 07:37:36 am
totallymaxed, gimme. :-)

-Thom


Hi Thom,

Private message me some where to ftp it to or your email address (its not big) and I'll send it later this morning. :-)

Andrew
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: ddamron on January 04, 2008, 07:47:06 am
Actually, Send it to me anyway, you already have my ftp info... :)

Thanks!

Dan
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: totallymaxed on January 04, 2008, 09:43:48 am
Actually, Send it to me anyway, you already have my ftp info... :)

Thanks!

Dan


Done ;-)
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: totallymaxed on January 04, 2008, 09:45:08 am
Would if I could, but can't so I won't.  :-\
(I don't know C++ well enough)

I bet the sample driver is written in C, not C++. You know C? ;-)

Yeah its C your right... no one really does much driver development in C++ :-)
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: totallymaxed on January 04, 2008, 05:12:38 pm
The new ACT Solutions ZCU201 has the following ID's that identify it to the Core;

Vendor ID is 04FC and Product ID is 0201.
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: coley on January 04, 2008, 06:01:51 pm
ok, gonna dip my toe in here, I should be able to help with some dev/dbg.
 - firstly where can I buy the ZCU201, I've been reading about it from ACT for ages but don't know who supplies it. I've googled and found a few places that supply it - any recommendations? I'm in Ireland.
 - next, totallymaxed, can I get the src please?

thx,
-Coley.
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: totallymaxed on January 05, 2008, 12:53:32 am
ok, gonna dip my toe in here, I should be able to help with some dev/dbg.
 - firstly where can I buy the ZCU201, I've been reading about it from ACT for ages but don't know who supplies it. I've googled and found a few places that supply it - any recommendations? I'm in Ireland.
 - next, totallymaxed, can I get the src please?

thx,
-Coley.

Hi Coley,

I'm not sure who might be stocking it here in Europe currently. Someone else here might want to comment on this. My company will be stocking in the near future for our own installations and when we do we could supply you with a unit.

Send me a private message with your email address or an ftp server and i will send the source to you.

Andrew
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: hari on January 05, 2008, 11:07:26 am
http://www.elekhomica.nl/product_info.php?cPath=91&products_id=707

br hari
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: totallymaxed on January 05, 2008, 11:52:33 am
http://www.elekhomica.nl/product_info.php?cPath=91&products_id=707

br hari

Thanks hari for the url

Just a reminder to provide me with an alternative way to send you large files ;-)

Andrew
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: ddamron on January 05, 2008, 01:00:42 pm
Hari and Totallymaxed,

You're both welcom to use my FTP if required.

Totallymaxed has the url/user/pass...

Dan
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: totallymaxed on January 05, 2008, 01:38:29 pm
Hari and Totallymaxed,

You're both welcom to use my FTP if required.

Totallymaxed has the url/user/pass...

Dan

Hey thanks Dan.

Hari upped the file size limit on his upload page... and all was ok.

Andrew

Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: coley on January 07, 2008, 03:41:48 pm
Quote
http://www.elekhomica.nl/product_info.php?cPath=91&products_id=707

br hari
Also found it here
http://www.smarthus.info/product_info.php?cPath=1_46_115&products_id=2281

-Coley.
Title: Re: Supporting the Seluxit Homecontroller USB Z-wave Interface
Post by: hari on January 07, 2008, 05:46:44 pm
Hi Guys,

some news from the Z-Wave front: A danish company (seluxit.com) produces the ViaSENS Homecontroller. It's a european version (868MHz) usb device. Daniel Lux from Seluxit provides me with a test sample. It should be accessible via /dev/ttyACM0 (cdc-acm module).
They also are thinking about some encapsulation library for linux for the z-wave sdk (like the windows zwave.dll) and would appreciate any feedback or feature wishes.
totallymaxed: maybe you can lend me a few Z-wave components to test the interface for some days?

best regards,
Hari
Title: Re: Supporting the Seluxit Homecontroller USB Z-wave Interface
Post by: totallymaxed on January 07, 2008, 06:18:51 pm
Hi Guys,

some news from the Z-Wave front: A danish company (seluxit.com) produces the ViaSENS Homecontroller. It's a european version (868MHz) usb device. Daniel Lux from Seluxit provides me with a test sample. It should be accessible via /dev/ttyACM0 (cdc-acm module).
They also are thinking about some encapsulation library for linux for the z-wave sdk (like the windows zwave.dll) and would appreciate any feedback or feature wishes.
totallymaxed: maybe you can lend me a few Z-wave components to test the interface for some days?

best regards,
Hari

Hi Hari,

The only product that i can see on there site is the http://seluxit.com/VS_Controllers.html (http://seluxit.com/VS_Controllers.html) which is a Z-wave connected energy meter. This is interesting in its own right for sure but it cannot be connected to z-wave switches but only to Seluxit's own z-wave remote metering units. Is this unit the one you refer to in your post above?

It really does not make much sense to loan z-wave hardware as the cost of shipping it to you and back again is more than the value of the units (in most cases).

Andrew
Title: Re: Supporting the Seluxit Homecontroller USB Z-wave Interface
Post by: hari on January 07, 2008, 06:31:02 pm
The only product that i can see on there site is the http://seluxit.com/VS_Controllers.html (http://seluxit.com/VS_Controllers.html) which is a Z-wave connected energy meter. This is interesting in its own right for sure but it cannot be connected to z-wave switches but only to Seluxit's own z-wave remote metering units. Is this unit the one you refer to in your post above?
No, you have to scroll down on the page. It's the viaSENS Homecontroller.

EDIT: they also have a nice Z-Wave multifunction sensor (http://www.seluxit.com/Multisensor.html) and sell the danfoss RA-plus, too.

best regards,
Hari
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: coley on January 07, 2008, 07:14:21 pm
ZCU201 and ZDW232 ordered for my experiments, from http://www.elekhomica.nl/
noticed all plug in modules were eu type plugs :(
have to go elsewhere for UK/Ireland 3pin plugin modules, which is a pain as shipping adds up!!

-Coley.

Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: Domodude on January 10, 2008, 09:41:21 am
Hi everyone,

I also noticed that there is a new unit ZCS201 available, which is direct RS232 (I think)  8). Does anyone actually own one of these, or did experiments with it?

Cheers,

Mark
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: hari on January 10, 2008, 11:30:30 am
Hi everyone,

I also noticed that there is a new unit ZCS201 available, which is direct RS232 (I think)  8). Does anyone actually own one of these, or did experiments with it?

Cheers,

Mark

i don't have found a shop with that on stock,

best regards,
Hari
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: totallymaxed on January 10, 2008, 11:31:55 am
Hi everyone,

I also noticed that there is a new unit ZCS201 available, which is direct RS232 (I think)  8). Does anyone actually own one of these, or did experiments with it?

Cheers,

Mark


We have ordered some of those for testing here... will report back once we have them ;-)
Title: Re: Supporting the Seluxit Homecontroller USB Z-wave Interface
Post by: totallymaxed on January 10, 2008, 12:00:43 pm
The only product that i can see on there site is the http://seluxit.com/VS_Controllers.html (http://seluxit.com/VS_Controllers.html) which is a Z-wave connected energy meter. This is interesting in its own right for sure but it cannot be connected to z-wave switches but only to Seluxit's own z-wave remote metering units. Is this unit the one you refer to in your post above?
No, you have to scroll down on the page. It's the viaSENS Homecontroller.

EDIT: they also have a nice Z-Wave multifunction sensor (http://www.seluxit.com/Multisensor.html) and sell the danfoss RA-plus, too.

best regards,
Hari


Got it... didn't scroll far enough!

Yes the multi-sensor looks very interesting indeed. Are they shipping those?
Title: Re: Supporting the Seluxit Homecontroller USB Z-wave Interface
Post by: hari on January 10, 2008, 01:11:19 pm
No, you have to scroll down on the page. It's the viaSENS Homecontroller.

Got it... didn't scroll far enough!

Yes the multi-sensor looks very interesting indeed. Are they shipping those?
was announced for Dec. 2007. I hope to get a test sample from Mr. Lux after having the Homecontroller working.
I will ask him for availability.

best regards,
Hari
Title: Re: Supporting the Seluxit Homecontroller USB Z-wave Interface
Post by: totallymaxed on January 10, 2008, 01:15:45 pm
No, you have to scroll down on the page. It's the viaSENS Homecontroller.

Got it... didn't scroll far enough!

Yes the multi-sensor looks very interesting indeed. Are they shipping those?
was announced for Dec. 2007. I hope to get a test sample from Mr. Lux after having the Homecontroller working.
I will ask him for availability.

best regards,
Hari

ok understood.

Do you have the HomeController yet? If yes have you looked into its usb interface/chipset for driver development etc?
Title: Re: Supporting the Seluxit Homecontroller USB Z-wave Interface
Post by: hari on January 14, 2008, 08:15:18 pm
ok understood.

Do you have the HomeController yet? If yes have you looked into its usb interface/chipset for driver development etc?
the home controller came today. I can verify that the device is available as /dev/ttyACM0 on LMCE (0704). For now i tricked lmce into using the HomeController by adding the ZWave device manually and assigning the com port (UpdateAvailableSerialports.sh needs a tweak for that to recognize the device file). Further research showed that we probably only have to add the usb device id to the device template in the database. I can engage "learn mode" for device download from a primary controller without errors.

More results to come (hari needs more hardware ;) )

EDIT: the logs with startup and output after sending:
/usr/pluto/bin/MessageSend localhost 0 99 1 757 9 ""
Code: [Select]
dcerouter_48407:/var/log/pluto# /usr/pluto/bin/ZWave -d 99
ZWave, v.2.0.0.44.0709022200
Visit www.plutohome.com for source code and license information

05      01/14/08 20:17:15.180           Creating child 100 <0xb79a96d0>
05      01/14/08 20:17:15.180           Note: Device manager has attached a device of type 1820 that this has no custom event handler for.  It will not fire events. <0xb79a96d0>
05      01/14/08 20:17:15.180           Note: Device manager has attached a device of type 1820 that this has no custom handler for.  This is normal for IR. <0xb79a96d0>
05      01/14/08 20:17:29.672           ZWave::ReportChildDevices 2.xx API ! <0xb49a2b90>
05      01/14/08 20:19:30.004           -------------------------- Job Timeout _________ <0xb69a6b90>

best regards,
Hari

Title: Re: Supporting the Seluxit Homecontroller USB Z-wave Interface
Post by: hari on January 14, 2008, 09:09:05 pm
Yes the multi-sensor looks very interesting indeed. Are they shipping those?
the sensor will be released in about 6 to 8 weeks.

best regards,
Hari
Title: Re: Supporting the Seluxit Homecontroller USB Z-wave Interface
Post by: totallymaxed on January 14, 2008, 09:49:09 pm
ok understood.

Do you have the HomeController yet? If yes have you looked into its usb interface/chipset for driver development etc?
the home controller came today. I can verify that the device is available as /dev/ttyACM0 on LMCE (0704). For now i tricked lmce into using the HomeController by adding the ZWave device manually and assigning the com port (UpdateAvailableSerialports.sh needs a tweak for that to recognize the device file). Further research showed that we probably only have to add the usb device id to the device template in the database. I can engage "learn mode" for device download from a primary controller without errors.

More results to come (hari needs more hardware ;) )

EDIT: the logs with startup and output after sending:
/usr/pluto/bin/MessageSend localhost 0 99 1 757 9 ""
Code: [Select]
dcerouter_48407:/var/log/pluto# /usr/pluto/bin/ZWave -d 99
ZWave, v.2.0.0.44.0709022200
Visit www.plutohome.com for source code and license information

05      01/14/08 20:17:15.180           Creating child 100 <0xb79a96d0>
05      01/14/08 20:17:15.180           Note: Device manager has attached a device of type 1820 that this has no custom event handler for.  It will not fire events. <0xb79a96d0>
05      01/14/08 20:17:15.180           Note: Device manager has attached a device of type 1820 that this has no custom handler for.  This is normal for IR. <0xb79a96d0>
05      01/14/08 20:17:29.672           ZWave::ReportChildDevices 2.xx API ! <0xb49a2b90>
05      01/14/08 20:19:30.004           -------------------------- Job Timeout _________ <0xb69a6b90>

best regards,
Hari



Hey thats great Hari... give us another update tomorrow ;-)
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: Domodude on January 14, 2008, 10:07:13 pm
I also noticed that there is a new unit ZCS201 available, which is direct RS232 (I think)  8). Does anyone actually own one of these, or did experiments with it?
We have ordered some of those for testing here... will report back once we have them ;-)

Of course, I could not wait on that  ;)
My ZCS201 should come in tomorrow, I'll check it out and report on the results. Supposedly it really does have a serial connector, so we'll see what happens. A previous thread (http://forum.linuxmce.org/index.php?topic=2766.msg13509#msg13509) mentioned the ZCS201, but refers to the USB connector! Hmmm... I am hoping that was a typo!  ;D

Mark
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: hari on January 14, 2008, 10:30:42 pm
Of course, I could not wait on that  ;)
My ZCS201 should come in tomorrow, I'll check it out and report on the results. Supposedly it really does have a serial connector, so we'll see what happens. A previous thread (http://forum.linuxmce.org/index.php?topic=2766.msg13509#msg13509) mentioned the ZCS201, but refers to the USB connector! Hmmm... I am hoping that was a typo!  ;D
where did you get that beast from? i was searching for ages..

btw: i added the usb device id to the Z-Wave template and the viaSENS Homecontroller got auto detected by pluto. But i think there is a problem with the function "TranslateSerialUSB" from "trunk/src/PlutoUtils":
Code: [Select]
42:         sCmd += "ls -l /sys/bus/usb-serial/devices/ | grep '" + sPciId + ".*-" + sUsbId + ":.*' >" + tmpFile;
houston, the device class is not serial but ACM:
Code: [Select]
[91845.244000] drivers/usb/class/cdc-acm.c: v0.25:USB Abstract Control Model driver for USB modems and ISDN adapters
so this is a perfect working serial port (i wish more rs232/usb bridge chip manufacturers would use that generic approach) but pluto does not know *grin*
As a quick fix i suggest running the following:
Code: [Select]
ln -s /dev/ttyACM0 /dev/ttyS_ZWAVE_0
/usr/pluto/bin/UpdateAvailableSerialPorts.sh
and select the port in the device data of the ZWave device.

question: anybody nearside berlin with Z-Wave equipment?

best regards,
Hari
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: hari on January 15, 2008, 01:58:04 am
works for me, the device is full pnp now:
Code: [Select]
hari@dcerouter:/usr/src/svn/trunk/trunk/src/PlutoUtils$ svn diff LinuxSerialUSB.cpp
Index: LinuxSerialUSB.cpp
===================================================================
--- LinuxSerialUSB.cpp  (revision 1464)
+++ LinuxSerialUSB.cpp  (working copy)
@@ -39,7 +39,8 @@
        if( sIPAddress.empty()==false )
                sCmd = "ssh " + sIPAddress + " ";
 
-       sCmd += "ls -l /sys/bus/usb-serial/devices/ | grep '" + sPciId + ".*-" + sUsbId + ":.*' >" + tmpFile;
+       sCmd += "find /sys/devices -name '*tty*' | grep '/tty:' | grep usb | grep '" + sPciId + ".*-" + sUsbId + ":.*' | sed 's/tty://g' >" + tmpFile;
+
        system(sCmd.c_str());
 
        vector<string> vectStr;
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: coley on January 15, 2008, 03:08:09 pm
wow! a lot happens in a few days, was away for a bit.
my zwave devices arrived so hopefully should get to play with them in the next few days.

btw does anyone know what the extra connector on the ZCU201 is besides the pwr and USB?

-Coley.
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: totallymaxed on January 15, 2008, 03:52:27 pm
I also noticed that there is a new unit ZCS201 available, which is direct RS232 (I think)  8). Does anyone actually own one of these, or did experiments with it?
We have ordered some of those for testing here... will report back once we have them ;-)

Of course, I could not wait on that  ;)
My ZCS201 should come in tomorrow, I'll check it out and report on the results. Supposedly it really does have a serial connector, so we'll see what happens. A previous thread (http://forum.linuxmce.org/index.php?topic=2766.msg13509#msg13509) mentioned the ZCS201, but refers to the USB connector! Hmmm... I am hoping that was a typo!  ;D

Mark


Mark there are two models of the ZCU201.... one USB and one serial. Hope you get the version you want ;-)
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: Domodude on January 15, 2008, 07:59:22 pm
My ZCS201 should come in tomorrow, I'll check it out and report on the results. Supposedly it really does have a serial connector, so we'll see what happens.

It's in, and it is RS232!  8)

OK. Hmm. Add interface, template 1754, go to advanced, send command "status report". Nothing. I am sure I am doing something wrong here.  :-[

Could anyone give me a pointer or two so I can check if this thing is supported by linuxmce? I'd love to control my plugin dimmers as well, but I suppose one step at a time!

Mark
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: Domodude on January 15, 2008, 08:01:54 pm
My ZCS201 should come in tomorrow
where did you get that beast from? i was searching for ages..

I got it from mypowershop.eu, a Dutch internet shop. But even though it is RS232, I am not sure yet it actually works... :-\
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: Domodude on January 15, 2008, 08:03:31 pm
Mark there are two models of the ZCU201.... one USB and one serial. Hope you get the version you want ;-)

Actually, the models can be told apart by the third letter. I got a ZCS201, not a ZCU201!  ;)
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: hari on January 15, 2008, 08:13:50 pm
Mark there are two models of the ZCU201.... one USB and one serial. Hope you get the version you want ;-)

Actually, the models can be told apart by the third letter. I got a ZCS201, not a ZCU201!  ;)
where did you get that beast from? i was searching for ages..
Title: Re: Supporting the ACT Solutions ZCS201 Serial Z-wave Interface
Post by: hari on January 16, 2008, 02:25:29 pm
news from the Z-Wave front:
after some device tweaking and package installation (mysterious indeed) with domodude we got the ZWave device to run with the ZCS201. As domodude has no primary controller, too, we have to wait until the shippings arrive for further tests.

best regards,
Hari
Title: Re: Supporting the ACT Solutions ZCS201 Serial Z-wave Interface
Post by: totallymaxed on January 16, 2008, 03:27:32 pm
news from the Z-Wave front:
after some device tweaking and package installation (mysterious indeed) with domodude we got the ZWave device to run with the ZCS201. As domodude has no primary controller, too, we have to wait until the shippings arrive for further tests.

best regards,
Hari

Hey Hari thats great... when you get a chance can you post the steps you needed to do to get the ZCS201 working? I will then test that here and we will try and get it into the 0710
Title: Re: Supporting the ACT Solutions ZCS201 Serial Z-wave Interface
Post by: hari on January 16, 2008, 03:37:54 pm
Hey Hari thats great... when you get a chance can you post the steps you needed to do to get the ZCS201 working? I will then test that here and we will try and get it into the 0710
we simply did a "ln -s /dev/ttyS0 /dev/ttyS_ZWAVE_0" and "UpdateAvailableSerialPorts.sh" and used that devicefile in the device config, because of some obscure reason the manually added device did not like the "/dev/ttyS0" port..

I'll keep you posted,

best regards,
Hari
Title: Re: Supporting the ACT Solutions ZCS201 Serial Z-wave Interface
Post by: totallymaxed on January 16, 2008, 03:58:37 pm
Hey Hari thats great... when you get a chance can you post the steps you needed to do to get the ZCS201 working? I will then test that here and we will try and get it into the 0710
we simply did a "ln -s /dev/ttyS0 /dev/ttyS_ZWAVE_0" and "UpdateAvailableSerialPorts.sh" and used that devicefile in the device config, because of some obscure reason the manually added device did not like the "/dev/ttyS0" port..

I'll keep you posted,

best regards,
Hari


We should get that added to the SVN somehow so that it can be easily chosen by users. With the new common SVN coming that should be easily achieved ;-)
Title: Re: Supporting the ACT Solutions ZCS201 Serial Z-wave Interface
Post by: hari on January 16, 2008, 04:14:39 pm
We should get that added to the SVN somehow so that it can be easily chosen by users. With the new common SVN coming that should be easily achieved ;-)
to become of topic maybe you want to contribute to the foundation thread?

best regards,
Hari
Title: Re: Supporting the ACT Solutions ZCS201 Serial Z-wave Interface
Post by: totallymaxed on January 16, 2008, 04:38:22 pm
We should get that added to the SVN somehow so that it can be easily chosen by users. With the new common SVN coming that should be easily achieved ;-)
to become of topic maybe you want to contribute to the foundation thread?

best regards,
Hari

;-) will do
Title: Re: Supporting the ACT Solutions ZCS201 Serial Z-wave Interface
Post by: hari on January 18, 2008, 01:18:39 am
some progress with Domodude and his ZCS201: we were able to download a device to the ZCS201. More tests to come (some problems with transfer of the full config).

hope to get my ZTH200 tomorrow for further tests with the Seluxit dongle.

best regards,
Hari
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: Domodude on January 18, 2008, 08:12:55 am
Morning all,

Almost there. As Hari wrote, we got a lot closer to a working Z-wave setup. The only problem remaining, I hope, is the transfer of the config from the ZTH200 Homepro primary controller to LinuxMCE.

(I had some trouble getting the ZCS201 recognized by lmce, but I think that it eventually worked again after I got rid of all interfaces, rebooted the core, and then started over. That included attaching the ZCS201, turning on the system, adding the interface in the web setup, update, reload dcerouter. I think that was all it took. I will replay everything once the download problem is out of the way.)

Andrew, I understand you own a ZTH200? Could you tell me if something is wrong here?
After this, lmce has only one light as a child device to the zcs201. If I select Transfer FULL Config, the transfer somehow fails, I think it mentions a Data Error.

Any ideas?

Thanks,
Mark
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: 1audio on January 18, 2008, 08:34:10 am
LMCE's ZWave supports the devices. It doesn't know scenes from the controller. In fact in ZWave controller scenes can only be transfered to identical controllers because they all do the UI very differently (and most are really awful).

If you have one device that is all you will see in LMCE. Once its there you can name it and build scenes and scenarios around it.

Did you add the device from the web interface or from the wizard?

I'm really encouraged that we can add a serial ZWave device since the Leviton is serial, and has the feedback from the Leviton switches.
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: Domodude on January 18, 2008, 09:21:15 am
LMCE's ZWave supports the devices. It doesn't know scenes from the controller. In fact in ZWave controller scenes can only be transfered to identical controllers because they all do the UI very differently (and most are really awful).
If you have one device that is all you will see in LMCE. Once its there you can name it and build scenes and scenarios around it.

At the time I tried it, I had two pluggable dimmers units, which where put in group 1 and group 2 of the controller, respectively. Are you saying I should just add all dimmers to the first group on the Homepro controller, and then do further setup in lmce after the upload of the config?

Quote
Did you add the device from the web interface or from the wizard?

I used the web interface; I selected "add device" under "Interfaces". I selected manufacturer Pluto, and just picked the ZWave option after updating the filter. Again, I still need to double-check this. However, the bottom line is that the interface can be recognized (running 0704 here).

Cheers
Mark
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: hari on January 18, 2008, 02:57:17 pm
works for me with the Seluxit viaSENS Homecontroller, a ZTH200 and a ZDP200 plug.
Download configuration works perfect (dongle flashes red). That created a child device that is now fully controllable!

Yippie, ZWave with Linux in Europe ;)

best regards,
Hari
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: Domodude on January 18, 2008, 03:16:49 pm
Yippie, ZWave with Linux in Europe ;)

You beat me to it!  ;)

I will try all three dimmer plugs in the same group on the homepro controller, and then upload the config. How did you do your config transfer to lmce, Hari?

Mark
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: hari on January 18, 2008, 03:52:08 pm
Yippie, ZWave with Linux in Europe ;)

You beat me to it!  ;)

I will try all three dimmer plugs in the same group on the homepro controller, and then upload the config. How did you do your config transfer to lmce, Hari?

Mark


only transfered system configuration as suggested by 1audio. As i have only one plug i don't have multiple groups.

best regards,
Hari
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: Domodude on January 18, 2008, 09:59:46 pm
I now get this in 62_ZWave.log:
...
1   01/18/08 21:44:12   62 (spawning-device)   Starting... 4
1   01/18/08 21:44:12   62 (spawning-device)   Found /usr/pluto/bin/ZWave
05   01/18/08 21:44:17.052      Creating child 63 <0xb78dd6d0>
05   01/18/08 21:44:17.052      Note: Device manager has attached a device of type 1820 that this has no custom event handler for.  It will not fire events. <0xb78dd6d0>
05   01/18/08 21:44:17.052      Note: Device manager has attached a device of type 1820 that this has no custom handler for.  This is normal for IR. <0xb78dd6d0>
05   01/18/08 21:44:17.053      Creating child 69 <0xb78dd6d0>
05   01/18/08 21:44:17.053      Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0xb78dd6d0>
05   01/18/08 21:44:17.053      Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0xb78dd6d0>
05   01/18/08 21:44:17.053      Creating child 70 <0xb78dd6d0>
05   01/18/08 21:44:17.053      Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0xb78dd6d0>
05   01/18/08 21:44:17.053      Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0xb78dd6d0>
...


Those two devices are supposed to be dimmers. I see them, but cannot properly send commands to them. Sending directly to the dimmers gets me an OK response, but nothing happens. The ZWave.log file prints:
05   01/18/08 21:54:35.035      ### Go to timeout queue <0xb68dab90>
05   01/18/08 21:54:35.035      ### skip the next job from timeout queue <0xb68dab90>
05   01/18/08 21:54:58.011      ### Go to timeout queue <0xb68dab90>
05   01/18/08 21:54:58.011      ### skip the next job from timeout queue <0xb68dab90>

 ???

Any ideas? I think I'd like to thoroughly clean up all children of the ZCS201 and resend the config, would deleting these devices and reloading dcerouter be enough?

Cheers,
Mark
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: 1audio on January 19, 2008, 07:39:56 am
 I'm attaching my log for reference. I have a few devices including one PIR device. I'm not sure if it looks right or not, but its almost all working.


Code: [Select]
05 12/30/07 0:00:07.520 Connect() failed, Error Code 111 (Connection refused)) <0xb79166d0>
05 12/30/07 0:00:29.117 Creating child 35 <0xb79166d0>
05 12/30/07 0:00:29.117 Note: Device manager has attached a device of type 1820 that this has no custom event handler for.  It will not fire events. <0xb79166d0>
05 12/30/07 0:00:29.117 Note: Device manager has attached a device of type 1820 that this has no custom handler for.  This is normal for IR. <0xb79166d0>
05 12/30/07 0:00:29.117 Creating child 232 <0xb79166d0>
05 12/30/07 0:00:29.117 Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0xb79166d0>
05 12/30/07 0:00:29.117 Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0xb79166d0>
05 12/30/07 0:00:29.117 Creating child 233 <0xb79166d0>
05 12/30/07 0:00:29.117 Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0xb79166d0>
05 12/30/07 0:00:29.117 Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0xb79166d0>
05 12/30/07 0:00:29.118 Creating child 234 <0xb79166d0>
05 12/30/07 0:00:29.118 Note: Device manager has attached a device of type 37 that this has no custom event handler for.  It will not fire events. <0xb79166d0>
05 12/30/07 0:00:29.118 Note: Device manager has attached a device of type 37 that this has no custom handler for.  This is normal for IR. <0xb79166d0>
05 12/30/07 0:00:29.118 Creating child 235 <0xb79166d0>
05 12/30/07 0:00:29.118 Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0xb79166d0>
05 12/30/07 0:00:29.118 Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0xb79166d0>
05 12/30/07 0:00:29.118 Creating child 236 <0xb79166d0>
05 12/30/07 0:00:29.118 Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0xb79166d0>
05 12/30/07 0:00:29.118 Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0xb79166d0>
05 12/30/07 0:00:29.118 Creating child 237 <0xb79166d0>
05 12/30/07 0:00:29.118 Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0xb79166d0>
05 12/30/07 0:00:29.118 Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0xb79166d0>
05 12/30/07 0:00:29.118 Creating child 238 <0xb79166d0>
05 12/30/07 0:00:29.118 Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0xb79166d0>
05 12/30/07 0:00:29.118 Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0xb79166d0>
05 12/30/07 0:00:29.118 Creating child 239 <0xb79166d0>
05 12/30/07 0:00:29.118 Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0xb79166d0>
05 12/30/07 0:00:29.118 Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0xb79166d0>
05 12/30/07 0:00:29.118 Creating child 240 <0xb79166d0>
05 12/30/07 0:00:29.118 Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0xb79166d0>
05 12/30/07 0:00:29.118 Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0xb79166d0>
05 12/30/07 0:00:29.118 Creating child 241 <0xb79166d0>
05 12/30/07 0:00:29.118 Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0xb79166d0>
05 12/30/07 0:00:29.118 Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0xb79166d0>
05 12/30/07 0:00:29.118 Creating child 242 <0xb79166d0>
05 12/30/07 0:00:29.118 Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0xb79166d0>
05 12/30/07 0:00:29.118 Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0xb79166d0>
05 12/30/07 0:00:29.118 Creating child 243 <0xb79166d0>
05 12/30/07 0:00:29.118 Note: Device manager has attached a device of type 1813 that this has no custom event handler for.  It will not fire events. <0xb79166d0>
05 12/30/07 0:00:29.118 Note: Device manager has attached a device of type 1813 that this has no custom handler for.  This is normal for IR. <0xb79166d0>
05 12/30/07 0:00:29.118 Creating child 244 <0xb79166d0>
05 12/30/07 0:00:29.118 Note: Device manager has attached a device of type 37 that this has no custom event handler for.  It will not fire events. <0xb79166d0>
05 12/30/07 0:00:29.118 Note: Device manager has attached a device of type 37 that this has no custom handler for.  This is normal for IR. <0xb79166d0>
05 12/30/07 0:00:29.118 Creating child 245 <0xb79166d0>
05 12/30/07 0:00:29.118 Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0xb79166d0>
05 12/30/07 0:00:29.119 Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0xb79166d0>
05 12/30/07 0:00:29.119 Creating child 246 <0xb79166d0>
05 12/30/07 0:00:29.119 Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0xb79166d0>
05 12/30/07 0:00:29.119 Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0xb79166d0>
05 12/30/07 0:00:29.119 Creating child 247 <0xb79166d0>
05 12/30/07 0:00:29.119 Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0xb79166d0>
05 12/30/07 0:00:29.119 Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0xb79166d0>
05 12/30/07 0:00:29.119 Creating child 248 <0xb79166d0>
05 12/30/07 0:00:29.119 Note: Device manager has attached a device of type 37 that this has no custom event handler for.  It will not fire events. <0xb79166d0>
05 12/30/07 0:00:29.119 Note: Device manager has attached a device of type 37 that this has no custom handler for.  This is normal for IR. <0xb79166d0>
05 12/30/07 0:00:29.119 Creating child 252 <0xb79166d0>
05 12/30/07 0:00:29.119 Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0xb79166d0>
05 12/30/07 0:00:29.119 Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0xb79166d0>
== ATTEMPT FRESH START ==
1 12/30/07 00:24:37 /usr/pluto/bin/Spawn_Device.sh 34 (spawning-device) 13855 Dev: 34; Already Running list: 15,16,17,18,27,
== FRESH START ==
1 12/30/07 00:24:37 /usr/pluto/bin/Spawn_Device.sh 34 (spawning-device) device: 34 ip: localhost cmd_line: ZWave
0 12/30/07 00:24:37 34 (spawning-device) Entering 34
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: ddamron on January 19, 2008, 10:02:35 am
1audio,

I get those messages for ALL child devices in all my coding too.
From what I can tell, they can be safely ignored.
38 is Lightswitch Dimmable, 37 is Lightswitch ON/OFF, 1820 and 1813 I'm not sure about..

HTH,

Dan
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: totallymaxed on January 19, 2008, 02:31:37 pm
Morning all,

Almost there. As Hari wrote, we got a lot closer to a working Z-wave setup. The only problem remaining, I hope, is the transfer of the config from the ZTH200 Homepro primary controller to LinuxMCE.

(I had some trouble getting the ZCS201 recognized by lmce, but I think that it eventually worked again after I got rid of all interfaces, rebooted the core, and then started over. That included attaching the ZCS201, turning on the system, adding the interface in the web setup, update, reload dcerouter. I think that was all it took. I will replay everything once the download problem is out of the way.)

Andrew, I understand you own a ZTH200? Could you tell me if something is wrong here?
  • Add units to the ZTH200. I have one plugin dimmer unit on group 1, 3 and 6 each.
  • From setup, select transfer partial configuration
  • The ZTH200 will tell me Transfer Successful (or something like it)
After this, lmce has only one light as a child device to the zcs201. If I select Transfer FULL Config, the transfer somehow fails, I think it mentions a Data Error.

Any ideas?

Thanks,
Mark


Yes we use the ZTH200 Master Controller/remote. We always use 'transfer full config' but we do see a transfer error sometimes. Just resend a few times until you get a good transfer. Are you using the Lighting Wizard to manage the transfer/addition of the lights?
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: 1audio on January 19, 2008, 05:18:20 pm
1813 and possibly 1820 are additional controllers on the network or the PIR. I have 3 additional ZWave controllers in the system which should explain that. Or they may be the PIR. I have one light with a device number after a large gap. It gets dumped buy the code and needs to be re-added with almost every router reload if I want to use it.
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: Domodude on January 19, 2008, 06:37:01 pm
Andrew, I understand you own a ZTH200? Could you tell me if something is wrong here?
Are you using the Lighting Wizard to manage the transfer/addition of the lights?

Thanks. I will try to use the full config transfer.

I am not using the lighting wizard, because the RS232 is not plug'n'play. It would be great to use the wizard, but so far I have had no luck. So, it's a matter of manually adding the interface, and then transfering the settings...

Mark
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: totallymaxed on January 19, 2008, 06:48:14 pm
Andrew, I understand you own a ZTH200? Could you tell me if something is wrong here?
Are you using the Lighting Wizard to manage the transfer/addition of the lights?

Thanks. I will try to use the full config transfer.

I am not using the lighting wizard, because the RS232 is not plug'n'play. It would be great to use the wizard, but so far I have had no luck. So, it's a matter of manually adding the interface, and then transfering the settings...

Mark

ok... well under the hood the same code is being called so doing the upload from Web Admin amounts to the same thing.
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: Domodude on January 19, 2008, 06:51:29 pm
Come to think of it....

I have not yet been able to get the floorplan function to work. I added my lights thorugh the "Download Config" route on the web admin site, and added the lights to my map. However, I see no lights on the map on orbiters!

Another thing: reaction to the web interface is sometimes quite slow, or the command does not get processed at all. To any of you experienced Z-wave users: Is that normal?

Thanks,
Mark
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: 1audio on January 19, 2008, 08:20:02 pm
The lights won't appear until you rebuild the Orbiter. Have you reset the router and rebuilt the Orbiters?
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: totallymaxed on January 19, 2008, 09:06:56 pm
Come to think of it....

I have not yet been able to get the floorplan function to work. I added my lights thorugh the "Download Config" route on the web admin site, and added the lights to my map. However, I see no lights on the map on orbiters!

Another thing: reaction to the web interface is sometimes quite slow, or the command does not get processed at all. To any of you experienced Z-wave users: Is that normal?

Thanks,
Mark


After adding your lights and then adding them to the lighting floorplan you must do a regen all. Then they should appear on the lighting floor plan.
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: 1audio on January 19, 2008, 09:28:55 pm
ZWave for a single device should be pretty quick. However many devices responding or network problems will slow ZWave down to a crawl. Every device in the system needs to get from the controller to the device to be live or the system will stall looking for them. I usually get almost instant response.
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: Domodude on January 19, 2008, 10:22:59 pm
 >:(
I am not a happy camper. Got everything recognized, including the three dimmers, I put them on my floorplan, and I even have the option of selecting 10%, 20% etc.

That's the good new. Bad news is that  the dimming to let's say 20% didn't do anything at all to the light. So, just to make sure, I reset the dcerouter and regenerated all orbiters. But after that exercise, all three dimmers are gone.

Code: [Select]
Sat Jan 19 22:15:57 CET 2008 Restart
========== NEW LOG SECTION ==========
1 01/19/08 22:16:05 71 (spawning-device) Starting... 8
1 01/19/08 22:16:05 71 (spawning-device) Found /usr/pluto/bin/ZWave
05 01/19/08 22:16:08.322 Creating child 72 <0xb79186d0>
05 01/19/08 22:16:08.326 Note: Device manager has attached a device of type 1820 that this has no custom event handler for.  It will not fire events. <0xb79186d0>
05 01/19/08 22:16:08.326 Note: Device manager has attached a device of type 1820 that this has no custom handler for.  This is normal for IR. <0xb79186d0>
05 01/19/08 22:16:08.326 Creating child 80 <0xb79186d0>
05 01/19/08 22:16:08.326 Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0xb79186d0>
05 01/19/08 22:16:08.326 Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0xb79186d0>
05 01/19/08 22:16:08.326 Creating child 81 <0xb79186d0>
05 01/19/08 22:16:08.326 Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0xb79186d0>
05 01/19/08 22:16:08.326 Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0xb79186d0>
05 01/19/08 22:16:08.326 Creating child 82 <0xb79186d0>
05 01/19/08 22:16:08.326 Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0xb79186d0>
05 01/19/08 22:16:08.326 Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0xb79186d0>
05 01/19/08 22:17:42.016 Got a reload command from 0  <0xb5112b90>
05 01/19/08 22:17:42.519 void ClientSocket::Disconnect() on this socket: 0x809a1e8 (m_Socket: 7) <0xb79186d0>
Return code: 2
2 01/19/08 22:17:42 71 (spawning-device) Device requests restart... count=8/50 dev=71
Sat Jan 19 22:17:42 CET 2008 Restart
========== NEW LOG SECTION ==========
1 01/19/08 22:17:50 71 (spawning-device) Starting... 8
1 01/19/08 22:17:50 71 (spawning-device) Found /usr/pluto/bin/ZWave
05 01/19/08 22:17:57.040 ### Go to timeout queue <0xb68e2b90>
05 01/19/08 22:17:57.040 ### execute the next job from timeout queue <0xb68e2b90>
05 01/19/08 22:17:57.040 ZWJobInitialize::timeoutHandler <0xb68e2b90>
05 01/19/08 22:18:02.041 ### Go to timeout queue <0xb68e2b90>
05 01/19/08 22:18:02.041 ### execute the next job from timeout queue <0xb68e2b90>
05 01/19/08 22:18:02.041 ZWJobInitialize::timeoutHandler <0xb68e2b90>
05 01/19/08 22:18:03.610 Creating child 72 <0xb78e56d0>
05 01/19/08 22:18:03.610 Note: Device manager has attached a device of type 1820 that this has no custom event handler for.  It will not fire events. <0xb78e56d0>
05 01/19/08 22:18:03.610 Note: Device manager has attached a device of type 1820 that this has no custom handler for.  This is normal for IR. <0xb78e56d0>


I am stumped. What's going on here??
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: 1audio on January 19, 2008, 11:05:39 pm
What do you see under lighting on the Web panel?

This is similar to the problem I have loosing a light form the system.
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: Domodude on January 20, 2008, 11:27:29 am
What do you see under lighting on the Web panel?
This is similar to the problem I have loosing a light form the system.
I saw no lights anymore on the web panel.

Yesterday, I again added all lights, and so far have all three lights in the system.

When I test it now, nothing is happening when I try to turn them on or off using an XP orbiter.
Checking the interface log shows problems connecting to the ttyS0 ZWave device, so I'm gonna see what will happen after a reboot. *hmm* Even though ZWave works sometimes, as far as I am concerned it is far from stable/predictable (at least with a RS232 interface).

Mark
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: Domodude on January 20, 2008, 11:45:43 am
I'm just wondering...
I frequently have no reaction to commands (mostly through the web page), but get the following in the log:
05   01/20/08 11:41:53.005      ### Go to timeout queue <0xb6977b90>
05   01/20/08 11:41:53.005      ### skip the next job from timeout queue <0xb6977b90>

What do those two lines mean? It looks like the command will just get skipped.

What also happens is that I try three commands fairly quickly after each other, and I only get the above two lines once.  ??? I'd expect at least six lines. Is there a way to get more verbose debugging output?
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: hari on January 20, 2008, 11:53:17 am
I'm just wondering...
I frequently have no reaction to commands (mostly through the web page), but get the following in the log:
05   01/20/08 11:41:53.005      ### Go to timeout queue <0xb6977b90>
05   01/20/08 11:41:53.005      ### skip the next job from timeout queue <0xb6977b90>

What do those two lines mean? It looks like the command will just get skipped.

What also happens is that I try three commands fairly quickly after each other, and I only get the above two lines once.  ??? I'd expect at least six lines. Is there a way to get more verbose debugging output?

hmm, your serial port seems strange. Please try to use a usb/rs232 adapter.

best regards,
Hari
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: Domodude on January 20, 2008, 04:47:45 pm
Well this is strange!  ::)

I installed LMCE on a different machine, that I was previously using as an MD. And guess what! It works.

The wizard did not initially recognize the RS232 interface, of course. So I skipped it initially, then I went to the web panel and manually added a Pluto/ZWave device. This recognized the interface, and immediately the video-Lady came on. Just to make sure, I reloaded the dcerouter anyway. I went back to the Setup Wizard through the orbiter, and it recognized my interface. What's more, it already knew that I have three lights. Is that cool or what?  8) Every step from that point on was easy and just *worked*. It's still working after a core reboot (that was a gamble on the other setup!).

So it seems that the ZCS201 is fully supported, obivously aside from the PnP-functionality.

It also seems that there are computers that have some sort of serial port stupidity going on that prevents proper communication. At the moment, I don't feel like investigating anymore. Perhaps later!

Cheers (I'm gonna have a beer!),

Mark
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: hari on January 20, 2008, 07:37:24 pm
It also seems that there are computers that have some sort of serial port stupidity going on that prevents proper communication. At the moment, I don't feel like investigating anymore. Perhaps later!
somehow i knew that ;) Do you provide power to the interface with a brick?

best regards,
Hari
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: Domodude on January 20, 2008, 08:41:44 pm
Yes, the RS232 version will not function without one. The USB version can be powered through USB.
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: totallymaxed on January 20, 2008, 09:32:18 pm
Well this is strange!  ::)

I installed LMCE on a different machine, that I was previously using as an MD. And guess what! It works.

The wizard did not initially recognize the RS232 interface, of course. So I skipped it initially, then I went to the web panel and manually added a Pluto/ZWave device. This recognized the interface, and immediately the video-Lady came on. Just to make sure, I reloaded the dcerouter anyway. I went back to the Setup Wizard through the orbiter, and it recognized my interface. What's more, it already knew that I have three lights. Is that cool or what?  8) Every step from that point on was easy and just *worked*. It's still working after a core reboot (that was a gamble on the other setup!).

So it seems that the ZCS201 is fully supported, obivously aside from the PnP-functionality.

It also seems that there are computers that have some sort of serial port stupidity going on that prevents proper communication. At the moment, I don't feel like investigating anymore. Perhaps later!

Cheers (I'm gonna have a beer!),

Mark


Nice work Mark ;-)
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: PeteK on January 21, 2008, 02:04:03 am
Just out of curiosity, has anyone found a source for the ZCU101/ZCS101 U.S. Versions of these products?
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: hari on January 21, 2008, 11:30:24 pm
I did some munching to the spcp8x5 code and managed to compile and load the module on 0704. If somebody feels like sending me a ZCU201...

you can download the binary here: http://vt100.at/spcp8x5.ko

compile:
Code: [Select]
dcerouter_48407:/usr/src/spcp8x5# make
make -C /lib/modules/2.6.20-15-generic/build M=/usr/src/spcp8x5 modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.20-15-generic'
  CC [M]  /usr/src/spcp8x5/spcp8x5.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /usr/src/spcp8x5/spcp8x5.mod.o
  LD [M]  /usr/src/spcp8x5/spcp8x5.ko
make[1]: Leaving directory `/usr/src/linux-headers-2.6.20-15-generic'
dcerouter_48407:/usr/src/spcp8x5#

dmesg:
Code: [Select]
[165370.468000] usbcore: registered new interface driver spcp8x5
[165370.468000] /usr/src/spcp8x5/spcp8x5.c: SPCP8x5 USB to serial adaptor driver v0.01

here is the patch:
Code: [Select]
diff -u spcp8x5.orig/spcp8x5.c spcp8x5/spcp8x5.c
--- spcp8x5.orig/spcp8x5.c      2006-09-11 08:26:50.000000000 +0200
+++ spcp8x5/spcp8x5.c   2008-01-21 23:17:37.000000000 +0100
@@ -34,7 +34,6 @@
 };
 
 static struct usb_driver spcp8x5_driver = {
-       .owner                          = THIS_MODULE,
        .name                           = "spcp8x5",
        .probe                          = usb_serial_probe,
        .disconnect             = usb_serial_disconnect,
@@ -43,7 +42,6 @@
 
 // All of the device info needed for the spcp8x5 SIO serial converter
 static struct usb_serial_device_type spcp8x5_device = {
-       .owner                          = THIS_MODULE,
        .name                           = "SPCP8x5",
        .id_table                       = id_table,
        .num_interrupt_in       = 0,
@@ -379,20 +377,16 @@
                tty_flag = TTY_FRAME;
        trace("tty_flag = %d\n",tty_flag);
 
-       tty = port->tty;
-       if (tty && urb->actual_length) {
-               // overrun is special, not associated with a char
-               if (status & UART_OVERRUN_ERROR)
-                       tty_insert_flip_char(tty, 0, TTY_OVERRUN);
-
-               for (i = 0; i < urb->actual_length; ++i) {
-                       if (tty->flip.count >= TTY_FLIPBUF_SIZE) {
-                               tty_flip_buffer_push(tty);
-                       }
-                       tty_insert_flip_char (tty, data[i], tty_flag);
-               }
-               tty_flip_buffer_push (tty);
-       }
+        tty = port->tty;
+        if (tty && urb->actual_length) {
+                tty_buffer_request_room(tty, urb->actual_length + 1);
+                /* overrun is special, not associated with a char */
+                if (status & UART_OVERRUN_ERROR)
+                        tty_insert_flip_char(tty, 0, TTY_OVERRUN);
+                for (i = 0; i < urb->actual_length; ++i)
+                        tty_insert_flip_char(tty, data[i], tty_flag);
+                tty_flip_buffer_push(tty);
+        }
 
        // Schedule the next read _if_ we are still open
        if (port->open_count) {
diff -u spcp8x5.orig/spcp8x5.h spcp8x5/spcp8x5.h
--- spcp8x5.orig/spcp8x5.h      2006-09-25 08:11:35.000000000 +0200
+++ spcp8x5/spcp8x5.h   2008-01-21 23:02:49.000000000 +0100
@@ -19,7 +19,6 @@
 #define SPCP8x5_835_VID                0x04fc
 #define SPCP8x5_835_PID                0x0231
 
-#include <linux/config.h>
 #include <linux/kernel.h>
 #include <linux/errno.h>
 #include <linux/init.h>
diff -u spcp8x5.orig/usb-serial.h spcp8x5/usb-serial.h
--- spcp8x5.orig/usb-serial.h   2004-12-24 22:35:50.000000000 +0100
+++ spcp8x5/usb-serial.h        2008-01-21 23:03:02.000000000 +0100
@@ -54,7 +54,6 @@
 #ifndef __LINUX_USB_SERIAL_H
 #define __LINUX_USB_SERIAL_H
 
-#include <linux/config.h>
 #include <linux/kref.h>
 
 #define SERIAL_TTY_MAJOR       188     /* Nice legal number now */
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: PeteK on January 22, 2008, 07:00:01 am
Guys--

I've started to update the Wiki with the implementation details I learned from communicating with Eugen on the Pluto Zwave implementation and with with going over his code to create an Insteon PLC driver.  The code could use a clean up and a refresh to bring it up to the current Z-Wave standard of functionality and I think documenting its current fucntionality is a good first step.  I'll be adding more to it over the next few days.

http://wiki.linuxmce.org/index.php/ZWave#Implementation

If anyone has a ZCU201 and has any questions on the current implementation, I'll be glad to help.

-Pete
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: Domodude on January 22, 2008, 10:44:14 am
Hi,

Merten has a fairly substantial Z-wave product line, and on February 8th, a salesperson will come by and show me some of their stuff. I will let the forum know about current possibilities and issues. Merten also has a USB interface, I will check that one too (I'll probably need Hari's fresh hack  ;) ).

Mark
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: hari on January 22, 2008, 11:25:19 am
Hi,

Merten has a fairly substantial Z-wave product line, and on February 8th, a salesperson will come by and show me some of their stuff. I will let the forum know about current possibilities and issues. Merten also has a USB interface, I will check that one too (I'll probably need Hari's fresh hack  ;) ).

Mark

last time i looked they took over 140€ for a single wall mounted switch!!

hope they did some sane pricing in between,

best regards,
Hari
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: totallymaxed on January 22, 2008, 06:13:39 pm
Hi,

Merten has a fairly substantial Z-wave product line, and on February 8th, a salesperson will come by and show me some of their stuff. I will let the forum know about current possibilities and issues. Merten also has a USB interface, I will check that one too (I'll probably need Hari's fresh hack  ;) ).

Mark

last time i looked they took over 140€ for a single wall mounted switch!!

hope they did some sane pricing in between,

best regards,
Hari

Hmmm... no they didn't!

Only 140€ per wall mounted switch ;-)

The Merten Connect range is one of the component products we will configure/install with our Dianemo professionally installed systems. In that market their quality and name means something... of course under the hood they are using the same z-wave chips and modules as everyone else. But Merten's products are engineered really well and their physical build quality is excellent.

Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: hari on January 22, 2008, 06:53:14 pm
The Merten Connect range is one of the component products we will configure/install with our Dianemo professionally installed systems. In that market their quality and name means something... of course under the hood they are using the same z-wave chips and modules as everyone else. But Merten's products are engineered really well and their physical build quality is excellent.
of course they make great products. But I think the prices are held high to not cannibalize their KNX program ;)

best regards,
Hari

btw: could you please try if the module works for you? Chances are high that you only have to load the module, add the usb man/dev id combination to the ZWave device template and plug that beast in.
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: Domodude on January 22, 2008, 07:40:11 pm
Andrew,
Do you have any experience with Merten/LMCE implementations, in particular how their software, touch panels and their central units?
Their stuff is real nice for retrofitting older houses with home automation, which is my situation. Prices are a bit steep, but if I include wiring etc with the purchase of cheaper stuff, it doesn't look just as bad...
Anyway. I'm not even considering it if it doesn't work properly with LMCE, so I'm real curious what you think.
Mark
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: hkmod25 on January 23, 2008, 09:58:54 am
We tested and delivered to customers Merten (Z-Wave) hardware from beg. of desember 2007.
Its look and feels OK but I will also agree - price to high. We dont make a test w/Linux MCE software
so long it was a support problems w/new ACT interface...
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: hari on January 23, 2008, 10:36:09 am
did anybody try the module yet?

Hacking does not make fun if one can't see results...

Pleazzzze (with cherry and sugar on top) could somebody test the kernel module with a ACT Homepro ZCU101 or ZCU201 interface?

best regards,
Hari
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: totallymaxed on January 23, 2008, 01:04:09 pm
I did some munching to the spcp8x5 code and managed to compile and load the module on 0704. If somebody feels like sending me a ZCU201...

you can download the binary here: http://vt100.at/spcp8x5.ko

compile:
Code: [Select]
dcerouter_48407:/usr/src/spcp8x5# make
make -C /lib/modules/2.6.20-15-generic/build M=/usr/src/spcp8x5 modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.20-15-generic'
  CC [M]  /usr/src/spcp8x5/spcp8x5.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /usr/src/spcp8x5/spcp8x5.mod.o
  LD [M]  /usr/src/spcp8x5/spcp8x5.ko
make[1]: Leaving directory `/usr/src/linux-headers-2.6.20-15-generic'
dcerouter_48407:/usr/src/spcp8x5#

dmesg:
Code: [Select]
[165370.468000] usbcore: registered new interface driver spcp8x5
[165370.468000] /usr/src/spcp8x5/spcp8x5.c: SPCP8x5 USB to serial adaptor driver v0.01

here is the patch:
Code: [Select]
diff -u spcp8x5.orig/spcp8x5.c spcp8x5/spcp8x5.c
--- spcp8x5.orig/spcp8x5.c      2006-09-11 08:26:50.000000000 +0200
+++ spcp8x5/spcp8x5.c   2008-01-21 23:17:37.000000000 +0100
@@ -34,7 +34,6 @@
 };
 
 static struct usb_driver spcp8x5_driver = {
-       .owner                          = THIS_MODULE,
        .name                           = "spcp8x5",
        .probe                          = usb_serial_probe,
        .disconnect             = usb_serial_disconnect,
@@ -43,7 +42,6 @@
 
 // All of the device info needed for the spcp8x5 SIO serial converter
 static struct usb_serial_device_type spcp8x5_device = {
-       .owner                          = THIS_MODULE,
        .name                           = "SPCP8x5",
        .id_table                       = id_table,
        .num_interrupt_in       = 0,
@@ -379,20 +377,16 @@
                tty_flag = TTY_FRAME;
        trace("tty_flag = %d\n",tty_flag);
 
-       tty = port->tty;
-       if (tty && urb->actual_length) {
-               // overrun is special, not associated with a char
-               if (status & UART_OVERRUN_ERROR)
-                       tty_insert_flip_char(tty, 0, TTY_OVERRUN);
-
-               for (i = 0; i < urb->actual_length; ++i) {
-                       if (tty->flip.count >= TTY_FLIPBUF_SIZE) {
-                               tty_flip_buffer_push(tty);
-                       }
-                       tty_insert_flip_char (tty, data[i], tty_flag);
-               }
-               tty_flip_buffer_push (tty);
-       }
+        tty = port->tty;
+        if (tty && urb->actual_length) {
+                tty_buffer_request_room(tty, urb->actual_length + 1);
+                /* overrun is special, not associated with a char */
+                if (status & UART_OVERRUN_ERROR)
+                        tty_insert_flip_char(tty, 0, TTY_OVERRUN);
+                for (i = 0; i < urb->actual_length; ++i)
+                        tty_insert_flip_char(tty, data[i], tty_flag);
+                tty_flip_buffer_push(tty);
+        }
 
        // Schedule the next read _if_ we are still open
        if (port->open_count) {
diff -u spcp8x5.orig/spcp8x5.h spcp8x5/spcp8x5.h
--- spcp8x5.orig/spcp8x5.h      2006-09-25 08:11:35.000000000 +0200
+++ spcp8x5/spcp8x5.h   2008-01-21 23:02:49.000000000 +0100
@@ -19,7 +19,6 @@
 #define SPCP8x5_835_VID                0x04fc
 #define SPCP8x5_835_PID                0x0231
 
-#include <linux/config.h>
 #include <linux/kernel.h>
 #include <linux/errno.h>
 #include <linux/init.h>
diff -u spcp8x5.orig/usb-serial.h spcp8x5/usb-serial.h
--- spcp8x5.orig/usb-serial.h   2004-12-24 22:35:50.000000000 +0100
+++ spcp8x5/usb-serial.h        2008-01-21 23:03:02.000000000 +0100
@@ -54,7 +54,6 @@
 #ifndef __LINUX_USB_SERIAL_H
 #define __LINUX_USB_SERIAL_H
 
-#include <linux/config.h>
 #include <linux/kref.h>
 
 #define SERIAL_TTY_MAJOR       188     /* Nice legal number now */

Hari... I am really sorry! I missed your post above... I have been really busy for last several days. So big apology to you.

I am away from the office until late Friday... but I will try to test your code then.

Thanks for working on this... and sorry for missing that you'd posted this!

Andrew
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: hari on January 23, 2008, 01:16:40 pm
Hari... I am really sorry! I missed your post above... I have been really busy for last several days. So big apology to you.
no problem! Hope your business is going fine ;)
Quote
I am away from the office until late Friday... but I will try to test your code then.
great!

thank you very much and best regards,
Hari
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: Domodude on January 23, 2008, 09:58:25 pm
We tested and delivered to customers Merten (Z-Wave) hardware from beg. of desember 2007.
Its look and feels OK but I will also agree - price to high. We dont make a test w/Linux MCE software
so long it was a support problems w/new ACT interface...

Well, I think the guy that's going to come by will have a suitcase full of Merten stuff, and we can probably see if their units are compatible...

Important question: Is it possible to make a full backup of my (currently working) z-wave setup, in case I do run into problems?
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: hkmod25 on January 24, 2008, 12:36:04 pm
First answer on your imp. question. No. It is not possible to make a backup with Merten Configuration Hardware/Software of one existing Z-Wave network. One must start from the ground and create a "new project".
About hardware compatibility. Yes it is a some problems her. Its look that many manufacturers dont know that a "Z-Wave Logo Program" is.
Merten still dont have Remote Control. But the "Merten Configuration Hardware/Software" dont support ZTH200 from ACT.
Only supportet Remote right now are one from Innovus (but you need a spesial configuration addons that are not delivered with original
Configurator software. Also all new wall modules from ACT will be recognized only with a Basic features. I talking in long time with Merten Support about possibility to get from them a spesial "Configuration files creation Tool" software, but answer was - NO. After all they said OK it will be available for downloading (end of 2007). But nothing happens yet.
Another thing - Z-Wave standard for battery powered devices are different in Europe vs USA. So long we had problems w/HomeSeer software and Merten wall (battery) controllers, probably the same problems can came in LinuxMCE.......................
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: coley on January 24, 2008, 02:01:57 pm
did anybody try the module yet?

Hacking does not make fun if one can't see results...

Pleazzzze (with cherry and sugar on top) could somebody test the kernel module with a ACT Homepro ZCU101 or ZCU201 interface?

best regards,
Hari
I should get a chance to check it out later.
hopefully will let you know how I get on.
I don't have a primary remote to download a config yet, but I should still be able to get it detected right?

-Coley.
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: hari on January 24, 2008, 02:10:24 pm
I don't have a primary remote to download a config yet, but I should still be able to get it detected right?
it should get detected as usb serial port. After that we can add the usb id's to the ZWave device template to allow pluto auto detect it when plugged in. We will then send a "download configuration" command to it and see if it behaves correctly.

best regards,
Hari
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: 1audio on January 24, 2008, 06:06:00 pm
The US ZWave and the EU ZWave run on different frequencies. They will not communicate. I will have access to one of the Homepro USB modules later this week. I will need to assemble a seperate machine to test it. Changing interfaces will screw up my system and with 20+ devices its a pain to reconstruct everything.
The ZWave stuff is not expensive but it does cost between $5-$10 us per device still. The rest of the cost is in dimming circuitry and reliability. The Leviton and Cooper stuff is much better made than the Homepro, and it shows. But the Homepro still works.

If you find a ZWave device that doesn't meet the minimum compatibility and has a ZWave logo complain loudly to the Zen-sys guys. They are supposed to be pretty aggressive on this. I know the current Harmony devices with ZWave are not compliant and they don't have logos any more.

There is software from both Homeseer and Controlthink that will do some tricks for backing up ZWave systems and restoring them. They should work with EU ZWave stuff. I like the Homeseer solution. You don't need a portable controller, just the software and your USB device. You set up your system with the USB and a laptop. Then transfer the stick to LMCE and it imports the devices from the stick. If you named the devices with the homeseer app it should be possible with a revised ZWave stack for LMCE to import those names and "autoconfigure" most of the setup.
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: Domodude on January 25, 2008, 09:03:18 am
1Audio,

So the ZWave-computer interface (e.g. the ZCS201) has the configuration stored? That would explain why lmce knew I have three devices after a re-install.

Merten advertises software where you can define routes etc. on a nice GUI, it would really be excellent if this is indeed fully compliant. Perhaps it would even be possible to use their software to set up a mixed-brand z-wave implementation (more or less like you described with Homeseer), store it in the interface, and have LMCE read it in?

Tonight I will download their software, and see what happens.

Cheers,
  Mark
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: caiman on January 25, 2008, 02:50:02 pm
On the same note, since it is possible to send some custom commands with LMCE, is there any way to get info - even manually or the hard way - on the state of the network, routes in place etc ?

Homeseer has a great software that allows you to poll that information, but because it will work only with their own USB controller which uses the US frequencies, no luck to get it here in Europe.

If that's not possible at all with LMCE, is there any chance to have some functionality added to the driver of the ZCU010 ?

If not, are there any other troubleshooting tools or network mapping tools available in europe ?

many questions here, but my z-wave network doesn't work well, and I'd like to dive into it to fix it :)

Caiman
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: hkmod25 on January 25, 2008, 06:52:11 pm
Merten Configuration software is very good and give a nice possibilities to configure and troublesh. your network.
It is also possible to transfer your upset when work is done to HomeSeer.
But:
1. You need Merten Conf. Tool HARDWARE to use this software.
2. New wall (dimmer/appliance) modules from ACT recognises only with basic functionality.
3. New wall (transmitter) modules from ACT not recognises at all.
4. Merten still not make available Configuration Files Creation Software.
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: 1audio on January 26, 2008, 07:05:02 am
The Homeseer setup software Z-Tool on their site ftp://homeseer.com/pub/setupztool1_0_0_0.exe (http://ftp://homeseer.com/pub/setupztool1_0_0_0.exe) works with a number of ZWave modules and is independent of frequency.

The issues about features comes from two aspects of ZWave. first there are standard features, something that increases with each new rev. Those unfortunately can be retrofitted into modules. All ZWave approved devices need to support those features (as of manufacture approval). Second are proprietary features that are unique to a vendor. Some of the things mentioned about Merten are proprietary.

The latest generation of controllers have a system rebuild function that tests the linking between modules and recreates the routing tables. Its not a true mesh like the Internet. It has fixed routing options. And sometimes they aren't ideal(!) The update tests all of the links and recreates the routing. the routing is only stored in controllers. And the user or manufacturer doesn't have access to muck with the algorithms, those are locked down by Zen-Sys in the chip libraries.

Updating the LMCE Zwave module could add a lot of functions and make it better. Better (newer) controllers also help.
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: totallymaxed on January 26, 2008, 11:24:41 am
1Audio,

So the ZWave-computer interface (e.g. the ZCS201) has the configuration stored? That would explain why lmce knew I have three devices after a re-install.

All SUC's like the ZCS201/ZCU201 store the config you send from the Master Controller... you can move the SUC to another LinuxMCE system and the new Core will interrogate it and sense the existing z-wave config and ask if you want to use it or create a new one.
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: totallymaxed on January 26, 2008, 11:27:07 am
Hari... I am really sorry! I missed your post above... I have been really busy for last several days. So big apology to you.
no problem! Hope your business is going fine ;)
Quote
I am away from the office until late Friday... but I will try to test your code then.
great!

thank you very much and best regards,
Hari

Hari i got back very late from my trip so i did not have any time to test the drive... I will look at it on Monday.
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: totallymaxed on January 26, 2008, 11:31:25 am
Andrew,
Do you have any experience with Merten/LMCE implementations, in particular how their software, touch panels and their central units?
Their stuff is real nice for retrofitting older houses with home automation, which is my situation. Prices are a bit steep, but if I include wiring etc with the purchase of cheaper stuff, it doesn't look just as bad...
Anyway. I'm not even considering it if it doesn't work properly with LMCE, so I'm real curious what you think.
Mark

Yes we do have some experience with Merten's Connect system... and we like it very much. However its early days in terms of the technical side and there also maybe some restrictions on what we can make openly available here. Its too early to say yet on this however.
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: cyr on January 26, 2008, 11:32:00 am
I did some munching to the spcp8x5 code and managed to compile and load the module on 0704. If somebody feels like sending me a ZCU201...


Thanks for the patch, I got the module to compile for my kernel (2.6.21.5) and it loaded.

However, when I loaded the module with my ZCU201 plugged in, this is what I got in my kernel log:

Code: [Select]
Jan 24 18:17:55 kira kernel: usbcore: registered new interface driver usbserial
Jan 24 18:17:55 kira kernel: drivers/usb/serial/usb-serial.c: USB Serial support registered for generic
Jan 24 18:17:55 kira kernel: usbcore: registered new interface driver usbserial_generic
Jan 24 18:17:55 kira kernel: drivers/usb/serial/usb-serial.c: USB Serial Driver core
Jan 24 18:17:55 kira kernel: drivers/usb/serial/usb-serial.c: USB Serial support registered for <NULL>
Jan 24 18:17:55 kira kernel: spcp8x5 2-2:1.0: <NULL> converter detected
Jan 24 18:17:55 kira kernel: usb 2-2: <NULL> converter now attached to ttyUSB0
Jan 24 18:17:55 kira kernel: usb 2-2: <NULL> converter now attached to ttyUSB1
Jan 24 18:17:55 kira kernel: usb 2-2: <NULL> converter now attached to ttyUSB2
Jan 24 18:17:55 kira kernel: usb 2-2: <NULL> converter now attached to ttyUSB3
Jan 24 18:17:55 kira kernel: usb 2-2: <NULL> converter now attached to ttyUSB4
Jan 24 18:17:55 kira kernel: usb 2-2: <NULL> converter now attached to ttyUSB5
Jan 24 18:17:55 kira kernel: usb 2-2: <NULL> converter now attached to ttyUSB6
Jan 24 18:17:55 kira kernel: usb 2-2: <NULL> converter now attached to ttyUSB7
Jan 24 18:17:55 kira kernel: usb 2-2: <NULL> converter now attached to ttyUSB8
Jan 24 18:17:55 kira kernel: usb 2-2: <NULL> converter now attached to ttyUSB9
Jan 24 18:17:55 kira kernel: usb 2-2: <NULL> converter now attached to ttyUSB10
Jan 24 18:17:55 kira kernel: usb 2-2: <NULL> converter now attached to ttyUSB11
Jan 24 18:17:55 kira kernel: usb 2-2: <NULL> converter now attached to ttyUSB12
Jan 24 18:17:55 kira kernel: usb 2-2: <NULL> converter now attached to ttyUSB13
Jan 24 18:17:55 kira kernel: usbcore: registered new interface driver spcp8x5
Jan 24 18:17:55 kira kernel: /usr/src/spcp8x5/spcp8x5.c: SPCP8x5 USB to serial adaptor driver v0.01

I didn't expect the driver to register 14 devices :)

I'm not much of a kernel hacker, so I have real idea how to debug this...

Worse things happened when I tried actually opening the device (ttyUSB0) in my test program...

Code: [Select]
Jan 24 20:15:10 kira kernel: BUG: unable to handle kernel NULL pointer dereference at virtual address 00000000
Jan 24 20:15:10 kira kernel:  printing eip:
Jan 24 20:15:10 kira kernel: cf988866
Jan 24 20:15:10 kira kernel: *pde = 00000000
Jan 24 20:15:10 kira kernel: Oops: 0000 [#1]
Jan 24 20:15:10 kira kernel: Modules linked in: spcp8x5(F) usbserial(F) rfcomm(F) l2cap(F) wlan_tkip wlan_xauth ipt_MAS$
Jan 24 20:15:10 kira kernel: CPU:    0
Jan 24 20:15:10 kira kernel: EIP:    0060:[<cf988866>]    Tainted: PF      VLI
Jan 24 20:15:10 kira kernel: EFLAGS: 00010086   (2.6.21.5 #4)
Jan 24 20:15:10 kira kernel: EIP is at spcp8x5_close+0x56/0x190 [spcp8x5]
Jan 24 20:15:10 kira kernel: eax: c1ce6ad0   ebx: 00000246   ecx: c9dede80   edx: c9dede74
Jan 24 20:15:10 kira kernel: esi: 00000000   edi: 00000000   ebp: ca9b6a00   esp: c9dede60
Jan 24 20:15:10 kira kernel: ds: 007b   es: 007b   fs: 00d8  gs: 0033  ss: 0068
Jan 24 20:15:10 kira kernel: Process zw_serial (pid: 7459, ti=c9dec000 task=c1ce6ad0 task.ti=c9dec000)
Jan 24 20:15:10 kira kernel: Stack: c0102ab3 ca9b6a00 cf98a5c0 ca9b6a08 c2280ca0 00000000 c1ce6ad0 c010e870
Jan 24 20:15:10 kira kernel:        c653911c c653911c ca9b6a00 c2280ca0 c6539000 ca9b6a08 cf9aa343 cd8027f8
Jan 24 20:15:10 kira kernel:        c01d880f cf9aff40 c6f954e0 fffffe00 c6539000 0bc00000 c6f954e0 00000100
Jan 24 20:15:10 kira kernel: Call Trace:
Jan 24 20:15:10 kira kernel:  [<c0102ab3>] common_interrupt+0x23/0x30
Jan 24 20:15:10 kira kernel:  [<c010e870>] default_wake_function+0x0/0x10
Jan 24 20:15:10 kira kernel:  [<cf9aa343>] serial_open+0x103/0x160 [usbserial]
Jan 24 20:15:10 kira kernel:  [<c01d880f>] kobject_get+0xf/0x20
Jan 24 20:15:10 kira kernel:  [<c01f58fd>] tty_open+0x14d/0x2c0
Jan 24 20:15:10 kira kernel:  [<c0152c60>] chrdev_open+0x70/0x130
Jan 24 20:15:10 kira kernel:  [<c0152bf0>] chrdev_open+0x0/0x130
Jan 24 20:15:10 kira kernel:  [<c014ed7f>] __dentry_open+0xaf/0x1c0
Jan 24 20:15:10 kira kernel:  [<c014ef45>] nameidata_to_filp+0x35/0x40
Jan 24 20:15:10 kira kernel:  [<c014ef9b>] do_filp_open+0x4b/0x60
Jan 24 20:15:10 kira kernel:  [<c014effa>] do_sys_open+0x4a/0xe0
Jan 24 20:15:10 kira kernel:  [<c014f0cc>] sys_open+0x1c/0x20
Jan 24 20:15:10 kira kernel:  [<c01027c6>] sysenter_past_esp+0x5f/0x89
Jan 24 20:15:10 kira kernel:  =======================
Jan 24 20:15:10 kira kernel: Code: 18 b8 70 e8 10 c0 89 54 24 14 8d 54 24 14 89 44 24 1c 8b 45 04 05 1c 01 00 00 e8 36 $
Jan 24 20:15:10 kira kernel: EIP: [<cf988866>] spcp8x5_close+0x56/0x190 [spcp8x5] SS:ESP 0068:c9dede60
Jan 24 20:16:14 kira kernel: usb 2-2: USB disconnect, address 2
Jan 24 20:16:14 kira kernel: BUG: unable to handle kernel paging request at virtual address 0100012c
Jan 24 20:16:14 kira kernel:  printing eip:
Jan 24 20:16:14 kira kernel: c011f1d3
Jan 24 20:16:14 kira kernel: *pde = 00000000
Jan 24 20:16:14 kira kernel: Oops: 0002 [#2]
Jan 24 20:16:14 kira kernel: Modules linked in: spcp8x5(F) usbserial(F) rfcomm(F) l2cap(F) wlan_tkip wlan_xauth ipt_MAS$
Jan 24 20:16:14 kira kernel: CPU:    0
Jan 24 20:16:14 kira kernel: EIP:    0060:[<c011f1d3>]    Tainted: PF      VLI
Jan 24 20:16:14 kira kernel: EFLAGS: 00010202   (2.6.21.5 #4)
Jan 24 20:16:14 kira kernel: EIP is at queue_work+0x3/0x30
Jan 24 20:16:14 kira kernel: eax: cefee8c0   ebx: cefee8c0   ecx: 00000000   edx: 0100012c
Jan 24 20:16:14 kira kernel: esi: 00000008   edi: c2280ca0   ebp: c475ac18   esp: ce049ea4
Jan 24 20:16:14 kira kernel: ds: 007b   es: 007b   fs: 00d8  gs: 0000  ss: 0068
Jan 24 20:16:14 kira kernel: Process khubd (pid: 512, ti=ce048000 task=c1225af0 task.ti=ce048000)
Jan 24 20:16:14 kira kernel: Stack: c3646c01 cf9a99d4 c3647b68 ca8a69a0 cf852543 c475ac00 c475ac18 cf98a4e0

etc. etc.

I had to reboot the machine.

Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: hari on January 26, 2008, 11:44:13 am
I had to reboot the machine.

ok, i'll look into that.. i hoped to come by with those little mods, but i have to go through the whole code.

I'll provide a new module soon.

best regards,
Hari
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: cyr on January 26, 2008, 11:50:37 am
Great, I'll be happy to test it (although not on my router/asterisk machine this time I think  ;) ).
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: hari on January 26, 2008, 12:08:52 pm
Great, I'll be happy to test it (although not on my router/asterisk machine this time I think  ;) ).
sorry, it was meant to be a test ;) i don't have the device myself, so i can't try..

i've made some changes and it should now register all usb stuff correctly (you should not get plenty of devices any more). But be aware, i still have 3 warnings left (initialization from incompatible pointer type).

I'm looking at that at the moment but if you are not faint hearted you may try that in between (v0.02):
[link removed - crashes]

best regards,
Hari
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: hari on January 26, 2008, 12:20:38 pm
Great, I'll be happy to test it (although not on my router/asterisk machine this time I think  ;) ).
sorry, it was meant to be a test ;) i don't have the device myself, so i can't try..

i've made some changes and it should now register all usb stuff correctly (you should not get plenty of devices any more). But be aware, i still have 3 warnings left (initialization from incompatible pointer type).

I'm looking at that at the moment but if you are not faint hearted you may try that in between (v0.02):
[link removed - crashes]



best regards,
Hari


ok, wait another 15 minutes, i found the problem and am fixing it.
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: hari on January 26, 2008, 12:23:32 pm
ok, lets try that:

http://vt100.at/spcp8x5.ko-003

no guarantees ;)

i'm still verifying some low level routines.

best regards,
Hari
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: hari on January 26, 2008, 12:40:14 pm
ok, lets try that:

http://vt100.at/spcp8x5.ko-003

no guarantees ;)

i'm still verifying some low level routines.

best regards,
Hari
i had not seen that you are not using 2.6.20 so I have committed the actual version into the trunk:
http://svn.charonmedia.org/trac.cgi/browser/home/hari/spcp8x5
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: hari on January 26, 2008, 08:26:00 pm
nobody?
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: cyr on January 27, 2008, 09:31:45 am
I'll try it out later today when I get back home.

Thanks!
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: hari on January 27, 2008, 12:40:16 pm
I'll try it out later today when I get back home.

Thanks!
ok,
best regards,
Hari
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: cyr on January 27, 2008, 05:46:21 pm
It works!

No crash, and my little Z-Wave test software works as well.

I just turned on some lights via Linux for the first time...
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: hari on January 27, 2008, 05:48:55 pm
perfect ;)

could you please tell me the usb id's (man./device).
If you want you could try to add the id to the ZWave device template. That should make it plug and play in lmce after the module is loaded (maybe even gets autoloaded after depmod and such)

best regards and thank you for testing,
Hari

ps: could you please provide me with the actual dmesg output?

EDIT: totallymaxed reported the id's: "Vendor ID is 04FC and Product ID is 0201."
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: cyr on January 27, 2008, 07:39:39 pm
Code: [Select]
usbcore: registered new interface driver usbserial
drivers/usb/serial/usb-serial.c: USB Serial support registered for generic
usbcore: registered new interface driver usbserial_generic
drivers/usb/serial/usb-serial.c: USB Serial Driver core
drivers/usb/serial/usb-serial.c: USB Serial support registered for SPCP8x5
usbcore: registered new interface driver spcp8x5
/usr/src/spcp8x5/spcp8x5.c: SPCP8x5 USB to serial adaptor driver v0.03
usb 2-2: new full speed USB device using uhci_hcd and address 3
usb 2-2: configuration #1 chosen from 1 choice
spcp8x5 2-2:1.0: SPCP8x5 converter detected
usb 2-2: SPCP8x5 converter now attached to ttyUSB0

And I can confirm the vendor/product ID.
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: hari on January 27, 2008, 07:47:02 pm
And I can confirm the vendor/product ID.
ok. Maybe you want to try it on lmce, too?

best regards,
Hari
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: ddamron on January 27, 2008, 08:37:42 pm
Great Work Hari!!!
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: hari on January 27, 2008, 09:16:14 pm
code moved: http://svn.charonmedia.org/svn/vendor/spcp8x5

best regards,
Hari
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: hari on January 27, 2008, 09:18:58 pm
Great Work Hari!!!

Thank you Mr. Lightz ;)

best regards,
Hari
Title: AGAIN, PLEASE TEST ZWAVE
Post by: hari on January 31, 2008, 12:48:17 pm
if nobody feels like testing i don't feel like pushing it into 0710...  :-[

regards,
Hari

Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: PeteK on January 31, 2008, 05:57:59 pm
Hari, I'd love to, but I can't find a source of ZCU101s.  Does anyone have a US distributor with these?
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: hari on January 31, 2008, 06:29:12 pm
Hari, I'd love to, but I can't find a source of ZCU101s.  Does anyone have a US distributor with these?
you can buy them from act itself (it's an US company iirc):
http://www.act-solutions.com/HomePro/HomePro.shtml

best regards,
Hari
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: PeteK on January 31, 2008, 09:56:26 pm
Great, thanks!   I'll give them a shot.  I'm looking for a device based on a newer version of the API to play with the current implementation.

-Peter
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: aaron.b on January 31, 2008, 10:57:38 pm
Thanks a lot, Hari!  Since those old ACT ZWave controllers aren't sold anymore, this is pretty important.  I just got one of the controllers and we're going to test it and try to make it work for the 0710 release.
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: hari on January 31, 2008, 11:29:01 pm
Thanks a lot, Hari!  Since those old ACT ZWave controllers aren't sold anymore, this is pretty important.  I just got one of the controllers and we're going to test it and try to make it work for the 0710 release.
You are welcome. Btw, the intermatic ha22 (04FC0204) should also work with this driver. When you modify the ZWave device template please don't forget to also add the two Seluxit usb id's (16c006eb, 1d6f0001).
I don't know if all fixes are in the lmce branch yet (one file got updated in the trunk, ListAvailableSerialPorts.sh is still missing, see notes on that issue: http://mantis.linuxmce.org/view.php?id=3823).

feel free to contact me if you need any assistance.

best regards,
Hari
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: dagb on February 03, 2008, 10:19:38 am
Thanks a lot, Hari!  Since those old ACT ZWave controllers aren't sold anymore, this is pretty important.  I just got one of the controllers and we're going to test it and try to make it work for the 0710 release.
You are welcome. Btw, the intermatic ha22 (04FC0204) should also work with this driver. When you modify the ZWave device template please don't forget to also add the two Seluxit usb id's (16c006eb, 1d6f0001).
I don't know if all fixes are in the lmce branch yet (one file got updated in the trunk, ListAvailableSerialPorts.sh is still missing, see notes on that issue: http://mantis.linuxmce.org/view.php?id=3823).

feel free to contact me if you need any assistance.

best regards,
Hari


Greetings. I assume the reference to the seluxit devices relates to the kernel driver at http://svn.charonmedia.org/svn/vendor/spcp8x5/ringbuf.c ?
In any case: the driver compiles and loads with 2.6.24, and I have taken the liberty to add the driver to http://www.linuxdriverproject.org/twiki/bin/view/Main/OutOfTreeDrivers

Now I just need to read up on zwave to figure out what to get and what to avoid...
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: hari on February 03, 2008, 11:20:56 am
Thanks a lot, Hari!  Since those old ACT ZWave controllers aren't sold anymore, this is pretty important.  I just got one of the controllers and we're going to test it and try to make it work for the 0710 release.
You are welcome. Btw, the intermatic ha22 (04FC0204) should also work with this driver. When you modify the ZWave device template please don't forget to also add the two Seluxit usb id's (16c006eb, 1d6f0001).
I don't know if all fixes are in the lmce branch yet (one file got updated in the trunk, ListAvailableSerialPorts.sh is still missing, see notes on that issue: http://mantis.linuxmce.org/view.php?id=3823).

feel free to contact me if you need any assistance.

best regards,
Hari


Greetings. I assume the reference to the seluxit devices relates to the kernel driver at http://svn.charonmedia.org/svn/vendor/spcp8x5/ringbuf.c ?
In any case: the driver compiles and loads with 2.6.24, and I have taken the liberty to add the driver to http://www.linuxdriverproject.org/twiki/bin/view/Main/OutOfTreeDrivers

Now I just need to read up on zwave to figure out what to get and what to avoid...
no, http://svn.charonmedia.org/svn/vendor/spcp8x5/ holds the driver for the Intermatic HA22 and ACT Hompro ZCU[1,2]01 series. The Seluxit uses the generic usb acm driver.

Thank you for the addition, I also contacted Greg Kroah but I am still waiting for response.

best regards,
Hari
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: uplink on February 04, 2008, 01:13:11 pm
I updated the device template with the ACT, Intermatic and Seluxit device IDs, but the ZWave software in LMCE can't connect to the device. I have a 04fc:0201 device.

I get lots of messages saying "size too small 1", then it says "Cannot connect to ZWave device ttyUSB1.", "Connect() Failed", and then the device dies.

Did anyone see this working or is there a need for extra modifications to the LMCE software?
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: hari on February 06, 2008, 09:53:55 am
could you please provide the error output and information from the logfile?

best regards,
Hari
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: totallymaxed on February 06, 2008, 01:57:50 pm
could you please provide the error output and information from the logfile?

best regards,
Hari

Hari - I am waiting for some new ZCU201 units. Our original unit died. As soon as we get the new units we'll do some tests. I know that Aaron is also testing your driver by the way.

Thanks for all your work on this.

Andrew
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: hari on February 06, 2008, 03:00:39 pm
Thanks for all your work on this.

you are welcome. I wish some sponsor would send me a unit for testing ;)

best regards,
Hari
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: totallymaxed on February 06, 2008, 06:33:53 pm
Thanks for all your work on this.

you are welcome. I wish some sponsor would send me a unit for testing ;)

best regards,
Hari

Hmmm... ok let me see what i can do ;-)
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: ddamron on February 06, 2008, 09:57:35 pm
Since you've said that,

I've been reworking my Insteon, and reading deeper into the devices themselves..

Does anyone have a PLC (2414) kicking around?  I'd like to intergrate that unit as well.

The PLC and PLM are two completely different devices..

Best Regards,

Dan
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: PeteK on February 06, 2008, 10:07:56 pm
Dan--

I can send you my PLC (USB) and my drivers if you want to use that.

Thanks,
-Peter
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: ddamron on February 07, 2008, 08:25:16 am
Thanks PeteK,
I'm deep in the Insteon code again..
Although the current code works, trying to follow it is spaghetti.  Being my first Ruby Project, I really didn't have a real grasp of the language at that time.

Now, I have a much better grasp, and will be writing it using the ThreadedRuby Routines.  This will MAJORLY simplify the structure, and make it easier to debug.

I've been digging down to the Chip level now.. all the IBIOS routines make sense, and I'm going to try to code so that driver creates a VIRTUAL switch (in memory) and that VIRTUAL switch corresponds directly to the physical switch.. right down to the memory map, and the SALad application...

Should be a fun project!

I'll let you know when I'm ready for it.

Best Regards,
 
Dan
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: coley on February 07, 2008, 05:48:38 pm
Hi,
I've tried to get the ZCU201 going.
I've loaded the module - no error msgs, but didn't show up on lsmod.
Added the device ID to a new template - plugging the module in is detected by the core.
I'm not sure if I have the template set up correctly - what options should I be choosing when adding a new device?

thanks
Coley.
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: hari on February 07, 2008, 06:06:09 pm
Hi,
I've tried to get the ZCU201 going.
I've loaded the module - no error msgs, but didn't show up on lsmod.
Added the device ID to a new template - plugging the module in is detected by the core.
I'm not sure if I have the template set up correctly - what options should I be choosing when adding a new device?

thanks
Coley.

can i get ssh access to your setup?

strange that it does not show up..
did you use insmod or modprobe?
do you have usbserial loaded?
what shows the dmesg command?

best regards,
Hari
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: coley on February 08, 2008, 05:07:54 pm
Hari, I don't have external access set up at the moment - I'll look into it.

I just used insmod - modprobe is probably a bit smarter to use.
Yes usbserial is loaded - I have another USB to serial port cable (can't remember manufacturer) and it works ok according to dmesg output.

I'll try again later and get more dbug info.

-Coley.
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: hari on February 08, 2008, 05:46:50 pm
greg did further improvements to the driver and it will be in the vanilla kernel soon:
http://www.kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/patches/usb/usb-add-usb-serial-spcp8x5-driver.patch

best regards,
Hari
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: ddamron on February 09, 2008, 01:27:33 am
Sweet!

Hari, You're a kernel hacker now!
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: totallymaxed on February 09, 2008, 03:11:31 am
greg did further improvements to the driver and it will be in the vanilla kernel soon:
http://www.kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/patches/usb/usb-add-usb-serial-spcp8x5-driver.patch

best regards,
Hari

Great :-)
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: hari on February 10, 2008, 10:30:44 am
Hari, You're a kernel hacker now!
yes, it was a hack ;)
Greg did some improvements.

btw, i put the changes from Greg in the trunk on charonmedia and did a tutorial for the Wiki:

http://wiki.linuxmce.org/index.php/SPCP8x5_Driver_Installation
http://wiki.linuxmce.org/index.php/ZWave_DeviceTemplate_PlugAndPlay

best regards,
Hari
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: totallymaxed on February 10, 2008, 06:46:25 pm
Hari, You're a kernel hacker now!
yes, it was a hack ;)
Greg did some improvements.

btw, i put the changes from Greg in the trunk on charonmedia and did a tutorial for the Wiki:

http://wiki.linuxmce.org/index.php/SPCP8x5_Driver_Installation
http://wiki.linuxmce.org/index.php/ZWave_DeviceTemplate_PlugAndPlay

best regards,
Hari

Nice work Hari ;-)

Andrew
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: Zaerc on February 12, 2008, 01:26:31 am
Hack or not, congratulations on a job well done Hari.
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: hari on February 12, 2008, 08:59:01 am

thanks, you are welcome :)

best regards,
Hari
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: uplink on February 18, 2008, 12:05:57 pm
could you please provide the error output and information from the logfile?

I updated the driver with the latest sources just now and ran the ZWave device. I can't attach the log to this post (forum gives an error when I attempt to do so), so I'm posting it inline.

ZWave log
Quote
ZWave, v.2.0.0.44.0802052200
Visit www.plutohome.com for source code and license information

10   02/18/08 2:54:08.910      Device: 63 starting.  Connecting to: localhost <0x2b415d9eab40>
10   02/18/08 2:54:08.916      Setting timeout for socket 3 to 20 <0x2b415d9eab40>
10   02/18/08 2:54:08.973      Socket::SendMessage type 5 id 37 from 63 to -1000 <0x2b415d9eab40>
10   02/18/08 2:54:09.069      TranslateSerialUSB found /sys/devices/pci0000:00/0000:00:04.0/usb4/4-1/4-1:1.0/ttyUSB1/ttyUSB1, returning /dev/ttyUSB1 <0x2b415d9eab40>
36   02/18/08 2:54:09.069      Using serial port: ttyUSB1. <0x2b415d9eab40>
36   02/18/08 2:54:09.081      SerialConnection::connect init serial mutex <0x2b415d9eab40>
36   02/18/08 2:54:09.081      receive thread created OK!!!! <0x2b415d9eab40>
35   02/18/08 2:54:09.081      entry point receiveFunction <0x41001950>
35   02/18/08 2:54:09.291      ++++++++++++ ZWave is connected <0x2b415d9eab40>
36   02/18/08 2:54:09.291      ### Run Current Job  <0x41802950>
36   02/18/08 2:54:09.347      SerialConnection::send lock serial mutex <0x41802950>
35   02/18/08 2:54:09.347      SerialConnection::send len = 2 buf = 0x00 0x15  <0x41802950>
36   02/18/08 2:54:09.347      SerialConnection::send unlock serial mutex <0x41802950>
05   02/18/08 2:54:14.023      ### Go to timeout queue <0x41802950>
05   02/18/08 2:54:14.023      ### execute the next job from timeout queue <0x41802950>
05   02/18/08 2:54:14.023      ZWJobInitialize::timeoutHandler <0x41802950>
36   02/18/08 2:54:14.083      SerialConnection::send lock serial mutex <0x41802950>
35   02/18/08 2:54:14.083      SerialConnection::send len = 2 buf = 0x00 0x15  <0x41802950>
36   02/18/08 2:54:14.083      SerialConnection::send unlock serial mutex <0x41802950>
05   02/18/08 2:54:19.031      ### Go to timeout queue <0x41802950>
05   02/18/08 2:54:19.031      ### execute the next job from timeout queue <0x41802950>
05   02/18/08 2:54:19.031      ZWJobInitialize::timeoutHandler <0x41802950>
36   02/18/08 2:54:19.091      SerialConnection::send lock serial mutex <0x41802950>
35   02/18/08 2:54:19.147      SerialConnection::send len = 2 buf = 0x00 0x15  <0x41802950>
36   02/18/08 2:54:19.147      SerialConnection::send unlock serial mutex <0x41802950>
35   02/18/08 2:54:19.499      size too small 1 <0x41802950>
35   02/18/08 2:54:19.559      size too small 1 <0x41802950>
35   02/18/08 2:54:19.615      size too small 1 <0x41802950>
35   02/18/08 2:54:19.675      size too small 1 <0x41802950>
35   02/18/08 2:54:19.735      size too small 1 <0x41802950>
35   02/18/08 2:54:19.795      size too small 1 <0x41802950>
35   02/18/08 2:54:19.855      size too small 1 <0x41802950>
35   02/18/08 2:54:19.915      size too small 1 <0x41802950>
35   02/18/08 2:54:19.971      size too small 1 <0x41802950>
35   02/18/08 2:54:20.027      size too small 1 <0x41802950>
35   02/18/08 2:54:20.087      size too small 1 <0x41802950>
35   02/18/08 2:54:20.147      size too small 1 <0x41802950>
35   02/18/08 2:54:20.203      size too small 1 <0x41802950>
35   02/18/08 2:54:20.263      size too small 1 <0x41802950>
35   02/18/08 2:54:20.319      size too small 1 <0x41802950>
35   02/18/08 2:54:20.379      size too small 1 <0x41802950>
35   02/18/08 2:54:20.435      size too small 1 <0x41802950>
35   02/18/08 2:54:20.495      size too small 1 <0x41802950>
35   02/18/08 2:54:20.555      size too small 1 <0x41802950>
35   02/18/08 2:54:20.611      size too small 1 <0x41802950>
35   02/18/08 2:54:20.667      size too small 1 <0x41802950>
35   02/18/08 2:54:20.723      size too small 1 <0x41802950>
35   02/18/08 2:54:20.783      size too small 1 <0x41802950>
35   02/18/08 2:54:20.843      size too small 1 <0x41802950>
35   02/18/08 2:54:20.903      size too small 1 <0x41802950>
35   02/18/08 2:54:20.963      size too small 1 <0x41802950>
35   02/18/08 2:54:21.023      size too small 1 <0x41802950>
35   02/18/08 2:54:21.083      size too small 1 <0x41802950>
35   02/18/08 2:54:21.143      size too small 1 <0x41802950>
35   02/18/08 2:54:21.203      size too small 1 <0x41802950>
35   02/18/08 2:54:21.263      size too small 1 <0x41802950>
35   02/18/08 2:54:21.323      size too small 1 <0x41802950>
35   02/18/08 2:54:21.383      size too small 1 <0x41802950>
35   02/18/08 2:54:21.439      size too small 1 <0x41802950>
35   02/18/08 2:54:21.495      size too small 1 <0x41802950>
35   02/18/08 2:54:21.551      size too small 1 <0x41802950>
35   02/18/08 2:54:21.607      size too small 1 <0x41802950>
35   02/18/08 2:54:21.667      size too small 1 <0x41802950>
35   02/18/08 2:54:21.723      size too small 1 <0x41802950>
35   02/18/08 2:54:21.779      size too small 1 <0x41802950>
35   02/18/08 2:54:21.835      size too small 1 <0x41802950>
35   02/18/08 2:54:21.891      size too small 1 <0x41802950>
35   02/18/08 2:54:21.951      size too small 1 <0x41802950>
35   02/18/08 2:54:22.007      size too small 1 <0x41802950>
35   02/18/08 2:54:22.063      size too small 1 <0x41802950>
35   02/18/08 2:54:22.119      size too small 1 <0x41802950>
35   02/18/08 2:54:22.175      size too small 1 <0x41802950>
35   02/18/08 2:54:22.231      size too small 1 <0x41802950>
35   02/18/08 2:54:22.287      size too small 1 <0x41802950>
35   02/18/08 2:54:22.347      size too small 1 <0x41802950>
35   02/18/08 2:54:22.407      size too small 1 <0x41802950>
35   02/18/08 2:54:22.467      size too small 1 <0x41802950>
35   02/18/08 2:54:22.527      size too small 1 <0x41802950>
35   02/18/08 2:54:22.587      size too small 1 <0x41802950>
35   02/18/08 2:54:22.647      size too small 1 <0x41802950>
35   02/18/08 2:54:22.703      size too small 1 <0x41802950>
35   02/18/08 2:54:22.759      size too small 1 <0x41802950>
35   02/18/08 2:54:22.815      size too small 1 <0x41802950>
35   02/18/08 2:54:22.875      size too small 1 <0x41802950>
35   02/18/08 2:54:22.931      size too small 1 <0x41802950>
35   02/18/08 2:54:22.987      size too small 1 <0x41802950>
35   02/18/08 2:54:23.047      size too small 1 <0x41802950>
35   02/18/08 2:54:23.107      size too small 1 <0x41802950>
35   02/18/08 2:54:23.167      size too small 1 <0x41802950>
35   02/18/08 2:54:23.227      size too small 1 <0x41802950>
35   02/18/08 2:54:23.287      size too small 1 <0x41802950>
35   02/18/08 2:54:23.347      size too small 1 <0x41802950>
35   02/18/08 2:54:23.407      size too small 1 <0x41802950>
35   02/18/08 2:54:23.467      size too small 1 <0x41802950>
35   02/18/08 2:54:23.527      size too small 1 <0x41802950>
35   02/18/08 2:54:23.587      size too small 1 <0x41802950>
35   02/18/08 2:54:23.647      size too small 1 <0x41802950>
35   02/18/08 2:54:23.707      size too small 1 <0x41802950>
35   02/18/08 2:54:23.767      size too small 1 <0x41802950>
35   02/18/08 2:54:23.827      size too small 1 <0x41802950>
35   02/18/08 2:54:23.887      size too small 1 <0x41802950>
35   02/18/08 2:54:23.947      size too small 1 <0x41802950>
35   02/18/08 2:54:24.007      size too small 1 <0x41802950>
05   02/18/08 2:54:24.007      ### Go to timeout queue <0x41802950>
05   02/18/08 2:54:24.007      ### skip the next job from timeout queue <0x41802950>
35   02/18/08 2:54:24.007      ----- INIT ---- 1 <0x41802950>
35   02/18/08 2:54:24.007      ----- INIT ---- 2 <0x41802950>
35   02/18/08 2:54:24.067      -------- 3 <0x2b415d9eab40>
35   02/18/08 2:54:24.067      SerialConnection ------------- asa 1 <0x2b415d9eab40>
35   02/18/08 2:54:24.219      SerialConnection ------------- asa 2 <0x2b415d9eab40>
36   02/18/08 2:54:24.219      waiting for thread to finish <0x2b415d9eab40>
35   02/18/08 2:54:24.319      exit receiveFunction : nr. of reads 49 <0x41001950>
36   02/18/08 2:54:24.319      thread finished <0x2b415d9eab40>
35   02/18/08 2:54:24.320      SerialConnection ------------- asa 3 <0x2b415d9eab40>
35   02/18/08 2:54:24.320      SerialConnection ------------- asa 4 <0x2b415d9eab40>
35   02/18/08 2:54:24.320      -------- 4 <0x2b415d9eab40>
10   02/18/08 2:54:24.320      Socket::SendMessage type 5 id 37 from 63 to -1000 <0x2b415d9eab40>
10   02/18/08 2:54:24.365      TranslateSerialUSB found /sys/devices/pci0000:00/0000:00:04.0/usb4/4-1/4-1:1.0/ttyUSB1/ttyUSB1, returning /dev/ttyUSB1 <0x2b415d9eab40>
36   02/18/08 2:54:24.365      Using serial port: ttyUSB1. <0x2b415d9eab40>
36   02/18/08 2:54:24.376      SerialConnection::connect init serial mutex <0x2b415d9eab40>
36   02/18/08 2:54:24.376      receive thread created OK!!!! <0x2b415d9eab40>
35   02/18/08 2:54:24.376      entry point receiveFunction <0x40800950>
35   02/18/08 2:54:24.588      ++++++++++++ ZWave is connected <0x2b415d9eab40>
36   02/18/08 2:54:24.595      ### Run Current Job  <0x41802950>
36   02/18/08 2:54:24.655      SerialConnection::send lock serial mutex <0x41802950>
35   02/18/08 2:54:24.655      SerialConnection::send len = 2 buf = 0x00 0x15  <0x41802950>
36   02/18/08 2:54:24.655      SerialConnection::send unlock serial mutex <0x41802950>
05   02/18/08 2:54:29.011      ### Go to timeout queue <0x41802950>
05   02/18/08 2:54:29.011      ### execute the next job from timeout queue <0x41802950>
05   02/18/08 2:54:29.011      ZWJobInitialize::timeoutHandler <0x41802950>
36   02/18/08 2:54:29.067      SerialConnection::send lock serial mutex <0x41802950>
35   02/18/08 2:54:29.151      SerialConnection::send len = 2 buf = 0x00 0x15  <0x41802950>
36   02/18/08 2:54:29.151      SerialConnection::send unlock serial mutex <0x41802950>
05   02/18/08 2:54:34.023      ### Go to timeout queue <0x41802950>
05   02/18/08 2:54:34.023      ### execute the next job from timeout queue <0x41802950>
05   02/18/08 2:54:34.023      ZWJobInitialize::timeoutHandler <0x41802950>
36   02/18/08 2:54:34.082      SerialConnection::send lock serial mutex <0x41802950>
35   02/18/08 2:54:34.123      SerialConnection::send len = 2 buf = 0x00 0x15  <0x41802950>
36   02/18/08 2:54:34.123      SerialConnection::send unlock serial mutex <0x41802950>
35   02/18/08 2:54:34.479      size too small 1 <0x41802950>
35   02/18/08 2:54:34.538      size too small 1 <0x41802950>
35   02/18/08 2:54:34.598      size too small 1 <0x41802950>
35   02/18/08 2:54:34.658      size too small 1 <0x41802950>
35   02/18/08 2:54:34.714      size too small 1 <0x41802950>
35   02/18/08 2:54:34.774      size too small 1 <0x41802950>
35   02/18/08 2:54:34.835      size too small 1 <0x41802950>
35   02/18/08 2:54:34.895      size too small 1 <0x41802950>
35   02/18/08 2:54:34.951      size too small 1 <0x41802950>
35   02/18/08 2:54:35.007      size too small 1 <0x41802950>
35   02/18/08 2:54:35.066      size too small 1 <0x41802950>
35   02/18/08 2:54:35.126      size too small 1 <0x41802950>
35   02/18/08 2:54:35.187      size too small 1 <0x41802950>
35   02/18/08 2:54:35.247      size too small 1 <0x41802950>
35   02/18/08 2:54:35.306      size too small 1 <0x41802950>
35   02/18/08 2:54:35.367      size too small 1 <0x41802950>
35   02/18/08 2:54:35.423      size too small 1 <0x41802950>
35   02/18/08 2:54:35.483      size too small 1 <0x41802950>
35   02/18/08 2:54:35.539      size too small 1 <0x41802950>
35   02/18/08 2:54:35.595      size too small 1 <0x41802950>
35   02/18/08 2:54:35.651      size too small 1 <0x41802950>
35   02/18/08 2:54:35.707      size too small 1 <0x41802950>
35   02/18/08 2:54:35.763      size too small 1 <0x41802950>
35   02/18/08 2:54:35.819      size too small 1 <0x41802950>
35   02/18/08 2:54:35.875      size too small 1 <0x41802950>
35   02/18/08 2:54:35.931      size too small 1 <0x41802950>
35   02/18/08 2:54:35.987      size too small 1 <0x41802950>
35   02/18/08 2:54:36.047      size too small 1 <0x41802950>
35   02/18/08 2:54:36.107      size too small 1 <0x41802950>
35   02/18/08 2:54:36.163      size too small 1 <0x41802950>
35   02/18/08 2:54:36.219      size too small 1 <0x41802950>
35   02/18/08 2:54:36.280      size too small 1 <0x41802950>
35   02/18/08 2:54:36.335      size too small 1 <0x41802950>
35   02/18/08 2:54:36.391      size too small 1 <0x41802950>
35   02/18/08 2:54:36.451      size too small 1 <0x41802950>
35   02/18/08 2:54:36.507      size too small 1 <0x41802950>
35   02/18/08 2:54:36.563      size too small 1 <0x41802950>
35   02/18/08 2:54:36.619      size too small 1 <0x41802950>
35   02/18/08 2:54:36.679      size too small 1 <0x41802950>
35   02/18/08 2:54:36.735      size too small 1 <0x41802950>
35   02/18/08 2:54:36.794      size too small 1 <0x41802950>
35   02/18/08 2:54:36.854      size too small 1 <0x41802950>
35   02/18/08 2:54:36.914      size too small 1 <0x41802950>
35   02/18/08 2:54:36.974      size too small 1 <0x41802950>
35   02/18/08 2:54:37.034      size too small 1 <0x41802950>
35   02/18/08 2:54:37.095      size too small 1 <0x41802950>
35   02/18/08 2:54:37.154      size too small 1 <0x41802950>
35   02/18/08 2:54:37.211      size too small 1 <0x41802950>
35   02/18/08 2:54:37.270      size too small 1 <0x41802950>
35   02/18/08 2:54:37.327      size too small 1 <0x41802950>
35   02/18/08 2:54:37.386      size too small 1 <0x41802950>
35   02/18/08 2:54:37.444      size too small 1 <0x41802950>
35   02/18/08 2:54:37.502      size too small 1 <0x41802950>
35   02/18/08 2:54:37.562      size too small 1 <0x41802950>
35   02/18/08 2:54:37.622      size too small 1 <0x41802950>
35   02/18/08 2:54:37.682      size too small 1 <0x41802950>
35   02/18/08 2:54:37.742      size too small 1 <0x41802950>
35   02/18/08 2:54:37.802      size too small 1 <0x41802950>
35   02/18/08 2:54:37.862      size too small 1 <0x41802950>
35   02/18/08 2:54:37.919      size too small 1 <0x41802950>
35   02/18/08 2:54:37.974      size too small 1 <0x41802950>
35   02/18/08 2:54:38.035      size too small 1 <0x41802950>
35   02/18/08 2:54:38.095      size too small 1 <0x41802950>
35   02/18/08 2:54:38.155      size too small 1 <0x41802950>
35   02/18/08 2:54:38.214      size too small 1 <0x41802950>
35   02/18/08 2:54:38.274      size too small 1 <0x41802950>
35   02/18/08 2:54:38.334      size too small 1 <0x41802950>
35   02/18/08 2:54:38.394      size too small 1 <0x41802950>
35   02/18/08 2:54:38.455      size too small 1 <0x41802950>
35   02/18/08 2:54:38.514      size too small 1 <0x41802950>
35   02/18/08 2:54:38.574      size too small 1 <0x41802950>
35   02/18/08 2:54:38.634      size too small 1 <0x41802950>
35   02/18/08 2:54:38.691      size too small 1 <0x41802950>
35   02/18/08 2:54:38.750      size too small 1 <0x41802950>
35   02/18/08 2:54:38.811      size too small 1 <0x41802950>
35   02/18/08 2:54:38.870      size too small 1 <0x41802950>
35   02/18/08 2:54:38.930      size too small 1 <0x41802950>
35   02/18/08 2:54:38.987      size too small 1 <0x41802950>
35   02/18/08 2:54:39.046      size too small 1 <0x41802950>
05   02/18/08 2:54:39.047      ### Go to timeout queue <0x41802950>
05   02/18/08 2:54:39.047      ### skip the next job from timeout queue <0x41802950>
35   02/18/08 2:54:39.047      ----- INIT ---- 1 <0x41802950>
35   02/18/08 2:54:39.047      ----- INIT ---- 2 <0x41802950>
05   02/18/08 2:54:39.063      Cannot connect to ZWave device ttyUSB1. <0x2b415d9eab40>
10   02/18/08 2:54:39.063      InternalSendCommand queue  id 791 conf -1 resp (nil) <0x2b415d9eab40>
01   02/18/08 2:54:39.063      Connect() Failed <0x2b415d9eab40>
35   02/18/08 2:54:39.063      -------- 3 <0x2b415d9eab40>
35   02/18/08 2:54:39.063      SerialConnection ------------- asa 1 <0x2b415d9eab40>
35   02/18/08 2:54:39.195      SerialConnection ------------- asa 2 <0x2b415d9eab40>
36   02/18/08 2:54:39.195      waiting for thread to finish <0x2b415d9eab40>
35   02/18/08 2:54:39.295      exit receiveFunction : nr. of reads 48 <0x40800950>
36   02/18/08 2:54:39.295      thread finished <0x2b415d9eab40>
35   02/18/08 2:54:39.295      SerialConnection ------------- asa 3 <0x2b415d9eab40>
35   02/18/08 2:54:39.295      SerialConnection ------------- asa 4 <0x2b415d9eab40>
35   02/18/08 2:54:39.295      -------- 4 <0x2b415d9eab40>
35   02/18/08 2:54:39.567      SerialConnection ------------- 3 <0x2b415d9eab40>
35   02/18/08 2:54:39.567      SerialConnection --- destructor <0x2b415d9eab40>
35   02/18/08 2:54:39.567      SerialConnection ------------- 4 <0x2b415d9eab40>
10   02/18/08 2:54:39.567      Waiting for message queue thread to quit <0x2b415d9eab40>
10   02/18/08 2:54:39.567      Socket m_Socket -1/0x6673c0 Command_Impl1 Dev #63 m_bQuit=1 <0x2b415d9eab40>
10   02/18/08 2:54:39.567      Socket m_Socket -1/0x6673c0 Command_Impl1 Dev #63 m_bQuit=1 <0x2b415d9eab40>
13   02/18/08 2:54:39.567      Socket::Close() m_Socket 3 <0x2b415d9eab40>
13   02/18/08 2:54:39.567      Socket::Close() m_Socket 3 closesocket: 0 <0x2b415d9eab40>
13   02/18/08 2:54:39.567      Socket::Close() m_Socket 4 <0x2b415d9eab40>
13   02/18/08 2:54:39.567      Socket::Close() m_Socket 4 closesocket: 0 <0x2b415d9eab40>
10   02/18/08 2:54:39.567      Message queue thread quit <0x2b415d9eab40>
10   02/18/08 2:54:39.567      Message queue thread joined <0x2b415d9eab40>
10   02/18/08 2:54:39.567      About to call kill spawned devices <0x2b415d9eab40>
10   02/18/08 2:54:39.567      Need to kill 0 child devices <0x2b415d9eab40>
10   02/18/08 2:54:39.567      Killing completed. <0x2b415d9eab40>
13   02/18/08 2:54:39.570      Socket::~Socket(): deleting socket @0x67b640 Event Dev #63 (socket id in destructor: m_Socket: -1) <0x2b415d9eab40>
13   02/18/08 2:54:39.570      Socket::~Socket(): deleting socket @0x689ea0 Event Dev #63 (socket id in destructor: m_Socket: -1) <0x2b415d9eab40>
10   02/18/08 2:54:39.570      ~Command_Impl finished <0x2b415d9eab40>
13   02/18/08 2:54:39.570      ~HandleRequestSocket 0x6673c0 device: 63 ip: 127.0.0.1 <0x2b415d9eab40>
13   02/18/08 2:54:39.570      RequestSocket::Disconnect 0x6673c0 device: 63 <0x2b415d9eab40>
13   02/18/08 2:54:39.570      Socket::~Socket(): deleting socket @0x6673c0 Command_Impl1 Dev #63 (socket id in destructor: m_Socket: -1) <0x2b415d9eab40>
10   02/18/08 2:54:39.570      Device: 63 ending <0x2b415d9eab40>

Other relevant information:

dmesg
Code: [Select]
[16684.922194] spcp8x5 4-1:1.0: SPCP8x5 converter detected
[16684.968406] usb 4-1: SPCP8x5 converter now attached to ttyUSB1
[16684.968880] usbcore: registered new interface driver spcp8x5
[16684.968886] /home/R/spcp8x5/spcp8x5.c: SPCP8x5 USB to serial adaptor driver v0.04

lsusb
Code: [Select]
Bus 004 Device 002: ID 04fc:0201 Sunplus Technology Co., Ltd
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: hari on February 18, 2008, 12:59:04 pm
...
could you please try again with revision 1494 of the spcp8x5 driver fro m charonmedia?

Can you enable remote access for me?

best regards,
Hari
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: uplink on February 18, 2008, 02:51:35 pm
...
could you please try again with revision 1494 of the spcp8x5 driver fro m charonmedia?

Can you enable remote access for me?
I sent you the details in a private message.
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: itspac on March 06, 2008, 04:54:00 am
I get this error in 710 b3 amd64. I am using the Intermatic HA22


[12912.030504] /drivers/spcp8x5/spcp8x5.c: Set UART format 0x30b failed (error = -32)
[12913.195497] printk: 248 messages suppressed.
[12913.195503] rtc: lost some interrupts at 1024Hz.

Quote
ZWave, v.2.0.0.44.0801142200
Visit www.plutohome.com for source code and license information

10      03/06/08 10:14:22.078           Device: 37 starting.  Connecting to: dcerouter <0x2ab972316b40>
10      03/06/08 10:14:22.080           Setting timeout for socket 3 to 20 <0x2ab972316b40>
10      03/06/08 10:14:22.173           Socket::SendMessage type 5 id 37 from 37 to -1000 <0x2ab972316b40>
10      03/06/08 10:14:22.221           TranslateSerialUSB found lrwxrwxrwx 1 root root 0 2008-03-05 22:36 ttyUSB0 -> ../../../devices/pci0000:00/0000:00:02.0/usb3/3-2/3-2:1.0/ttyUSB0, returning /dev/ttyUSB0 <0x2ab972316b40>
36      03/06/08 10:14:22.221           Using serial port: ttyUSB0. <0x2ab972316b40>
36      03/06/08 10:14:22.238           SerialConnection::connect init serial mutex <0x2ab972316b40>
36      03/06/08 10:14:22.238           receive thread created OK!!!! <0x2ab972316b40>
35      03/06/08 10:14:22.238           entry point receiveFunction <0x41001950>
35      03/06/08 10:14:22.448           ++++++++++++ ZWave is connected <0x2ab972316b40>
36      03/06/08 10:14:22.449           ### Run Current Job  <0x41802950>
36      03/06/08 10:14:22.508           SerialConnection::send lock serial mutex <0x41802950>
35      03/06/08 10:14:22.509           SerialConnection::send len = 2 buf = 0x00 0x15  <0x41802950>
36      03/06/08 10:14:22.509           SerialConnection::send unlock serial mutex <0x41802950>
05      03/06/08 10:14:27.005           ### Go to timeout queue <0x41802950>
05      03/06/08 10:14:27.005           ### execute the next job from timeout queue <0x41802950>
05      03/06/08 10:14:27.005           ZWJobInitialize::timeoutHandler <0x41802950>
36      03/06/08 10:14:27.064           SerialConnection::send lock serial mutex <0x41802950>
35      03/06/08 10:14:27.065           SerialConnection::send len = 2 buf = 0x00 0x15  <0x41802950>
36      03/06/08 10:14:27.065           SerialConnection::send unlock serial mutex <0x41802950>
35      03/06/08 10:14:27.424           SerialConnection::hasCommand() popping ACK <0x41802950>
35      03/06/08 10:14:27.425           SerialConnection::hasCommand() front is SOF <0x41802950>
35      03/06/08 10:14:27.425           SerialConnection::hasCommand lock serial mutex <0x41802950>
35      03/06/08 10:14:27.425           SerialConnection::hasCommand wrote ack <0x41802950>
35      03/06/08 10:14:27.425           SerialConnection::hasCommand unlock serial mutex <0x41802950>
35      03/06/08 10:14:27.425           receiveCommand::begin <0x41802950>
35      03/06/08 10:14:27.425           buffer.size()= 18 <0x41802950>
35      03/06/08 10:14:27.425           receiveCommand: eat another command <0x41802950>
35      03/06/08 10:14:27.425           SerialConnection : received command len = 15 buf = 0x01 0x15 0x5a 0x2d 0x57 0x61 0x76 0x65 0x20 0x31 0x2e 0x39 0x31 0x00 0x01  <0x41802950>
35      03/06/08 10:14:27.425           ZWJobInitialize len = 15 buf = 0x01 0x15 0x5a 0x2d 0x57 0x61 0x76 0x65 0x20 0x31 0x2e 0x39 0x31 0x00 0x01  <0x41802950>
35      03/06/08 10:14:27.425           ZWJobGetVersion len = 15 buf = 0x01 0x15 0x5a 0x2d 0x57 0x61 0x76 0x65 0x20 0x31 0x2e 0x39 0x31 0x00 0x01  <0x41802950>
35      03/06/08 10:14:27.425           Z-Wave 1.91 <0x41802950>
36      03/06/08 10:14:27.484           SerialConnection::send lock serial mutex <0x41802950>
35      03/06/08 10:14:27.485           SerialConnection::send len = 2 buf = 0x00 0x20  <0x41802950>
36      03/06/08 10:14:27.485           SerialConnection::send unlock serial mutex <0x41802950>
35      03/06/08 10:14:27.720           SerialConnection::hasCommand() popping ACK <0x41802950>
35      03/06/08 10:14:27.721           SerialConnection::hasCommand() front is SOF <0x41802950>
35      03/06/08 10:14:27.721           SerialConnection::hasCommand lock serial mutex <0x41802950>
35      03/06/08 10:14:27.721           SerialConnection::hasCommand wrote ack <0x41802950>
35      03/06/08 10:14:27.721           SerialConnection::hasCommand unlock serial mutex <0x41802950>
35      03/06/08 10:14:27.721           receiveCommand::begin <0x41802950>
35      03/06/08 10:14:27.721           buffer.size()= 10 <0x41802950>
35      03/06/08 10:14:27.721           receiveCommand: eat another command <0x41802950>
35      03/06/08 10:14:27.721           SerialConnection : received command len = 7 buf = 0x01 0x20 0x01 0x32 0x19 0x0c 0x01  <0x41802950>
35      03/06/08 10:14:27.721           ZWJobInitialize len = 7 buf = 0x01 0x20 0x01 0x32 0x19 0x0c 0x01  <0x41802950>
35      03/06/08 10:14:27.721           ZWJobGetID len = 7 buf = 0x01 0x20 0x01 0x32 0x19 0x0c 0x01  <0x41802950>
36      03/06/08 10:14:27.780           SerialConnection::send lock serial mutex <0x41802950>
35      03/06/08 10:14:27.781           SerialConnection::send len = 2 buf = 0x00 0x02  <0x41802950>
36      03/06/08 10:14:27.781           SerialConnection::send unlock serial mutex <0x41802950>
35      03/06/08 10:14:28.021           SerialConnection::hasCommand() popping ACK <0x41802950>
35      03/06/08 10:14:28.021           SerialConnection::hasCommand() front is SOF <0x41802950>
35      03/06/08 10:14:28.021           SerialConnection::hasCommand lock serial mutex <0x41802950>
35      03/06/08 10:14:28.021           SerialConnection::hasCommand wrote ack <0x41802950>
35      03/06/08 10:14:28.021           SerialConnection::hasCommand unlock serial mutex <0x41802950>
35      03/06/08 10:14:28.021           receiveCommand::begin <0x41802950>
35      03/06/08 10:14:28.021           buffer.size()= 39 <0x41802950>
35      03/06/08 10:14:28.021           receiveCommand: eat another command <0x41802950>
35      03/06/08 10:14:28.021           SerialConnection : received command len = 36 buf = 0x01 0x02 0x04 0x00 0x1d 0x01 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x01 0x02  <0x41802950>
35      03/06/08 10:14:28.021           ZWJobInitialize len = 36 buf = 0x01 0x02 0x04 0x00 0x1d 0x01 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x01 0x02  <0x41802950>
35      03/06/08 10:14:28.021           ZWJobGetInitData len = 36 buf = 0x01 0x02 0x04 0x00 0x1d 0x01 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x01 0x02  <0x41802950>
36      03/06/08 10:14:28.081           SerialConnection::send lock serial mutex <0x41802950>
35      03/06/08 10:14:28.081           SerialConnection::send len = 3 buf = 0x00 0x52 0x01  <0x41802950>
36      03/06/08 10:14:28.081           SerialConnection::send unlock serial mutex <0x41802950>
35      03/06/08 10:14:28.381           SerialConnection::hasCommand() popping ACK <0x41802950>
35      03/06/08 10:14:28.381           SerialConnection::hasCommand() front is SOF <0x41802950>
35      03/06/08 10:14:28.381           SerialConnection::hasCommand lock serial mutex <0x41802950>
35      03/06/08 10:14:28.381           SerialConnection::hasCommand wrote ack <0x41802950>
35      03/06/08 10:14:28.381           SerialConnection::hasCommand unlock serial mutex <0x41802950>
35      03/06/08 10:14:28.381           receiveCommand::begin <0x41802950>
35      03/06/08 10:14:28.381           buffer.size()= 6 <0x41802950>
35      03/06/08 10:14:28.381           receiveCommand: eat another command <0x41802950>
35      03/06/08 10:14:28.381           SerialConnection : received command len = 3 buf = 0x01 0x52 0x01  <0x41802950>
35      03/06/08 10:14:28.381           ZWJobInitialize len = 3 buf = 0x01 0x52 0x01  <0x41802950>
35      03/06/08 10:14:28.381           ZWJobGetSUC len = 3 buf = 0x01 0x52 0x01  <0x41802950>
36      03/06/08 10:14:28.441           SerialConnection::send lock serial mutex <0x41802950>
35      03/06/08 10:14:28.441           SerialConnection::send len = 2 buf = 0x00 0x56  <0x41802950>
36      03/06/08 10:14:28.441           SerialConnection::send unlock serial mutex <0x41802950>
35      03/06/08 10:14:28.681           SerialConnection::hasCommand() popping ACK <0x41802950>
35      03/06/08 10:14:28.681           SerialConnection::hasCommand() front is SOF <0x41802950>
35      03/06/08 10:14:28.681           SerialConnection::hasCommand lock serial mutex <0x41802950>
35      03/06/08 10:14:28.681           SerialConnection::hasCommand wrote ack <0x41802950>
35      03/06/08 10:14:28.681           SerialConnection::hasCommand unlock serial mutex <0x41802950>
35      03/06/08 10:14:28.681           receiveCommand::begin <0x41802950>
35      03/06/08 10:14:28.681           buffer.size()= 6 <0x41802950>
35      03/06/08 10:14:28.681           receiveCommand: eat another command <0x41802950>
35      03/06/08 10:14:28.681           SerialConnection : received command len = 3 buf = 0x01 0x56 0x00  <0x41802950>
35      03/06/08 10:14:28.681           ZWJobInitialize len = 3 buf = 0x01 0x56 0x00  <0x41802950>
35      03/06/08 10:14:28.681           ZWJobGetSUC len = 3 buf = 0x01 0x56 0x00  <0x41802950>
36      03/06/08 10:14:28.737           SerialConnection::send lock serial mutex <0x41802950>
35      03/06/08 10:14:28.737           SerialConnection::send len = 3 buf = 0x00 0x41 0x01  <0x41802950>
36      03/06/08 10:14:28.737           SerialConnection::send unlock serial mutex <0x41802950>
35      03/06/08 10:14:28.973           SerialConnection::hasCommand() popping ACK <0x41802950>
35      03/06/08 10:14:28.973           SerialConnection::hasCommand() front is SOF <0x41802950>
35      03/06/08 10:14:28.973           SerialConnection::hasCommand lock serial mutex <0x41802950>
35      03/06/08 10:14:28.973           SerialConnection::hasCommand wrote ack <0x41802950>
35      03/06/08 10:14:28.973           SerialConnection::hasCommand unlock serial mutex <0x41802950>
35      03/06/08 10:14:28.973           receiveCommand::begin <0x41802950>
35      03/06/08 10:14:28.973           buffer.size()= 11 <0x41802950>
35      03/06/08 10:14:28.973           receiveCommand: eat another command <0x41802950>
35      03/06/08 10:14:28.973           SerialConnection : received command len = 8 buf = 0x01 0x41 0xca 0x06 0x00 0x02 0x02 0x01  <0x41802950>
35      03/06/08 10:14:28.973           ZWJobInitialize len = 8 buf = 0x01 0x41 0xca 0x06 0x00 0x02 0x02 0x01  <0x41802950>
35      03/06/08 10:14:28.973           ZWJobGetNodeProtocolInfo len = 8 buf = 0x01 0x41 0xca 0x06 0x00 0x02 0x02 0x01  <0x41802950>
35      03/06/08 10:14:28.973           ----- INIT ---- 3 <0x41802950>
35      03/06/08 10:14:28.973           ----- INIT ---- 1 <0x41802950>
35      03/06/08 10:14:28.973           ----- INIT ---- 2 <0x41802950>
36      03/06/08 10:14:28.973           ## Current Job Finished --- Left = 0 <0x41802950>
36      03/06/08 10:14:28.981           ZWave::ReportChildDevices trying to get list of devices <0x42003950>
36      03/06/08 10:14:28.981           ZWave::ReportChildDevices got: <0x42003950>
36      03/06/08 10:14:28.981            <0x42003950>
10      03/06/08 10:14:28.981           Socket::SendMessage type 2 id 54 from 37 to -1001 <0x42003950>
10      03/06/08 10:14:28.982           Connect OK <0x2ab972316b40>
05      03/06/08 10:14:28.982           Creating child 38 <0x2ab972316b40>
10      03/06/08 10:14:28.983           Got CreateEvent for unknown type 1820. <0x2ab972316b40>
05      03/06/08 10:14:28.983           Note: Device manager has attached a device of type 1820 that this has no custom event handler for.  It will not fire events. <0x2ab972316b40>
10      03/06/08 10:14:28.983           Got CreateCommand for unknown type 1820. <0x2ab972316b40>
05      03/06/08 10:14:28.983           Note: Device manager has attached a device of type 1820 that this has no custom handler for.  This is normal for IR. <0x2ab972316b40>
10      03/06/08 10:14:28.983           Requesthandler 0x6670e0 (device: 37) runThread now running <0x43005950>

Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: hari on March 06, 2008, 07:21:21 pm
I get this error in 710 b3 amd64. I am using the Intermatic HA22
did you try to download the configuration?

after the first timeout on x00 x15 it looks pretty good..

Danielk22 did some improvements to the serial routines for better frame error handling.

best regards,
Hari
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: itspac on March 06, 2008, 07:45:18 pm
I get this error in 710 b3 amd64. I am using the Intermatic HA22
did you try to download the configuration?

after the first timeout on x00 x15 it looks pretty good..

Danielk22 did some improvements to the serial routines for better frame error handling.

best regards,
Hari

Here is from trying to download configuration.  The master remote reports "not successful"

Quote
linuxmce@dcerouter:~$ /usr/pluto/bin/ZWave -d 37
ZWave, v.2.0.0.44.0801142200
Visit www.plutohome.com for source code and license information

10      03/06/08 13:41:27.142           Device: 37 starting.  Connecting to: dcerouter <0x2b3b039f3b40>
10      03/06/08 13:41:27.145           Setting timeout for socket 3 to 20 <0x2b3b039f3b40>
10      03/06/08 13:41:27.242           Socket::SendMessage type 5 id 37 from 37 to -1000 <0x2b3b039f3b40>
10      03/06/08 13:41:27.345           TranslateSerialUSB found lrwxrwxrwx 1 root root 0 2008-03-06 13:37 ttyUSB0 -> ../../../devices/pci0000:00/0000:00:02.0/usb3/3-2/3-2:1.0/ttyUSB0, returning /dev/ttyUSB0 <0x2b3b039f3b40>
36      03/06/08 13:41:27.345           Using serial port: ttyUSB0. <0x2b3b039f3b40>
36      03/06/08 13:41:27.367           SerialConnection::connect init serial mutex <0x2b3b039f3b40>
36      03/06/08 13:41:27.367           receive thread created OK!!!! <0x2b3b039f3b40>
35      03/06/08 13:41:27.367           entry point receiveFunction <0x41001950>
35      03/06/08 13:41:27.575           ++++++++++++ ZWave is connected <0x2b3b039f3b40>
36      03/06/08 13:41:27.575           ### Run Current Job  <0x41802950>
36      03/06/08 13:41:27.637           SerialConnection::send lock serial mutex <0x41802950>
35      03/06/08 13:41:27.637           SerialConnection::send len = 2 buf = 0x00 0x15  <0x41802950>
36      03/06/08 13:41:27.637           SerialConnection::send unlock serial mutex <0x41802950>
05      03/06/08 13:41:32.003           ### Go to timeout queue <0x41802950>
05      03/06/08 13:41:32.003           ### execute the next job from timeout queue <0x41802950>
05      03/06/08 13:41:32.003           ZWJobInitialize::timeoutHandler <0x41802950>
36      03/06/08 13:41:32.063           SerialConnection::send lock serial mutex <0x41802950>
35      03/06/08 13:41:32.063           SerialConnection::send len = 2 buf = 0x00 0x15  <0x41802950>
36      03/06/08 13:41:32.063           SerialConnection::send unlock serial mutex <0x41802950>
35      03/06/08 13:41:32.179           SerialConnection::hasCommand() front is SOF <0x41802950>
35      03/06/08 13:41:32.179           SerialConnection::hasCommand lock serial mutex <0x41802950>
35      03/06/08 13:41:32.179           SerialConnection::hasCommand wrote ack <0x41802950>
35      03/06/08 13:41:32.179           SerialConnection::hasCommand unlock serial mutex <0x41802950>
35      03/06/08 13:41:32.179           receiveCommand::begin <0x41802950>
35      03/06/08 13:41:32.179           buffer.size()= 18 <0x41802950>
35      03/06/08 13:41:32.179           receiveCommand: eat another command <0x41802950>
35      03/06/08 13:41:32.179           SerialConnection : received command len = 15 buf = 0x01 0x15 0x5a 0x2d 0x57 0x61 0x76 0x65 0x20 0x31 0x2e 0x39 0x31 0x00 0x01  <0x41802950>
35      03/06/08 13:41:32.179           ZWJobInitialize len = 15 buf = 0x01 0x15 0x5a 0x2d 0x57 0x61 0x76 0x65 0x20 0x31 0x2e 0x39 0x31 0x00 0x01  <0x41802950>
35      03/06/08 13:41:32.180           ZWJobGetVersion len = 15 buf = 0x01 0x15 0x5a 0x2d 0x57 0x61 0x76 0x65 0x20 0x31 0x2e 0x39 0x31 0x00 0x01  <0x41802950>
35      03/06/08 13:41:32.180           Z-Wave 1.91 <0x41802950>
36      03/06/08 13:41:32.235           SerialConnection::send lock serial mutex <0x41802950>
35      03/06/08 13:41:32.235           SerialConnection::send len = 2 buf = 0x00 0x20  <0x41802950>
36      03/06/08 13:41:32.235           SerialConnection::send unlock serial mutex <0x41802950>
35      03/06/08 13:41:32.483           SerialConnection::hasCommand() popping ACK <0x41802950>
35      03/06/08 13:41:32.483           SerialConnection::hasCommand() front is SOF <0x41802950>
35      03/06/08 13:41:32.483           SerialConnection::hasCommand lock serial mutex <0x41802950>
35      03/06/08 13:41:32.483           SerialConnection::hasCommand wrote ack <0x41802950>
35      03/06/08 13:41:32.483           SerialConnection::hasCommand unlock serial mutex <0x41802950>
35      03/06/08 13:41:32.483           receiveCommand::begin <0x41802950>
35      03/06/08 13:41:32.483           buffer.size()= 10 <0x41802950>
35      03/06/08 13:41:32.483           receiveCommand: eat another command <0x41802950>
35      03/06/08 13:41:32.483           SerialConnection : received command len = 7 buf = 0x01 0x20 0x01 0x32 0x19 0x0c 0x01  <0x41802950>
35      03/06/08 13:41:32.483           ZWJobInitialize len = 7 buf = 0x01 0x20 0x01 0x32 0x19 0x0c 0x01  <0x41802950>
35      03/06/08 13:41:32.483           ZWJobGetID len = 7 buf = 0x01 0x20 0x01 0x32 0x19 0x0c 0x01  <0x41802950>
36      03/06/08 13:41:32.539           SerialConnection::send lock serial mutex <0x41802950>
35      03/06/08 13:41:32.539           SerialConnection::send len = 2 buf = 0x00 0x02  <0x41802950>
36      03/06/08 13:41:32.539           SerialConnection::send unlock serial mutex <0x41802950>
35      03/06/08 13:41:32.832           SerialConnection::hasCommand() popping ACK <0x41802950>
35      03/06/08 13:41:32.832           SerialConnection::hasCommand() front is SOF <0x41802950>
35      03/06/08 13:41:32.832           SerialConnection::hasCommand lock serial mutex <0x41802950>
35      03/06/08 13:41:32.832           SerialConnection::hasCommand wrote ack <0x41802950>
35      03/06/08 13:41:32.832           SerialConnection::hasCommand unlock serial mutex <0x41802950>
35      03/06/08 13:41:32.832           receiveCommand::begin <0x41802950>
35      03/06/08 13:41:32.832           buffer.size()= 39 <0x41802950>
35      03/06/08 13:41:32.832           receiveCommand: eat another command <0x41802950>
35      03/06/08 13:41:32.832           SerialConnection : received command len = 36 buf = 0x01 0x02 0x04 0x00 0x1d 0x01 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x01 0x02  <0x41802950>
35      03/06/08 13:41:32.832           ZWJobInitialize len = 36 buf = 0x01 0x02 0x04 0x00 0x1d 0x01 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x01 0x02  <0x41802950>
35      03/06/08 13:41:32.832           ZWJobGetInitData len = 36 buf = 0x01 0x02 0x04 0x00 0x1d 0x01 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x01 0x02  <0x41802950>
36      03/06/08 13:41:32.891           SerialConnection::send lock serial mutex <0x41802950>
35      03/06/08 13:41:32.891           SerialConnection::send len = 3 buf = 0x00 0x52 0x01  <0x41802950>
36      03/06/08 13:41:32.891           SerialConnection::send unlock serial mutex <0x41802950>
35      03/06/08 13:41:33.120           SerialConnection::hasCommand() popping ACK <0x41802950>
35      03/06/08 13:41:33.120           SerialConnection::hasCommand() front is SOF <0x41802950>
35      03/06/08 13:41:33.120           SerialConnection::hasCommand lock serial mutex <0x41802950>
35      03/06/08 13:41:33.120           SerialConnection::hasCommand wrote ack <0x41802950>
35      03/06/08 13:41:33.120           SerialConnection::hasCommand unlock serial mutex <0x41802950>
35      03/06/08 13:41:33.120           receiveCommand::begin <0x41802950>
35      03/06/08 13:41:33.120           buffer.size()= 6 <0x41802950>
35      03/06/08 13:41:33.120           receiveCommand: eat another command <0x41802950>
35      03/06/08 13:41:33.120           SerialConnection : received command len = 3 buf = 0x01 0x52 0x01  <0x41802950>
35      03/06/08 13:41:33.120           ZWJobInitialize len = 3 buf = 0x01 0x52 0x01  <0x41802950>
35      03/06/08 13:41:33.120           ZWJobGetSUC len = 3 buf = 0x01 0x52 0x01  <0x41802950>
36      03/06/08 13:41:33.175           SerialConnection::send lock serial mutex <0x41802950>
35      03/06/08 13:41:33.175           SerialConnection::send len = 2 buf = 0x00 0x56  <0x41802950>
36      03/06/08 13:41:33.175           SerialConnection::send unlock serial mutex <0x41802950>
35      03/06/08 13:41:33.464           SerialConnection::hasCommand() popping ACK <0x41802950>
35      03/06/08 13:41:33.464           SerialConnection::hasCommand() front is SOF <0x41802950>
35      03/06/08 13:41:33.464           SerialConnection::hasCommand lock serial mutex <0x41802950>
35      03/06/08 13:41:33.464           SerialConnection::hasCommand wrote ack <0x41802950>
35      03/06/08 13:41:33.464           SerialConnection::hasCommand unlock serial mutex <0x41802950>
35      03/06/08 13:41:33.464           receiveCommand::begin <0x41802950>
35      03/06/08 13:41:33.464           buffer.size()= 6 <0x41802950>
35      03/06/08 13:41:33.464           receiveCommand: eat another command <0x41802950>
35      03/06/08 13:41:33.464           SerialConnection : received command len = 3 buf = 0x01 0x56 0x00  <0x41802950>
35      03/06/08 13:41:33.464           ZWJobInitialize len = 3 buf = 0x01 0x56 0x00  <0x41802950>
35      03/06/08 13:41:33.464           ZWJobGetSUC len = 3 buf = 0x01 0x56 0x00  <0x41802950>
36      03/06/08 13:41:33.519           SerialConnection::send lock serial mutex <0x41802950>
35      03/06/08 13:41:33.519           SerialConnection::send len = 3 buf = 0x00 0x41 0x01  <0x41802950>
36      03/06/08 13:41:33.519           SerialConnection::send unlock serial mutex <0x41802950>
35      03/06/08 13:41:33.747           SerialConnection::hasCommand() popping ACK <0x41802950>
35      03/06/08 13:41:33.747           SerialConnection::hasCommand() front is SOF <0x41802950>
35      03/06/08 13:41:33.747           SerialConnection::hasCommand lock serial mutex <0x41802950>
35      03/06/08 13:41:33.747           SerialConnection::hasCommand wrote ack <0x41802950>
35      03/06/08 13:41:33.747           SerialConnection::hasCommand unlock serial mutex <0x41802950>
35      03/06/08 13:41:33.747           receiveCommand::begin <0x41802950>
35      03/06/08 13:41:33.747           buffer.size()= 11 <0x41802950>
35      03/06/08 13:41:33.747           receiveCommand: eat another command <0x41802950>
35      03/06/08 13:41:33.747           SerialConnection : received command len = 8 buf = 0x01 0x41 0xca 0x06 0x00 0x02 0x02 0x01  <0x41802950>
35      03/06/08 13:41:33.747           ZWJobInitialize len = 8 buf = 0x01 0x41 0xca 0x06 0x00 0x02 0x02 0x01  <0x41802950>
35      03/06/08 13:41:33.747           ZWJobGetNodeProtocolInfo len = 8 buf = 0x01 0x41 0xca 0x06 0x00 0x02 0x02 0x01  <0x41802950>
35      03/06/08 13:41:33.748           ----- INIT ---- 3 <0x41802950>
35      03/06/08 13:41:33.748           ----- INIT ---- 1 <0x41802950>
35      03/06/08 13:41:33.748           ----- INIT ---- 2 <0x41802950>
36      03/06/08 13:41:33.748           ## Current Job Finished --- Left = 0 <0x41802950>
36      03/06/08 13:41:33.749           ZWave::ReportChildDevices trying to get list of devices <0x42003950>
36      03/06/08 13:41:33.749           ZWave::ReportChildDevices got: <0x42003950>
36      03/06/08 13:41:33.749            <0x42003950>
10      03/06/08 13:41:33.749           Socket::SendMessage type 2 id 54 from 37 to -1001 <0x42003950>
10      03/06/08 13:41:33.750           Connect OK <0x2b3b039f3b40>
05      03/06/08 13:41:33.750           Creating child 38 <0x2b3b039f3b40>
10      03/06/08 13:41:33.750           Got CreateEvent for unknown type 1820. <0x2b3b039f3b40>
05      03/06/08 13:41:33.750           Note: Device manager has attached a device of type 1820 that this has no custom event handler for.  It will not fire events. <0x2b3b039f3b40>
10      03/06/08 13:41:33.750           Got CreateCommand for unknown type 1820. <0x2b3b039f3b40>
05      03/06/08 13:41:33.750           Note: Device manager has attached a device of type 1820 that this has no custom handler for.  This is normal for IR. <0x2b3b039f3b40>
10      03/06/08 13:41:33.751           Requesthandler 0x6670e0 (device: 37) runThread now running <0x43005950>
10      03/06/08 13:41:49.571           Receive string: MESSAGE 72             <0x43005950>
10      03/06/08 13:41:49.571           Received MESSAGE 72             0x6670e0 device: 37 <0x43005950>
10      03/06/08 13:41:49.571           Received Message type 1 ID 757 from 0 to 37 (device: 37) resp 0 <0x43005950>
36      03/06/08 13:41:49.572           ZWave::DownloadConfiguration trying to get list of devices <0x43806950>
35      03/06/08 13:41:49.572           -------- 3 <0x43806950>
35      03/06/08 13:41:49.572           SerialConnection ------------- asa 1 <0x43806950>
35      03/06/08 13:41:49.771           SerialConnection ------------- asa 2 <0x43806950>
36      03/06/08 13:41:49.772           waiting for thread to finish <0x43806950>
35      03/06/08 13:41:49.867           exit receiveFunction : nr. of reads 72 <0x41001950>
36      03/06/08 13:41:49.868           thread finished <0x43806950>
35      03/06/08 13:41:49.868           SerialConnection ------------- asa 3 <0x43806950>
35      03/06/08 13:41:49.868           SerialConnection ------------- asa 4 <0x43806950>
35      03/06/08 13:41:49.868           -------- 4 <0x43806950>
36      03/06/08 13:41:49.892           SerialConnection::connect init serial mutex <0x43806950>
36      03/06/08 13:41:49.892           receive thread created OK!!!! <0x43806950>
35      03/06/08 13:41:49.892           entry point receiveFunction <0x40800950>
35      03/06/08 13:41:50.099           ++++++++++++ ZWave is connected <0x43806950>
36      03/06/08 13:41:50.103           ### Run Current Job  <0x41802950>
36      03/06/08 13:41:50.159           SerialConnection::send lock serial mutex <0x41802950>
35      03/06/08 13:41:50.159           SerialConnection::send len = 7 buf = 0x00 0x03 0x01 0x02 0x01 0x01 0x21  <0x41802950>
36      03/06/08 13:41:50.159           SerialConnection::send unlock serial mutex <0x41802950>
36      03/06/08 13:41:50.720           SerialConnection::send lock serial mutex <0x41802950>
35      03/06/08 13:41:50.720           SerialConnection::send len = 3 buf = 0x00 0x42 0x01  <0x41802950>
36      03/06/08 13:41:50.720           SerialConnection::send unlock serial mutex <0x41802950>
35      03/06/08 13:41:54.444           SerialConnection::hasCommand() front is SOF <0x41802950>
35      03/06/08 13:41:54.444           SerialConnection::hasCommand lock serial mutex <0x41802950>
35      03/06/08 13:41:54.444           SerialConnection::hasCommand wrote ack <0x41802950>
35      03/06/08 13:41:54.444           SerialConnection::hasCommand unlock serial mutex <0x41802950>
35      03/06/08 13:41:54.444           receiveCommand::begin <0x41802950>
35      03/06/08 13:41:54.444           buffer.size()= 6 <0x41802950>
35      03/06/08 13:41:54.444           receiveCommand: eat another command <0x41802950>
35      03/06/08 13:41:54.444           SerialConnection : received command len = 3 buf = 0x00 0x42 0x01  <0x41802950>
35      03/06/08 13:41:54.444           ZWJobReset len = 3 buf = 0x00 0x42 0x01  <0x41802950>
36      03/06/08 13:41:54.444           ## Current Job Finished --- Left = 0 <0x41802950>
36      03/06/08 13:41:54.504           ### Run Current Job  <0x41802950>
36      03/06/08 13:41:54.563           SerialConnection::send lock serial mutex <0x41802950>
35      03/06/08 13:41:54.564           SerialConnection::send len = 4 buf = 0x00 0x43 0x02 0x02  <0x41802950>
36      03/06/08 13:41:54.564           SerialConnection::send unlock serial mutex <0x41802950>
35      03/06/08 13:41:54.735           SerialConnection::hasCommand() popping ACK <0x41802950>

Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: itspac on March 06, 2008, 09:37:59 pm
well, I did the download to the connecter on a windows machine then installed the HA22 back on the core and I can controll the light, but I was not able to do the download with the configuration with LinuxMCE
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: 1audio on March 07, 2008, 05:04:22 am
I have found that the LMCE ZWave routine for updating the controller is very unreliable. I now use an inexpensive package from Homeseer called the Z-Tool that allows me to directly control the interface module. Its designed to allow the user to setup the system with a laptop and the USB module. No manual controller needed and at $29.95 for the download its cheaper than a remote. http://www.homeseer.com/products/software/Z-Tool.htm (http://www.homeseer.com/products/software/Z-Tool.htm)
Once the network is in the usb module LMCE seems to read it OK. I have had to reload modules several times because of failures with the LMCE pairing /update routine. If we can get the ZWave software updated to use the "naming class" the whole process will be even nicer.
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: kengtay on May 04, 2008, 03:01:10 pm
I have myself reload the LinuxMCE at least 10 times, so far I have only get one success to learn from my remote. I have finally use a trial version of Homeseer and learn from remote, then plug my USB remote back to LinuxMCE, it work great!!
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: hari on May 04, 2008, 04:29:53 pm
the problem with the download configuration is that recent controllers also send group and scene information. As the actual code does not acknowledge that the download fails.

I'm working on a proof of concept now and will start with the rewrite of the ZWave device next weekend.

best regards,
Hari
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: yann on August 01, 2008, 03:24:05 pm
hello,

i have followed the configuration steps that you wrote on linuxmce:

http://wiki.linuxmce.org/index.php/ACT_Homepro_Motion_Detector

But i still can not make it work. How do you know that it is working or not ? (should i see somehting in the log or on the admin site ?)

if you can let me know

Thanks a lot

yann
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: hari on August 01, 2008, 05:42:13 pm
never got it to work with the original driver. But maybe I was too stupid. It works fine with my new driver (under active development). The new driver does no automatic configuration for now, so the steps are a bit different.

best regards,
Hari
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: Domodude on August 04, 2008, 04:05:19 pm
Yesterday I added a merten dimmer to the ZTH100, and transfered the configuration to the ZCS201.
It did not work at first, because the ZCS201 would not even start reading. I had to reset the ZCS201 (through the LMCE web interface), after which I could upload the config.
I tried a full copy, that did not work. I needed yet another reset after that, before I could finally upload the limited config.
The device reset of the ZCS201 seemed to do the trick after an unsuccessful upload.
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: hari on August 04, 2008, 05:24:49 pm
the svn driver should support both transfer modes (full/network only).

best regards,
Hari
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: Domodude on August 04, 2008, 10:18:40 pm
the svn driver should support both transfer modes (full/network only).


I know it should, but I just have worst of luck with the full transfer. Oh well.
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: hari on August 04, 2008, 10:25:23 pm
the svn driver should support both transfer modes (full/network only).


I know it should, but I just have worst of luck with the full transfer. Oh well.
ah, did not know you were using the svn driver.

best regards,
Hari
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: cyf4746 on October 16, 2008, 11:46:01 am
Hi .. Hari, I got problem to transfer the configuration from the Home Pro Master Controller. I am using the ZCS201 Srial Z-Wave Interface.
Please help.

Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: hari on October 16, 2008, 01:48:03 pm
activate log levels 36,40 and 41 and send me the log
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: cyf4746 on October 17, 2008, 06:49:39 am
Hari,
How to activate log level?
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: habazot on November 23, 2008, 10:51:31 pm
Hi, struggling with getting a ZCU201 USB interface up and running.
Plain 0710 on a AMD64 machine. I'm getting this in the log file (in an endless loop):

========== NEW LOG SECTION ==========
1       11/23/08 21:47:31       77 (spawning-device)    Starting... 10
1       11/23/08 21:47:31       77 (spawning-device)    Found /usr/pluto/bin/ZWave
01      11/23/08 21:47:31.892           asynchThread started <0x2b6fc11f8b40>
05      11/23/08 21:47:36.048           ### Go to timeout queue <0x41802950>
05      11/23/08 21:47:36.048           ### execute the next job from timeout queue <0x41802950>
05      11/23/08 21:47:36.048           ZWJobInitialize::timeoutHandler <0x41802950>
05      11/23/08 21:47:41.032           ### Go to timeout queue <0x41802950>
05      11/23/08 21:47:41.032           ### execute the next job from timeout queue <0x41802950>
05      11/23/08 21:47:41.032           ZWJobInitialize::timeoutHandler <0x41802950>
05      11/23/08 21:47:46.016           ### Go to timeout queue <0x41802950>
05      11/23/08 21:47:46.016           ### skip the next job from timeout queue <0x41802950>
05      11/23/08 21:47:51.040           ### Go to timeout queue <0x41802950>
05      11/23/08 21:47:51.040           ### execute the next job from timeout queue <0x41802950>
05      11/23/08 21:47:51.040           ZWJobInitialize::timeoutHandler <0x41802950>
05      11/23/08 21:47:56.020           ### Go to timeout queue <0x41802950>
05      11/23/08 21:47:56.020           ### execute the next job from timeout queue <0x41802950>
05      11/23/08 21:47:56.020           ZWJobInitialize::timeoutHandler <0x41802950>
05      11/23/08 21:48:01.031           ### Go to timeout queue <0x41802950>
05      11/23/08 21:48:01.032           ### skip the next job from timeout queue <0x41802950>
05      11/23/08 21:48:01.051           Cannot connect to ZWave device ttyUSB0. <0x2b6fc11f8b40>
01      11/23/08 21:48:01.052           Connect() Failed <0x2b6fc11f8b40>
Return code: 1
3       11/23/08 21:48:01       77 (spawning-device)    Device died... count=10/50 dev=77
Sun Nov 23 21:48:01 CET 2008 died

Any clues on how to get a response from this interface?
dcerouter_93878:~# lsusb
Bus 002 Device 007: ID 04fc:0201 Sunplus Technology Co., Ltd
...

dcerouter_93878:~# lsmod
Module                  Size  Used by
spcp8x5                14980  0
usbserial              40688  1 spcp8x5
...

Device data:
Com port: pci0000:00/0000:00:02,0+6
Serial : /org/freedesktop/Hal/devices/usb_device_4fc_201_noserial

Not sure how this maps to ttyUSB0, though..

Any help appreciated :)
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: hari on November 23, 2008, 11:22:53 pm
You could try to use the new zwave driver. But the ZCU101/201 is crap.

best regards,
Hari
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: habazot on November 23, 2008, 11:36:45 pm
You could try to use the new zwave driver. But the ZCU101/201 is crap.

best regards,
Hari

Ok, glad to get some straight talk :)
Which one seems to be the one to recommend these days?
I was looking at the Mi Casa Verde USB/inclusion controller.
How is your experience with it wrt LMCE?

Regards
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: hari on November 23, 2008, 11:44:13 pm
Which one seems to be the one to recommend these days?
I was looking at the Mi Casa Verde USB/inclusion controller.
How is your experience with it wrt LMCE?
I can recommend the Seluxit, full PNP. The tricklestar should work with manual tweaks. The MCV stick should work too, my unit is at the customs office, will report these days.

br, Hari
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: coley on January 13, 2009, 05:59:10 pm
You could try to use the new zwave driver. But the ZCU101/201 is crap.

best regards,
Hari

I know I'm draggin up an old thread - what are the low level issues mentioned in the wiki which reference this thread?
I jumped in and bought one last year but its been sitting idle since I got proof of concept going. When I get back to my system will the ZCU201 be headed for the bin?

thanks
Coley.
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: Tonop on May 17, 2010, 01:47:20 pm
Hi all!

I have this old device ZCU201 and let to know where I can get Linux drivers for it? Can anybody provide me with this info?

Thanks in advance!
Title: Re: Supporting the ACT Solutions ZCU201 USB Z-wave Interface
Post by: totallymaxed on May 17, 2010, 06:33:41 pm
Hi all!

I have this old device ZCU201 and let to know where I can get Linux drivers for it? Can anybody provide me with this info?

Thanks in advance!

The only viable ZWave driver for LinuxMCE is the open one that is currently used - this may or may not work with the ZCU201. If you have a unit test it and let us know if it works.

All the best


Andrew