Messages

1

Users / Re: Heating Control

« on: October 18, 2011, 09:10:41 pm »

Please be aware that Danfoss Living is not supported by Linuxmce at the moment.


http://forum.linuxmce.org/index.php/topic,11999.0.html

2

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

« on: September 25, 2011, 03:55:14 pm »

Hi Hari,

I need a unit for testing..

Can you use my setup for testing? ssh or something?


/Jones

3

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>}

4

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

5

Users / Re: DVB Cards info needed for Templates

« on: January 05, 2010, 01:14:35 am »

Jones is your card the Hauppauge Nova-T 

No, it is a 2 x Satelco EasyWatch PCI (DVB-C)
http://www.linuxtv.org/wiki/index.php/Satelco_EasyWatch_PCI_(DVB-C)


Keep up the good work :-)
Jones

6

Users / Re: Is there any Smoke alarm z-wave ? Or other solution as gc100 ?

« on: December 31, 2009, 01:11:55 am »

Hi Viking and everyone else ;-)

Have you seen this Danish site??
http://www.homeestore.com/index.php/da/produkter?page=shop.product_details&flypage=flypage.tpl&product_id=117&category_id=6

It seems like Silvan is also starting to sell zwave devices :-)
http://eshop.silvan.dk/webapp/wcs/stores/servlet/kategori_El-og-Belysning-House-Control_22658

However, I'm still thinking about going with KNX and KNX-RF...


/Jones

7

Users / Re: DVB Cards info needed for Templates

« on: December 30, 2009, 04:02:23 pm »

Correct :-) Only an antenna port...

8

Users / Re: DVB Cards info needed for Templates

« on: December 29, 2009, 08:02:59 pm »

Here you go :-)

Card information:
   Philips Semiconductors SAA7146 (rev 01)
   Interface: PCI
   DVB-C

sudo lspci -vn

09:00.0 0480: 1131:7146 (rev 01)
        Subsystem: 1894:0022
        Flags: bus master, medium devsel, latency 64, IRQ 16
        Memory at fbeffc00 (32-bit, non-prefetchable) [size=512]
        Kernel driver in use: budget_av
        Kernel modules: budget-av

sudo v4l2-ctl -n
Failed to open /dev/video0: No such file or directory

Is this because that mythtv is running right now???


Have a nice and productive day :-)
/Jones

9

Installation issues / Re: NetUP Dual DVB T C CI RF

« on: December 29, 2009, 04:25:54 pm »

Hi guys,

I'm thinking about buying this one – maybe it also meets you needs:
http://translate.google.dk/translate?js=y&prev=_t&hl=da&ie=UTF-8&layout=1&eotf=1&u=http%3A%2F%2Fwww.linuxshoppen.dk%2Fproducts.php%3Fshowvariant_id%3D7237&sl=da&tl=en

Any thoughts about this is – except that it is not internal ;-)


/Jones

10

Installation issues / Re: Is this DVB-tuner plug & play in LinuxMCE 810

« on: December 29, 2009, 04:13:27 pm »

As off LinuxMCE 810 Beta2 it is detected correctly by v4l.
So, all that are need by the user is to configure it in MythTv.

Thanks Andrew
/Jonas

11

Installation issues / Re: Howto get a SAA7146 based DVB-c tuner to work in 810?

« on: December 29, 2009, 04:10:39 pm »

Well, just to be a good boy…

The problem turned out to be signal/quality issue... So I rewired my house and now it is starting to work – I still have some channels that I’m unable to fully “lock” on – but I’m hoping that it will be fixed when I’m all done with the new wiring.


Anyway thanks to Viking and Andrew 
/Jones

12

Installation issues / Re: Howto get a SAA7146 based DVB-c tuner to work in 810?

« on: September 27, 2009, 01:30:15 pm »

Hi everyone 

Thanks Viking, but my problem seems to be the “Skanderborg AF” problem, and should be solved by applying a patch called “dvbstreamdata.cpp.patch.”

So my question is:
- How to I obtain the dvbstreamdata.cpp.patch patch(http://www.mythtv.org/wiki/Channel_tuning_broken_with_DVB-C#Skanderborg_AF)
-  And finally, how do I apply the patch?

Hope that there is someone out there that can point me in the right direction :-)


Thanks
Jones

13

Installation issues / Re: Howto get a SAA7146 based DVB-c tuner to work in 810?

« on: September 22, 2009, 12:57:51 am »

Okay, maybe a was a little to fast there... Sorry! 

I found the following article on mythtv's wiki:
http://www.mythtv.org/wiki/Channel_tuning_broken_with_DVB-C

so right now I running a the scanall.sh script. Hope that it will work 


Br
/Jones

14

Installation issues / Re: Howto get a SAA7146 based DVB-c tuner to work in 810?

« on: September 21, 2009, 11:39:57 pm »

Hi Andrew and Viking,

I'm getting closer :-)

So i have managed to go the tuner to work – I think.
But I'm unable to get any real channels imported into Mythtv.

I have manged to generate the following dump using the scan tool from dvb-utils:

Code: [Select]

R2:370000000:INVERSION_AUTO:6875000:FEC_AUTO:QAM_64:211:221:102
UPD/Te:370000000:INVERSION_AUTO:6875000:FEC_AUTO:QAM_64:311:321:103
TV 2 N:370000000:INVERSION_AUTO:6875000:FEC_AUTO:QAM_64:0:0:211
TV 2 M:370000000:INVERSION_AUTO:6875000:FEC_AUTO:QAM_64:2111:2121:212
TV 2�j:370000000:INVERSION_AUTO:6875000:FEC_AUTO:QAM_64:0:0:213
TV 2 S:370000000:INVERSION_AUTO:6875000:FEC_AUTO:QAM_64:0:0:214
TV 2 F:370000000:INVERSION_AUTO:6875000:FEC_AUTO:QAM_64:0:0:215
TV 2 �:370000000:INVERSION_AUTO:6875000:FEC_AUTO:QAM_64:0:0:216
TV 2 L:370000000:INVERSION_AUTO:6875000:FEC_AUTO:QAM_64:0:0:217
TV 2 B:370000000:INVERSION_AUTO:6875000:FEC_AUTO:QAM_64:0:0:218
DR1Syn:370000000:INVERSION_AUTO:6875000:FEC_AUTO:QAM_64:0:0:111
Enable:370000000:INVERSION_AUTO:6875000:FEC_AUTO:QAM_64:0:0:7000
DR1:370000000:INVERSION_AUTO:6875000:FEC_AUTO:QAM_64:111:121:101
[2ede]:418000000:INVERSION_AUTO:6875000:FEC_AUTO:QAM_64:0:0:11998
[031f]:442000000:INVERSION_AUTO:6875000:FEC_AUTO:QAM_64:0:0:799
C+F HD:442000000:INVERSION_AUTO:6875000:FEC_AUTO:QAM_64:0:0:4500
C+SpHD:442000000:INVERSION_AUTO:6875000:FEC_AUTO:QAM_64:0:4601:4600
Via NC*:442000000:INVERSION_AUTO:6875000:FEC_AUTO:QAM_64:7200:7201:7200
Explor*:442000000:INVERSION_AUTO:6875000:FEC_AUTO:QAM_64:7210:7211:7210
DR HD:442000000:INVERSION_AUTO:6875000:FEC_AUTO:QAM_64:0:0:3500
SET:490000000:INVERSION_AUTO:6875000:FEC_AUTO:QAM_64:1800:1801:1800
ThaiTV:490000000:INVERSION_AUTO:6875000:FEC_AUTO:QAM_64:2840:2841:2840
RaiUno:490000000:INVERSION_AUTO:6875000:FEC_AUTO:QAM_64:1710:1711:1710
TVE:490000000:INVERSION_AUTO:6875000:FEC_AUTO:QAM_64:1770:1771:1770
Franc2:490000000:INVERSION_AUTO:6875000:FEC_AUTO:QAM_64:1810:1811:1810
Spil:490000000:INVERSION_AUTO:6875000:FEC_AUTO:QAM_64:0:0:739
FilmHD:490000000:INVERSION_AUTO:6875000:FEC_AUTO:QAM_64:0:0:4200
MAX:490000000:INVERSION_AUTO:6875000:FEC_AUTO:QAM_64:2640:2641:2640
SVT1:514000000:INVERSION_AUTO:6875000:FEC_AUTO:QAM_64:220:221:220
SVT2:514000000:INVERSION_AUTO:6875000:FEC_AUTO:QAM_64:230:231:230
Sat1:514000000:INVERSION_AUTO:6875000:FEC_AUTO:QAM_64:240:241:240
Discov:514000000:INVERSION_AUTO:6875000:FEC_AUTO:QAM_64:260:261:260
Pro7:514000000:INVERSION_AUTO:6875000:FEC_AUTO:QAM_64:820:821:280
T211:514000000:INVERSION_AUTO:6875000:FEC_AUTO:QAM_64:0:900:900
TV3:514000000:INVERSION_AUTO:6875000:FEC_AUTO:QAM_64:210:211:210
TCM:514000000:INVERSION_AUTO:6875000:FEC_AUTO:QAM_64:270:271:270
World:538000000:INVERSION_AUTO:6875000:FEC_AUTO:QAM_64:1820:1821:1820
TraLiv:538000000:INVERSION_AUTO:6875000:FEC_AUTO:QAM_64:1830:1831:1830
Scienc:538000000:INVERSION_AUTO:6875000:FEC_AUTO:QAM_64:1840:1841:1840
DR1:538000000:INVERSION_AUTO:6875000:FEC_AUTO:QAM_64:1850:1851:1850
DR2:538000000:INVERSION_AUTO:6875000:FEC_AUTO:QAM_64:1860:1861:1860
K5 HD:538000000:INVERSION_AUTO:6875000:FEC_AUTO:QAM_64:0:3201:3200
2Film:554000000:INVERSION_AUTO:6875000:FEC_AUTO:QAM_64:410:411:410
Zulu:554000000:INVERSION_AUTO:6875000:FEC_AUTO:QAM_64:420:421:420
EuroSp:554000000:INVERSION_AUTO:6875000:FEC_AUTO:QAM_64:430:431:430
DR1_43:554000000:INVERSION_AUTO:6875000:FEC_AUTO:QAM_64:440:441:440
ARD:554000000:INVERSION_AUTO:6875000:FEC_AUTO:QAM_64:460:461:460
2Sport:554000000:INVERSION_AUTO:6875000:FEC_AUTO:QAM_64:470:471:470
T214:554000000:INVERSION_AUTO:6875000:FEC_AUTO:QAM_64:0:920:920
24Nord:554000000:INVERSION_AUTO:6875000:FEC_AUTO:QAM_64:1900:1901:1900
It's all look very nice – I think :-) But whenever I import the conf-file into MythTv it only finds two “channels” that it names 21#0 and 37#0 :-/

Any thoughts?


Br
Jones

15

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