Topics

1

Users / Z-Wave: Danfoss Living Connect thermostat: unable to control them...

« on: September 23, 2011, 07:53:35 pm »

Hi guys,
I have bought Danfoss’ new z-wave (Danfoss Type ID 014G0001) thermostats for all my radiators, but I cant control they though LinuxMCE  
The devices has been added successful to LinuxMCE and are shown as Standard Thermostats (based on Device template # 1754), and and data such as battery status is shown just fine in LinuxMCE and a test of my FlexControll Smoke Dector is firering of the Fire scenario, so I think that the basic Zwave is working...

However, I’m unable to set the temperature using the test buttons such as the “72 deg.” Button on the climate device page.

Has anyone had success using this brand new z-wave devices with LinuxMCE 8.10?


Please help me out


Here is a dump of my Z-wave controller log:

_{========== NEW LOG SECTION ==========1   
09/23/11 16:01:58   33 (spawning-device)   Starting... 11   
09/23/11 16:01:59   33 (spawning-device)   Found /usr/pluto/bin/ZWave01   
09/23/11 16:01:59.126      TranslateSerialUSB pci0000:00/0000:00:1d.1+2 result /dev/ttyACM0 <0xb70f26c0>01   
09/23/11 16:01:59.130      ERROR! Out of frame flow!! <0xb68f0b90>05   
09/23/11 16:01:59.131      Creating child 34 <0xb70f26c0>05   
09/23/11 16:01:59.131      Note: Device manager has attached a device of type 1820 that this has no custom event handler for.  It will not fire events. <0xb70f26c0>
05   
09/23/11 16:01:59.131      Note: Device manager has attached a device of type 1820 that this has no custom handler for.  This is normal for IR. <0xb70f26c0>05   
09/23/11 16:01:59.131      Creating child 77 <0xb70f26c0>05   
09/23/11 16:01:59.131      Note: Device manager has attached a device of type 4 that this has no custom event handler for.  It will not fire events. <0xb70f26c0>05   
09/23/11 16:01:59.131      Note: Device manager has attached a device of type 4 that this has no custom handler for.  This is normal for IR. <0xb70f26c0>05   
09/23/11 16:01:59.131      Creating child 78 <0xb70f26c0>05   
09/23/11 16:01:59.131      Note: Device manager has attached a device of type 4 that this has no custom event handler for.  It will not fire events. <0xb70f26c0>05   
09/23/11 16:01:59.131      Note: Device manager has attached a device of type 4 that this has no custom handler for.  This is normal for IR. <0xb70f26c0>05   
09/23/11 16:01:59.131      Creating child 79 <0xb70f26c0>05   
09/23/11 16:01:59.131      Note: Device manager has attached a device of type 4 that this has no custom event handler for.  It will not fire events. <0xb70f26c0>05   
09/23/11 16:01:59.131      Note: Device manager has attached a device of type 4 that this has no custom handler for.  This is normal for IR. <0xb70f26c0>05   
09/23/11 16:01:59.131      Creating child 80 <0xb70f26c0>05   
09/23/11 16:01:59.131      Note: Device manager has attached a device of type 4 that this has no custom event handler for.  It will not fire events. <0xb70f26c0>05   
09/23/11 16:01:59.131      Note: Device manager has attached a device of type 4 that this has no custom handler for.  This is normal for IR. <0xb70f26c0>05   
09/23/11 16:01:59.131      Creating child 81 <0xb70f26c0>05   
09/23/11 16:01:59.131      Note: Device manager has attached a device of type 4 that this has no custom event handler for.  It will not fire events. <0xb70f26c0>05   
09/23/11 16:01:59.131      Note: Device manager has attached a device of type 4 that this has no custom handler for.  This is normal for IR. <0xb70f26c0>05   
09/23/11 16:01:59.131      Creating child 82 <0xb70f26c0>05   
09/23/11 16:01:59.131      Note: Device manager has attached a device of type 4 that this has no custom event handler for.  It will not fire events. <0xb70f26c0>05   
09/23/11 16:01:59.131      Note: Device manager has attached a device of type 4 that this has no custom handler for.  This is normal for IR. <0xb70f26c0>05   
09/23/11 16:01:59.131      Creating child 35 <0xb70f26c0>05   
09/23/11 16:01:59.131      Note: Device manager has attached a device of type 1922 that this has no custom event handler for.  It will not fire events. <0xb70f26c0>05   
09/23/11 16:01:59.131      Note: Device manager has attached a device of type 1922 that this has no custom handler for.  This is normal for IR. <0xb70f26c0>05   
09/23/11 16:01:59.131      Creating child 66 <0xb70f26c0>05   
09/23/11 16:01:59.131      Note: Device manager has attached a device of type 55 that this has no custom event handler for.  It will not fire events. <0xb70f26c0>05   
09/23/11 16:01:59.131      Note: Device manager has attached a device of type 55 that this has no custom handler for.  This is normal for IR. <0xb70f26c0>05   
09/23/11 16:01:59.131      Creating child 67 <0xb70f26c0>05   
09/23/11 16:01:59.131      Note: Device manager has attached a device of type 55 that this has no custom event handler for.  It will not fire events. <0xb70f26c0>05   
09/23/11 16:01:59.131      Note: Device manager has attached a device of type 55 that this has no custom handler for.  This is normal for IR. <0xb70f26c0>05
09/23/11 16:01:59.131      Creating child 68 <0xb70f26c0>05   
09/23/11 16:01:59.131      Note: Device manager has attached a device of type 55 that this has no custom event handler for.  It will not fire events. <0xb70f26c0>05   
09/23/11 16:01:59.131      Note: Device manager has attached a device of type 55 that this has no custom handler for.  This is normal for IR. <0xb70f26c0>05
09/23/11 16:01:59.131      Creating child 70 <0xb70f26c0>05   
09/23/11 16:01:59.131      Note: Device manager has attached a device of type 55 that this has no custom event handler for.  It will not fire events. <0xb70f26c0>05   
09/23/11 16:01:59.131      Note: Device manager has attached a device of type 55 that this has no custom handler for.  This is normal for IR. <0xb70f26c0>05   09/23/11 16:01:59.131      Creating child 71 <0xb70f26c0>05   
09/23/11 16:01:59.131      Note: Device manager has attached a device of type 55 that this has no custom event handler for.  It will not fire events. <0xb70f26c0>05   
09/23/11 16:01:59.132      Note: Device manager has attached a device of type 55 that this has no custom handler for.  This is normal for IR. <0xb70f26c0>05
09/23/11 16:01:59.132      Creating child 72 <0xb70f26c0>05   
09/23/11 16:01:59.132      Note: Device manager has attached a device of type 55 that this has no custom event handler for.  It will not fire events. <0xb70f26c0>05   
09/23/11 16:01:59.132      Note: Device manager has attached a device of type 55 that this has no custom handler for.  This is normal for IR. <0xb70f26c0>05   
09/23/11 16:01:59.132      Creating child 36 <0xb70f26c0>05   
09/23/11 16:01:59.132      Note: Device manager has attached a device of type 1945 that this has no custom event handler for.  It will not fire events. <0xb70f26c0>05   
09/23/11 16:01:59.132      Note: Device manager has attached a device of type 1945 that this has no custom handler for.  This is normal for IR. <0xb70f26c0>05   
09/23/11 16:01:59.132      Creating child 69 <0xb70f26c0>05   
09/23/11 16:01:59.132      Note: Device manager has attached a device of type 1945 that this has no custom event handler for.  It will not fire events. <0xb70f26c0>05   
09/23/11 16:01:59.132      Note: Device manager has attached a device of type 1945 that this has no custom handler for.  This is normal for IR. <0xb70f26c0>01   
09/23/11 16:01:59.134      ERROR! Out of frame flow!! <0xb68f0b90>01   
09/23/11 16:01:59.134      ERROR! Out of frame flow!! <0xb68f0b90>01   
09/23/11 16:01:59.134      ERROR! Out of frame flow!! <0xb68f0b90>01   
09/23/11 16:01:59.134      ERROR! Out of frame flow!! <0xb68f0b90>01   
09/23/11 16:01:59.134      ERROR! Out of frame flow!! <0xb68f0b90>01   
09/23/11 16:01:59.134      ERROR! Out of frame flow!! <0xb68f0b90>01   
09/23/11 16:01:59.134      ERROR! Out of frame flow!! <0xb68f0b90>01   
09/23/11 16:01:59.134      ERROR! Out of frame flow!! <0xb68f0b90>01   
09/23/11 16:01:59.134      ERROR! Out of frame flow!! <0xb68f0b90>01   
09/23/11 16:01:59.262      ZWave Version: 2.31 <0xb68f0b90>01   
09/23/11 16:01:59.371      Home id: 0x00092a4c, our node id: 1 <0xb68f0b90>01   
09/23/11 16:01:59.483      SerAppV:2,r67,Manf 0,Typ 1,Prod 1 <0xb68f0b90>05   
09/23/11 16:01:59.590      Got reply to GET_SUC_NODE_ID, node: 1 <0xb68f0b90>05   
09/23/11 16:02:00.646      Error: ZW_SEND failed, removing job after three tries <0xb68f0b90>05   
09/23/11 16:02:02.171      Finished building node list: <0xb68f0b90>05   
09/23/11 16:02:02.171      Node: 1 basic: 0x2 generic: 0x2 specific: 0x1 pluto: 1945 <0xb68f0b90>05   
09/23/11 16:02:02.171      Node: 2 basic: 0x1 generic: 0x1 specific: 0x1 pluto: 1945 <0xb68f0b90>05   
09/23/11 16:02:02.171      Node: 3 basic: 0x4 generic: 0xa1 specific: 0x7 pluto: 55 <0xb68f0b90>05   
09/23/11 16:02:02.171      Node: 4 basic: 0x4 generic: 0xa1 specific: 0x7 pluto: 55 <0xb68f0b90>05   
09/23/11 16:02:02.171      Node: 5 basic: 0x4 generic: 0xa1 specific: 0x7 pluto: 55 <0xb68f0b90>05   
09/23/11 16:02:02.171      Node: 6 basic: 0x4 generic: 0xa1 specific: 0x7 pluto: 55 <0xb68f0b90>05   
09/23/11 16:02:02.171      Node: 7 basic: 0x4 generic: 0xa1 specific: 0x7 pluto: 55 <0xb68f0b90>05   
09/23/11 16:02:02.171      Node: 8 basic: 0x4 generic: 0xa1 specific: 0x7 pluto: 55 <0xb68f0b90>05   
09/23/11 16:02:02.171      Node: 11 basic: 0x4 generic: 0x8 specific: 0x4 pluto: 4 <0xb68f0b90>05   
09/23/11 16:02:02.171      Node: 12 basic: 0x4 generic: 0x8 specific: 0x4 pluto: 4 <0xb68f0b90>05   
09/23/11 16:02:02.171      Node: 13 basic: 0x4 generic: 0x8 specific: 0x4 pluto: 4 <0xb68f0b90>05   
09/23/11 16:02:02.171      Node: 14 basic: 0x4 generic: 0x8 specific: 0x4 pluto: 4 <0xb68f0b90>05   
09/23/11 16:02:02.171      Node: 15 basic: 0x4 generic: 0x8 specific: 0x4 pluto: 4 <0xb68f0b90>05   
09/23/11 16:02:02.171      Node: 16 basic: 0x4 generic: 0x8 specific: 0x4 pluto: 4 <0xb68f0b90>05   
09/23/11 16:02:32.187      Error: ZW_SEND failed, removing job after three tries <0xb68f0b90>05   
09/23/11 16:04:39.366      Error: ZW_SEND failed, removing job after three tries <0xb68f0b90>05   
09/23/11 16:06:28.654      Error: ZW_SEND failed, removing job after three tries <0xb68f0b90>05   
09/23/11 16:07:11.987      Error: ZW_SEND failed, removing job after three tries <0xb68f0b90>05   
09/23/11 16:14:42.770      Error: ZW_SEND failed, removing job after three tries <0xb68f0b90>}

2

Users / Video: Black screen but sound!

« on: August 08, 2011, 12:39:33 am »

Hi guys,
I have installed my Ion2 based MD in UI3 mode with overlaying graphic, which caused Screen tearing until I changed “composite” from true to false.

Now, we can watch live and recorded video from within MythTV without any screen tearing! However, this change seems to have effected xine(?), because now we have only sound if we start a video from the LinuxMCE GUI.


Please help me, I finally so close to a working kickass setup
Jones

3

Installation issues / [SOLVED] Howto get a SAA7146 based DVB-c tuner to work in 810?

« on: September 19, 2009, 12:49:17 pm »

Hi again,
 
I need some help... Again

So I managed to get by test/setup to work with my MSI DIGIVOX mini II (V3.0).
Anyway, now I'm trying to install 810 with my 2 x Satelco EasyWatch PCI (DVB-C)
http://www.linuxtv.org/wiki/index.php/Satelco_EasyWatch_PCI_(DVB-C)

It seems like Linux is detecting them correctly, but LinuxMCE and MythTv is unaware of them.

01:00.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01)
01:01.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
01:02.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01)

I can see that there are a couple of guys using this type of card in here(Viking, nite_man and some others).
So it seems possible to get it to work, so I just need some dummy guide for adding it to LinuxMce and/or Mythtv.


Thanks
Jones

4

Installation issues / [SOLVED] Is this DVB-tuner plug & play in LinuxMCE 810

« on: September 10, 2009, 02:51:26 pm »

Hi everyone,

I need to setup a cheap linuxmce, and i was looking into this tuner:
http://www.linuxtv.org/wiki/index.php/MSI_DigiVox_mini_II

But is there anyone who has tried it in Linuxmce or knows if it will work with a minimum of modifications?


Thanks
Jones

5

Installation issues / Tuner not detected - kernel upgrade?

« on: December 29, 2008, 10:16:03 am »

Hi guys,

I’m trying to setup my new mediacenter and everything goes fine until I have to use my DVB-C tuners(SATELCO EasyWatch PCI DVB-C HDTV "Basic Edition", see http://linuxtv.org/wiki/index.php/Satelco_EasyWatch_PCI_%28DVB-C%29).

I thing, that they are not supported by the kernel version that LinuxMCE is shipped with.
So I have been trying to follow this wiki-page (http://wiki.linuxmce.org/index.php/Upgrading_the_Kernel) to upgrade the kernel, however

I get the following error right after typing the command:
mkinitramfs -o /boot/initrd.img-2.6.26.5 2.6.26.5

I get the following errors:
find:  /lib/firmware/2.6.26.5: No such file or directory
find:  /lib/firmware/2.6.26.5: No such file or directory
find:  /lib/firmware/2.6.26.5: No such file or directory
find:  /lib/firmware/2.6.26.5: No such file or directory
find:  /lib/firmware/2.6.26.5: No such file or directory
find:  /lib/firmware/2.6.26.5: No such file or directory

I have tried just to ignore it, however the computer cannot boot of it – it can’t see my soft raid drives – and I have included the soft raid in the kernel 

Anyone who can help me with this one?


Please
/Jones

6

Users / RS-232 support for Panasonic PZ800 series

« on: November 27, 2008, 09:12:09 pm »

Hi guys,

I'm thinking about buying Panasonics 42PZ800 instead of the PZ85 since the PZ800 series has RS232  - nice :-)
(Yes I know that is can use a UIRT for this, but I need the one I have for the bedroom, and I think that RS-232 is more stable then IF)

Anyway, my question to you guys is:
Is there an template for this device in LinxuMCE, and if not, how simple is it to make one?

The only thing I want to be able to do is:
Turn it on/off
Select source (HDMI 1 or whatever my LMCE is on)


I have tried to Google for any information about the commands for PZ800 rs232 interface but without any luck.
The only thing that I have found is this:
http://sleepytom.co.uk/files/panasonic-pseries-plasma-rs232.pdf


Thanks
Jones

7

Installation issues / Z-WAVE: How to get Seluxit ViaSENS Homecontroller to work?

« on: May 10, 2008, 08:02:38 pm »

Hi everyone.

I need help to configuration a Seluxit ViaSENS Homecontroller. I can see in this forum and on the wiki pages that it is confirmed to work with LinuxMCE version 710 or newer.
The users Hari is also using it, however i can't figure out how to add it as a Interface in LinuxMCE, can anyone guide me through?

I have tried to added it under ”Devices\Interfaces”.
Manufacturer: Click on “Add device” and then add the vendor Seluxit since it is not listed.
Device: “Interfaces”
Device template “Zwave”
And then I click “Pick device template”.

The interface get listed under Interfaces, so fare so good. So what do I have to do now?
I expected that I have to do something under “Advanced” settings for the interface that I have added, but I can't figure out way I have to do now.


Can someone please help me???



PS: When I attach the usb device to my core computer is writes “[    316.841156]  /build/buildd/linux-source-2.6.22-2.6.22/drivers/usb/class/cdc-acm.c: This device cannot do calls on its own. It is a no modem.”