Hi Hari, have a ha22, having some issues downloading device config from primary Ha07 controller to usb stick. I tried the wizard and the manual method to no avail. Here's what i get thanks:
1 05/04/09 20:16:06 108 (spawning-device) [1;00mStarting... 1[1;00m
1 05/04/09 20:16:06 108 (spawning-device) [1;00mFound /usr/pluto/bin/ZWave[1;00m
01 05/04/09 20:16:07.004 [31;1masynchThread started[0m <0xb79956c0>
05 05/04/09 20:16:12.032 [33;1m### Go to timeout queue[0m <0xb6992b90>
05 05/04/09 20:16:12.033 [33;1m### execute the next job from timeout queue[0m <0xb6992b90>
05 05/04/09 20:16:12.033 [33;1mZWJobInitialize::timeoutHandler[0m <0xb6992b90>
05 05/04/09 20:16:13.864 [33;1mCreating child 109[0m <0xb79956c0>
05 05/04/09 20:16:13.864 [33;1mNote: Device manager has attached a device of type 1820 that this has no custom event handler for. It will not fire events.[0m <0xb79956c0>
05 05/04/09 20:16:13.864 [33;1mNote: Device manager has attached a device of type 1820 that this has no custom handler for. This is normal for IR.[0m <0xb79956c0>
05 05/04/09 20:16:13.864 [33;1mCreating child 110[0m <0xb79956c0>
05 05/04/09 20:16:13.864 [33;1mNote: Device manager has attached a device of type 1922 that this has no custom event handler for. It will not fire events.[0m <0xb79956c0>
05 05/04/09 20:16:13.864 [33;1mNote: Device manager has attached a device of type 1922 that this has no custom handler for. This is normal for IR.[0m <0xb79956c0>
05 05/04/09 20:21:26.005 [33;1m-------------------------- Job Timeout 0x80bd8a0 _________[0m <0xb6992b90>
did you try the new driver, too?
Hari is the new driver also recommended with the MCV stick?
Yes, it works great.
-Thom
hari, I am using the new driver, i'm wondering if it's my dongle, but wanted to see if you saw any errors in the log beofre i spend the 50 bucks, thanks
I used Hcontrol z wave utility (windows) to add my devices to the usb controller via the master controller and I am able to use it with linuxmce now. Anybody want to take the log above into account and venture as to why this would be?
that log above is not from the new driver..
ok, i verified it, but i will swap it out again just to ensure, thanks.