227 replies to this topic

[zeros]

My friendly advice would be to change the default value in the HDMI-CEC setup 'Minimum send interval' to at least 100 ms. Default value is at the moment 'Disabled', what is pure nonsense (as it clears from the trials). I believe that 100 ms is sufficient for vast majority of users.

What works also then:
- Switch TV to correct input
- TV switches also from its internal DVB-T to correct input (to the input, were is connected our STB, if we launch it ON)

[theparasol]

Hope this will help others too since:

 

To let my samsung UE32C6000 TV work correct with hdmi CEC:

 

1) Enable Anynet+ (HDMI-CEC)

2) Enable Automatic poweroff

 

Due to a bug in the C series firmware the "Enable Automatic poweroff" feature will be set to off after some time.

As for a result after some time if you switch the receiver to standby the television wont powerdown any more.

If you inspect the anynet+ menu on the television again the "Enable Automatic poweroff" is set to "no" again.

You can workaround this bug by setting "Upgrade standby-mode" to off.

This setting can be found in the "software upgrade" menu

[Tii]

I'm having a strange HDMI-CEC issue between a Sharp TV & my xtrend 9x00 ,

 

when I'm in any kind of list, and I press the down button for a longer period on the TV remote, instead of scrolling down the list, the result is the same as if I had pushed the Menu button.

Scrolling down click by click works fine.

 

Does any one recognize this? Or any ideas?

[Tii]

bump ?

[thedogg]

I have also similar problem. I took py files provided in this topic but there is no way to compile it on pyo. After restart it is still py. What have I done wrongly?

[Erik Slagter]

The py files remain, the pyo files are updated from the py.

[s3n0]

Hi all,

is there any chance to get somewhere communication protocol LG Simplink standard? I need to know how to turn-off LG TV through HDMI-CEC. Exactly how devices communicate with each other device over Simplink LG technology. My TV LG 32SL8000 has been successfully switched on when I turn on Formuler_F3. My TV responds to primitive command "CEC_OPCODE_IMAGE_VIEW_ON = 0x04" that sends Formuler_F3 to my TV. I tested it with plugins HdmiTest_v0.4 and I also saw a record of sending codes in the system log of booting Formuler_F3.

It is true that must be reported Formuler_F3 as equipment manufactured under the brand LG to launch television to communicate? Is there any need to pair devices? Or is there some simple code to send to LG TV to be switched to the standby mode?

 

HdmiTest v0.4 plugin does not work corretly in the firmware OpenATV5.3. HDMI-CEC codes sent by the TV does not see the system log and also they do not see the plugin HdmiTest. Of course the problem with OpenATV5.3 may also consist in HdmiCEC drivers that are unable to detect receives HDMI-CEC. But I can send the commands into LG TV. Also I tested there "0x04" command to waking up of LG TV.

HdmiTest v0.4 plugin works in firmware OpenPLi4 - received HDMI-CEC codes are visible, but after receiving about 1-3 lines plugin crashes (  enigma2_crash.log   4.17KB   7 downloads - "green screen of death"), and then restart the system.

 

 

I know that LG Simplink is unusual CEC communication, but we could give this issue by sending a single code string CEC. Then I edit the script for python-driver HdmiCEC or add also another option in the configuration menu on the HDMI-CEC for example - "LG TV tuning-off command: Enable/Disable".

 

Thanks.

 

(sorry but my English is very poooooor)

Edited by s3n0, 28 December 2016 - 16:22.

[littlesat]

Bug in HdmiTest plugin... Er komt blijkbaar een abort reason uit die niet in de abortReason dict staat... misschien een sanity check omheen bouwen..... iets met abortReason.get(ord(data[1])), "Unknown")... ???

 

[code=auto:0]

<  5877.582>   File "/usr/lib/enigma2/python/Plugins/Extensions/HdmiTest/plugin.py", line 374, in messageReceived

<  5877.584>     self["rxtext"].setText(self.rxText(cmd, data, length) + "\n" + self["rxtext"].getText())

<  5877.585>   File "/usr/lib/enigma2/python/Plugins/Extensions/HdmiTest/plugin.py", line 394, in rxText

<  5877.588>     return "%02X" % ord(data[0]) + " " + abortReason[ord(data[1])]

<  5877.588> KeyError: 224

[/quote]

[Martin_B]

I have some problems with HDMI-CEC on VU Uno 4k.

 

HDMI-CEC works from/to standby.

But not from/to deep standby.

 

The VU ist connected to AV-Receiver (Panasonic)

TV (Samsung) is connected to AV-Receiver.

 

When I start VU from deep-standby, TV & receiver do not switch on.

I have to swich them on manually.

 

But when VU goes to standby, both switch off.

When VU comes from standby, both switch on.

 

When VU goes to deep-standby, TV & receiver do not switch off.

 

 

Settings (HDMI-CEC setup):

 

enabled: yes

put TV in standby: yes

wakeup TV from standby: yes

regard deep standby as standby: yes

use TV remote control: no

handle standby from TV: no

handle wakeup from TV: no

wakeup signal from TV: any activity

foreward volume keys: no

put receiver in standby: yes

wakeup receiver from standby: yes

minimum send interval: 150ms

repeat leave standby message: disabled

 

 

I think this is NOT a PLI problem since the behaviour seems similar with VTI image ...

 

Any ideas?

 

 

Thanks & regards

[s3n0]

F*k the HDMI-CEC usage :-).

 

I need help to shut down / power on with my LG-TV, but stupid Simplink-CEC has problems with standard of HDMI-CEC which is used on all other devices.

OpenPLi-4 is making use of Stanby.py (.pyo) python script with user bash-script support.

Inside of the Standby.py script is the call of script by leaving and entering stand-by mode.

So, I can interconnect LG-TV with my satellite box (Formuler F3) with using of the RS232C interface.

Connected by the simple serial cable type - "null modem without handshaking".

 

/usr/script/standby_enter.sh

(if the folder and file does not exist, make it then and set the file rights/attributes to 0755)

#!/bin/sh
echo "ka 01 00" > /dev/ttyS0        # power down LG-TV over RS232 interface

/usr/script/standby_leave.sh

(if the folder and file does not exist, make it then and set the file rights/attributes to 0755)

#!/bin/sh

echo "ka 01 01" > /dev/ttyS0        # power on LG-TV over RS232 interface

Maybe this helps someone.

GL

 

[1] https://www.lg.com/u...c-ba-rs232c.pdf - LG TV serial connection

[2] https://www.lammertb...null_modem.html - example of the null modem pinouts

[Dimitrij]

Martin_B

repeat leave standby message: enabled

[imperia]

Recently my HDMI-CEC is acting strangely.

 

My LG TV LB670 recently got updated, but I don't see changes related to HDMI-CEC. firmware 05.05.35

I updated my xTrend multiple times too (tried to search change log - didn't noticed HDMI-CEC related changes too)

 

Here is what happened:

I tried to turn OFF my STB, but it immediately goes back ON. I found out that this is because HDMI-CEC option "Wake up signal from TV". It was set to "Any Activity". (All other options are unable to wake up my STB)

I need to be able to turn OFF my STB so tuner is free and I can sometimes watch TV from my PC.

 

Because TV is unable to wake up the STB and I am using my TV to wake me up every morning - I set "Put receiver in standby" to OFF. Else there is no picture(signal from STB) in the morning because the TV turns OFF the STB with its Sleep function.

 

With today OpenPli update (no HDMI-CEC related changes) the STB no longer respect the "Put receiver in standby" option. It always goes OFF with the TV. 

 

Anybody know what is going on? Any HDMI-CEC changes recently?

 

Some additional information:
I am unable to control my STB with TV remote unless I turn OFF/ON the STB or unplug/plug the HDMI cable.

Before there was working option other that "Any activity" that was able to wake up my STB. 

[Martin_B]

repeat leave standby message: enabled

 

Thanks, but does not work.

I tried VTI Image, doesn't work either.

 

Now I solved it this way:

Installed "EnhancedPowerSave" Plugin.

Configured Standby -> DeepStandby 10 minutes.

 

I switch the VU to standby; AV-Receiver & TV switch off.

After 10 Minutes vu goes to deep standby.

 

Could also fix the "switch on" problem.

Enabled AV-Receiver option "HDMI-THROUGH"

 

Works perfectly this way ... 

[hawkeye116477]

My friendly advice would be to change the default value in the HDMI-CEC setup 'Minimum send interval' to at least 100 ms. Default value is at the moment 'Disabled', what is pure nonsense (as it clears from the trials). I believe that 100 ms is sufficient for vast majority of users.

What works also then:
- Switch TV to correct input
- TV switches also from its internal DVB-T to correct input (to the input, were is connected our STB, if we launch it ON)

With my LG TV only 800 ms and above works correct, bellow this value TV does not switch to the correct input. So slightly higher values should be added.

Edited by hawkeye116477, 5 February 2017 - 14:38.

[zeros]

The best sending interval is the smallest interval which the TV responds. 800 ms, is significant and noticeable interval, I have here all the TV's 100 ms to handle it. I can't tell if there is a auto-detect functionality, or it must be the test and trial of error to find the correct value. As I told, for me is 100 ms correct value, the smaller interval can not reach the TV respond and 800 ms is still a scary long to wait ;-)

[hawkeye116477]

The best sending interval is the smallest interval which the TV responds. 800 ms, is significant and noticeable interval, I have here all the TV's 100 ms to handle it. I can't tell if there is a auto-detect functionality, or it must be the test and trial of error to find the correct value. As I told, for me is 100 ms correct value, the smaller interval can not reach the TV respond and 800 ms is still a scary long to wait ;-)

I have tested now and 550 ms is the smallest, so probably I previously something wrong checked. Unfortunately 500 ms and bellow - LG UH6507 doesn't switch to correct input. So higher vales than 250 ms (not as default, but to choose), should be added, like in Egami Image

[Dimitrij]

[HdmiCec] add more value for "Minimum send interval"

[Erik Slagter]

Applied.

[littlesat]

I thought we stopped merging this week...?

 

Could we also merge this one...

https://github.com/O...nigma2/pull/631

[Erik Slagter]

Only when the build environment is working again like it should. We still have problems for a whole stack of receivers.