I have a Raspberry Pi, running Rasplex. I have the Pi hooked up via HDMI to a Marantz receiver, and then that is hooked up to my Panasonic plasma. I use the receiver as the "hub" of my system, switching its input does audio and video switching.
Now, to my question: If I boot the RPi up freshly, CEC detection works great, and all of my functions work like a champ. Once I switch off of the input on the receiver, and then back again, the CEC connection seems to be lost. I have to reboot the Pi, or kill PHT to get it to redetect.
Is there a fix for this? Potentially a command I could run on the Pi via SSH to "redetect" the CEC connection? Maybe there is a bug in PHT? Any ideas?
Similar setup to yours; I have a Pi running Rasplex connected to my Marantz SR6008 receiver, which is then connected to my Samsung SmartTV - I cannot get CEC to work at all in this configuration, no control of Rasplex using either the Samsung or Marantz remote. If I hook the Pi up directly to the TV, then it works perfectly. Are you using your Panasonic remote to control the Pi?
Similar setup to yours; I have a Pi running Rasplex connected to my Marantz SR6008 receiver, which is then connected to my Samsung SmartTV - I cannot get CEC to work at all in this configuration, no control of Rasplex using either the Samsung or Marantz remote. If I hook the Pi up directly to the TV, then it works perfectly. Are you using your Panasonic remote to control the Pi?
I'm using a Logitech Harmony remote, and it works great. I had to tweak some of the buttons and edit my Pi's remote key bindings to make everything work perfectly, but it mostly just worked out of the box. I still have the above "re-detection" problem, which I have mitigated by making a little app for my phone which ssh's into the Pi and restarts PHT, which resolves the problem.
I have some kind of the same issue.
Rasplex --> Yamaha REceiver -> Samsung TV
Constantly it redetects HDMI on the TV .. It runs okay during playback though.. Very strange problem.
Have tried disabling cec and almost any hdmi configuration .. Only way it runs without redetection is by putting it directly in the Samsung TV's hdmi port.
I have some kind of the same issue.
Rasplex --> Yamaha REceiver -> Samsung TV
Constantly it redetects HDMI on the TV .. It runs okay during playback though.. Very strange problem.
Have tried disabling cec and almost any hdmi configuration .. Only way it runs without redetection is by putting it directly in the Samsung TV's hdmi port.
I use samsung remote to control the Pi.
Did you guys find a solution?
/Trazz
Unfortunately, I didn't find a solution. This is the main blocker for me with rasplex. I honestly believe that there is a software bug in Plex Home Theater, but I can't prove it. Why do I believe this? Because I don't have to reboot the pi to fix the problem. I simply have to `killall plexhometheater` and it re-establishes a CEC handshake, and everything works again.
In the meantime, I have worked around the problem by creating a shortcut on my iPhone to ssh into my Pi and restart PHT.
Having redetections no matter which resolution (Redection as in Samsung TV doing black screen for a second, and coming back showing 1080p@60hz) .. Tried cec off. HDMI control off on receiver.. all combinations possible.. Even changed HDMI cable to a better quality and shorter one..
Also Myplex keeps signing out, and back in..
However during playback everything was fine.. Maybe 1 or 2 redetections noticed during 10 MKV TV shows (over 3 days)
THEN..... I was looking at my powersupply as well as usb cable ..
I had a 5 volt usb powersupply only delivering 0.15A .. (one stolen from an e-cigarette charger) ..
I changed to one from apple (one of my iPads I guess) 5 Volt 2 AMP ..
I also changed the USB cable to a longer one (needed for the "nice look" of the installation)
Now we have sucessfully been logged in to MyPlex 2 days in a row. Not a single redetection.. It seems extremely stable..
I dont know if it helps anyone else, but this is my story .. Can't seem to find any other on google with HDMI vs. powersupply issues though..
I have a similar issue with my LG 2011 TV. CEC works initially, but if I come back to it after a few hours it doesnt respond to any CEC input. If, however, i connect using android or web client as remote, it seems to bring it back to life again and I can use my TV remote via CEC.
I have a similar issue with my LG 2011 TV. CEC works initially, but if I come back to it after a few hours it doesnt respond to any CEC input. If, however, i connect using android or web client as remote, it seems to bring it back to life again and I can use my TV remote via CEC.
I have the exact same issue with a slightly older LG TV. This worked 100% reliably with raspbmc so I'm sure it's not a power issue.
Same problem with my 2013 LG TV. CEC works great with rasplex. When i shut the tv off and on again the CEC is gone. The Input Page of the tv doesnt even show the simlink symbol.
I can play files on the rasplex via "send to" without problems. After a restart cec works fine again.
Did anyone solve their issues? I can test another power supply but with raspmbc i didnt have any issues.
No this is still an issue for me. I also didn't have any problems with raspbmc so I doubt its a power issue it seems to be more a problem of re-detecting CEC after the TV is off or the channel is changed.
Yes, this problem still exists for me too. I am currently using PlexConnect with my ATV more frequently than the Rasplex setup as a result. My wife simply won't tolerate anything that doesn't "just work," and I don't blame her.
Well there are many HDMI / CEC settings in config.txt simply because there are many different configurations possible and not a single way to handle them.
This is a long term issue, but i think that diffing those options and try them out is the way to go.
I am not sure we can come up with a single 'for all config', but if you find something that is suiting most people then we could have this defaulted in rasplex.
Yes, this problem still exists for me too. I am currently using PlexConnect with my ATV more frequently than the Rasplex setup as a result. My wife simply won't tolerate anything that doesn't "just work," and I don't blame her.
Hopefully, this issue will get fixed eventually!
Have you tried googling LG CEC, seems there are issues with Raspbmc and XBMC, although CEC is a 'standard' there are different ways that TV manufacturers implement it within their firmware. CEC works fine with the defaults in Rasplex with a Sony TV, Panasonic TV users have reported problems. So this is not a simple 'one size fits all'.
There are only two places afaik, where you can setup different behavior with CEC. one is in config.txt as mentionned above, the other one is on Preferences / System / input devices / peripherals (iirc).
There you can define XBMC options on how to hadle CEC.
The only few issues i had with My Samsung setup i was able to handle them with a combination of those params, so i'd suggest you dig them & make a few tests.
As stated before, CEC implementations can vary quite a lot from a manufacturer to the other and there is nothing that rasplex handles specifically regarding it. it's 100% handled by openelec stuff.
Now if the latest openelec seems to work it would probably be because gotham code has been reworked, and we'll merge with it, but this is gonna take a couple months before anything is available.
A quick update on this topic. I tried every single toggle, switch, setting, and configuration change I could find throughout Plex, XBMC, config.txt, etc. I debugged using CEC command line tools. I looked at source code. No matter what, I still lost CEC handshake, and the only resolution was to SSH into the Raspberry Pi and restart Plex Home Theater, or to reboot the Pi.
That said, I finally decided to bite the bullet and buy a Flirc - http://flirc.tv. I configured it in about 10 minutes, disabled CEC on the Pi, and rebooted, and its working perfectly. I wish I had done this much earlier. The Flirc is a great little device, is inexpensive, and means that you don't have to deal with CEC, which is overcomplex, poorly supported, and flaky at best.
The only downsides to the Flirc:
The software for configuration is a little crashy on my Mac, but it does work.
It makes my pretty Raspberry Pi, with its pretty Short Crust case - http://shortcrust.net - a bit less pretty.
Now that I have configured it successfully, I think #1 is basically a non-issue for me going forward, and #2 I am hoping to deal with by getting a USB extension cable to move the Flirc to a more inconspicuous location.
TL;DR - Skip CEC, buy a Flirc, and you'll be a happier person.
