Hi there,

I have finally replaced my AV receiver with one having HDMI inputs. I have connected my DM920 with the receiver and hooked the TV on it too.

Yesterday I was quite happy it works how I always wanted it, when I power the Dreambox the TV and AVR are powered on too, the same goes for shut down. Having the volume control redirected to AVR, I don't need any other RC most of the time.

But during the night Dreambox powered on and started the AVR too (luckily the AVR power on volume limit was set quite low, so nobody was woken). The TV stayed off.

I have been able to reproduce it in the morning. I am not sure I am reading the log properly, but it looks like the TV is starting to communicate after being in stanby for 45 minutes and wakes the Dreambox, which wakes the AVR. I was able to prevent Dreambox from being woken byt disabling the option "Power on/off based on CEC Events", but this also prevented to wake Dreambox up while switching the AVR input from Radio to Dreambox. Is there any way to blocklist the TV to ignore its power on requests while allowing it from the AVR?

If not, how difficult would it be to extend the "Power on/off based on CEC Events" options by two blocklists, one for Power-on and other for Power-off)?

And as it looks, I have one additional issue with the TV doing something after 45 minutes, what puts it in a state which makes it immune to the CEC Power on calls, the only way to power it on is via the Samsung RC. In the attachments you can see the logs from each of the 3 phases. First when I put the Dreambox to Standby, second where you can see the communication from TV and third, where I Powered on the Dreambox, where it didn't wake up TV.

Please can somebody look at the logs, see if I interpret the logs properly and if there is some extra command or sequence of commands to wake the TV from the strange state.

Thanks, and have a peaceful and relaxing festive season!

PiGeon

I know some vendors' implementation of CEC is horrible, additionally, the TV is quite old, so one can't really hope Samsung will fix it and that's exactly the reason I am asking here

Because here come the people who might have had a similar setup and found a solution already and the other reason is that Reichi could adjust the CEC plugin to make a workaround possible, either via the vendor specific or the experimental extension or implement the suggested blocklist.

The old AVR had a learning RC, so I could use its remote to start the TV as well and so could have just two RCs on the table, it was the same with DMs RC10. But the new AVR RC is not able to control the TV via infrared, it looks like they have bet everything on CEC.

It has been years since I tried to solve the "too many RCs on the table" situation with CEC, I really hoped the new AVR could change the game.

Yesterday I found out one can learn the RCU-BT to control other devices via the irdb.json, so there is a chance I could have just 2 RCs on the table again, but today I learned that I must find someone with Dreambox one or two to do the update

thanks for helping

PiGeon

I know the cause is the Samsung TV, but we all know they will not fix it.

And I am not going to throw the TV in garbage if it still works perfectly, I don't want to create unnecessary waste.

So, I still hope there is some workaround possible with the HDMI vendor/experimental option/feature.

thanks for understanding

PiGeon

Here is my config

thanks

PiGeon