HDMI-CEC

The hdmi_cec integration provides services that allow selecting the active device, powering on all devices, setting all devices to standby and creates switch entities for HDMI devices. Devices are defined in the configuration file by associating HDMI port number and a device name. Connected devices that provide further HDMI ports, such as sound-bars and AVRs are also supported. Devices are listed from the perspective of the CEC-enabled Home Assistant device. Any connected device can be listed, regardless of whether it supports CEC. Ideally the HDMI port number on your device will map correctly the CEC physical address. If it does not, use cec-client (part of the libcec package) to listen to traffic on the CEC bus and discover the correct numbers.

CEC Setup

Home Assistant OS

To test if HDMI-CEC will work on your Home Assistant OS installation, you can use the official CEC Scanner add-on. Run this add-on to see if your hardware has HDMI-CEC capabilities and which devices are connected. Do not have this add-on Start on boot as it will interfere with the integration.

Once you’ve run the add-on, you can use the resulting scan information to configure the integration.

Adapter

The computer running Home Assistant must support CEC, and of course be connected via HDMI to a device also supporting CEC. You can purchase a USB CEC adapter to add support if necessary. Note that all Raspberry Pi models support CEC natively.

libcec

This section only applies to users of Home Assistant Core in a Python virtual environment.

libcec must be installed for this integration to work. Follow the installation instructions for your environment, provided at the link. libcec installs Python 3 bindings by default as a system Python module. If you are running Home Assistant in a Python virtual environment, make sure it can access the system module, by either symlinking it or using the --system-site-packages flag.

Symlinking into virtual environment

Create a symlink to the cec installation including the _cec.so file. Keep in mind different installation methods will result in different locations of cec.

ln -s /path/to/your/installation/of/cec.py /path/to/your/venv/lib/python*/site-packages
ln -s /path/to/your/installation/of/_cec.so /path/to/your/venv/lib/python*/site-packages

Symlinking examples

For the default virtual environment of a Manual install for Raspberry Pi the command would be as follows.

ln -s /usr/local/lib/python*/dist-packages/cec.py /srv/homeassistant/lib/python*/site-packages
ln -s /usr/local/lib/python*/dist-packages/_cec.so /srv/homeassistant/lib/python*/site-packages

Testing your installation

• Login to Raspberry Pi

ssh pi@your_raspberry_pi_ip

• at the command line type:

echo scan | cec-client -s -d 1

Note: to use this command you have to install cec-utils package. In Debian based should be: sudo apt install cec-utils

• This will give you the list of devices that are on the bus

opening a connection to the CEC adapter...
requesting CEC bus information ...
CEC bus information
===================
device #4: Playback 1
address:       3.0.0.0
active source: no
vendor:        Sony
osd string:    BD
CEC version:   1.4
power status:  on
language:      ???

Configuration Example

In the following example, a Pi Zero running Home Assistant is on a TV’s HDMI port 1. HDMI port 2 is attached to a AV receiver. Three devices are attached to the AV receiver on HDMI ports 1 through 3.

You can use either direct mapping name to physical address of device

hdmi_cec:
  devices:
    TV: 0.0.0.0
    Pi Zero: 1.0.0.0
    Fire TV Stick: 2.1.0.0
    Chromecast: 2.2.0.0
    Another Device: 2.3.0.0
    BlueRay player: 3.0.0.0

or port mapping tree:

hdmi_cec:
  devices:
    1: Pi Zero
    2:
      1: Fire TV Stick
      2: Chromecast
      3: Another Device
    3: BlueRay player

Choose just one schema. Mixing both approaches is not possible.

Another option you can use in configuration is platform which specifying of default platform of HDMI devices. “switch” and “media_player” are supported. Switch is default.

hdmi_cec:
  platform: media_player

Then you set individual platform for devices in customizations:

hdmi_cec:
  types:
    hdmi_cec.hdmi_5: media_player

And the last option is host. PyCEC supports bridging CEC commands over TCP. When you start pyCEC on machine with HDMI port (python -m pycec), you can then run Home Assistant on another machine and connect to CEC over TCP. Specify TCP address of pyCEC server:

hdmi_cec:
  host: 192.168.1.3

Services

Select Device

Call the hdmi_cec.select_device service with the name of the device from configuration or entity_id or physical address”to select it, for example:

{"device": "Chromecast"}

{"device": "switch.hdmi_3"}

{"device": "1.1.0.0"}

So an Automation action using the example above would look something like this.

action:
  service: hdmi_cec.select_device
    data:
      device: Chromecast

Power On

Call the hdmi_cec.power_on service (no arguments) to power on any devices that support this function.

An Automation action using the example above would look something like this.

action:
  service: hdmi_cec.power_on

Standby

Call the hdmi_cec.standby service (no arguments) to place in standby any devices that support this function.

An Automation action using the example above would look something like this.

action:
  service: hdmi_cec.standby

Change volume level

Call the hdmi_cec.volume service with one of following commands:

Volume up

Increase volume three times:

{"up": 3}

Keep increasing volume until release is called:

{"up": "press"}

Stop increasing volume:

{"up": "release"}

Volume down

Decrease volume three times:

{"down": 3}

Keep decreasing volume until release is called:

{"down": "press"}

Stop decreasing volume:

{"down": "release"}

Volume mute

Toggle mute:

{"mute": ""}

value is ignored.

Useful References

• CEC overview
• CEC-o-matic