ahey guys, I'm running an up to date 8.10 and i have a tricklestar usb dongle. Is does not get detected automatically as a zwave dongle. upon plugging it in it runs through a detection script for a few other devices such as a denon receiver. So i added it to the zwave template. It still does not get detected until a manually add the zwave template to core as a child device. after a reload, all the switches and dimmers are listed and i can run the wizard. following that, i would try to turn on a switch and it will work fine for about 2-3 commands, but always dies soon after. i saw another post where posde suggested a wget from the svn. I did that but the same issues occurs. thanks in advance, here's the log fellas:
102 (spawning-device) Found /usr/pluto/bin/ZWave
05 04/27/10 12:58:42.147 Connect() failed, Error Code 111 (Connection refused)) <0xb70a76c0>
05 04/27/10 12:58:43.147 Connect() failed, Error Code 111 (Connection refused)) <0xb70a76c0>
05 04/27/10 12:58:44.147 Connect() failed, Error Code 111 (Connection refused)) <0xb70a76c0>
05 04/27/10 12:58:45.147 Connect() failed, Error Code 111 (Connection refused)) <0xb70a76c0>
05 04/27/10 12:58:50.553 Creating child 103 <0xb70a76c0>
05 04/27/10 12:58:50.553 Note: Device manager has attached a device of type 1820 that this has no custom event handler for. It will not fire events. <0xb70a76c0>
05 04/27/10 12:58:50.553 Note: Device manager has attached a device of type 1820 that this has no custom handler for. This is normal for IR. <0xb70a76c0>
05 04/27/10 12:58:50.553 Creating child 104 <0xb70a76c0>
05 04/27/10 12:58:50.553 Note: Device manager has attached a device of type 1922 that this has no custom event handler for. It will not fire events. <0xb70a76c0>
05 04/27/10 12:58:50.553 Note: Device manager has attached a device of type 1922 that this has no custom handler for. This is normal for IR. <0xb70a76c0>
05 04/27/10 12:58:50.553 Creating child 105 <0xb70a76c0>
05 04/27/10 12:58:50.553 Note: Device manager has attached a device of type 37 that this has no custom event handler for. It will not fire events. <0xb70a76c0>
05 04/27/10 12:58:50.553 Note: Device manager has attached a device of type 37 that this has no custom handler for. This is normal for IR. <0xb70a76c0>
05 04/27/10 12:58:50.553 Creating child 106 <0xb70a76c0>
05 04/27/10 12:58:50.553 Note: Device manager has attached a device of type 1945 that this has no custom event handler for. It will not fire events. <0xb70a76c0>
05 04/27/10 12:58:50.553 Note: Device manager has attached a device of type 1945 that this has no custom handler for. This is normal for IR. <0xb70a76c0>
05 04/27/10 12:58:50.553 Creating child 107 <0xb70a76c0>
05 04/27/10 12:58:50.553 Note: Device manager has attached a device of type 38 that this has no custom event handler for. It will not fire events. <0xb70a76c0>
05 04/27/10 12:58:50.554 Note: Device manager has attached a device of type 38 that this has no custom handler for. This is normal for IR. <0xb70a76c0>
05 04/27/10 12:58:50.555 Creating child 108 <0xb70a76c0>
05 04/27/10 12:58:50.555 Note: Device manager has attached a device of type 38 that this has no custom event handler for. It will not fire events. <0xb70a76c0>
05 04/27/10 12:58:50.555 Note: Device manager has attached a device of type 38 that this has no custom handler for. This is normal for IR. <0xb70a76c0>
05 04/27/10 12:58:50.555 Creating child 109 <0xb70a76c0>
05 04/27/10 12:58:50.555 Note: Device manager has attached a device of type 38 that this has no custom event handler for. It will not fire events. <0xb70a76c0>
05 04/27/10 12:58:50.555 Note: Device manager has attached a device of type 38 that this has no custom handler for. This is normal for IR. <0xb70a76c0>
05 04/27/10 12:58:53.583 No callback received: await_callback: 139155812 timer: 31 <0xb70a6b90>
05 04/27/10 12:58:53.795 Got reply to ZW_MEMORY_GET_ID, Home id: 0x007a4ab6, our node id: 2 <0xb70a6b90>
05 04/27/10 12:58:54.007 Got reply to GET_SUC_NODE_ID, node: 0 <0xb70a6b90>
05 04/27/10 12:58:54.007 No SUC, we become SUC <0xb70a6b90>
05 04/27/10 12:58:57.468 No callback received: await_callback: 1 timer: 31 <0xb70a6b90>
05 04/27/10 12:59:05.167 No callback received: await_callback: 1 timer: 31 <0xb70a6b90>
05 04/27/10 12:59:08.371 No callback received: await_callback: 1 timer: 31 <0xb70a6b90>
01 04/27/10 12:59:08.371 ERROR: Dropping command, no callback received after three resends <0xb70a6b90>
05 04/27/10 12:59:08.895 Finished building node list: <0xb70a6b90>
05 04/27/10 12:59:08.895 Node: 1 basic: 0x3 generic: 0x10 specific: 0x0 pluto: 37 <0xb70a6b90>
05 04/27/10 12:59:08.895 Node: 2 basic: 0x2 generic: 0x2 specific: 0x0 pluto: 1945 <0xb70a6b90>
05 04/27/10 12:59:08.895 Node: 4 basic: 0x3 generic: 0x11 specific: 0x0 pluto: 38 <0xb70a6b90>
05 04/27/10 12:59:08.895 Node: 6 basic: 0x3 generic: 0x11 specific: 0x0 pluto: 38 <0xb70a6b90>
05 04/27/10 12:59:08.895 Node: 9 basic: 0x3 generic: 0x11 specific: 0x0 pluto: 38 <0xb70a6b90>
01 04/27/10 13:00:35.867 Checksum incorrect 2f - sending NAK <0xb70a6b90>
05 04/27/10 13:01:09.319 No callback received: await_callback: 8 timer: 31 <0xb70a6b90>
05 04/27/10 13:01:12.519 No callback received: await_callback: 8 timer: 31 <0xb70a6b90>
05 04/27/10 13:01:15.719 No callback received: await_callback: 8 timer: 31 <0xb70a6b90>
01 04/27/10 13:01:15.719 ERROR: Dropping command, no callback received after three resends <0xb70a6b90>
05 04/27/10 13:01:18.919 No callback received: await_callback: 9 timer: 31 <0xb70a6b90>
05 04/27/10 13:01:22.119 No callback received: await_callback: 9 timer: 31 <0xb70a6b90>
05 04/27/10 13:01:25.319 No callback received: await_callback: 9 timer: 31 <0xb70a6b90>
01 04/27/10 13:01:25.319 ERROR: Dropping command, no callback received after three resends <0xb70a6b90>
05 04/27/10 13:01:58.627 No callback received: await_callback: 10 timer: 31 <0xb70a6b90>
05 04/27/10 13:02:01.828 No callback received: await_callback: 10 timer: 31 <0xb70a6b90>
05 04/27/10 13:02:05.027 No callback received: await_callback: 10 timer: 31 <0xb70a6b90>
01 04/27/10 13:02:05.027 ERROR: Dropping command, no callback received after three resends <0xb70a6b90>
05 04/27/10 13:02:08.239 No callback received: await_callback: 11 timer: 31 <0xb70a6b90>
05 04/27/10 13:02:11.439 No callback received: await_callback: 11 timer: 31 <0xb70a6b90>
05 04/27/10 13:02:14.640 No callback received: await_callback: 11 timer: 31 <0xb70a6b90>
01 04/27/10 13:02:14.640 ERROR: Dropping command, no callback received after three resends <0xb70a6b90>
05 04/27/10 13:02:48.039 No callback received: await_callback: 12 timer: 31 <0xb70a6b90>
05 04/27/10 13:02:51.239 No callback received: await_callback: 12 timer: 31 <0xb70a6b90>
05 04/27/10 13:02:54.439 No callback received: await_callback: 12 timer: 31 <0xb70a6b90>
01 04/27/10 13:02:54.440 ERROR: Dropping command, no callback received after three resends <0xb70a6b90>
05 04/27/10 13:02:57.639 No callback received: await_callback: 13 timer: 31 <0xb70a6b90>
05 04/27/10 13:03:00.840 No callback received: await_callback: 13 timer: 31 <0xb70a6b90>
05 04/27/10 13:03:04.048 No callback received: await_callback: 13 timer: 31 <0xb70a6b90>
01 04/27/10 13:03:04.048 ERROR: Dropping command, no callback received after three resends <0xb70a6b90>
05 04/27/10 13:03:24.547 No callback received: await_callback: 14 timer: 31 <0xb70a6b90>
05 04/27/10 13:03:27.747 No callback received: await_callback: 14 timer: 31 <0xb70a6b90>
05 04/27/10 13:03:30.951 No callback received: await_callback: 14 timer: 31 <0xb70a6b90>
01 04/27/10 13:03:30.951 ERROR: Dropping command, no callback received after three resends <0xb70a6b90>
05 04/27/10 13:03:35.348 No callback received: await_callback: 15 timer: 31 <0xb70a6b90>
05 04/27/10 13:03:38.695 No callback received: await_callback: 15 timer: 31 <0xb70a6b90>
05 04/27/10 13:03:41.895 No callback received: await_callback: 15 timer: 31 <0xb70a6b90>
01 04/27/10 13:03:41.895 ERROR: Dropping command, no callback received after three resends <0xb70a6b90>
Is anybody having similar issues or am I doing something wrong? Should I buy a mcv dongle instead?
Hari or anybody, can someone tell me what I'm doing wrong or what is wrong please. If I'm being a bother cause due to me doing something retarded, sorry :)
I don't like the incorrect checksum error in the log, and it seems that it does not receive callbacks afterwards (the callbacks should always arrive, even if they tell us that the send failed). It looks like the dongle is stuck after that. I'd try to reset the dongle completely and rebuild the network. If this does not help, I'd guess that the hardware is bad. The tricklestar should work fine in general (I was testing it for quite some time), so maybe you can have it replaced instead of going for an Aeon Labs.
best regards,
Hari
Ok thanks Hari, is the dongle automatically detected plug n play when working?
no, unfortunately not. It uses the usb manufacturer/device id from the prolific pl2303 usb/serial converter. We would need to do a serial detection script. I had one ready but never managed to test and commit it..
br Hari
Ok cool, I just wanted to know if it was my error as why it wasn't being detected, thanks again Hari