Wetek Play (1st gen) CEC not working after TV turn off

pawnthep · December 26, 2016 at 11:38 PM

My box is Wetek Play (1st gen).
I've tried almost LibreELEC builds, including the newest 7.90.010, just to check CEC issue that keep me not upgrading from OpenELEC to LibreELEC.

That is, CEC will not work again after TV is off an then turn on later. (I always leave the box running all the time as tvheadend server.)
I have to start/reboot Wetek when TV is on in order to get CEC to work.

This never be an issue with OpenELEC builds.

Now I'm still at OpenELEC just because this CEC issue.

Would anyone with Wetek Play please help check and confirm if this is only me or it's a real annoying bug?

Thanks

pawnthep · January 1, 2017 at 2:49 PM

No one with WP suffer from this issue?

Sent from my X900+ using Tapatalk

rniessen · January 8, 2017 at 5:05 PM

I got the same problem. Also have a wetek play 1. With openelec it works fine, but after installation of LibreElec, cec does not work again after I turned off/on the tv.
Do you already have a solution or workaround?
thanks

pawnthep · January 9, 2017 at 1:31 AM

Sadly no.

Now I'm using this box mainly as tvheadend server.

I'm thinking about trying Kodi Callbacks addon.
- set task to Kodi built-in function: RestartApp (or whatever function that suite your condition.)
- set event to "On screensaver deactivated"

Right now I can't test this because on LG TV, which my Wetek connected to now, will not make it deactivates screensaver when TV is powered on. But I think my other TV, Panasonic, can do that. So if it does maybe CEC might work again through RestarApp function.

-Thomas- · January 16, 2017 at 8:29 PM

I experience the same problem with LibreELEC 7.0.3 and my Samsung TV (UE46F6470). Here's an excerpt from my log file with CEC debugging activated, at the moment I turned on my TV again:

Code

21:20:31 T:2971837344   DEBUG: CecLogMessage - >> 0f:32:67:65:72
21:20:31 T:2971837344   DEBUG: CecLogMessage - >> TV (0) -> Broadcast (F): set menu language (32)
21:20:34 T:2971837344   DEBUG: CecLogMessage - >> 0f:80:00:00:10:00
21:20:34 T:2971837344   DEBUG: CecLogMessage - making Recorder 1 (1) the active source
21:20:34 T:2971837344   DEBUG: CecLogMessage - >> source activated: Recorder 1 (1)
21:20:34 T:2971837344   DEBUG: CecLogMessage - sending active source message for 'Recorder 1'
21:20:34 T:2971837344   DEBUG: CecLogMessage - << powering on 'TV' (0)
21:20:34 T:2971837344   DEBUG: CecLogMessage - << 10:04
21:20:34 T:2971837344   DEBUG: CecLogMessage - >> TV (0) -> Broadcast (F): routing change (80)
21:20:34 T:2971837344   DEBUG: CecLogMessage - << Recorder 1 (1) -> broadcast (F): active source (1000)
21:20:34 T:2971837344   DEBUG: CecLogMessage - << 1f:82:10:00
21:20:34 T:2971837344   DEBUG: CecLogMessage - << Recorder 1 (1) -> TV (0): menu state 'activated'
21:20:34 T:2971837344   DEBUG: CecLogMessage - << 10:8e:00
21:20:35 T:2971837344   DEBUG: CecLogMessage - >> 4f:84:30:00:04
21:20:35 T:2971837344   DEBUG: CecLogMessage - >> Playback 1 (4) -> Broadcast (F): report physical address (84)
21:20:37 T:2971837344   DEBUG: CecLogMessage - >> 0f:85
21:20:37 T:2971837344   DEBUG: CecLogMessage - >> 0 requests active source
21:20:37 T:2971837344   DEBUG: CecLogMessage - << Recorder 1 (1) -> broadcast (F): active source (1000)
21:20:37 T:2971837344   DEBUG: CecLogMessage - << 1f:82:10:00
21:20:37 T:2971837344   DEBUG: CecLogMessage - >> TV (0) -> Broadcast (F): request active source (85)

Display More

It's interesting that Kodi tries to send an active source message even though I deactivated all corresponding options in Settings -> System -> Input devices -> libcec. Looks like a bug in Kodi to me...

Cheers
Thomas

Pirat5 · January 22, 2017 at 7:30 PM

I confirm the same problem in LibreElec.