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.


Messages - donpaul

Pages: 1 [2] 3 4 ... 20
16
Users / Re: Zwave Out of Frame Flow error
« on: August 01, 2010, 05:06:54 pm »
Is there anything that could stick around from my previous MCV stick/setup, or the bad Tricklestar USB stick/setup? Is there anything I should do besides remove the ZWave device? I don't want any lingering issues when I set up the new stick.

17
Users / Re: Zwave Out of Frame Flow error
« on: August 01, 2010, 04:47:11 pm »
However I still can't say that I have ever seen that error...so its possible (and I say 'possible') that your Tricklestar USB interface is faulty.

All the best

Andrew

I think you're right, the controller has disappeared from the web interface and at hangs here:

05      08/01/10 10:41:51.142           Creating child 295 <0xb70ac6c0>
05      08/01/10 10:41:51.142           Note: Device manager has attached a device of type 1820 that this has no custom event handler for.  It will not fire events. <0xb70ac6c0>
05      08/01/10 10:41:51.142           Note: Device manager has attached a device of type 1820 that this has no custom handler for.  This is normal for IR. <0xb70ac6c0>
05      08/01/10 10:41:51.144           Creating child 296 <0xb70ac6c0>
05      08/01/10 10:41:51.144           Note: Device manager has attached a device of type 1922 that this has no custom event handler for.  It will not fire events. <0xb70ac6c0>
05      08/01/10 10:41:51.144           Note: Device manager has attached a device of type 1922 that this has no custom handler for.  This is normal for IR. <0xb70ac6c0>
05      08/01/10 10:41:51.144           Creating child 297 <0xb70ac6c0>
05      08/01/10 10:41:51.144           Note: Device manager has attached a device of type 1945 that this has no custom event handler for.  It will not fire events. <0xb70ac6c0>
05      08/01/10 10:41:51.144           Note: Device manager has attached a device of type 1945 that this has no custom handler for.  This is normal for IR. <0xb70ac6c0>
05      08/01/10 10:41:53.832           No callback received: await_callback: -1 timer: 31 <0xb70abb90>


I can't get the USB to work at all, I have removed the Zwave device and readded, tried adding the controller manually, tried resetting the usb stick - nothing works. Time to get another stick.

18
Users / Re: zwave tricklestar include problem
« on: July 31, 2010, 11:38:55 pm »
Can someone verify if this is the preferred procedure:

   1. First select 'Add node' from the 'Send to this device the command' drop-down menu and click send (there is no need to fill in any values in this screen).
   2. Next put the remote in configuration mode, then press and hold up until the LED flashes green, then press up four times. The LED will begin flashing green. Once added, the remote LED should start flashing faster then go steady green indicating success. If it goes red then reset the remote (hold up til green, then hold up 10 seconds until 3 color LED), and redo step 1-2.

19
Users / Re: zwave tricklestar include problem
« on: July 31, 2010, 10:03:05 pm »
It worked when I did the copy mode (hold up, 4 up).

20
Users / Re: Zwave Out of Frame Flow error
« on: July 31, 2010, 10:01:57 pm »
Which Zwave binary are you using? Can't say I have ever seen that.

Andrew

This is a fresh install from a snapshot 2 weeks back.

ZWave, open edition, v.0.2

21
Users / Re: Zwave Out of Frame Flow error
« on: July 31, 2010, 08:32:30 pm »
I am getting the same error when trying to add lights with the tricklestar remote. The lights are failing to add.

22
Installation issues / Re: Cannot get tricklestar to work!
« on: July 31, 2010, 07:53:13 pm »
So after lots of reading and trial/error, I am at the point where the tricklestar dongle is added and works, and I added the tricklestar remote as node 2 (put Tricklestar remote in config mode - hold up, then 4 up, then send code to zwave device -> add node).

Here is the log after reload:

05      07/31/10 13:48:46.253           Creating child 141 <0xb71056c0>
05      07/31/10 13:48:46.253           Note: Device manager has attached a device of type 1820 that this has no custom event handler for.  It will not fire events. <0xb71056c0>
05      07/31/10 13:48:46.253           Note: Device manager has attached a device of type 1820 that this has no custom handler for.  This is normal for IR. <0xb71056c0>
05      07/31/10 13:48:46.253           Creating child 142 <0xb71056c0>
05      07/31/10 13:48:46.253           Note: Device manager has attached a device of type 1922 that this has no custom event handler for.  It will not fire events. <0xb71056c0>
05      07/31/10 13:48:46.253           Note: Device manager has attached a device of type 1922 that this has no custom handler for.  This is normal for IR. <0xb71056c0>
05      07/31/10 13:48:46.253           Creating child 154 <0xb71056c0>
05      07/31/10 13:48:46.253           Note: Device manager has attached a device of type 1945 that this has no custom event handler for.  It will not fire events. <0xb71056c0>
05      07/31/10 13:48:46.253           Note: Device manager has attached a device of type 1945 that this has no custom handler for.  This is normal for IR. <0xb71056c0>
05      07/31/10 13:48:46.253           Creating child 162 <0xb71056c0>
05      07/31/10 13:48:46.253           Note: Device manager has attached a device of type 1945 that this has no custom event handler for.  It will not fire events. <0xb71056c0>
05      07/31/10 13:48:46.253           Note: Device manager has attached a device of type 1945 that this has no custom handler for.  This is normal for IR. <0xb71056c0>
05      07/31/10 13:48:49.146           No callback received: await_callback: -1 timer: 31 <0xb7104b90>
05      07/31/10 13:48:49.354           Got reply to ZW_MEMORY_GET_ID, Home id: 0x00d8b265, our node id: 1 <0xb7104b90>
05      07/31/10 13:48:49.566           Got reply to GET_SUC_NODE_ID, node: 1 <0xb7104b90>
05      07/31/10 13:48:51.739           Finished building node list: <0xb7104b90>
05      07/31/10 13:48:51.739           Node: 1 basic: 0x2 generic: 0x2 specific: 0x1 pluto: 1945 <0xb7104b90>
05      07/31/10 13:48:51.739           Node: 2 basic: 0x1 generic: 0x1 specific: 0x1 pluto: 1945 <0xb7104b90>


Now I can add lights using SIS and the tricklestar remote. I am going to update the wiki so this process is less confusing for others.

23
Users / Re: zwave tricklestar include problem
« on: July 31, 2010, 06:50:03 pm »
yeah, make sure that the dongle is the master (node 1) not the remote. You can then remove the remote, reset it, and add it again without loosing the network information.

br Hari

Hari, what is the proper procedure to make sure the dongle is the master? When I add the tricklestar remote by following the wiki (hold up, 1 up - then send command: download), it takes the master spot and moves the dongle down to 2. When I follow the tricklestar procedure for making the remote a secondary (hold up - then 4 up), the dongle stays 1 and the remote is 2 - BUT I am not able to add lights using the tricklestar remote. How did you make it work.

(I will update the wiki once I get this figured out).

24
Installation issues / Re: Cannot get tricklestar to work!
« on: July 31, 2010, 05:10:48 pm »
I got the dongle added, and I see this is the log after a reset:

05      07/31/10 11:03:45.229           Got reply to ZW_MEMORY_GET_ID, Home id: 0x00d8b265, our node id: 1 <0xb71d8b90>
05      07/31/10 11:03:45.441           Got reply to GET_SUC_NODE_ID, node: 0 <0xb71d8b90>
05      07/31/10 11:03:45.441           No SUC, we become SUC <0xb71d8b90>
05      07/31/10 11:03:48.913           No callback received: await_callback: 1 timer: 31 <0xb71d8b90>
05      07/31/10 11:03:52.121           No callback received: await_callback: 1 timer: 31 <0xb71d8b90>
05      07/31/10 11:03:55.329           No callback received: await_callback: 1 timer: 31 <0xb71d8b90>
01      07/31/10 11:03:55.329           ERROR: Dropping command, no callback received after three resends <0xb71d8b90>
05      07/31/10 11:03:55.433           ZWave::InternalIDToDevice() No device found for id 1 <0xb71d8b90>
05      07/31/10 11:03:55.497           ZWave::InternalIDToDevice() No device found for id 1 <0xb71d8b90>
05      07/31/10 11:03:55.497           Finished building node list: <0xb71d8b90>
05      07/31/10 11:03:55.497           Node: 1 basic: 0x2 generic: 0x2 specific: 0x1 pluto: 1945 <0xb71d8b90>


And after a reload, this:

05      07/31/10 11:04:37.321           Got reply to ZW_MEMORY_GET_ID, Home id: 0x00d8b265, our node id: 1 <0xb7244b90>
05      07/31/10 11:04:37.538           Got reply to GET_SUC_NODE_ID, node: 1 <0xb7244b90>
05      07/31/10 11:04:40.532           Finished building node list: <0xb7244b90>
05      07/31/10 11:04:40.532           Node: 1 basic: 0x2 generic: 0x2 specific: 0x1 pluto: 1945 <0xb7244b90>


I see this in the web:
                         ZWave
            ZWave Embedded Climate Interfa
            ZWave Embedded Security Interf
            ZWave Controller


The ZWave Controller is node 1.

How do I add the trickestar remote and start adding lights? Everything I try fails to work.

25
Installation issues / Re: Cannot get tricklestar to work!
« on: July 31, 2010, 04:38:34 pm »
The wiki does not specify which process to follow when using the USB dongle with the remote (both the 200 and 300).

Do I follow the steps in How to install and use ZWave -> SUC/SIS Mode (recommended)? Specifically this step:

When using SUC/SIS mode you must add an Inclusion Controller as the 2nd device in your ZWave network (the first device being the ZWave USB interface itself). An Inclusion Controller is the device you use to include ZWave devices into the ZWave network - this might be your ZWave remote control or possibly a wireless wall switch as these can often do double duty as an Inclusion Controller. You can add additional Inclusion Controllers or indeed any other ZWave devices at any time in the future as needed, and they will be added to your Device Tree automatically for you - this is the unique power of SUC/SIS.

   1. Next select 'Add node' from the 'Send to this device the command' drop-down menu and click send (there is no need to fill in any values in this screen).
   2. Now bring your Inclusion Controller close to your Core's/MD's ZWave USB interface and click once on its button or paddle (if a Wireless light switch) to include it into the ZWave Network.


Or do I follow the steps for Manual Setup using SIS Mode with the Tricklestar Remote, and download the configuration from the Tricklestar remote into the USB ZWave controller everytime I add lights.

26
Installation issues / Cannot get tricklestar to work! [SOLVED]
« on: July 31, 2010, 04:19:39 pm »
I decided to ditch my MCV dongle for tricklestar. I have been trying for 2 days to get my new tricklestar USB dongle working with LinuxMCE. I have followed the steps in the wiki, I have tried manually adding the template, I have tried adding the device ID and letting it auto-detect. The zwave device is always added but it doesn't work. When I did have it successfully starting and logging, it would not add devices. The light on the dongle is lit during the install but then it goes out, and stays out. Now, I get this message and nothing else after:

05      07/31/10 9:46:33.150            No callback received: await_callback: -1 timer: 31 <0xb7099b90>
05      07/31/10 9:46:33.363            Got reply to ZW_MEMORY_GET_ID, Home id: 0x00d8b265, our node id: 1 <0xb7099b90>
05      07/31/10 9:46:33.583            Got reply to GET_SUC_NODE_ID, node: 1 <0xb7099b90>
05      07/31/10 9:46:33.844            Finished building node list: <0xb7099b90>
05      07/31/10 9:46:33.844            Node: 1 basic: 0x2 generic: 0x2 specific: 0x1 pluto: 1945 <0xb7099b90>
05      07/31/10 9:50:42.584            Got a reload command from 0  <0xb6097b90>
05      07/31/10 9:50:42.840            void ClientSocket::Disconnect() on this socket: 0x88ea348 (m_Socket: 7) <0xb709a6c0>
Return code: 2
2       07/31/10 09:50:42       139 (spawning-device)   Device requests restart... count=1/50 dev=139
2       07/31/10 09:50:43       139 (spawning-device)   Device was disabled or removed. Stopping and marking as not running.

Any ideas, I am getting frustrated.

27
Same thing happens to me. I just bought the Tricklestar 300ZW today, and I can't get it to work either.

28
Users / Re: Sick Beard and SABnzbd integration
« on: July 30, 2010, 03:15:18 am »
SABnzdb is a python based full-auto newsreader, and is used to download movies, tv shows, music, etc from newgroups (such as giganews or or usenetserver). It is similar to bittorrent except that is uses secure newsgroups and nzb files rather than torrent files. Sick Beard is a python based TV show management software, and is used to automatically download tv shows as they are made available. It is a PVR on crack.

If you haven't heard of it, or aren't using it, do yourself a HUGE favor and install them both - start using it. It took me 15 minutes to get it installed and start using it. I will create a wiki soon, and create a deb file for automagically setting them both up in minutes.

This is a better solution than Hulu, netflix, and mythtv pvr for both tv shows and movies. I am very excited about it.

http://gizmodo.com/5343260/how-to-kick-your-torrent-addiction-with-usenet

29
Users / Sick Beard and SABnzbd integration
« on: July 29, 2010, 09:18:20 pm »
Is anyone using SickBeard and/or SABnzbd? I am, and will be working on integrating it with LinuxMCE. If you haven't heard of it or aren't using it, you should check it out!

Thoughts/ideas? Anyone interested?

30
Users / Re: OpenVPN
« on: July 29, 2010, 06:18:57 am »
donpaul,

looking at the tar, I fail to see any web admin stuff. Do I miss anything, or is the web admin stuff elsewhere?

I attached the diff svn patch and a tar of the added php scripts earlier in the thread. I did not put those in my deb source - I assumed they should go in the existing web admin package.

Let me know what I can do to help get it in the next snapshot.

Pages: 1 [2] 3 4 ... 20