1
Users / Re: Zwave issues
« on: May 05, 2010, 10:00:44 pm »
Ok cool, I just wanted to know if it was my error as why it wasn't being detected, thanks again Hari
News:
Rule #1 - Be Patient - Rule #2 - Don't ask when, if you don't contribute - Rule #3 - You have coding skills - LinuxMCE's small brother is available: http://www.agocontrol.com
LinuxMCE sponsor
open.home.automation
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
2
Users / Re: Zwave issues
« on: May 05, 2010, 05:44:57 pm »
Ok thanks Hari, is the dongle automatically detected plug n play when working?
3
Users / Re: Zwave issues
« on: May 04, 2010, 10:48:50 pm »
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 
4
Users / Re: Zwave issues
« on: April 28, 2010, 05:58:27 pm »
Is anybody having similar issues or am I doing something wrong? Should I buy a mcv dongle instead?
5
Users / Re: Zwave issues
« on: April 27, 2010, 07:19:22 pm »
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>
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>
6
Users / Zwave issues
« on: April 27, 2010, 07:19:06 pm »
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:
7
Users / Re: zotac ion n330 md
« on: October 31, 2009, 07:17:09 pm »
gentlemen, i greatly appreciate your input. thanks for taking the time to answer.
-fred
-fred
8
Users / Re: zotac ion n330 md
« on: October 31, 2009, 04:16:46 pm »I know there is wiki,I just want a definitive answer as to whether there is a noticeable gain in spending the extra dough on the zotac ion N330 rather than getting the 230? is it worth the extra money or is it a overkill for a lmce md?
Our experience is that there is a small gain in overall performance due to the 2nd core but in terms of video playback performance there is really no advantage.
Andrew
andrew, no degradation in HD playback right?
9
Users / zotac ion n330 md
« on: October 31, 2009, 01:40:55 am »
I know there is wiki,I just want a definitive answer as to whether there is a noticeable gain in spending the extra dough on the zotac ion N330 rather than getting the 230? is it worth the extra money or is it a overkill for a lmce md?
10
Users / Re: strange harddrive quirks
« on: October 29, 2009, 10:44:20 pm »
nope, installed on one drive, let lmce setup structure on other
11
Users / Re: strange harddrive quirks
« on: October 29, 2009, 09:28:38 pm »first off, dont use /mnt/device..., they are available in /home/public/data for a reason.
second, due to permissions issues (kde desktop runninng as unprivileged user, lmce managing the drives as root) its much easier to connect to the network shares than access the local filesystem.
aaaahhhh forgive my ignorance, linux is not my string suit, but there isn't a /home/public/data, only /home/public. also, can someone tell me what i can do to make the core harddrive available inthe admin and be able write to my other drive?
12
Users / strange harddrive quirks
« on: October 29, 2009, 07:01:14 pm »
Hi, my core harddrive is not showing up in lmce 8.10 admin or otherwise. it is as if the lmce file structure is non existent or something. then i had a harddrive i added which has video/audio which was detected fine. all the files show up and are playing fine. I can even rip a dvd to the drive using lmce. the problem occurs if i'm trying to copy files or save a download to the harddrive on the kubuntu desktop. i get a message "access denied could not write to /mnt/device/51/public/data/videos".....i have tried changing permissions and changing ownership. what have i done wrong?
13
Users / Re: weird md issue
« on: September 14, 2009, 11:27:08 pm »I have an old asus 8nv mobo i've been using as a 7.10 MD, i installed 8.10. everything, seems to okay, then it hangs atthanks, but i tried tried that. I also tried changing the architecture to i386 and rebuilt the image to no avail. Two other md's work fine. the two older md boards that worked with 710 wont work in 810. i appreciate the help, if i did anything else wrong let me know. thanks.
Ubuntu 8.10 moon59 ttyl
moon login *Starting daemons
...done.
* Reloading /etc/samba/smb.conf smbd only
...done
*reloading system log daemon
...done
nothing happens after that
anybody know what's up?
14
Users / weird md issue
« on: September 11, 2009, 09:51:19 pm »
I have an old asus 8nv mobo i've been using as a 7.10 MD, i installed 8.10. everything, seems to okay, then it hangs at
Ubuntu 8.10 moon59 ttyl
moon login *Starting daemons
...done.
* Reloading /etc/samba/smb.conf smbd only
...done
*reloading system log daemon
...done
nothing happens after that
anybody know what's up?
Ubuntu 8.10 moon59 ttyl
moon login *Starting daemons
...done.
* Reloading /etc/samba/smb.conf smbd only
...done
*reloading system log daemon
...done
nothing happens after that
anybody know what's up?
15
Users / Re: Call for donations for features.
« on: August 15, 2009, 02:01:30 am »
I would contribute to:
1) video phone such as skype, i'm a little bit shocked that I haven't seen this requested very often when posts like these come up. Am I only the one who is interested in that being a part of a advanced system like LinuxMCE?
2) I would contribute to another up to date mobile orbiter. Windows and Android phones will be available on cdma and gsm networks so everyone would be able to utilize a mobile orbiter. Presence detection for alarm purposes would be great.
3) Return of the Disked MD option
1) video phone such as skype, i'm a little bit shocked that I haven't seen this requested very often when posts like these come up. Am I only the one who is interested in that being a part of a advanced system like LinuxMCE?
2) I would contribute to another up to date mobile orbiter. Windows and Android phones will be available on cdma and gsm networks so everyone would be able to utilize a mobile orbiter. Presence detection for alarm purposes would be great.
3) Return of the Disked MD option