Author Topic: [Dianemo S]Z-Wave lights are removed from list after reload router!  (Read 1161 times)

Domodude

  • Guest
Title says it all, really. A significant part of my AC z-wave dimmers and switches are removed from the list of lights after a reload of the router. This is what happens in the (somewhat long) log:
Code: [Select]
[color=yellow]05 03/15/12 7:40:41.295 Dev=128 Logs rotated <0x40c71b70>
05 03/15/12 21:28:30.621 Got a reload command from 0  <0x40c71b70>
05 03/15/12 21:28:30.873 void ClientSocket::Disconnect() on this socket: 0x9abdf90 (m_Socket: 7) <0x4066d140>
Return code: 2
2 03/15/12 21:28:30 128 (spawning-device) Device requests restart... count=1/50 dev=128
Thu Mar 15 21:28:31 CET 2012 Restart
========== NEW LOG SECTION ==========
1 03/15/12 21:28:39 128 (spawning-device) Starting... 1
1 03/15/12 21:28:39 128 (spawning-device) Found /usr/pluto/bin/ZWave
01 03/15/12 21:28:43.552 TranslateSerialUSB pci0000:00/0000:00:04.0+2 result /dev/ttyUSB2 <0x4066d140>
05 03/15/12 21:28:43.582 Creating child 129 <0x4066d140>
05 03/15/12 21:28:43.582 Note: Device manager has attached a device of type 1820 that this has no custom event handler for.  It will not fire events. <0x4066d140>
05 03/15/12 21:28:43.583 Note: Device manager has attached a device of type 1820 that this has no custom handler for.  This is normal for IR. <0x4066d140>
05 03/15/12 21:28:43.583 Creating child 130 <0x4066d140>
05 03/15/12 21:28:43.583 Note: Device manager has attached a device of type 1922 that this has no custom event handler for.  It will not fire events. <0x4066d140>
05 03/15/12 21:28:43.583 Note: Device manager has attached a device of type 1922 that this has no custom handler for.  This is normal for IR. <0x4066d140>
05 03/15/12 21:28:43.583 Creating child 192 <0x4066d140>
05 03/15/12 21:28:43.583 Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0x4066d140>
05 03/15/12 21:28:43.583 Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0x4066d140>
05 03/15/12 21:28:43.583 Creating child 193 <0x4066d140>
05 03/15/12 21:28:43.583 Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0x4066d140>
05 03/15/12 21:28:43.583 Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0x4066d140>
05 03/15/12 21:28:43.583 Creating child 194 <0x4066d140>
05 03/15/12 21:28:43.583 Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0x4066d140>
05 03/15/12 21:28:43.583 Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0x4066d140>
05 03/15/12 21:28:43.583 Creating child 195 <0x4066d140>
05 03/15/12 21:28:43.583 Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0x4066d140>
05 03/15/12 21:28:43.583 Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0x4066d140>
05 03/15/12 21:28:43.583 Creating child 196 <0x4066d140>
05 03/15/12 21:28:43.583 Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0x4066d140>
05 03/15/12 21:28:43.583 Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0x4066d140>
05 03/15/12 21:28:43.583 Creating child 197 <0x4066d140>
05 03/15/12 21:28:43.583 Note: Device manager has attached a device of type 37 that this has no custom event handler for.  It will not fire events. <0x4066d140>
05 03/15/12 21:28:43.583 Note: Device manager has attached a device of type 37 that this has no custom handler for.  This is normal for IR. <0x4066d140>
05 03/15/12 21:28:43.583 Creating child 198 <0x4066d140>
05 03/15/12 21:28:43.583 Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0x4066d140>
05 03/15/12 21:28:43.583 Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0x4066d140>
05 03/15/12 21:28:43.583 Creating child 206 <0x4066d140>
05 03/15/12 21:28:43.583 Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0x4066d140>
05 03/15/12 21:28:43.583 Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0x4066d140>
05 03/15/12 21:28:43.583 Creating child 207 <0x4066d140>
05 03/15/12 21:28:43.583 Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0x4066d140>
05 03/15/12 21:28:43.583 Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0x4066d140>
05 03/15/12 21:28:43.583 Creating child 208 <0x4066d140>
05 03/15/12 21:28:43.583 Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0x4066d140>
05 03/15/12 21:28:43.583 Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0x4066d140>
05 03/15/12 21:28:43.583 Creating child 209 <0x4066d140>
05 03/15/12 21:28:43.583 Note: Device manager has attached a device of type 37 that this has no custom event handler for.  It will not fire events. <0x4066d140>
05 03/15/12 21:28:43.583 Note: Device manager has attached a device of type 37 that this has no custom handler for.  This is normal for IR. <0x4066d140>
05 03/15/12 21:28:43.583 Creating child 210 <0x4066d140>
05 03/15/12 21:28:43.583 Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0x4066d140>
05 03/15/12 21:28:43.583 Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0x4066d140>
05 03/15/12 21:28:43.583 Creating child 211 <0x4066d140>
05 03/15/12 21:28:43.583 Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0x4066d140>
05 03/15/12 21:28:43.583 Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0x4066d140>
05 03/15/12 21:28:43.583 Creating child 212 <0x4066d140>
05 03/15/12 21:28:43.583 Note: Device manager has attached a device of type 37 that this has no custom event handler for.  It will not fire events. <0x4066d140>
05 03/15/12 21:28:43.583 Note: Device manager has attached a device of type 37 that this has no custom handler for.  This is normal for IR. <0x4066d140>
05 03/15/12 21:28:43.583 Creating child 213 <0x4066d140>
05 03/15/12 21:28:43.583 Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0x4066d140>
05 03/15/12 21:28:43.583 Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0x4066d140>
05 03/15/12 21:28:46.705 Got a reload command from 0  <0x40c71b70>
05 03/15/12 21:28:46.810 No callback received: await_callback: 1072 timer: 31 <0x4086fb70>
05 03/15/12 21:28:46.957 void ClientSocket::Disconnect() on this socket: 0x927af90 (m_Socket: 7) <0x4066d140>
Return code: 2
2 03/15/12 21:28:47 128 (spawning-device) Device requests restart... count=1/50 dev=128
Thu Mar 15 21:28:47 CET 2012 Restart
========== NEW LOG SECTION ==========
1 03/15/12 21:28:55 128 (spawning-device) Starting... 1
1 03/15/12 21:28:55 128 (spawning-device) Found /usr/pluto/bin/ZWave
01 03/15/12 21:28:58.405 TranslateSerialUSB pci0000:00/0000:00:04.0+2 result /dev/ttyUSB2 <0x4066d140>
05 03/15/12 21:28:58.425 Creating child 129 <0x4066d140>
05 03/15/12 21:28:58.425 Note: Device manager has attached a device of type 1820 that this has no custom event handler for.  It will not fire events. <0x4066d140>
05 03/15/12 21:28:58.425 Note: Device manager has attached a device of type 1820 that this has no custom handler for.  This is normal for IR. <0x4066d140>
05 03/15/12 21:28:58.425 Creating child 130 <0x4066d140>
05 03/15/12 21:28:58.425 Note: Device manager has attached a device of type 1922 that this has no custom event handler for.  It will not fire events. <0x4066d140>
05 03/15/12 21:28:58.425 Note: Device manager has attached a device of type 1922 that this has no custom handler for.  This is normal for IR. <0x4066d140>
05 03/15/12 21:28:58.425 Creating child 192 <0x4066d140>
05 03/15/12 21:28:58.425 Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0x4066d140>
05 03/15/12 21:28:58.425 Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0x4066d140>
05 03/15/12 21:28:58.425 Creating child 193 <0x4066d140>
05 03/15/12 21:28:58.425 Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0x4066d140>
05 03/15/12 21:28:58.425 Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0x4066d140>
05 03/15/12 21:28:58.425 Creating child 194 <0x4066d140>
05 03/15/12 21:28:58.425 Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0x4066d140>
05 03/15/12 21:28:58.425 Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0x4066d140>
05 03/15/12 21:28:58.425 Creating child 195 <0x4066d140>
05 03/15/12 21:28:58.425 Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0x4066d140>
05 03/15/12 21:28:58.425 Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0x4066d140>
05 03/15/12 21:28:58.425 Creating child 196 <0x4066d140>
05 03/15/12 21:28:58.425 Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0x4066d140>
05 03/15/12 21:28:58.425 Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0x4066d140>
05 03/15/12 21:28:58.425 Creating child 197 <0x4066d140>
05 03/15/12 21:28:58.425 Note: Device manager has attached a device of type 37 that this has no custom event handler for.  It will not fire events. <0x4066d140>
05 03/15/12 21:28:58.425 Note: Device manager has attached a device of type 37 that this has no custom handler for.  This is normal for IR. <0x4066d140>
05 03/15/12 21:28:58.425 Creating child 198 <0x4066d140>
05 03/15/12 21:28:58.425 Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0x4066d140>
05 03/15/12 21:28:58.425 Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0x4066d140>
05 03/15/12 21:28:58.425 Creating child 206 <0x4066d140>
05 03/15/12 21:28:58.425 Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0x4066d140>
05 03/15/12 21:28:58.425 Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0x4066d140>
05 03/15/12 21:28:58.425 Creating child 207 <0x4066d140>
05 03/15/12 21:28:58.425 Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0x4066d140>
05 03/15/12 21:28:58.425 Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0x4066d140>
05 03/15/12 21:28:58.426 Creating child 208 <0x4066d140>
05 03/15/12 21:28:58.426 Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0x4066d140>
05 03/15/12 21:28:58.426 Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0x4066d140>
05 03/15/12 21:28:58.426 Creating child 209 <0x4066d140>
05 03/15/12 21:28:58.426 Note: Device manager has attached a device of type 37 that this has no custom event handler for.  It will not fire events. <0x4066d140>
05 03/15/12 21:28:58.426 Note: Device manager has attached a device of type 37 that this has no custom handler for.  This is normal for IR. <0x4066d140>
05 03/15/12 21:28:58.426 Creating child 210 <0x4066d140>
05 03/15/12 21:28:58.426 Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0x4066d140>
05 03/15/12 21:28:58.426 Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0x4066d140>
05 03/15/12 21:28:58.426 Creating child 211 <0x4066d140>
05 03/15/12 21:28:58.426 Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0x4066d140>
05 03/15/12 21:28:58.426 Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0x4066d140>
05 03/15/12 21:28:58.426 Creating child 212 <0x4066d140>
05 03/15/12 21:28:58.426 Note: Device manager has attached a device of type 37 that this has no custom event handler for.  It will not fire events. <0x4066d140>
05 03/15/12 21:28:58.426 Note: Device manager has attached a device of type 37 that this has no custom handler for.  This is normal for IR. <0x4066d140>
05 03/15/12 21:28:58.426 Creating child 213 <0x4066d140>
05 03/15/12 21:28:58.426 Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0x4066d140>
05 03/15/12 21:28:58.426 Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0x4066d140>
05 03/15/12 21:29:01.528 No callback received: await_callback: 1072 timer: 31 <0x4086fb70>
05 03/15/12 21:29:01.734 Got reply to ZW_MEMORY_GET_ID, Home id: 0xee9d7297, our node id: 40 <0x4086fb70>
05 03/15/12 21:29:01.942 Got reply to GET_SUC_NODE_ID, node: 0 <0x4086fb70>
05 03/15/12 21:29:01.942 No SUC, we become SUC <0x4086fb70>
05 03/15/12 21:29:05.402 No callback received: await_callback: 1 timer: 31 <0x4086fb70>
05 03/15/12 21:29:08.608 No callback received: await_callback: 1 timer: 31 <0x4086fb70>
05 03/15/12 21:29:11.815 No callback received: await_callback: 1 timer: 31 <0x4086fb70>
01 03/15/12 21:29:11.815 ERROR: Dropping command, no callback received after three resends <0x4086fb70>
05 03/15/12 21:29:11.918 ZWave::InternalIDToDevice() No device found for id 2 <0x4086fb70>
05 03/15/12 21:29:12.770 ZWave::InternalIDToDevice() No device found for id 10 <0x4086fb70>
05 03/15/12 21:29:12.794 ZWave::InternalIDToDevice() No device found for id 10 <0x4086fb70>
05 03/15/12 21:29:12.897 ZWave::InternalIDToDevice() No device found for id 11 <0x4086fb70>
05 03/15/12 21:29:12.926 ZWave::InternalIDToDevice() No device found for id 11 <0x4086fb70>
05 03/15/12 21:29:13.029 ZWave::InternalIDToDevice() No device found for id 12 <0x4086fb70>
05 03/15/12 21:29:13.090 ZWave::InternalIDToDevice() No device found for id 12 <0x4086fb70>
05 03/15/12 21:29:13.193 ZWave::InternalIDToDevice() No device found for id 13 <0x4086fb70>
05 03/15/12 21:29:13.259 ZWave::InternalIDToDevice() No device found for id 13 <0x4086fb70>
05 03/15/12 21:29:13.362 ZWave::InternalIDToDevice() No device found for id 14 <0x4086fb70>
05 03/15/12 21:29:13.397 ZWave::InternalIDToDevice() No device found for id 14 <0x4086fb70>
05 03/15/12 21:29:13.500 ZWave::InternalIDToDevice() No device found for id 15 <0x4086fb70>
05 03/15/12 21:29:13.603 ZWave::InternalIDToDevice() No device found for id 16 <0x4086fb70>
05 03/15/12 21:29:13.706 ZWave::InternalIDToDevice() No device found for id 17 <0x4086fb70>
05 03/15/12 21:29:13.743 ZWave::InternalIDToDevice() No device found for id 17 <0x4086fb70>
05 03/15/12 21:29:13.846 ZWave::InternalIDToDevice() No device found for id 18 <0x4086fb70>
05 03/15/12 21:29:13.949 ZWave::InternalIDToDevice() No device found for id 19 <0x4086fb70>
05 03/15/12 21:29:13.975 ZWave::InternalIDToDevice() No device found for id 19 <0x4086fb70>
05 03/15/12 21:29:14.396 ZWave::InternalIDToDevice() No device found for id 23 <0x4086fb70>
05 03/15/12 21:29:14.817 ZWave::InternalIDToDevice() No device found for id 29 <0x4086fb70>
05 03/15/12 21:29:15.132 ZWave::InternalIDToDevice() No device found for id 37 <0x4086fb70>
05 03/15/12 21:29:15.235 ZWave::InternalIDToDevice() No device found for id 38 <0x4086fb70>
05 03/15/12 21:29:15.338 ZWave::InternalIDToDevice() No device found for id 40 <0x4086fb70>
05 03/15/12 21:29:15.338 Finished building node list: <0x4086fb70>
05 03/15/12 21:29:15.338 Node: 2 basic: 0x1 generic: 0x12 specific: 0x0 pluto: 0 <0x4086fb70>
05 03/15/12 21:29:15.338 Node: 3 basic: 0x4 generic: 0x11 specific: 0x1 pluto: 38 <0x4086fb70>
05 03/15/12 21:29:15.338 Node: 4 basic: 0x4 generic: 0x11 specific: 0x1 pluto: 38 <0x4086fb70>
05 03/15/12 21:29:15.338 Node: 5 basic: 0x4 generic: 0x11 specific: 0x1 pluto: 38 <0x4086fb70>
05 03/15/12 21:29:15.338 Node: 6 basic: 0x3 generic: 0x11 specific: 0x0 pluto: 38 <0x4086fb70>
05 03/15/12 21:29:15.338 Node: 7 basic: 0x3 generic: 0x11 specific: 0x0 pluto: 38 <0x4086fb70>
05 03/15/12 21:29:15.338 Node: 8 basic: 0x4 generic: 0x10 specific: 0x1 pluto: 37 <0x4086fb70>
05 03/15/12 21:29:15.338 Node: 9 basic: 0x4 generic: 0x11 specific: 0x1 pluto: 38 <0x4086fb70>
05 03/15/12 21:29:15.338 Node: 10 basic: 0x4 generic: 0x10 specific: 0x1 pluto: 37 <0x4086fb70>
05 03/15/12 21:29:15.338 Node: 11 basic: 0x4 generic: 0x11 specific: 0x1 pluto: 38 <0x4086fb70>
05 03/15/12 21:29:15.338 Node: 12 basic: 0x4 generic: 0x11 specific: 0x1 pluto: 38 <0x4086fb70>
05 03/15/12 21:29:15.338 Node: 13 basic: 0x4 generic: 0x11 specific: 0x1 pluto: 38 <0x4086fb70>
05 03/15/12 21:29:15.338 Node: 14 basic: 0x4 generic: 0x11 specific: 0x1 pluto: 38 <0x4086fb70>
05 03/15/12 21:29:15.338 Node: 15 basic: 0x1 generic: 0x12 specific: 0x0 pluto: 0 <0x4086fb70>
05 03/15/12 21:29:15.338 Node: 16 basic: 0x1 generic: 0x12 specific: 0x0 pluto: 0 <0x4086fb70>
05 03/15/12 21:29:15.338 Node: 17 basic: 0x4 generic: 0x10 specific: 0x1 pluto: 37 <0x4086fb70>
05 03/15/12 21:29:15.338 Node: 18 basic: 0x1 generic: 0x12 specific: 0x0 pluto: 0 <0x4086fb70>
05 03/15/12 21:29:15.338 Node: 19 basic: 0x4 generic: 0x11 specific: 0x1 pluto: 38 <0x4086fb70>
05 03/15/12 21:29:15.338 Node: 20 basic: 0x4 generic: 0x11 specific: 0x1 pluto: 38 <0x4086fb70>
05 03/15/12 21:29:15.338 Node: 21 basic: 0x4 generic: 0x11 specific: 0x1 pluto: 38 <0x4086fb70>
05 03/15/12 21:29:15.338 Node: 22 basic: 0x4 generic: 0x11 specific: 0x1 pluto: 38 <0x4086fb70>
05 03/15/12 21:29:15.339 Node: 23 basic: 0x1 generic: 0x12 specific: 0x0 pluto: 0 <0x4086fb70>
05 03/15/12 21:29:15.339 Node: 24 basic: 0x4 generic: 0x10 specific: 0x1 pluto: 37 <0x4086fb70>
05 03/15/12 21:29:15.339 Node: 25 basic: 0x4 generic: 0x11 specific: 0x1 pluto: 38 <0x4086fb70>
05 03/15/12 21:29:15.339 Node: 28 basic: 0x4 generic: 0x11 specific: 0x1 pluto: 38 <0x4086fb70>
05 03/15/12 21:29:15.339 Node: 29 basic: 0x1 generic: 0x12 specific: 0x0 pluto: 0 <0x4086fb70>
05 03/15/12 21:29:15.339 Node: 31 basic: 0x4 generic: 0x10 specific: 0x1 pluto: 37 <0x4086fb70>
05 03/15/12 21:29:15.339 Node: 36 basic: 0x4 generic: 0x11 specific: 0x1 pluto: 38 <0x4086fb70>
05 03/15/12 21:29:15.339 Node: 37 basic: 0x2 generic: 0x2 specific: 0x1 pluto: 0 <0x4086fb70>
05 03/15/12 21:29:15.339 Node: 38 basic: 0x2 generic: 0x2 specific: 0x1 pluto: 0 <0x4086fb70>
05 03/15/12 21:29:15.339 Node: 40 basic: 0x2 generic: 0x2 specific: 0x1 pluto: 0 <0x4086fb70>[/color]
Ideas, anyone? The lights are still there initially, but get tossed out somehow in a later stage!

hari

  • Administrator
  • LinuxMCE God
  • *****
  • Posts: 2420
    • View Profile
    • ago control
Re: [Dianemo S]Z-Wave lights are removed from list after reload router!
« Reply #1 on: March 17, 2012, 08:28:35 pm »
does not look like a z-wave specific issue as the lights are there on the z-wave side...
rock your home - http://www.agocontrol.com home automation

Domodude

  • Guest
Re: [Dianemo S]Z-Wave lights are removed from list after reload router!
« Reply #2 on: March 17, 2012, 10:05:31 pm »
does not look like a z-wave specific issue as the lights are there on the z-wave side...
Yep. To make sure something was not sitting right in LMCE I deleted the ZWave device, reloaded the router, and added a new device. All lights appeared, but after a reload of the router, many disappear from the web interface list, for example lights 11, 12, 13. Dunno, looks like something is happening to the list of devices as presented by the zwave driver. Is it possible that something is lost due to some processing within Dianemo?

hari

  • Administrator
  • LinuxMCE God
  • *****
  • Posts: 2420
    • View Profile
    • ago control
Re: [Dianemo S]Z-Wave lights are removed from list after reload router!
« Reply #3 on: March 18, 2012, 09:34:51 pm »
please redo these steps and watch the dce router logs when reloading the router. See if there are "Delete Device" messages from the Z-Wave device to the General Info Plugin
rock your home - http://www.agocontrol.com home automation

Domodude

  • Guest
Re: [Dianemo S]Z-Wave lights are removed from list after reload router!
« Reply #4 on: March 18, 2012, 11:24:55 pm »
This does not seem right:
Code: [Select]
07 03/18/12 23:21:47.071 Event #81 has no handlers <0x4f937b70>
07 03/18/12 23:21:47.071 Received Message from 295 (Kitchen ceiling / Kitchen) to -1001 (unknown / ), type 2 id 81 Event:State Changed, retry none, parameters: <0x4f937b70>
07 03/18/12 23:21:47.071   Parameter 66(State): 0 <0x4f937b70>
07 03/18/12 23:21:47.241 Event #81 has no handlers <0x4f937b70>
07 03/18/12 23:21:47.241 Received Message from 294 (Light Switch (on/off) / ) to -1001 (unknown / ), type 2 id 81 Event:State Changed, retry none, parameters: <0x4f937b70>
07 03/18/12 23:21:47.241   Parameter 66(State): 0 <0x4f937b70>
07 03/18/12 23:21:47.401 Event #81 has no handlers <0x4f937b70>
07 03/18/12 23:21:47.401 Received Message from 277 (Light Switch (dimmable) / ) to -1001 (unknown / ), type 2 id 81 Event:State Changed, retry none, parameters: <0x4f937b70>
07 03/18/12 23:21:47.401   Parameter 66(State): 0 <0x4f937b70>
...and I am also not sure about this:  ???
Code: [Select]
08 03/18/12 23:21:03.638 Received Message from 271 (ZWave / Home Theater) to 4 (General Info Plug-in / Home Theater), type 1 id 719 Command:Delete Device, retry none, parameters: <0x4f937b70>
08 03/18/12 23:21:03.677 Received Message from 271 (ZWave / Home Theater) to 4 (General Info Plug-in / Home Theater), type 1 id 719 Command:Delete Device, retry none, parameters: <0x4f937b70>
08 03/18/12 23:21:03.679 Received Message from 271 (ZWave / Home Theater) to 4 (General Info Plug-in / Home Theater), type 1 id 719 Command:Delete Device, retry none, parameters: <0x4f937b70>
08 03/18/12 23:21:03.680 Received Message from 271 (ZWave / Home Theater) to 4 (General Info Plug-in / Home Theater), type 1 id 719 Command:Delete Device, retry none, parameters: <0x4f937b70>
08 03/18/12 23:21:03.682 Received Message from 271 (ZWave / Home Theater) to 4 (General Info Plug-in / Home Theater), type 1 id 719 Command:Delete Device, retry none, parameters: <0x4f937b70>
08 03/18/12 23:21:03.686 Received Message from 271 (ZWave / Home Theater) to 4 (General Info Plug-in / Home Theater), type 1 id 719 Command:Delete Device, retry none, parameters: <0x4f937b70>
08 03/18/12 23:21:03.689 Received Message from 271 (ZWave / Home Theater) to 4 (General Info Plug-in / Home Theater), type 1 id 719 Command:Delete Device,
And mind you, this is with the Tricklestar USB stick, since I wanted to see if that would work better. Guess not. :(

hari

  • Administrator
  • LinuxMCE God
  • *****
  • Posts: 2420
    • View Profile
    • ago control
Re: [Dianemo S]Z-Wave lights are removed from list after reload router!
« Reply #5 on: March 19, 2012, 07:56:06 am »
This does not seem right
why not? that is just the status reporting

Quote
...and I am also not sure about this:  ???
Code: [Select]
08 03/18/12 23:21:03.638 Received Message from 271 (ZWave / Home Theater) to 4 (General Info Plug-in / Home Theater), type 1 id 719 Command:Delete Device, retry none, parameters: <0x4f937b70>
08 03/18/12 23:21:03.677 Received Message from 271 (ZWave / Home Theater) to 4 (General Info Plug-in / Home Theater), type 1 id 719 Command:Delete Device, retry none, parameters: <0x4f937b70>
08 03/18/12 23:21:03.679 Received Message from 271 (ZWave / Home Theater) to 4 (General Info Plug-in / Home Theater), type 1 id 719 Command:Delete Device, retry none, parameters: <0x4f937b70>
08 03/18/12 23:21:03.680 Received Message from 271 (ZWave / Home Theater) to 4 (General Info Plug-in / Home Theater), type 1 id 719 Command:Delete Device, retry none, parameters: <0x4f937b70>
08 03/18/12 23:21:03.682 Received Message from 271 (ZWave / Home Theater) to 4 (General Info Plug-in / Home Theater), type 1 id 719 Command:Delete Device, retry none, parameters: <0x4f937b70>
08 03/18/12 23:21:03.686 Received Message from 271 (ZWave / Home Theater) to 4 (General Info Plug-in / Home Theater), type 1 id 719 Command:Delete Device, retry none, parameters: <0x4f937b70>
08 03/18/12 23:21:03.689 Received Message from 271 (ZWave / Home Theater) to 4 (General Info Plug-in / Home Theater), type 1 id 719 Command:Delete Device,
And mind you, this is with the Tricklestar USB stick, since I wanted to see if that would work better. Guess not. :(
ok. so the z-wave device is sending delete commands. I'd not yet blame the tricklestar, it was working fine here all the time.
We need to find out why the z-wave device believes it shall delete these devices. Could you please compare the nodelist in the debug output from before and after the reload?
rock your home - http://www.agocontrol.com home automation

Domodude

  • Guest
Re: [Dianemo S]Z-Wave lights are removed from list after reload router!
« Reply #6 on: March 19, 2012, 08:20:34 am »
why not? that is just the status reporting
-1001 seems strange, but I suppose my view is a bit skewed by not having had a look at dcerouter.log before  ;)

ok. so the z-wave device is sending delete commands. I'd not yet blame the tricklestar, it was working fine here all the time.
We need to find out why the z-wave device believes it shall delete these devices. Could you please compare the nodelist in the debug output from before and after the reload?

You mean the nodelist from the "report" command, in the zwave device log?
BTW, not only the tricklestar, but also the aeon labs shows this behavior all of a sudden. I am 99.999% it is not both USB sticks!

Domodude

  • Guest
Re: [Dianemo S]Z-Wave lights are removed from list after reload router!
« Reply #7 on: March 19, 2012, 08:28:38 am »
Strange, I tell the device (#271) to do a status report, and I get nothing back except from an 'ok' from MessageSend. The MessageSend command was given after 8am, notice the time stamp on the latest log entries:
Code: [Select]
mark@dcerouter:/var/log/pluto$ /usr/pluto/bin/MessageSend localhost -r 0 271 1 788 51 ""
RESP: OK
mark@dcerouter:/var/log/pluto$ tail -f 271_ZWave.log
05 03/19/12 7:43:42.291 ZWave::InternalIDToDevice() No device found for id 5/1 <0x4086fb70>
05 03/19/12 7:43:42.368 ZWave::InternalIDToDevice() No device found for id 9/1 <0x4086fb70>
05 03/19/12 7:46:50.066 No callback received: await_callback: 126 timer: 31 <0x4086fb70>
05 03/19/12 7:46:50.222 ZWave::InternalIDToDevice() No device found for id 36/1 <0x4086fb70>
05 03/19/12 7:46:50.299 ZWave::InternalIDToDevice() No device found for id 9/1 <0x4086fb70>
05 03/19/12 7:46:50.679 ZWave::InternalIDToDevice() No device found for id 5/1 <0x4086fb70>
05 03/19/12 7:55:05.607 No callback received: await_callback: 174 timer: 31 <0x4086fb70>
05 03/19/12 7:55:05.763 ZWave::InternalIDToDevice() No device found for id 36/1 <0x4086fb70>
05 03/19/12 7:55:05.981 ZWave::InternalIDToDevice() No device found for id 5/1 <0x4086fb70>
05 03/19/12 7:55:06.176 ZWave::InternalIDToDevice() No device found for id 9/1 <0x4086fb70>

The same happens to the other commands. Have not tried reset though  :D   I think I will put the aeon labs back for now. Then, redo the tests. I'll report on the results in two days I think, I've got to travel for a bit.
Maybe I will order a minimote too. I have a Merten Central Unit, but I cannot (and do not) use that anyway at this point!
« Last Edit: March 19, 2012, 08:30:14 am by Domodude »

hari

  • Administrator
  • LinuxMCE God
  • *****
  • Posts: 2420
    • View Profile
    • ago control
Re: [Dianemo S]Z-Wave lights are removed from list after reload router!
« Reply #8 on: March 19, 2012, 06:28:41 pm »
You mean the nodelist from the "report" command, in the zwave device log?
no, i mean the nodelist that gets printed in the z-wave device log when you enable log level 36
rock your home - http://www.agocontrol.com home automation

Domodude

  • Guest
Re: [Dianemo S]Z-Wave lights are removed from list after reload router!
« Reply #9 on: March 21, 2012, 09:20:44 pm »
OK. Will do. I'll be out of the country until about 10 days from now, so there's going to be a bit of a delay - sorry.

EDIT Found a minute in between packing :) Trip starts tomorrow!

Code: [Select]
36 03/22/12 20:56:12.372 BASIC TYPE: Slave <0xb7741b70>
36 03/22/12 20:56:12.372 GENERIC TYPE: Multilevel Switch <0xb7741b70>
36 03/22/12 20:56:12.372 SPECIFIC TYPE: 0x0 <0xb7741b70>
36 03/22/12 20:56:12.377 Device capabilities: BAD PARAMETER <0xb7741b70>
36 03/22/12 20:56:12.481 Got reply to FUNC_ID_ZW_GET_NODE_PROTOCOL_INFO: <0xb7741b70>
36 03/22/12 20:56:12.481 ***FOUND NODE: 8 <0xb7741b70>
36 03/22/12 20:56:12.481 listening node <0xb7741b70>
36 03/22/12 20:56:12.481 BASIC TYPE: Routing Slave <0xb7741b70>
36 03/22/12 20:56:12.481 GENERIC TYPE: Binary Switch <0xb7741b70>
36 03/22/12 20:56:12.481 SPECIFIC TYPE: 0x1 <0xb7741b70>
36 03/22/12 20:56:12.487 Device capabilities: BAD PARAMETER <0xb7741b70>
36 03/22/12 20:56:12.590 Got reply to FUNC_ID_ZW_GET_NODE_PROTOCOL_INFO: <0xb7741b70>
36 03/22/12 20:56:12.590 ***FOUND NODE: 9 <0xb7741b70>
36 03/22/12 20:56:12.590 listening node <0xb7741b70>
36 03/22/12 20:56:12.590 BASIC TYPE: Routing Slave <0xb7741b70>
36 03/22/12 20:56:12.590 GENERIC TYPE: Multilevel Switch <0xb7741b70>
36 03/22/12 20:56:12.590 SPECIFIC TYPE: 0x1 <0xb7741b70>
36 03/22/12 20:56:12.597 Device capabilities: BAD PARAMETER <0xb7741b70>
36 03/22/12 20:56:12.700 Got reply to FUNC_ID_ZW_GET_NODE_PROTOCOL_INFO: <0xb7741b70>
36 03/22/12 20:56:12.700 ***FOUND NODE: 10 <0xb7741b70>
36 03/22/12 20:56:12.700 listening node <0xb7741b70>
36 03/22/12 20:56:12.700 BASIC TYPE: Routing Slave <0xb7741b70>
36 03/22/12 20:56:12.700 GENERIC TYPE: Binary Switch <0xb7741b70>
36 03/22/12 20:56:12.700 SPECIFIC TYPE: 0x1 <0xb7741b70>
05 03/22/12 20:56:12.700 ZWave::InternalIDToDevice() No device found for id 10 <0xb7741b70>
05 03/22/12 20:56:12.740 ZWave::InternalIDToDevice() No device found for id 10 <0xb7741b70>
36 03/22/12 20:56:12.740 Device capabilities:  <0xb7741b70>
36 03/22/12 20:56:12.844 Got reply to FUNC_ID_ZW_GET_NODE_PROTOCOL_INFO: <0xb7741b70>
36 03/22/12 20:56:12.844 ***FOUND NODE: 11 <0xb7741b70>
36 03/22/12 20:56:12.844 listening node <0xb7741b70>
36 03/22/12 20:56:12.844 BASIC TYPE: Routing Slave <0xb7741b70>
36 03/22/12 20:56:12.844 GENERIC TYPE: Multilevel Switch <0xb7741b70>
36 03/22/12 20:56:12.844 SPECIFIC TYPE: 0x1 <0xb7741b70>
05 03/22/12 20:56:12.844 ZWave::InternalIDToDevice() No device found for id 11 <0xb7741b70>
05 03/22/12 20:56:12.901 ZWave::InternalIDToDevice() No device found for id 11 <0xb7741b70>
36 03/22/12 20:56:12.901 Device capabilities:  <0xb7741b70>
36 03/22/12 20:56:13.006 Got reply to FUNC_ID_ZW_GET_NODE_PROTOCOL_INFO: <0xb7741b70>
36 03/22/12 20:56:13.006 ***FOUND NODE: 12 <0xb7741b70>
36 03/22/12 20:56:13.006 listening node <0xb7741b70>
36 03/22/12 20:56:13.006 BASIC TYPE: Routing Slave <0xb7741b70>
36 03/22/12 20:56:13.006 GENERIC TYPE: Multilevel Switch <0xb7741b70>
36 03/22/12 20:56:13.006 SPECIFIC TYPE: 0x1 <0xb7741b70>
05 03/22/12 20:56:13.006 ZWave::InternalIDToDevice() No device found for id 12 <0xb7741b70>
05 03/22/12 20:56:13.074 ZWave::InternalIDToDevice() No device found for id 12 <0xb7741b70>
36 03/22/12 20:56:13.074 Device capabilities:  <0xb7741b70>
36 03/22/12 20:56:13.178 Got reply to FUNC_ID_ZW_GET_NODE_PROTOCOL_INFO: <0xb7741b70>
36 03/22/12 20:56:13.178 ***FOUND NODE: 13 <0xb7741b70>
36 03/22/12 20:56:13.178 listening node <0xb7741b70>
36 03/22/12 20:56:13.178 BASIC TYPE: Routing Slave <0xb7741b70>
36 03/22/12 20:56:13.178 GENERIC TYPE: Multilevel Switch <0xb7741b70>
36 03/22/12 20:56:13.178 SPECIFIC TYPE: 0x1 <0xb7741b70>
05 03/22/12 20:56:13.178 ZWave::InternalIDToDevice() No device found for id 13 <0xb7741b70>
05 03/22/12 20:56:13.221 ZWave::InternalIDToDevice() No device found for id 13 <0xb7741b70>
36 03/22/12 20:56:13.221 Device capabilities:  <0xb7741b70>
36 03/22/12 20:56:13.325 Got reply to FUNC_ID_ZW_GET_NODE_PROTOCOL_INFO: <0xb7741b70>
36 03/22/12 20:56:13.325 ***FOUND NODE: 14 <0xb7741b70>
36 03/22/12 20:56:13.325 listening node <0xb7741b70>
36 03/22/12 20:56:13.325 BASIC TYPE: Routing Slave <0xb7741b70>
36 03/22/12 20:56:13.325 GENERIC TYPE: Multilevel Switch <0xb7741b70>
36 03/22/12 20:56:13.325 SPECIFIC TYPE: 0x1 <0xb7741b70>
05 03/22/12 20:56:13.325 ZWave::InternalIDToDevice() No device found for id 14 <0xb7741b70>
05 03/22/12 20:56:13.399 ZWave::InternalIDToDevice() No device found for id 14 <0xb7741b70>
36 03/22/12 20:56:13.399 Device capabilities:  <0xb7741b70>
36 03/22/12 20:56:13.503 Got reply to FUNC_ID_ZW_GET_NODE_PROTOCOL_INFO: <0xb7741b70>
36 03/22/12 20:56:13.503 ***FOUND NODE: 15 <0xb7741b70>
36 03/22/12 20:56:13.503 sleeping node <0xb7741b70>
36 03/22/12 20:56:13.503 BASIC TYPE: Controller <0xb7741b70>
36 03/22/12 20:56:13.503 GENERIC TYPE: Remote Switch <0xb7741b70>
36 03/22/12 20:56:13.503 SPECIFIC TYPE: 0x0 <0xb7741b70>
05 03/22/12 20:56:13.503 ZWave::InternalIDToDevice() No device found for id 15 <0xb7741b70>
36 03/22/12 20:56:13.503 Device capabilities:  <0xb7741b70>
36 03/22/12 20:56:13.607 Got reply to FUNC_ID_ZW_GET_NODE_PROTOCOL_INFO: <0xb7741b70>
36 03/22/12 20:56:13.607 ***FOUND NODE: 16 <0xb7741b70>
36 03/22/12 20:56:13.607 sleeping node <0xb7741b70>
36 03/22/12 20:56:13.607 BASIC TYPE: Controller <0xb7741b70>
36 03/22/12 20:56:13.607 GENERIC TYPE: Remote Switch <0xb7741b70>
36 03/22/12 20:56:13.607 SPECIFIC TYPE: 0x0 <0xb7741b70>
05 03/22/12 20:56:13.607 ZWave::InternalIDToDevice() No device found for id 16 <0xb7741b70>
36 03/22/12 20:56:13.607 Device capabilities:  <0xb7741b70>
36 03/22/12 20:56:13.711 Got reply to FUNC_ID_ZW_GET_NODE_PROTOCOL_INFO: <0xb7741b70>
36 03/22/12 20:56:13.711 ***FOUND NODE: 17 <0xb7741b70>
36 03/22/12 20:56:13.711 listening node <0xb7741b70>
36 03/22/12 20:56:13.711 BASIC TYPE: Routing Slave <0xb7741b70>
36 03/22/12 20:56:13.711 GENERIC TYPE: Binary Switch <0xb7741b70>
36 03/22/12 20:56:13.711 SPECIFIC TYPE: 0x1 <0xb7741b70>
05 03/22/12 20:56:13.711 ZWave::InternalIDToDevice() No device found for id 17 <0xb7741b70>
05 03/22/12 20:56:13.757 ZWave::InternalIDToDevice() No device found for id 17 <0xb7741b70>
36 03/22/12 20:56:13.757 Device capabilities:  <0xb7741b70>
36 03/22/12 20:56:13.861 Got reply to FUNC_ID_ZW_GET_NODE_PROTOCOL_INFO: <0xb7741b70>
36 03/22/12 20:56:13.861 ***FOUND NODE: 18 <0xb7741b70>
36 03/22/12 20:56:13.861 sleeping node <0xb7741b70>
36 03/22/12 20:56:13.861 BASIC TYPE: Controller <0xb7741b70>
36 03/22/12 20:56:13.861 GENERIC TYPE: Remote Switch <0xb7741b70>
36 03/22/12 20:56:13.861 SPECIFIC TYPE: 0x0 <0xb7741b70>
05 03/22/12 20:56:13.861 ZWave::InternalIDToDevice() No device found for id 18 <0xb7741b70>
36 03/22/12 20:56:13.861 Device capabilities:  <0xb7741b70>
36 03/22/12 20:56:13.965 Got reply to FUNC_ID_ZW_GET_NODE_PROTOCOL_INFO: <0xb7741b70>
36 03/22/12 20:56:13.965 ***FOUND NODE: 19 <0xb7741b70>
36 03/22/12 20:56:13.965 listening node <0xb7741b70>
36 03/22/12 20:56:13.965 BASIC TYPE: Routing Slave <0xb7741b70>
36 03/22/12 20:56:13.965 GENERIC TYPE: Multilevel Switch <0xb7741b70>
36 03/22/12 20:56:13.965 SPECIFIC TYPE: 0x1 <0xb7741b70>
05 03/22/12 20:56:13.965 ZWave::InternalIDToDevice() No device found for id 19 <0xb7741b70>
05 03/22/12 20:56:14.045 ZWave::InternalIDToDevice() No device found for id 19 <0xb7741b70>
36 03/22/12 20:56:14.045 Device capabilities:  <0xb7741b70>
36 03/22/12 20:56:14.149 Got reply to FUNC_ID_ZW_GET_NODE_PROTOCOL_INFO: <0xb7741b70>
36 03/22/12 20:56:14.149 ***FOUND NODE: 20 <0xb7741b70>
36 03/22/12 20:56:14.149 listening node <0xb7741b70>
36 03/22/12 20:56:14.149 BASIC TYPE: Routing Slave <0xb7741b70>
36 03/22/12 20:56:14.149 GENERIC TYPE: Multilevel Switch <0xb7741b70>
36 03/22/12 20:56:14.149 SPECIFIC TYPE: 0x1 <0xb7741b70>
36 03/22/12 20:56:14.153 Device capabilities: BAD PARAMETER <0xb7741b70>
36 03/22/12 20:56:14.257 Got reply to FUNC_ID_ZW_GET_NODE_PROTOCOL_INFO: <0xb7741b70>
36 03/22/12 20:56:14.257 ***FOUND NODE: 21 <0xb7741b70>
36 03/22/12 20:56:14.257 listening node <0xb7741b70>
36 03/22/12 20:56:14.257 BASIC TYPE: Routing Slave <0xb7741b70>
36 03/22/12 20:56:14.257 GENERIC TYPE: Multilevel Switch <0xb7741b70>
36 03/22/12 20:56:14.257 SPECIFIC TYPE: 0x1 <0xb7741b70>
36 03/22/12 20:56:14.261 Device capabilities: BAD PARAMETER <0xb7741b70>
36 03/22/12 20:56:14.365 Got reply to FUNC_ID_ZW_GET_NODE_PROTOCOL_INFO: <0xb7741b70>
36 03/22/12 20:56:14.365 ***FOUND NODE: 22 <0xb7741b70>
36 03/22/12 20:56:14.365 listening node <0xb7741b70>
36 03/22/12 20:56:14.365 BASIC TYPE: Routing Slave <0xb7741b70>
36 03/22/12 20:56:14.365 GENERIC TYPE: Multilevel Switch <0xb7741b70>
36 03/22/12 20:56:14.365 SPECIFIC TYPE: 0x1 <0xb7741b70>
36 03/22/12 20:56:14.369 Device capabilities: BAD PARAMETER <0xb7741b70>
36 03/22/12 20:56:14.473 Got reply to FUNC_ID_ZW_GET_NODE_PROTOCOL_INFO: <0xb7741b70>
36 03/22/12 20:56:14.473 ***FOUND NODE: 23 <0xb7741b70>
36 03/22/12 20:56:14.473 sleeping node <0xb7741b70>
36 03/22/12 20:56:14.473 BASIC TYPE: Controller <0xb7741b70>
36 03/22/12 20:56:14.473 GENERIC TYPE: Remote Switch <0xb7741b70>
36 03/22/12 20:56:14.473 SPECIFIC TYPE: 0x0 <0xb7741b70>
05 03/22/12 20:56:14.473 ZWave::InternalIDToDevice() No device found for id 23 <0xb7741b70>
36 03/22/12 20:56:14.473 Device capabilities:  <0xb7741b70>
36 03/22/12 20:56:14.577 Got reply to FUNC_ID_ZW_GET_NODE_PROTOCOL_INFO: <0xb7741b70>
36 03/22/12 20:56:14.577 ***FOUND NODE: 24 <0xb7741b70>
36 03/22/12 20:56:14.577 listening node <0xb7741b70>
36 03/22/12 20:56:14.577 optional functionality <0xb7741b70>
36 03/22/12 20:56:14.577 BASIC TYPE: Routing Slave <0xb7741b70>
36 03/22/12 20:56:14.577 GENERIC TYPE: Binary Switch <0xb7741b70>
36 03/22/12 20:56:14.577 SPECIFIC TYPE: 0x1 <0xb7741b70>
36 03/22/12 20:56:14.581 Device capabilities: BAD PARAMETER <0xb7741b70>
36 03/22/12 20:56:14.685 Got reply to FUNC_ID_ZW_GET_NODE_PROTOCOL_INFO: <0xb7741b70>
36 03/22/12 20:56:14.685 ***FOUND NODE: 25 <0xb7741b70>
36 03/22/12 20:56:14.685 listening node <0xb7741b70>
36 03/22/12 20:56:14.685 BASIC TYPE: Routing Slave <0xb7741b70>
36 03/22/12 20:56:14.685 GENERIC TYPE: Multilevel Switch <0xb7741b70>
36 03/22/12 20:56:14.685 SPECIFIC TYPE: 0x1 <0xb7741b70>
36 03/22/12 20:56:14.690 Device capabilities: BAD PARAMETER <0xb7741b70>
36 03/22/12 20:56:14.794 Got reply to FUNC_ID_ZW_GET_NODE_PROTOCOL_INFO: <0xb7741b70>
36 03/22/12 20:56:14.794 ***FOUND NODE: 28 <0xb7741b70>
36 03/22/12 20:56:14.794 listening node <0xb7741b70>
36 03/22/12 20:56:14.794 BASIC TYPE: Routing Slave <0xb7741b70>
36 03/22/12 20:56:14.794 GENERIC TYPE: Multilevel Switch <0xb7741b70>
36 03/22/12 20:56:14.794 SPECIFIC TYPE: 0x1 <0xb7741b70>
36 03/22/12 20:56:14.799 Device capabilities: BAD PARAMETER <0xb7741b70>
36 03/22/12 20:56:14.902 Got reply to FUNC_ID_ZW_GET_NODE_PROTOCOL_INFO: <0xb7741b70>
36 03/22/12 20:56:14.902 ***FOUND NODE: 29 <0xb7741b70>
36 03/22/12 20:56:14.902 sleeping node <0xb7741b70>
36 03/22/12 20:56:14.902 BASIC TYPE: Controller <0xb7741b70>
36 03/22/12 20:56:14.902 GENERIC TYPE: Remote Switch <0xb7741b70>
36 03/22/12 20:56:14.902 SPECIFIC TYPE: 0x0 <0xb7741b70>
05 03/22/12 20:56:14.902 ZWave::InternalIDToDevice() No device found for id 29 <0xb7741b70>
36 03/22/12 20:56:14.902 Device capabilities:  <0xb7741b70>
36 03/22/12 20:56:15.006 Got reply to FUNC_ID_ZW_GET_NODE_PROTOCOL_INFO: <0xb7741b70>
36 03/22/12 20:56:15.006 ***FOUND NODE: 31 <0xb7741b70>
36 03/22/12 20:56:15.006 listening node <0xb7741b70>
36 03/22/12 20:56:15.006 BASIC TYPE: Routing Slave <0xb7741b70>
36 03/22/12 20:56:15.006 GENERIC TYPE: Binary Switch <0xb7741b70>
36 03/22/12 20:56:15.006 SPECIFIC TYPE: 0x1 <0xb7741b70>
36 03/22/12 20:56:15.019 Device capabilities: BAD PARAMETER <0xb7741b70>
36 03/22/12 20:56:15.122 Got reply to FUNC_ID_ZW_GET_NODE_PROTOCOL_INFO: <0xb7741b70>
36 03/22/12 20:56:15.122 ***FOUND NODE: 36 <0xb7741b70>
36 03/22/12 20:56:15.122 listening node <0xb7741b70>
36 03/22/12 20:56:15.122 BASIC TYPE: Routing Slave <0xb7741b70>
36 03/22/12 20:56:15.122 GENERIC TYPE: Multilevel Switch <0xb7741b70>
36 03/22/12 20:56:15.122 SPECIFIC TYPE: 0x1 <0xb7741b70>
36 03/22/12 20:56:15.126 Device capabilities: BAD PARAMETER <0xb7741b70>
36 03/22/12 20:56:15.230 Got reply to FUNC_ID_ZW_GET_NODE_PROTOCOL_INFO: <0xb7741b70>
36 03/22/12 20:56:15.230 ***FOUND NODE: 37 <0xb7741b70>
36 03/22/12 20:56:15.230 listening node <0xb7741b70>
36 03/22/12 20:56:15.230 BASIC TYPE: Static Controller <0xb7741b70>
36 03/22/12 20:56:15.230 GENERIC TYPE: Static Controller <0xb7741b70>
36 03/22/12 20:56:15.230 SPECIFIC TYPE: 0x1 <0xb7741b70>
05 03/22/12 20:56:15.230 ZWave::InternalIDToDevice() No device found for id 37 <0xb7741b70>
36 03/22/12 20:56:15.230 Device capabilities:  <0xb7741b70>
36 03/22/12 20:56:15.334 Got reply to FUNC_ID_ZW_GET_NODE_PROTOCOL_INFO: <0xb7741b70>
36 03/22/12 20:56:15.334 ***FOUND NODE: 38 <0xb7741b70>
36 03/22/12 20:56:15.334 listening node <0xb7741b70>
36 03/22/12 20:56:15.334 optional functionality <0xb7741b70>
36 03/22/12 20:56:15.334 BASIC TYPE: Static Controller <0xb7741b70>
36 03/22/12 20:56:15.334 GENERIC TYPE: Static Controller <0xb7741b70>
36 03/22/12 20:56:15.334 SPECIFIC TYPE: 0x1 <0xb7741b70>
05 03/22/12 20:56:15.334 ZWave::InternalIDToDevice() No device found for id 38 <0xb7741b70>
36 03/22/12 20:56:15.334 Device capabilities:  <0xb7741b70>
36 03/22/12 20:56:15.438 Got reply to FUNC_ID_ZW_GET_NODE_PROTOCOL_INFO: <0xb7741b70>
36 03/22/12 20:56:15.438 ***FOUND NODE: 40 <0xb7741b70>
36 03/22/12 20:56:15.438 listening node <0xb7741b70>
36 03/22/12 20:56:15.438 optional functionality <0xb7741b70>
36 03/22/12 20:56:15.438 BASIC TYPE: Static Controller <0xb7741b70>
36 03/22/12 20:56:15.438 GENERIC TYPE: Static Controller <0xb7741b70>
36 03/22/12 20:56:15.438 SPECIFIC TYPE: 0x1 <0xb7741b70>
05 03/22/12 20:56:15.438 ZWave::InternalIDToDevice() No device found for id 40 <0xb7741b70>
36 03/22/12 20:56:15.438 Device capabilities:  <0xb7741b70>
36 03/22/12 20:56:15.542 Got reply to FUNC_ID_ZW_GET_NODE_PROTOCOL_INFO: <0xb7741b70>
36 03/22/12 20:56:15.542 ***FOUND NODE: 41 <0xb7741b70>
36 03/22/12 20:56:15.542 listening node <0xb7741b70>
36 03/22/12 20:56:15.542 BASIC TYPE: Static Controller <0xb7741b70>
36 03/22/12 20:56:15.542 GENERIC TYPE: Static Controller <0xb7741b70>
36 03/22/12 20:56:15.542 SPECIFIC TYPE: 0x1 <0xb7741b70>
05 03/22/12 20:56:15.542 ZWave::InternalIDToDevice() No device found for id 41 <0xb7741b70>
36 03/22/12 20:56:15.542 Device capabilities:  <0xb7741b70>
05 03/22/12 20:56:15.542 Finished building node list: <0xb7741b70>
05 03/22/12 20:56:15.542 Node: 2 basic: 0x1 generic: 0x12 specific: 0x0 pluto: 0 <0xb7741b70>
05 03/22/12 20:56:15.542 Node: 3 basic: 0x4 generic: 0x11 specific: 0x1 pluto: 38 <0xb7741b70>
05 03/22/12 20:56:15.542 Node: 4 basic: 0x4 generic: 0x11 specific: 0x1 pluto: 38 <0xb7741b70>
05 03/22/12 20:56:15.542 Node: 5 basic: 0x4 generic: 0x11 specific: 0x1 pluto: 38 <0xb7741b70>
05 03/22/12 20:56:15.542 Node: 6 basic: 0x3 generic: 0x11 specific: 0x0 pluto: 38 <0xb7741b70>
05 03/22/12 20:56:15.542 Node: 7 basic: 0x3 generic: 0x11 specific: 0x0 pluto: 38 <0xb7741b70>
05 03/22/12 20:56:15.542 Node: 8 basic: 0x4 generic: 0x10 specific: 0x1 pluto: 37 <0xb7741b70>
05 03/22/12 20:56:15.542 Node: 9 basic: 0x4 generic: 0x11 specific: 0x1 pluto: 38 <0xb7741b70>
05 03/22/12 20:56:15.542 Node: 10 basic: 0x4 generic: 0x10 specific: 0x1 pluto: 37 <0xb7741b70>
05 03/22/12 20:56:15.542 Node: 11 basic: 0x4 generic: 0x11 specific: 0x1 pluto: 38 <0xb7741b70>
05 03/22/12 20:56:15.542 Node: 12 basic: 0x4 generic: 0x11 specific: 0x1 pluto: 38 <0xb7741b70>
05 03/22/12 20:56:15.542 Node: 13 basic: 0x4 generic: 0x11 specific: 0x1 pluto: 38 <0xb7741b70>
05 03/22/12 20:56:15.542 Node: 14 basic: 0x4 generic: 0x11 specific: 0x1 pluto: 38 <0xb7741b70>
05 03/22/12 20:56:15.542 Node: 15 basic: 0x1 generic: 0x12 specific: 0x0 pluto: 0 <0xb7741b70>
05 03/22/12 20:56:15.543 Node: 16 basic: 0x1 generic: 0x12 specific: 0x0 pluto: 0 <0xb7741b70>
05 03/22/12 20:56:15.543 Node: 17 basic: 0x4 generic: 0x10 specific: 0x1 pluto: 37 <0xb7741b70>
05 03/22/12 20:56:15.543 Node: 18 basic: 0x1 generic: 0x12 specific: 0x0 pluto: 0 <0xb7741b70>
05 03/22/12 20:56:15.543 Node: 19 basic: 0x4 generic: 0x11 specific: 0x1 pluto: 38 <0xb7741b70>
05 03/22/12 20:56:15.543 Node: 20 basic: 0x4 generic: 0x11 specific: 0x1 pluto: 38 <0xb7741b70>
05 03/22/12 20:56:15.543 Node: 21 basic: 0x4 generic: 0x11 specific: 0x1 pluto: 38 <0xb7741b70>
05 03/22/12 20:56:15.543 Node: 22 basic: 0x4 generic: 0x11 specific: 0x1 pluto: 38 <0xb7741b70>
05 03/22/12 20:56:15.543 Node: 23 basic: 0x1 generic: 0x12 specific: 0x0 pluto: 0 <0xb7741b70>
05 03/22/12 20:56:15.543 Node: 24 basic: 0x4 generic: 0x10 specific: 0x1 pluto: 37 <0xb7741b70>
05 03/22/12 20:56:15.543 Node: 25 basic: 0x4 generic: 0x11 specific: 0x1 pluto: 38 <0xb7741b70>
05 03/22/12 20:56:15.543 Node: 28 basic: 0x4 generic: 0x11 specific: 0x1 pluto: 38 <0xb7741b70>
05 03/22/12 20:56:15.543 Node: 29 basic: 0x1 generic: 0x12 specific: 0x0 pluto: 0 <0xb7741b70>
05 03/22/12 20:56:15.543 Node: 31 basic: 0x4 generic: 0x10 specific: 0x1 pluto: 37 <0xb7741b70>
05 03/22/12 20:56:15.543 Node: 36 basic: 0x4 generic: 0x11 specific: 0x1 pluto: 38 <0xb7741b70>
05 03/22/12 20:56:15.543 Node: 37 basic: 0x2 generic: 0x2 specific: 0x1 pluto: 0 <0xb7741b70>
05 03/22/12 20:56:15.543 Node: 38 basic: 0x2 generic: 0x2 specific: 0x1 pluto: 0 <0xb7741b70>
05 03/22/12 20:56:15.543 Node: 40 basic: 0x2 generic: 0x2 specific: 0x1 pluto: 0 <0xb7741b70>
05 03/22/12 20:56:15.543 Node: 41 basic: 0x2 generic: 0x2 specific: 0x1 pluto: 0 <0xb7741b70>
36 03/22/12 20:56:45.681 We have been idle for 30 seconds, polling device states <0xb7741b70>
36 03/22/12 20:56:45.785 ZW_SEND delivered to Z-Wave stack <0xb7741b70>
36 03/22/12 20:56:45.806 ZW_SEND Response with callback 2 received <0xb7741b70>
36 03/22/12 20:56:45.806 ZW_SEND was successful, removing job <0xb7741b70>
36 03/22/12 20:56:45.831 FUNC_ID_APPLICATION_COMMAND_HANDLER: <0xb7741b70>
36 03/22/12 20:56:45.831 COMMAND_CLASS_BASIC -  <0xb7741b70>
36 03/22/12 20:56:45.831 Got basic report from node 36, value: 0 <0xb7741b70>
36 03/22/12 20:56:45.831 State changed, send light changed event <0xb7741b70>
36 03/22/12 20:56:45.831 Sending EVENT_State_Changed_CONST event from node 36/-1, level 0 <0xb7741b70>
36 03/22/12 20:56:45.935 ZW_SEND delivered to Z-Wave stack <0xb7741b70>
36 03/22/12 20:56:45.940 FUNC_ID_APPLICATION_COMMAND_HANDLER: <0xb7741b70>
36 03/22/12 20:56:45.940 COMMAND_CLASS_BASIC -  <0xb7741b70>
36 03/22/12 20:56:45.940 Got basic report from node 6, value: 0 <0xb7741b70>
36 03/22/12 20:56:45.940 State changed, send light changed event <0xb7741b70>
36 03/22/12 20:56:45.940 Sending EVENT_State_Changed_CONST event from node 6/-1, level 0 <0xb7741b70>
36 03/22/12 20:56:45.941 Generic callback handling for command 4, ERROR: wrong callback type: 19 <0xb7741b70>
36 03/22/12 20:56:45.982 ZW_SEND Response with callback 3 received <0xb7741b70>
36 03/22/12 20:56:45.982 ZW_SEND was successful, removing job <0xb7741b70>
36 03/22/12 20:56:46.087 ZW_SEND delivered to Z-Wave stack <0xb7741b70>
36 03/22/12 20:56:46.108 ZW_SEND Response with callback 4 received <0xb7741b70>
36 03/22/12 20:56:46.108 ZW_SEND was successful, removing job <0xb7741b70>
36 03/22/12 20:56:46.170 FUNC_ID_APPLICATION_COMMAND_HANDLER: <0xb7741b70>
36 03/22/12 20:56:46.170 COMMAND_CLASS_BASIC -  <0xb7741b70>
36 03/22/12 20:56:46.170 Got basic report from node 5, value: 0 <0xb7741b70>
36 03/22/12 20:56:46.170 State changed, send light changed event <0xb7741b70>
36 03/22/12 20:56:46.170 Sending EVENT_State_Changed_CONST event from node 5/-1, level 0 <0xb7741b70>

I see things like:

05   03/22/12 20:56:14.473      ZWave::InternalIDToDevice() No device found for id 23 <0xb7741b70>

These are the devices that are not on the list after a reload router.
« Last Edit: March 23, 2012, 09:45:58 pm by Domodude »

Domodude

  • Guest
Re: [Dianemo S]Z-Wave lights are removed from list after reload router!
« Reply #10 on: March 22, 2012, 09:35:21 pm »
BTW I _still_ have not figured out what makes the devices reappear after some (seemingly) random amount of time....

Domodude

  • Guest
Re: [Dianemo S]Z-Wave lights are removed from list after reload router!
« Reply #11 on: March 31, 2012, 10:46:29 am »
Little bump.
I am now back from my journey, and am about to start using the minimote. That should do the trick. Anything else that I should provide, log-wise? I plan to start configuration with the minimote in a few hours, but then this strange situation will hopefully also be gone. Hari, if you're interested in more info than the above log, lemme know  ;)...
Cheers,

hari

  • Administrator
  • LinuxMCE God
  • *****
  • Posts: 2420
    • View Profile
    • ago control
Re: [Dianemo S]Z-Wave lights are removed from list after reload router!
« Reply #12 on: April 02, 2012, 02:36:05 pm »
i need the logs before and after the "vanish" event
rock your home - http://www.agocontrol.com home automation

Domodude

  • Guest
Re: [Dianemo S]Z-Wave lights are removed from list after reload router!
« Reply #13 on: April 02, 2012, 03:10:49 pm »
Ah that's unfortunate -- I went ahead and used the minimote in a SUC-SIS inclusion of my network. This works, as you predicted, flawlessly. Too bad that we cannot figure out anymore why the units kept disappearing from the list, but the problem is "solved" and it looks like it happened only on my system...

hari

  • Administrator
  • LinuxMCE God
  • *****
  • Posts: 2420
    • View Profile
    • ago control
Re: [Dianemo S]Z-Wave lights are removed from list after reload router!
« Reply #14 on: April 02, 2012, 11:14:12 pm »
maybe something stored in the eeprom of the stick was bad.. a rebuild would have overwritten the old, maybe buggy network config..
rock your home - http://www.agocontrol.com home automation