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:
[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!