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.


Topics - rebelkiller

Pages: [1] 2
1
Users / ZWave: Fibaro Smoke Detector FGSD-02?
« on: February 09, 2016, 05:14:20 pm »
Hello there,

I bought a Fibaro Smoke Detector FGSD-02 (newer version).
Adding it to lmce it will be recognized correctly.

LMCE adds an "Generic Sensor" (27 in my case), which is taking battery state.
Manually I added an Temperatur sensor with instance 1 (27/1 in my case), which is working correctly.

Now I am trying to get smoke and tamper detection to work.

Watching Zwave logs I found the following entry regarding my Fibaro smoke detector:

Code: [Select]
...
Device mapping: <0xb7786700>
05 02/09/16 17:01:00.102 * Device id = 27, dt = 1813 (Generic Sensor), main label = Sensor, pk_parent = 32 <0xb7786700>
05 02/09/16 17:01:00.102   -> Already mapped to device, PK_Device=207 <0xb7786700>
01 02/09/16 17:01:00.102     -> No device template for node with generic 7, specific 1, label  <0xb7786700>
05 02/09/16 17:01:00.102 * Device id = 27/1, dt = 0 (), main label = , pk_parent = 0 <0xb7786700>...

What does row "no device template for..." mean?

Anyone using this device, too?

Thanks!

Best regards!

Bernd

2
Hello there,


on my rpi2 ("normal" disked rpi2-MD, 31723) text ist partially missing.

The buttons do have the correct text. But what is missing:

- all media pages do not have a text (file names, disk drive entries, channel names etc.)
- the loading screen right before onscreen orbiter is showing (during router reload or reboot) does not have text
- the little text box at the top left corner of the screen showing after MD start in onscreen orbiter does not have text either.

I already tried different skins. Currently i am using basic skin.

I think it could be a missing font.

Which fonts are have to be installed?
Any other ideas?

Greets

Bernd

3
Installation issues / Raspberry pi 2 installation -> HDMI CEC problems
« on: November 17, 2015, 08:20:59 pm »
Hello!

 did fresh installation of jessie on my rpi2. I want to use HDMI-CEC with my rpi2, Panasonic-Plasma and DENON AVR.

Testing with cec-client gives the right outputs (addresses, Vendors etc.). So basically I it is a working setup. (A further test with a another rpi2 and a recent KODI/Openelec installation HDMI works OOTB). So I assume that there are no incompatibilities between the devices.

I followed instructions in the wiki regarding pulse eight adaptor and give the right(?) address entries of those three devices in webadmin. COM port of the CEC-Adaptor is left blank. I set the Audio/Videos pipes and reloaded the core.

Now on the rpi2 MD my TV remote does not show any reaction on button presses.


Partially the log of CEC_Adaptor:

Code: [Select]
========== NEW LOG SECTION ==========
1       11/17/15 18:43:52       143 (spawning-device)   ^[[1;00mStarting... 1^[[1;00m
1       11/17/15 18:43:52       143 (spawning-device)   ^[[1;00mFound /usr/pluto/bin/CEC_Adaptor^[[1;00m
05      11/17/15 18:43:53.646           ^[[33;1mConnect() failed, Error Code 111 (Connection refused))^[[0m <0x76f64000>
05      11/17/15 18:43:54.648           ^[[33;1mConnect() failed, Error Code 111 (Connection refused))^[[0m <0x76f64000>
05      11/17/15 18:44:19.104           ^[[33;1mNo COM Port specified. Trying autodetect.  Please set a port in the Interfaces section of Web Admin, or re-detect device.^[[0m <0x76f64000>
01      11/17/15 18:44:21.298           ^[[31;1mCECCommand: CALLBACK! From: 0, To: 4, set=1, Opcode: 135/device vendor id, Parm1=0, sParms: ''^[[0m <0x7640d450>
01      11/17/15 18:44:21.299           ^[[31;1mCECCommand: CALLBACK! VendorID     : 0/Unknown^[[0m <0x7640d450>
05      11/17/15 18:44:27.624           ^[[33;1mCreating child 144^[[0m <0x76f64000>
05      11/17/15 18:44:27.625           ^[[33;1mNote: Device manager has attached a device of type 2303 that this has no custom event handler for.  It will not fire events.^[[0m <0x76f64000>
05      11/17/15 18:44:27.625           ^[[33;1mNote: Device manager has attached a device of type 2303 that this has no custom handler for.  This is normal for IR.^[[0m <0x76f64000>
05      11/17/15 18:44:27.625           ^[[33;1mCreating child 146^[[0m <0x76f64000>
05      11/17/15 18:44:27.625           ^[[33;1mNote: Device manager has attached a device of type 2304 that this has no custom event handler for.  It will not fire events.^[[0m <0x76f64000>
05      11/17/15 18:44:27.625           ^[[33;1mNote: Device manager has attached a device of type 2304 that this has no custom handler for.  This is normal for IR.^[[0m <0x76f64000>
05      11/17/15 18:44:27.625           ^[[33;1mCreating child 147^[[0m <0x76f64000>
05      11/17/15 18:44:27.625           ^[[33;1mNote: Device manager has attached a device of type 2306 that this has no custom event handler for.  It will not fire events.^[[0m <0x76f64000>
05      11/17/15 18:44:27.625           ^[[33;1mNote: Device manager has attached a device of type 2306 that this has no custom handler for.  This is normal for IR.^[[0m <0x76f64000>
01      11/17/15 18:47:06.215           ^[[31;1mCECCommand: CALLBACK! Unhandled!^[[0m <0x7640d450>
01      11/17/15 18:47:08.273           ^[[31;1mCECCommand: CALLBACK! Unhandled!^[[0m <0x7640d450>
01      11/17/15 18:47:10.328           ^[[31;1mCECCommand: CALLBACK! Unhandled!^[[0m <0x7640d450>
01      11/17/15 18:47:12.383           ^[[31;1mCECCommand: CALLBACK! Unhandled!^[[0m <0x7640d450>
01      11/17/15 18:47:14.437           ^[[31;1mCECCommand: CALLBACK! Unhandled!^[[0m <0x7640d450>
01      11/17/15 18:47:16.492           ^[[31;1mCECCommand: CALLBACK! Unhandled!^[[0m <0x7640d450>
...
01      11/17/15 18:48:12.012           ^[[31;1mCECCommand: CALLBACK! Unhandled!^[[0m <0x7640d450>
01      11/17/15 18:48:14.073           ^[[31;1mCECCommand: CALLBACK! Unhandled!^[[0m <0x7640d450>
01      11/17/15 18:48:16.127           ^[[31;1mCECCommand: CALLBACK! Unhandled!^[[0m <0x7640d450>
01      11/17/15 18:48:18.183           ^[[31;1mCECCommand: CALLBACK! Unhandled!^[[0m <0x7640d450>
01      11/17/15 18:48:20.237           ^[[31;1mCECCommand: CALLBACK! Unhandled!^[[0m <0x7640d450>
01      11/17/15 18:48:22.293           ^[[31;1mCECCommand: CALLBACK! Unhandled!^[[0m <0x7640d450>
01      11/17/15 18:48:24.352           ^[[31;1mCECCommand: CALLBACK! Unhandled!^[[0m <0x7640d450>
01      11/17/15 18:48:26.407           ^[[31;1mCECCommand: CALLBACK! Unhandled!^[[0m <0x7640d450>
05      11/17/15 18:56:21.696           ^[[33;1mlibCEC: unhandled response received: opcode=0 initiator=e destination=0 response=0^[[0m <0x7640d450>
05      11/17/15 18:56:21.792           ^[[33;1mlibCEC: unhandled response received: opcode=8c initiator=e destination=0 response=0^[[0m <0x7640d450>
05      11/17/15 18:56:22.604           ^[[33;1mlibCEC: unhandled response received: opcode=84 initiator=4 destination=f response=0^[[0m <0x7640d450>
05      11/17/15 18:56:22.904           ^[[33;1mlibCEC: unhandled response received: opcode=47 initiator=4 destination=0 response=0^[[0m <0x7640d450>
05      11/17/15 18:56:23.087           ^[[33;1mlibCEC: unhandled response received: opcode=8f initiator=4 destination=0 response=0^[[0m <0x7640d450>
01      11/17/15 18:56:23.638           ^[[31;1mCECCommand: CALLBACK! From: 0, To: 4, set=1, Opcode: 135/device vendor id, Parm1=0, sParms: ''^[[0m <0x7640d450>
01      11/17/15 18:56:23.639           ^[[31;1mCECCommand: CALLBACK! VendorID     : 0/Unknown^[[0m <0x7640d450>
05      11/17/15 18:56:23.791           ^[[33;1mlibCEC: unhandled response received: opcode=87 initiator=4 destination=f response=0^[[0m <0x7640d450>
05      11/17/15 18:56:24.280           ^[[33;1mlibCEC: unhandled response received: opcode=89 initiator=4 destination=0 response=0^[[0m <0x7640d450>


Some ideas?

Thank you!


Greets
Bernd

4
Installation issues / Raspberry pi 2 installation -> VDR problems
« on: November 17, 2015, 08:03:02 pm »
Hello,
I just wanted to give a feedback to a fresh rpi2 installation. I updated my LMCE-installation (Core and MD) today (31620).

Basically installation process works fine.
I am using VDR. I have still problems getting VDR to work:

Here are my observations:
- vdr-plugin-remotetimers is not getting installed -> apt-show cache shows it as a virtual package?
- adding e-tobi-repos for VDR in sources.list fixed installation von remotetimer-plugin
- in /etc/vdr/conf.d I had to manually edit some config files (e.g. video directory, disabling lirc as it fires error messages in syslog etc.)

Now that VDR-client is starting and running I still get a black screen when pressing TV on the rpi2-Orbiter. I don't really find out where the problem is.

Maybe some can help.


/var/log/syslog from rpi-MD after pressing TV on the orbiter:


Code: [Select]
...
Nov 17 19:53:30 moon127 vdr: [31046] loading /var/lib/vdr/themes/lcars-default.theme
Nov 17 19:53:30 moon127 vdr: [31046] starting plugin: remotetimers
Nov 17 19:53:30 moon127 vdr: [31046] starting plugin: streamdev-client
Nov 17 19:53:30 moon127 vdr: [31046] starting plugin: svdrpservice
Nov 17 19:53:30 moon127 vdr: [31046] starting plugin: xineliboutput
Nov 17 19:53:30 moon127 vdr: [31098] Remote decoder/display server (cXinelibServer) thread started (pid=31046, tid=31098, prio=high)
v 17 19:53:30 moon127 vdr: [31046] no DVB device found
Nov 17 19:53:30 moon127 vdr: [31095] reading EPG data from /var/cache/vdr/epg.data
Nov 17 19:53:30 moon127 vdr: [31046] initializing plugin: remotetimers (1.0.2): Timer eines anderen VDR bearbeiten
Nov 17 19:53:30 moon127 vdr: [31095] epg data reader thread ended (pid=31046, tid=31095)
Nov 17 19:53:30 moon127 vdr: [31046] initializing plugin: streamdev-client (0.6.1-git): VTP Streaming Client
Nov 17 19:53:30 moon127 vdr: [31046] initializing plugin: svdrpservice (1.0.0): SVDRP client
Nov 17 19:53:30 moon127 vdr: [31046] initializing plugin: xineliboutput (2.0.0-cvs): X11/xine-lib Ausgabe-Plugin
Nov 17 19:53:30 moon127 vdr: [31046] new device number 1
Nov 17 19:53:30 moon127 vdr: [31046] [xine..put] cTimePts: clock_gettime(CLOCK_MONOTONIC): clock resolution 0 us
Nov 17 19:53:30 moon127 vdr: [31046] [xine..put] cTimePts: using monotonic clock
Nov 17 19:53:30 moon127 vdr: [31046] [xine..put] RTP SSRC: 0x7392389b
Nov 17 19:53:30 moon127 vdr: [31046] setting primary device to 1
Nov 17 19:53:30 moon127 vdr: [31046] assuming manual start of VDR
Nov 17 19:53:30 moon127 vdr: [31046] SVDRP listening on port 2001
Nov 17 19:53:30 moon127 vdr: [31046] setting current skin to "lcars"
Nov 17 19:53:30 moon127 vdr: [31046] loading /var/lib/vdr/themes/lcars-default.theme
Nov 17 19:53:30 moon127 vdr: [31046] starting plugin: remotetimers
Nov 17 19:53:30 moon127 vdr: [31046] starting plugin: streamdev-client
Nov 17 19:53:30 moon127 vdr: [31046] starting plugin: svdrpservice
Nov 17 19:53:30 moon127 vdr: [31046] starting plugin: xineliboutput
Nov 17 19:53:30 moon127 vdr: [31098] Remote decoder/display server (cXinelibServer) thread started (pid=31046, tid=31098, prio=high)
Nov 17 19:53:30 moon127 vdr: [31098] [xine..put] cXinelibServer priority set successful SCHED_RR 2 [1,99]
Nov 17 19:53:30 moon127 vdr: [31097] remotetimers update file watcher thread started (pid=31046, tid=31097, prio=high)
Nov 17 19:53:30 moon127 vdr: [31098] [xine..put] Binding server to 127.0.0.1:37890
Nov 17 19:53:30 moon127 vdr: [31097] remotetimers update file watcher now monitoring '/var/lib/video.00/.update'
Nov 17 19:53:30 moon127 vdr: [31098] [xine..put] Listening on port 37890
Nov 17 19:53:30 moon127 vdr: [31098] [xine..put] Listening for UDP broadcasts on port 37890
Nov 17 19:53:30 moon127 vdr: [31098] [discovery] BROADCAST: VDR xineliboutput DISCOVERY 1.0#015#012Server port: 37890#015#012Server address: 127.0.0.1#015#012Server version: xineliboutput-2.0.0-cvs#015#012#015
Nov 17 19:53:30 moon127 vdr: [31094] video directory scanner thread ended (pid=31046, tid=31094)
Nov 17 19:53:30 moon127 vdr: [31093] video directory scanner thread ended (pid=31046, tid=31093)
Nov 17 19:53:30 moon127 vdr: [31046] [xine..put] cXinelibDevice::StartDevice(): Device started
Nov 17 19:53:30 moon127 vdr: [31046] cTimeMs: using monotonic clock (resolution is 1 ns)
Nov 17 19:53:30 moon127 vdr: [31046] switching to channel 1 (Aristo.TV)
Nov 17 19:53:30 moon127 vdr: [31046] info: Kanal nicht verfügbar!
Nov 17 19:53:30 moon127 vdr: [31046] [xine..put] cXinelibOsd::CanHandleAreas(): Device does not support ARGB
Nov 17 19:53:32 moon127 vdr: [31046] setting watchdog timer to 60 seconds
Nov 17 19:53:32 moon127 vdr: [31046] OSD size changed to 720x576 @ 1,42222
Nov 17 19:53:32 moon127 vdr: [31046] [xine..put] cXinelibOsd::CanHandleAreas(): Device does not support ARGB
...

I know that channel 1 not available in this example. LMCE should show at least "nosignal" but it does not.


When starting "StartVDRClient.sh" from the command line I am getting some error messages:

Code: [Select]
Starting Linux Video Disk Recorder: vdr - seems to be running already.
220 moon127 SVDRP VideoDiskRecorder 2.2.0; Tue Nov 17 19:59:20 2015; UTF-8
250 Key "Ok" accepted
221 moon127 closing connection
vdr-sxfe 2.0.0-cvs  (build with xine-lib 1.2.6, using xine-lib 1.2.6)

Automatic reconnection enabled
Post plugins: tvtime:method=use_vo_driver
Fullscreen mode
Protocol: TCP
Verbose mode

VDR server not given, searching ...
Found VDR server: host 127.0.0.1, port 37890
Loaded configuration from file '/root/.xine/config_xineliboutput'
Benchmarking memcpy methods (smaller is better):
        libc memcpy() : 196590365

...
load_plugins: plugin /usr/lib/xine/plugins/2.5/xineplug_decode_spucmml.so found
load_plugins: plugin /usr/lib/xine/plugins/2.5/xineplug_decode_spu.so found
Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
vo_vdpau: Can't create vdp device : No vdpau implementation.
video_out_dxr3: Failed to open control device /dev/em8300-0 (No such file or directory)
libva info: VA-API version 0.36.0
libva info: va_getDriverName() returns -1
libva error: va_getDriverName() failed with unknown libva error,driver_name=(null)
video_out_vaapi Error : vaInitialize(): unknown libva error
video_out_vaapi vaapi_init : error init vaapi
video_out_xv: Xv extension is present but I couldn't find a usable yuv12 port.
        Looks like your graphics hardware driver doesn't support Xv?!
video_out_opengl: Testing for hardware accelerated direct rendering visual
video_out_opengl: Didn't find any
vo_opengl2 : compiling shader yuv420_frag
vo_opengl2 : compiling shader yuv422_frag
vo_opengl2: initialized.
audio_alsa_out : supported modes are 8bit 16bit 24bit 32bit mono stereo (4-channel not enabled in xine config) (4.1-channel not enabled in xine config) (5-channel not enabled in xine config) (5.1-channel not enabled in xine config) (a/52 and DTS pass-through not enabled in xine config)
...

Available SPU decoder plugins:   dxr3-spudec spudec spuhdmv spucc spucmml spudvb sputext
params.c:OpenConfFile() - Unable to open configuration file "/root/.smb/smb.conf.append":
        No such file or directory
added interface eth0 ip=192.168.80.2 bcast=192.168.80.255 netmask=255.255.255.0
xine: found input plugin  : VDR (Video Disk Recorder) input plugin
unknown option in get_option: 4100
input cache plugin disabled
xine: found demuxer plugin: XVDR demux plugin


Press Esc to exit

av_offset=0 pts
setterm: argument error: 'off'
video_out_opengl2: b 0 c 128 s 128 h 0 [ITU-R 470 BG / SDTV]
X Error of failed request:  BadMatch (invalid parameter attributes)
  Major opcode of failed request:  72 (X_PutImage)
  Serial number of failed request:  203
  Current serial number in output stream:  234
vdr-sxfe: Kein Prozess gefunden
Restarting Linux Video Disk Recorder: vdr.


...


Thanks for your help.



Greets

Bernd

5
Users / Advanced_IP_Camera => eventmethod "httpserver"?
« on: November 11, 2015, 09:21:52 pm »
Hello there,

I'm using an IP Camera with Advanced_IP_Camera DT. I want to use the camera as motion detector so I need events.
As described in the wiki there are three eventmethods that can be used for motion detecting.

urlpoll method is working but polling interval ist too slow. For example: When someone goes by and polling interval is set to 10 seconds results in an empty picture.  :)

I am trying to optimize that. My camera is capable of sending http events. So my camera can send notifications directly to the core (as a http message). But I am not quite sure how to get it to work.


Here are my questions:

1. webadmin settings:
In camera DT I have to set "eventMethod1=httpserver". What about "eventURL1"? What about "eventInterval"?

In child motion detector I have to chose "method=1" and "triggerMethod=pattern". the "patternOn" and "patternOff" will get the message patterns I specified in the camera.


2. camera settings:
To which server address do i have to send event notifications? -> just "192.168.80.1"?


Thanks for your help.

Bernd

6
Installation issues / Fresh install 12.04:VDR not working ("libcec.so.2")?
« on: November 02, 2015, 10:45:17 am »
Hello!

after my HDD crashed I had to do a fresh install of 12.04.
System is running fine except VDR client. VDR backend is working fine.

VDR-Client is not starting when I klick on "TV" in onscreen orbiter. VDR-log and syslog are showing no errors.
When I start the script "StartVDRClient.sh" from the command line it throws endless errors:

/usr/bin/vdr-sxfe: error while loading shared libraries: libcec.so.2: cannot open shared object file: No such file or directory


Output of "ldd /usr/bin/vdr-sxfe":
...
libcec.so.2 => not found
...


Output of "dpkg -l *cec*":
...
un  libcec                        <keine>                       (keine Beschreibung vorhanden)
un  libcec1                       <keine>                       (keine Beschreibung vorhanden)
un  libcec2                       <keine>                       (keine Beschreibung vorhanden)
ii  libcec3                       3.0.1-1-precise1              libCEC communication Library (shared library)
ii  lmce-cec-adaptor              2.0.0.46.15103131564          <insert up to 60 chars description>
ii  pluto-dcecommon               2.0.0.46.15103131564          <insert up to 60 chars description>
...

Output of "dpkg -l *vdr*":
...
un  libdvdread3                   <keine>                       (keine Beschreibung vorhanden)
ii  libdvdread4                   4.2.0-1ubuntu4                library for reading DVDs
un  libxine-xvdr                  <keine>                       (keine Beschreibung vorhanden)
ii  libxine1-xvdr                 2.0.0+git20150220-0yavdr0~pre Xine input plugin for vdr-plugin-xineliboutput streams
ii  pluto-vdr                     2.0.0.46.15103131564          <insert up to 60 chars description>
ii  pluto-vdr-plugin              2.0.0.46.15103131564          <insert up to 60 chars description>
ii  vdr                           2.0.6-6yavdr1                 Video Disk Recorder for DVB cards
un  vdr-abi-2.0.6-yavdr0          <keine>                       (keine Beschreibung vorhanden)
un  vdr-plugin-dvbsddevice        <keine>                       (keine Beschreibung vorhanden)
ii  vdr-plugin-remotetimers       1.0.1-2yavdr4~precise         VDR plugin to edit timers on a remote VDR
ii  vdr-plugin-streamdev-client   0.6.1.git20140518-0yavdr1~pre VDR Plugin to stream Live-TV to other VDR's - client part
ii  vdr-plugin-streamdev-server   0.6.1.git20140518-0yavdr1~pre VDR Plugin to stream Live-TV to other VDR's - server part
ii  vdr-plugin-svdrpservice       1.0.0-6yavdr4~precise         VDR plugin that provides a SVDRP service for other plugins
ii  vdr-plugin-vnsiserver         2:1.2.0~git20150103-a48edf135 VDR-Network-Streaming-Interface
ii  vdr-plugin-xineliboutput      1.1.0-22-g1d98107-1yavdr4~pre VDR plugin for Xine based sofdevice frontends


Any ideas?

Greets!

Bernd



7
Users / LinuxMCE NVR????
« on: August 14, 2015, 05:35:18 pm »
Would some be so kind and give me just a few hints how to use LinuxMCE NVR?
I already have an IP Camera working (based on Advanced_IP_camera DT).

Unfortunately I did not find a documentation, what to put in the configuration fields in web admin and how to handle my existing device with this NVR-device.

My LinuxMCE created this device automatically.


Thanks

8
Installation issues / 12.04: invoke-rc.d broken on MDs?
« on: April 26, 2015, 06:44:53 pm »
Hello there,

in 12.04 there are two different versions of invoke-rc.d  in /usr/sbin/

-rwxr-xr-x 1 root root    70 Apr 19 13:47 /usr/sbin/invoke-rc.d
-rwxr-xr-x 1 root root 11308 Jul 26  2012 /usr/sbin/invoke-rc.d.orig

But those files are only on the diskless MDs. On the core there is only one invoke-rc.d in /usr/sbin/.

The ones on the MD are not working. So the (e.g.) the script "StartVDRClient.sh" does not work properly. The two ones one the MDs do not even return an error code (!).

Can someone confirm this is a bug?

BR

Bernd

9
Feature requests & roadmap / Integration of streaming sites?
« on: April 26, 2015, 04:13:23 pm »
Hello there,

video streaming sites like watchever, netflix or amazon instant video are getting more important these days. I would really appreciate a better integration of those streaming sites into LinuxMCE without using the web browser.

At the moment I'm using those sites via appletv or via apps integrated into my Panasonic smart tv.

Personally I'm using the classical satellite tv less and less....


BR

Bernd




10
Users / Advanced IP Camera: snaphot directory? [solved]
« on: January 28, 2015, 02:59:29 pm »
Hello there,

I successfully installed a LevelOne WCS-0030 IP network camera (in my case device #251). I created DT #2314 (and uploaded it!).
I can watch the snapshot on every MD's orbiter and on the web admin page. The "/home/cameras" directory exists.

Now I want to save snapshots when motion is detected. I have separate motion detectors which report motion correctly to LMCE.

Somewhere in the forum I read that snapshots (in my case) should be saved in "home/cameras/251". But this directory does not exist.

1. Should "home/cameras/251" be created automatically? Do I have do create it manually?
2. Under "Events handler" -> "Respond to events" I created an event when motion is detected -> device: camera -> command: "GetVideoFrame". But I am not sure what to put into the configuration fields.

Please give me some hints to get this working.

Thanks!

B.

11
Users / Pulse Eight HDMI CEC - Port?
« on: January 22, 2015, 09:09:12 am »
Hello there,

I bought the adaptor mentioned above.
I need help understanding ports and pipes in LMCE.

My MD ist connected to an AVR input, as well as my PS3.
The output of the AVR is connected to the TV (all via HDMI).

My actual channel setup in webadmin is as follows:

0000 TV
2000 AVR
2100 HDMI adaptor
2200 PS3

- Does the HDMI adaptor need an address setting?
- what about address setting Nr. 5 (instead 0) as mentioned in the the libcec documentation, when HTPC is connected to an Avr.

Thanks!

Bernd


12
Users / ZWave sensor values ??
« on: January 16, 2015, 03:22:43 pm »
Hello all together,

I have three multisensor devices (two Fibaro FGMS and one Aeon multisensor) working in lmce 12.04. In the ZWave-log you can see that they are reporting motion, luminance, humidity (Aeon) and temperature as expected. But at the moment only temperature and motion detection finds its way into webadmin device's "state".

I want to use the values as event criteria, so I need them e.g. as "state" in lmce devices.

What needs to done to get this working?

Thanks for your hints!


Bernd

13
Users / SPDIF in 12.04 please help! [solved]
« on: November 09, 2014, 05:46:13 pm »
I am trying to connect my sound card to my denon a/v receiver via SPDIF (coax).

I have an Asus G31-Intel board with an onboard connector which is connected to the correspondent ASUS-SPDIF bracket. The SPDIF bracket is connected via coax (cinch) to my denon receiver.

Sound card is a ALC662 and is recognized correctly. Analog and digital devices are shown when typing aplay -l and aplay -L.

I already tried every setting in webadmin for MD (analog, SPDIF coax, SPDIF optical, HDMI, Manual). None of them is working.

Analog sound does work, but no digital sound. Doing a speaker-test results in playing (as shown in terminal) but no sound output out of my speakers. And: yes it its unmuted via alsamixer.

But: in alsamixer i can mute/unmute SPDIF but i cannot move the SPDIF sliders.

The SPDIF bracket has an optical and a coax output. Unfortunately i have not got an optical cable atm.


Any hints?

bernd

(again something which should work ootb and does not....)

14
Users / [solved] Configuration of VDR remotetimers
« on: October 21, 2014, 11:40:30 am »
Hello there!  :)

I'm using LMCE 12.04 with VDR 2.0.6 with a (non-graphic) Core and 2 diskless MDs. VDR is working properly, except remotetimers.

I want to use central recordings and timers on the core. How do I configure remotetimers-plugin to do that? Which directories are getting used and where do I put them?

e.g.
- /var/lib/video.00
- /home/public/data/pvr


Thanks for some hints!

Bernd

15
Installation issues / "Fresh" installation 12.04 July 24 29195
« on: July 30, 2014, 11:25:45 am »
Hello!

Yesterday I did a fresh install of 12.04 snap 29195 (July 24):

- full DVD installation
- core/hybrid
- vdr

Observations:

- If there is no dhcp on the external lan then network configuration is not properly set by the installer. After first reboot you must wait a very long time to boot up. Fixed by setting external router to act as dhcp and complete reinstall, which is much faster than manually configure network settings. -> Asking the user during installation could make sense to avoid this.

- A/V Wizard comes up after second reboot (still no sound). At first reboot Sara comes up but with no video and no sound. Install wizard can be completed without seeing oder hearing her.

- VDR does not work from the start (I). Errors in VDR-log show connection refusals. Fixed by: streamdevhosts.conf/allowed_hosts.conf must be configured manually to 0.0.0.0.
=> version 1.7.22 is quite old -> is it possible to integrate more recent versions?

- VDR does not work from the start (II): /var/lib/video.00 does not exist -> created it manually + added "user=root" in /etc/default/vdr

- Installation is faster than 10.04; less minor problems during installation compared to 10.04. (e.g. setting screen resolution)


Next steps:

- Diskless MD creation (2x)
- ZWave setup

Best regards

Pages: [1] 2