New Z-Wave driver

[davegravy]

Having a similar issue with the Aeon, but with ACT Homepro Dimmable Lamp Modules. After pairing and pluggin in the stick, it says

"Waiting for the new device to startup..... One moment, please."

Then says

"The device failed to start properly. Something is not right."

Here's the ZWave device log:

Code:

Return code: 2
2 09/03/09 21:03:51 32 (spawning-device) Device requests restart... count=1/50 dev=32
Thu Sep  3 21:03:51 EDT 2009 Restart
========== NEW LOG SECTION ==========
1 09/03/09 21:03:59 32 (spawning-device) Starting... 1
1 09/03/09 21:03:59 32 (spawning-device) Found ./ZWave
05 09/03/09 21:04:00.020 Creating child 33 <0xb794e6c0>
05 09/03/09 21:04:00.020 Note: Device manager has attached a device of type 1820 that this has no custom event handler for.  It will not fire events. <0xb794e6c0>
05 09/03/09 21:04:00.020 Note: Device manager has attached a device of type 1820 that this has no custom handler for.  This is normal for IR. <0xb794e6c0>
05 09/03/09 21:04:00.021 Creating child 34 <0xb794e6c0>
05 09/03/09 21:04:00.021 Note: Device manager has attached a device of type 1922 that this has no custom event handler for.  It will not fire events. <0xb794e6c0>
05 09/03/09 21:04:00.021 Note: Device manager has attached a device of type 1922 that this has no custom handler for.  This is normal for IR. <0xb794e6c0>
05 09/03/09 21:04:00.021 Creating child 39 <0xb794e6c0>
05 09/03/09 21:04:00.021 Note: Device manager has attached a device of type 1945 that this has no custom event handler for.  It will not fire events. <0xb794e6c0>
05 09/03/09 21:04:00.021 Note: Device manager has attached a device of type 1945 that this has no custom handler for.  This is normal for IR. <0xb794e6c0>
05 09/03/09 21:04:00.021 Creating child 45 <0xb794e6c0>
05 09/03/09 21:04:00.021 Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0xb794e6c0>
05 09/03/09 21:04:00.021 Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0xb794e6c0>
05 09/03/09 21:04:00.021 Creating child 46 <0xb794e6c0>
05 09/03/09 21:04:00.021 Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0xb794e6c0>
05 09/03/09 21:04:00.021 Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0xb794e6c0>
05 09/03/09 21:04:00.021 Creating child 47 <0xb794e6c0>
05 09/03/09 21:04:00.021 Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0xb794e6c0>
05 09/03/09 21:04:00.021 Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0xb794e6c0>
05 09/03/09 21:04:00.021 Creating child 48 <0xb794e6c0>
05 09/03/09 21:04:00.021 Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0xb794e6c0>
05 09/03/09 21:04:00.021 Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0xb794e6c0>
05 09/03/09 21:04:03.117 No callback received: await_callback: -1 timer: 31 <0xb794db90>
05 09/03/09 21:04:03.325 Got reply to ZW_MEMORY_GET_ID, Home id: 0x00061b58, our node id: 1 <0xb794db90>
05 09/03/09 21:04:03.537 Got reply to GET_SUC_NODE_ID, node: 1 <0xb794db90>
05 09/03/09 21:04:04.006 Finished building node list: <0xb794db90>
05 09/03/09 21:04:04.006 Node: 1 basic: 0x2 generic: 0x2 specific: 0x1 pluto: 1945 <0xb794db90>
05 09/03/09 21:04:04.006 Node: 4 basic: 0x3 generic: 0x11 specific: 0x1 pluto: 38 <0xb794db90>
05 09/03/09 21:04:04.006 Node: 5 basic: 0x3 generic: 0x11 specific: 0x1 pluto: 38 <0xb794db90>

EDIT: For shits and giggles, I installed the new driver (even though I'm running 810 and read that it was already included in 810). Everything's running fine now as far as I can tell.

[hari]

I manually added Motion detections ensor udner Security, but after i do quick reload of the Core, sensor disappers from the Security.

because you did not include the devices into _your z-wave network_. The z-wave driver gets the node list from the dongle.

I really wish people would read the z-wave manuals that come with the hardware before attempting to do strange things...

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.

Include the devices, then they will show up "automagically".

Hari

[hari]

Having a similar issue with the Aeon, but with ACT Homepro Dimmable Lamp Modules.

this is not even slighty related to the previous post.

EDIT: For shits and giggles, I installed the new driver (even though I'm running 810 and read that it was already included in 810). Everything's running fine now as far as I can tell.

this is not needed and just coincidence. It could be related to the LaunchManager problems, tschak fixed them a few hours ago. You probably rebooted the core or something like that when replacing the binary.

Hari

[davegravy]

this is not needed and just coincidence [...] You probably rebooted the core or something like that when replacing the binary.

Hari

Actually I didn't. Before replacing the binary I rebooted, reloaded the router, removed the usb stick, replaced the usb stick, and did a spiritual dance around my CORE about 20 times in just about every possible sequence to no avail. As soon as I replaced the binary it started working instantly.

[hari]

are you trying to argue with me over my own code? This is not related to the z-wave driver version.

[hari]

btw, the log from your previous post shows perfect operation on the z-wave side.

[davegravy]

are you trying to argue with me over my own code?

Not at all, just posting my observations in the hopes that it may help others in the future.

[hari]

the device startup problem is a general one, not related to z-wave, and was fixed by tschak a few hours ago. The new launchmanager package should prevent those issues from happening, for bluetooth, HID, zwave (either driver), ...

best regards,
Hari

[Kooma]

hari, do you have an idea how long this general startup issues has been present? I've had this annoying bluetooth problem..
PS. Thanks for you work on the Z-wave driver!

[hari]

all 0810 alpha releases are affected, the new launchmanager package should be available very soon.

best regards,
Hari

[PeteK]

Hari--

Thanks for the info and again for the driver.  I can confirm that the z-wave devices does start correctly with Thom's updated launch manager.  However, I did notice some quirkiness with the Hybrid orbiter (random orbiter screens appearing and disappearing).  The z-wave interface seems to be working, but I didn't get the wizard that cycled the lights and allowed me assign rooms.  Is this wizard still present or has that gone away.

Thanks!
PeteK

[tschak909]

Yes, this screen is still present.

-Thom

[hari]

i've never tried to run a z-wave device on a MD..

best regards,
Hari

[pga57]

Hello Hari,

I had a problem with my remote control and have receive a new one (Tricklestar 200ZW-EU-W).
   
I tried using the SIS mode to register it on the network with a "download configuration" command and have lost my zwave setup ! ;-)
So, I tried to make a new configuration but I can no more include each ZWave devices into the ZWave network.
The remote control do not see them more !

Is there something special to do?

Else, when I do a "quick reload router", I find 4 Zwave Remote Controleur in the device tree !!!
One should suffice no? ;-)
If I delete the 3 last, they reappear after a "quick reload router".

Best Regards,
Philippe

[hari]

when you initiate a download configuration on the lmce side, it will replicate the network information from a controller. LMCE sets the SIS (static update controller with node id server) flags. When you have a recent portable controller, and do the download config step, it will enable the sis. **But it will also remove any stored network information from the dongle on the lmce side**. It will also use the network id of the portable controller. When all your controllers were reset, the portable controller will have node id 1, the static controller (dongle) on the lmce side will have id 2. You then usually start to add other devices.

When the static controller on the lmce side shall be the primary controller, you just send the "reset" command to it with the web admin. It is then the primary static (update) controller (with node id server). You can then use the "add node" command from 0810 to add any inclusion controllers. The static controller will then have node id 1 and use its own factory programmed network id. After that start to add your other z-wave devices. I prefer this approach but it needs 0810 as the add/remove node commands needed for primary operation were not present in 0710.

As you've "lost" your old remote, and you got a new one without any network configuration, you've replicated the "empty" network to the dongle. That is why you've "lost" all devices. Reset all your z-wave nodes and re-add them after doing one of the above initialization methods.

best regards,
Hari