Author Topic: ZWave never starts up properly (Beta2) [SOLVED]  (Read 454 times)

chrisbirkinshaw

  • Guru
  • ****
  • Posts: 431
    • View Profile
ZWave never starts up properly (Beta2) [SOLVED]
« on: December 18, 2009, 04:06:16 pm »
Edit: The only way I managed to fix this was by deleting the device and adding again. No idea why this worked!




When I set the COM port of my ZWave device and reload the router I get the following in the device log:

========== NEW LOG SECTION ==========
1   12/18/09 14:31:13   35 (spawning-device)   Starting... 20
1   12/18/09 14:31:13   35 (spawning-device)   Found /usr/pluto/bin/ZWave
Return code: 255
3   12/18/09 14:31:13   35 (spawning-device)   Device died... count=20/50 dev=35
Fri Dec 18 14:31:13 GMT 2009 died


When I run the device from the command line I get success:

# /usr/pluto/bin/ZWave -d 35
ZWave, open edition, v.0.2
Visit www.linuxmce.org for source code and license information

05   12/18/09 15:00:05.975      Child device 36 is disabled <0xb79406c0>
05   12/18/09 15:00:05.976      Child device 37 is disabled <0xb79406c0>
05   12/18/09 15:00:05.976      Child device 38 is disabled <0xb79406c0>
05   12/18/09 15:00:05.976      Child device 39 is disabled <0xb79406c0>
05   12/18/09 15:00:05.976      Child device 40 is disabled <0xb79406c0>
05   12/18/09 15:00:05.976      Child device 41 is disabled <0xb79406c0>
05   12/18/09 15:00:05.976      Child device 42 is disabled <0xb79406c0>
05   12/18/09 15:00:05.976      Child device 43 is disabled <0xb79406c0>
05   12/18/09 15:00:09.071      No callback received: await_callback: 64 timer: 31 <0xb793fb90>
05   12/18/09 15:00:09.279      Got reply to ZW_MEMORY_GET_ID, Home id: 0x00d8c4d8, our node id: 1 <0xb793fb90>
05   12/18/09 15:00:09.491      Got reply to GET_SUC_NODE_ID, node: 1 <0xb793fb90>
05   12/18/09 15:00:10.267      Finished building node list: <0xb793fb90>
05   12/18/09 15:00:10.268      Node: 1 basic: 0x2 generic: 0x2 specific: 0x1 pluto: 1945 <0xb793fb90>
05   12/18/09 15:00:10.268      Node: 5 basic: 0x4 generic: 0x11 specific: 0x1 pluto: 38 <0xb793fb90>
05   12/18/09 15:00:10.268      Node: 6 basic: 0x4 generic: 0x11 specific: 0x1 pluto: 38 <0xb793fb90>
05   12/18/09 15:00:10.268      Node: 7 basic: 0x3 generic: 0x10 specific: 0x0 pluto: 37 <0xb793fb90>
05   12/18/09 15:00:10.268      Node: 8 basic: 0x4 generic: 0x11 specific: 0x1 pluto: 38 <0xb793fb90>
05   12/18/09 15:00:10.268      Node: 9 basic: 0x4 generic: 0x11 specific: 0x1 pluto: 38 <0xb793fb90>
05   12/18/09 15:02:12.334      void ClientSocket::Disconnect() on this socket: 0x8c4d3e8 (m_Socket: 6) <0xb79406c0>


Right now the only workaround I have is to run the command line in a screen, but as soon as the router is reloaded it is killed, then on the failed restart the device is set to disabled and the COM port cleared, which is quite annoying.

Has anyone got any ideas about this one?

Regards,

Chris
« Last Edit: December 21, 2009, 03:45:10 pm by chrisbirkinshaw »