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

Main Menu
Menu

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.

Show posts Menu

Messages - habazot

#1
Users / Re: Barix Extreamer support
November 23, 2008, 11:49:23 PM
I have 6 of the Extreamers already installed...
It is a nice piece of hardware, and I would presume it resembles other streaming audio solutions closely.
I was just hoping someone else had done the work for me.. :)

Regards
#2
Quote from: hari on November 23, 2008, 11:22:53 PM
You could try to use the new zwave driver. But the ZCU101/201 is crap.

best regards,
Hari

Ok, glad to get some straight talk :)
Which one seems to be the one to recommend these days?
I was looking at the Mi Casa Verde USB/inclusion controller.
How is your experience with it wrt LMCE?

Regards
#3
Users / Barix Extreamer support
November 23, 2008, 11:27:41 PM
Hi, I see on the wiki some references to the Barix Extreamer (http://www.barix.com/index.php?linkid=441), and it seems like it was supported at some point.
However, I can not find any more detailed information on how to integrate it with LMCE.
Anyone out there with some experience or tips?
#4
Users / Re: New Z-Wave driver
November 23, 2008, 11:14:16 PM
Hi, do you have a 64bit version of the new ZWave binary as well..?.
On a general note: is using 64bit LMCE going to cause me more pain than gain..?..
#5
Hi, struggling with getting a ZCU201 USB interface up and running.
Plain 0710 on a AMD64 machine. I'm getting this in the log file (in an endless loop):

========== NEW LOG SECTION ==========
1       11/23/08 21:47:31       77 (spawning-device)    Starting... 10
1       11/23/08 21:47:31       77 (spawning-device)    Found /usr/pluto/bin/ZWave
01      11/23/08 21:47:31.892           asynchThread started <0x2b6fc11f8b40>
05      11/23/08 21:47:36.048           ### Go to timeout queue <0x41802950>
05      11/23/08 21:47:36.048           ### execute the next job from timeout queue <0x41802950>
05      11/23/08 21:47:36.048           ZWJobInitialize::timeoutHandler <0x41802950>
05      11/23/08 21:47:41.032           ### Go to timeout queue <0x41802950>
05      11/23/08 21:47:41.032           ### execute the next job from timeout queue <0x41802950>
05      11/23/08 21:47:41.032           ZWJobInitialize::timeoutHandler <0x41802950>
05      11/23/08 21:47:46.016           ### Go to timeout queue <0x41802950>
05      11/23/08 21:47:46.016           ### skip the next job from timeout queue <0x41802950>
05      11/23/08 21:47:51.040           ### Go to timeout queue <0x41802950>
05      11/23/08 21:47:51.040           ### execute the next job from timeout queue <0x41802950>
05      11/23/08 21:47:51.040           ZWJobInitialize::timeoutHandler <0x41802950>
05      11/23/08 21:47:56.020           ### Go to timeout queue <0x41802950>
05      11/23/08 21:47:56.020           ### execute the next job from timeout queue <0x41802950>
05      11/23/08 21:47:56.020           ZWJobInitialize::timeoutHandler <0x41802950>
05      11/23/08 21:48:01.031           ### Go to timeout queue <0x41802950>
05      11/23/08 21:48:01.032           ### skip the next job from timeout queue <0x41802950>
05      11/23/08 21:48:01.051           Cannot connect to ZWave device ttyUSB0. <0x2b6fc11f8b40>
01      11/23/08 21:48:01.052           Connect() Failed <0x2b6fc11f8b40>
Return code: 1
3       11/23/08 21:48:01       77 (spawning-device)    Device died... count=10/50 dev=77
Sun Nov 23 21:48:01 CET 2008 died

Any clues on how to get a response from this interface?
dcerouter_93878:~# lsusb
Bus 002 Device 007: ID 04fc:0201 Sunplus Technology Co., Ltd
...

dcerouter_93878:~# lsmod
Module                  Size  Used by
spcp8x5                14980  0
usbserial              40688  1 spcp8x5
...

Device data:
Com port: pci0000:00/0000:00:02,0+6
Serial : /org/freedesktop/Hal/devices/usb_device_4fc_201_noserial

Not sure how this maps to ttyUSB0, though..

Any help appreciated :)