diff --git a/atom.xml b/atom.xml index d6663ed6ec..a195637dbc 100644 --- a/atom.xml +++ b/atom.xml @@ -4,7 +4,7 @@
Now teach LIRC about your particular remote control by preparing a lircd configuration file (/etc/lirc/lircd.conf
). Search the LIRC remote database for your model. If you can’t find it, then you can always use the irrecord
program to learn your remote. This will create a valid configuration file. Add as many remotes as you want by pasting them into the file. If irrecord
doesn’t work (e.g. for some air conditioner remotes), then the mode2
program is capable of reading the codes in raw mode, followed by irrecord -a
to extract hex codes.
Next, you have to make a ~/.lircrc
file that maps keypresses to system actions. The configuration is a bit tedious but it must be done. Use the prog = home-assistant
for all keys you want to be recognized by Home Assistant. The values you set for button
must be the same as in the lircd.conf
file and the values you put for config
entry will be the sensor value in Home Assistant when you press the button. An example may look like this:
and pressing some buttons on the remote.
-# Example configuration.yaml entry
@@ -153,6 +155,10 @@ end
+If you are on a Debian based system (like Raspberry Pi) and are having issues loading the component due to it being unable to install python-lirc, install it manually using apt-get install python3-lirc
.
+
The LIRC component fires ir_command_received
events on the bus. You can capture the events and respond to them in automation scripts like this: