Req Extending builtin CEC commands
#1
Hi,

We have nowday three builtin commands for CEC (CECActivateSource, CECStandby and CECToggleState).

It would be very usefull to add some more possibilities like adding somme parameters in order to addressing a particular equipment (TV, AMP, VP, ALL, ...)
and why not volumeUp or VolumeDown...

Thank's a lot.

Regards,

Big
Reply
#2
If I understand correctly, and something like that could possibly allow a smartphone/tablet remote to control the TV's CEC volume, then that would be really awesome and I am all for it :D
Reply
#3
Yes, that it!

With a smartphone/ tablet you would be able although to switch on the TV or only the amp in order to listen music, and easily.
Reply
#4
149356 (thread)
211527 (thread)
https://github.com/joshjowen/script.json-cec
Reply
#5
Thank's for this answer, but this is json api commmands based on builtin functions...

You cannot command amp directly with this.

Having the possibility to do something like CECActivateSource(TV), or CECActivateSource(Ampli) or CECStandby(All) or some new commands like CECVolumeUp(Ampli) would be fantastic.

Regards,

Big
Reply
#6
I think he's just listing related links for anyone interested.
Reply
#7
@bigbig6

what you are asking is (from most part) not possible.

for instance AS is command where local device (the one sending it) is asking to become Active device. It can't declare other device as being active.

other commands, with wider "permissions" (like for instance SetStreamPath()) are allowed to be sent from only one device and this is TV.

even other things (like your CECStandby(All)) is something defined as responsibility of device itself when TV is being turned off (depending on device, it can be set to "off").

if you are interested how all this works, you can play a bit on http://www.cec-o-matic.com

truth is CEC is a plain protocol with no any permission control, check or authentication, what means you can hack into the bus any bytes you want - but if other device is following cec specs - it won't respond/react on combinations not specified in specs - which indeed define such details like what type of device can send what messages, to what addresses (types of devices) and who can, or must not respond to them.
Reply
#8
(2015-07-09, 20:17)mk01 Wrote: @bigbig6

what you are asking is (from most part) not possible.

for instance AS is command where local device (the one sending it) is asking to become Active device. It can't declare other device as being active.

other commands, with wider "permissions" (like for instance SetStreamPath()) are allowed to be sent from only one device and this is TV.

even other things (like your CECStandby(All)) is something defined as responsibility of device itself when TV is being turned off (depending on device, it can be set to "off").

if you are interested how all this works, you can play a bit on http://www.cec-o-matic.com

truth is CEC is a plain protocol with no any permission control, check or authentication, what means you can hack into the bus any bytes you want - but if other device is following cec specs - it won't respond/react on combinations not specified in specs - which indeed define such details like what type of device can send what messages, to what addresses (types of devices) and who can, or must not respond to them.

Hello,

I don't understand most part of your post.

All of these functionality are allready in place in the of Kodi's CEC config...
When Kodi is powered off, you can switch off via CEC TV, ampli, only one or all of them.

Why it wouldn't be possible via buildin commands?

And there is a lot of possibilities via libcec client, which is used by internal command so why?

A+

Big
Reply
#9
Is there any news about it?

Regards,

Big
Reply
#10
I would really like to have a separate function CECInactivateSource as a complement to the already existing CECActivateSource.

My reason---and I believe there will be others with a similar setup---is that I am running Kodi on a Raspberry Pi (OpenElec 6.0), which I never turn off. But with the current CEC implementation, shutting down Kodi is the only way to return the active source to the TV.

My setup is as follows: Samsung TV----Teufel Corestation AVR----OpenElec 6.0 ~ ~ Yatse app

I can easily switch to Kodi by starting any media playback or manually invoking the CECActivateSource function. But for returning the active source back to the TV set I always have to fumble around with the TV remote, cycling the source back to the TV.

It would be great to just add an item in the Kodi main menu "Switch back to TV", invoking the missing function CECInactivateSource.

I am aware of the limitations of CEC mentioned by mk01, but this should not be an issue in this specific case. Kodi is running as the active source and just has to inform the system that it wants to inactivate. It is basically the same thing Kodi already does before shutting down.
Reply
#11
I know this is quite an old Thread, but this is still a missing feature and i also would like to see it implemented.
My setup is pretty much the same as thomasfl's.

A function to pass through raw CEC commands to the bus (like cec-client) would be sufficient to begin with,
and would open a lot of possibilities to addon developers.

I initially made a bug report about this because i was not sure if its a bug or not:
331235 (thread)
Reply
#12
(2018-05-04, 08:39)kleinem Wrote: I know this is quite an old Thread, but this is still a missing feature and i also would like to see it implemented.
My setup is pretty much the same as thomasfl's.

A function to pass through raw CEC commands to the bus (like cec-client) would be sufficient to begin with,
and would open a lot of possibilities to addon developers.

I initially made a bug report about this because i was not sure if its a bug or not:
331235 (thread)
@kleinem  Did you get an answer on this (or have you made any further progress?)
Reply
 
Thread Rating:
  • 0 Vote(s) - 0 Average



Logout Mark Read Team Forum Stats Members Help
Extending builtin CEC commands00
This forum uses Lukasz Tkacz MyBB addons.