New Z-Wave driver

[hari]

http://vt100.at/files/ZWave-0710-32bit-20090605.bz2

br, Hari

[hari]

Hi Domodude,

cool to hear. Yes, watch it for a few days and I'll prepare some code in the meantime.

br, Hari

[hari]

yeah, that script should do the job in the meantime.

Btw, how often does the stick get stuck for you?

best regards,
Hari

[hari]

@domodude: btw, my remote switches are just being reflashed by merten. They should work without issues when I get them back. With the recent code additions, you can set all associations from the web admin for them.

br, Hari

[pga57]

http://vt100.at/files/ZWave-0710-32bit-20090605.bz2

br, Hari

Hello Hari,

I have those errors when extracting the archive:

linuxmce@dcerouter:~$ sudo tar jxvf ZWave-0710-32bit-20090605.bz2
tar: This does not look like a tar archive
tar: Skipping to next header
tar: Error exit delayed from previous errors

I have made a lot of downloads with the same result :-(
Is the file ok on your side ?

Philippe

[pga57]

Hi Philippe,

It is not a tar archive. All you need is to bunzip it (command is bunzip2 if I remember correctly).

Good luck,
Mark

[/quote]

Hi Mark,
I thought there was a problem because the input file did not have the same name as the previous version (ZWave-0710-32bit-20090605 instead ZWave).
So, I've use bunzip2 and have install this new version on my core.
I'll see if that corrects the problems that I described
previously (April 15)

Thank's for your help !
Philippe

[pga57]

Hello Hari,

For me, the lastest ZWave driver (ZWave-0710-32bit-20090605.bz2) don't resolve the error I have    
after a few days of proper functioning.
The Seluxit viaSENS Homecontroller give me the same problem I have with my previous Tricklestar 300ZW-EU-W and ZWave-0.0.2-0710-32bit.bz2 driver.

36   06/09/09 7:12:43.254      ERROR: ZW_SEND could not be delivered to Z-Wave stack <0xb792fb90>
36   06/09/09 7:12:46.353      No callback received: await_callback: 141 timer: 31 <0xb792fb90>
36   06/09/09 7:12:46.353      ERROR: Dropping command, no callback received after three resends <0xb792fb90>
36   06/09/09 7:13:16.461      We have been idle for 30 seconds, polling device states <0xb792fb90>

Do I set all associations    again?

Philippe

[pga57]

The StatusReport command works, but ZWave worked again this after-noon without intervention.
I thought the reset would be automatic with this new driver.
I did not translate correctly your exchanges.

Thank you for these details

Philippe

[hari]

mark, did you use the merten tool to setup the network? 10 seconds is nearly the worst case scenario. You should be able to tweak links between devices and get sub-second times. Or is your mesh not dense enough?

best regards,
Hari

[Viking]

http://vt100.at/files/ZWave-0710-32bit-20090605.bz2

Thanks hari

I have now installed the new version and will report back what happens.

Greetings
Viking

[scott]

Hi I am new to Zwave development.
For a prototype I was thinking to control a zwave device from my linux box.
I have few quick questions on your zwave driver

1. what USB dongle should I buy to use your zwave driver?

2. what zwave device should I buy to control it from your control point.

Any help is greatly appreciated...

Thanks
scott

[Murdock]

Scott -

  Here's what I'm running right now (not much, but building):
http://wiki.linuxmce.org/index.php/User:Murdock#Z-Wave_Setup

  It's a good starting point for the controller plus a dimmer, my zwave setup was fully plug and play which is really nice.

  All zwave items are here:
http://wiki.linuxmce.org/index.php/Category:ZWave

Ryan

[scott]

Thanks Ryan
I have seen your setup instructions and it seems like I need to install kubuntu to install LinuxMCE. I have both Intel X86 Atom board and Arm board. I am not sure if I can put kubuntu on either of it.

If i attach MiCasa Verde USB Controller to X86 Atom board,
How can my app communicate to  controller? Is there anyway I can download Zwave controller on to my board.

What I was expecting is, there may be Zwave controller souce code which I can put on the board and it will do serial communication to usb dongle. please let me know if iam going in wrong direction.

Thank You
Scott

[hari]

you mean you want to run the Z-Wave driver outside of LinuxMCE, say like in the below listed example on Fedora?

Code: [Select]

[root@test bin]# more /etc/redhat-release
Fedora release 10 (Cambridge)
[root@test bin]# ./ZWave -d 20
ZWave, open edition, v.0.2
Visit www.linuxmce.org for source code and license information

05 07/30/09 14:57:13.696 Creating child 21 <0xb8055a60>
05 07/30/09 14:57:13.697 Note: Device manager has attached a device of type 1820 that this has no custom event handler for.  It will not fire events. <0xb8055a60>
05 07/30/09 14:57:13.697 Note: Device manager has attached a device of type 1820 that this has no custom handler for.  This is normal for IR. <0xb8055a60>
05 07/30/09 14:57:13.697 Creating child 22 <0xb8055a60>
05 07/30/09 14:57:13.698 Note: Device manager has attached a device of type 1922 that this has no custom event handler for.  It will not fire events. <0xb8055a60>
05 07/30/09 14:57:13.698 Note: Device manager has attached a device of type 1922 that this has no custom handler for.  This is normal for IR. <0xb8055a60>
05 07/30/09 14:57:13.715 Router::RemoveAndDeleteSocket 0x8f0ac98 20 <0xaf1f9b90>
05 07/30/09 14:57:16.695 No callback received: await_callback: 3674480 timer: 31 <0xb8054b90>
05 07/30/09 14:57:16.904 Got reply to ZW_MEMORY_GET_ID, Home id: 0x00061e9b, our node id: 1 <0xb8054b90>
05 07/30/09 14:57:17.112 Got reply to GET_SUC_NODE_ID, node: 1 <0xb8054b90>
08 07/30/09 14:57:17.367 Received Message from 20 (ZWave / ) to 4 (unknown / ), type 1 id 718 Command:Create Device, retry none, parameters: <0xb05fbb90>
08 07/30/09 14:57:17.368   Parameter 2(PK_Device): 0 <0xb05fbb90>
08 07/30/09 14:57:17.368   Parameter 44(PK_DeviceTemplate): 1945 <0xb05fbb90>
08 07/30/09 14:57:17.368   Parameter 47(Mac address):  <0xb05fbb90>
08 07/30/09 14:57:17.368   Parameter 57(PK_Room): 0 <0xb05fbb90>
08 07/30/09 14:57:17.368   Parameter 58(IP Address):  <0xb05fbb90>
08 07/30/09 14:57:17.368   Parameter 109(Data String): 12|1 <0xb05fbb90>
08 07/30/09 14:57:17.368   Parameter 150(PK_DHCPDevice): 0 <0xb05fbb90>
08 07/30/09 14:57:17.368   Parameter 156(PK_Device_ControlledVia): 20 <0xb05fbb90>
08 07/30/09 14:57:17.368   Parameter 163(Description):  <0xb05fbb90>
08 07/30/09 14:57:17.368   Parameter 198(PK_Orbiter): 0 <0xb05fbb90>
08 07/30/09 14:57:17.368   Parameter 201(PK_Device_Related): 0 <0xb05fbb90>
05 07/30/09 14:57:17.368 Sender: 20 sent message type: 1 ID: 718 and expected a message reply from 4 <0xb05fbb90>
08 07/30/09 14:57:17.473 Received Message from 20 (ZWave / ) to 4 (unknown / ), type 1 id 718 Command:Create Device, retry none, parameters: <0xb05fbb90>
08 07/30/09 14:57:17.473   Parameter 2(PK_Device): 0 <0xb05fbb90>
08 07/30/09 14:57:17.474   Parameter 44(PK_DeviceTemplate): 37 <0xb05fbb90>
08 07/30/09 14:57:17.474   Parameter 47(Mac address):  <0xb05fbb90>
08 07/30/09 14:57:17.474   Parameter 57(PK_Room): 0 <0xb05fbb90>
08 07/30/09 14:57:17.474   Parameter 58(IP Address):  <0xb05fbb90>
08 07/30/09 14:57:17.474   Parameter 109(Data String): 12|2 <0xb05fbb90>
08 07/30/09 14:57:17.474   Parameter 150(PK_DHCPDevice): 0 <0xb05fbb90>
08 07/30/09 14:57:17.474   Parameter 156(PK_Device_ControlledVia): 20 <0xb05fbb90>
08 07/30/09 14:57:17.474   Parameter 163(Description):  <0xb05fbb90>
08 07/30/09 14:57:17.474   Parameter 198(PK_Orbiter): 0 <0xb05fbb90>
08 07/30/09 14:57:17.474   Parameter 201(PK_Device_Related): 0 <0xb05fbb90>
05 07/30/09 14:57:17.474 Sender: 20 sent message type: 1 ID: 718 and expected a message reply from 4 <0xb05fbb90>
08 07/30/09 14:57:17.579 Received Message from 20 (ZWave / ) to 4 (unknown / ), type 1 id 718 Command:Create Device, retry none, parameters: <0xb05fbb90>
08 07/30/09 14:57:17.580   Parameter 2(PK_Device): 0 <0xb05fbb90>
08 07/30/09 14:57:17.580   Parameter 44(PK_DeviceTemplate): 37 <0xb05fbb90>
08 07/30/09 14:57:17.580   Parameter 47(Mac address):  <0xb05fbb90>
08 07/30/09 14:57:17.580   Parameter 57(PK_Room): 0 <0xb05fbb90>
08 07/30/09 14:57:17.580   Parameter 58(IP Address):  <0xb05fbb90>
08 07/30/09 14:57:17.580   Parameter 109(Data String): 12|3 <0xb05fbb90>
08 07/30/09 14:57:17.580   Parameter 150(PK_DHCPDevice): 0 <0xb05fbb90>
08 07/30/09 14:57:17.580   Parameter 156(PK_Device_ControlledVia): 20 <0xb05fbb90>
08 07/30/09 14:57:17.580   Parameter 163(Description):  <0xb05fbb90>
08 07/30/09 14:57:17.580   Parameter 198(PK_Orbiter): 0 <0xb05fbb90>
08 07/30/09 14:57:17.580   Parameter 201(PK_Device_Related): 0 <0xb05fbb90>
05 07/30/09 14:57:17.580 Sender: 20 sent message type: 1 ID: 718 and expected a message reply from 4 <0xb05fbb90>
05 07/30/09 14:57:17.581 Finished building node list: <0xb8054b90>
05 07/30/09 14:57:17.581 Node: 1 basic: 0x2 generic: 0x2 specific: 0x20 pluto: 1945 <0xb8054b90>
05 07/30/09 14:57:17.581 Node: 2 basic: 0x3 generic: 0x10 specific: 0x0 pluto: 37 <0xb8054b90>
05 07/30/09 14:57:17.581 Node: 3 basic: 0x3 generic: 0x10 specific: 0x0 pluto: 37 <0xb8054b90>

br, Hari

[ivanp]

I feel stupid:(.
I have Aeon Labs Z-Wave Interface with built-In Inclusion Remote (EU) and Everspring SP103 Z-Wave Motion Detector and cant get them to work. I paired them together, put Aeon into USB, core picked it up and Sarah video came up. I couldnt finisk the setup, so went to webadmin and there i could see 3 Zwave interfaces: 28 Zwave, 29 Zwave Embedded Climate Interface, 30 ZWave Embedded Security Interface. I manually added Motion detections ensor udner Security, but after i do quick reload of the Core, sensor disappers from the Security.
Next, i downloaded the new Zwave driver, "unziped it" and placed it in usr/pluto/bin/. After it the Zwave device could not start. I renamed it to Zwave, like the original file, but still the same. After putting back the original file all worked ok.
What am i doing wrong? Hoping for any help on this, i am close to pairing the motion detector with my IP camera.