Getting lirc to work with Raspberry Pi 3 (Raspbian Stretch)

lirc-pi3.txt

Notes to make IR shield (made by LinkSprite) work in Raspberry Pi 3 (bought from Amazon [1]). 
The vendor has some documentation [2] but that is not complete and sufficient for Raspbian Stretch. 
Following are the changes that I made to make it work.

$ sudo apt-get update
$ sudo apt-get install lirc

# Add the following lines to /etc/modules file
lirc_dev
lirc_rpi gpio_in_pin=18 gpio_out_pin=17

# Add the following lines to /etc/lirc/hardware.conf file
LIRCD_ARGS="--uinput --listen"
LOAD_MODULES=true
DRIVER="default"
DEVICE="/dev/lirc0"
MODULES="lirc_rpi"

# Update the following line in /boot/config.txt
dtoverlay=lirc-rpi,gpio_in_pin=18,gpio_out_pin=17

# Update the following lines in /etc/lirc/lirc_options.conf
driver    = default
device    = /dev/lirc0

$ sudo /etc/init.d/lircd stop
$ sudo /etc/init.d/lircd start

# Check status to make lirc is running
$ sudo /etc/init.d/lircd status

# Reboot before testing
$ reboot

# To test if lirc driver is working
$ sudo /etc/init.d/lircd stop
$ mode2 -d /dev/lirc0
<press a key in remote and you should see multple lines like below>
pulse 560
space 1706
pulse 535

# to record a custom remote/register a remote device
$ sudo /etc/init.d/lircd stop
$ sudo irrecord -d /dev/lirc0 ~/lircd.conf
# follow the instruction prompted by the above command carefully
# at the end ~/lircd.conf file will be generated

# backup the original lircd.conf
$ sudo mv /etc/lirc/lircd.conf /etc/lirc/lircd_original.conf
$ sudo cp ~/lircd.conf /etc/lirc/lircd.conf
$ sudo /etc/init.d/lircd start

# you can test if the recorded remote works by
$ irsend SEND_ONCE <device-name> KEY_POWER
$ irsend SEND_ONCE <device-name> KEY_VOLUMEUP

[1] https://www.amazon.com/Infrared-Shield-for-Raspberry-Pi/dp/B00K2IICKK/ref=pd_sbs_328_1?_encoding=UTF8&psc=1&refRID=1QPY33VFCGETBJ17K8QE
[2] http://learn.linksprite.com/raspberry-pi/shield/infrared-transceiver-on-raspberry-pi-lirc-software-installation-and-configuration/

This is the only place amongst the many I have looked at that is both carefully written and laid out, and works.

Well Done and thanks

Exactly what I wanted to say :)

Thank you @prasanthj!

i like this

Only Tutorial that worked! Thank You

spent the last 4-5 hours trying to get this to work on an old RPI 1 and energenie IR board, this worked perfectly

one thing I would add that I found elsewhere is to run the following command as well ...

sudo /usr/share/lirc/lirc-old2new

while this might not have been the cause of my problems this is where I managed to get things to start working, but the above sorted things out ...

HI, I'm trying to get lirc working on Strech, but theres no "/etc/lirc/hardware.conf" because it's version 0.9.4 for what I've been told:
In Raspian Stretch lirc 0.9.4 is included in the Debian package. The configuration is slightly different : - The hardware.conf file is not supported, obsoleted by a new lirc_options.conf file and systemd unit definitions.
Should I create the hardware.conf file?
Thanks in advanced

@prasanthj Very good How-to, but, as remarked by Alkuimista, there's no hardware.conf file.
Do you have a solution to solve the new way of integration?

Best regards and, of course, happy new Year :)

hardware.conf missing here too
Raspbian GNU/Linux 9 (stretch)
latest lirc

Thank you very much for making this work. I looked for a long time but nothing worked. now everything is operational.

@Alkuimista @siggi60 @ageorgios
simply create the file and paste the settings. works for me.

also, i have faced a problem where everything seemed to work fine, but i didn't get any output running irw command. in case someone's stuck there: the problem is lircd.conf file which you've just generated. take a look at it - you probably will get two hex codes for each button, where the second one is always the same. simply delete this value from each line and everything should work now.

Hi Guys,
Same issues here, every single one of your issues I had. Segmentation Fault, "read 8 bytes", etc. I tried everything (including moving rooms, but still had problems!)

I might have something that someone else might find useful, that I couldn't find anywhere else on the web.

Details:
#################################
I'm running Debian Stretch.
Raspberry Pi Zero W (doesnt matter what version, all the same)
pi@raspberrypi:~ $ apt list lirc
Listing... Done
lirc/stable,now 0.9.4c-9 armhf [installed]
#################################

Some of your issues I "resolved" by jumping around the web, but this one was what solved it all for me.

1. I apt-get remove lirc
2. then apt-get purge lirc (no backtick of course).
3. Followed what @prasanthj had to say in the above noted guide.
4. Stopped lircd.service and lirc.socket (systemctl stop lircd.....xyz)

My biggest issue was non-cfl... IR noise, even with the TSOP in a cardboard box (with a lid loosely on). I'm in practical darkness (where the sporadic noise is)

mode -2 /dev/lirc0 kept saying "received 8 bytes" or "received 12 bytes", and would stop without any remote input.

irrecord kept telling me that it was detecting "170 bytes" but that it was minimal noise. Once I moved it to the GOOD location in my house, it stopped reporting any sign of IR. "No significant noise (received 0 bytes)" is what you want IRRECORD to say; anything else and YOU WILL HAVE PROBLEMS.

Another would be dead give away: irrecord would ask for button input, then a second or two later (before I press the button) it would say that it received a signal.
Should have been a dead giveaway, but the last and final was what really helped.

What really helped conclude was: cat /dev/lirc0, and seeing tons of random jibberish all across my screen for 30 seconds (and would pause for a couple seconds, then repeat). I would expect to see non-unicode characters, but ONLY when I press the button! No other time, because it is NOISE! Maybe a few characters are acceptable (here and there)...

While running cat /dev/lirc0 and moving the TSOP38328 sensor: I noticed it dropped right off as soon as I left my dark living room.

I can't believe that someone (myself) dealing with RF on a day to day basis; took 3 days to figure out this problem!

Thanks to all!

Hi @Alkuimista, the link below has info about new setup for Raspberry Raspbian Stretch Lircd version 0.9.4c

https://github.com/josemotta/IoT.Starter.Api/tree/master/gpio-base

I am running Raspbian Stretch with Desktop (kernel version 4.9) on a Raspberry Pi 3. and ANAVI Infrared pHAT IR board. I followed the steps as in this how-to. Created a hardware.conf as this was missing . But when I tried recording a panasonic aircon remote, it failed to create .conf file and seemed to hung in irrecord after two lines of dots of button presses.

Any help on this?

log

pi@raspberrypi:~ $ sudo irrecord -d /dev/lirc0 ~/lircd.conf
Running as regular user pi
Using driver default on device /dev/lirc0

irrecord - application for recording IR-codes ----

---

Press RETURN to continue.

Checking for ambient light creating too much disturbances.
Please don't press any buttons, just wait a few seconds...

No significant noise (received 0 bytes)

Enter name of remote (only ascii, no spaces) :panasonicir
Using panasonicir.lircd.conf as output filename

Now start pressing buttons on your remote control.

It is very important that you press many different buttons randomly
and hold them down for approximately one second. Each button should
generate at least one dot but never more than ten dots of output.
Don't stop pressing buttons until two lines of dots (2x80) have
been generated.

Press RETURN now to start recording.
................................................................................
Got gap (78301 us)}

Please keep on pressing buttons like described above.
...............................................................................

I am now able to control the Panasonic aircon with anavi infrared phat on a raspberry pi board :-) by following the steps in the tutorial link https://www.cnx-software.com/2017/03/12/how-to-control-your-air-conditioner-with-raspberry-pi-board-and-anavi-infrared-phat/. Then, I had to update the lircd.conf file with the gap value that I had obtained in the past using irrecord (see my log posted earlier). The gap value was 78301 us.
Just a side note, for the latest Raspbian Stretch, it didn't require to update /etc/modules and /etc/lirc/hardware.conf.

I used that, too!

Just had to remove the trailing "large value" from every command, as well as the large one near the beginning.

Hello! Do you know if it could work in GPIO16=IN and GPIO13=OUT? I'm testing with these pins and it not work for me 😭

Just to Update. Thank You! I followed it and works on my MATRIX Creator Thank You!!!

Tks my friend.
I install my RC using lircd on OSMC and now migrate to raspbian.
Only put my file .conf in new system and works
...best

For lircd 0.9.4c Rpi3 with PiFi DAC+ v2.0 and Humax RM-F04 remote
Add dtoverlay=lirc-rpi,gpio_in_pin=26 into /boot/config.txt

Install lirc
sudo apt-get install lirc

Download the index from the remote repository
sudo irdb-get update

Find your remote
sudo irdb-get find humax

Download your remote
sudo irdb-get download humax/RM-F04.lircd.conf

Copy your remote
sudo cp RM-F04.lircd.conf /etc/lirc/lircd.conf.d/

Change etc/lirc/lircd.conf/lirc_options.conf
sudo nano /etc/lirc/lircd.conf/lirc_options.conf
Change following items:
driver = default
device = /dev/lirc0

Restart lirc deamon
systemctl restart lircd.service
Check if loaded without errors
sudo systemctl status lircd.socket lircd.service

Check your remote with command irw

With pressing remote Vol-Up output should be like this:
000000000008f807 00 KEY_VOLUMEUP humax
000000000008f807 01 KEY_VOLUMEUP humax
000000000008f807 02 KEY_VOLUMEUP humax

Just wanted to echo other peoples comments - best description of how to get everything setup I've found. Thank you for your efforts.

Thanks a lot ! I was having a rough time making this work on RPi

Anyone else using Raspbian Stretch that runs into the error: Info: Cannot configure the rc device for /dev/lirc0 try following the last comment in the bug report: https://sourceforge.net/p/lirc/tickets/168/

When I recorded signals with irrecord, I got:

begin codes
      KEY_POWER                0x219E48B7 0x7E825B6C
      KEY_HOME                 0x219E609F 0x7E825B6C
      KEY_UP                   0x219EA05F 0x7E825B6C
      KEY_LEFT                 0x219EE01F 0x7E825B6C
      KEY_ENTER                0x219E10EF 0x7E825B6C
      KEY_RIGHT                0x219E906F 0x7E825B6C
      KEY_DOWN                 0x219E00FF 0x7E825B6C
      KEY_BACK                 0x219ED827 0x7E825B6C
      KEY_STOP                 0x219E20DF 0x7E825B6C
      KEY_OPTION               0x219E58A7 0x7E825B6C
      KEY_REWIND               0x219EF807 0x7E825B6C
      KEY_PLAYPAUSE            0x219E50AF 0x7E825B6C
      KEY_FASTFORWARD          0x219E7887 0x7E825B6C
      KEY_PREVIOUS             0x219E40BF 0x7E825B6C
      KEY_NEXT                 0x219E807F 0x7E825B6C
      KEY_SEARCH               0x219EF00F 0x7E825B6C
      KEY_EJECTCD              0x219E08F7 0x7E825B6C
  end codes

After installing this configuration file at /etc/lirc/lircd.conf.d and rebooting, irw produced no output, though I could see using strace
that my /usr/sbin/lircd --nodaemon process was reading data from /dev/lirc0. Removing the 0x7E825B6C codes from each of the
above lines and rebooting caused irw to begin showing the key values in the left column above when I pressed the corresponding
buttons on my WD TV Live remote control.

After I removed the right hand codes from my *.lircd.conf file it all started working nicely!

This instruction set doesn't appear to be working. After stopping and starting lircd, I get this:

lircd-0.9.4c[3841]: Notice: /etc/lirc/lircd.conf.d/devinput.lircd.conf: devinput: Multiple values for same …BTN_MOUSE
lircd-0.9.4c[3841]: Warning: Duplicate remotes "devinput" found, problems ahead
lircd-0.9.4c[3841]: Notice: lircd(default) ready, using /var/run/lirc/lircd
lircd-0.9.4c[3841]: Notice: /etc/lirc/lircd.conf.d/devinput.lircd.conf: devinput: Multiple values for same …BTN_SOUTH
lircd-0.9.4c[3841]: Notice: /etc/lirc/lircd.conf.d/devinput.lircd.conf: devinput: Multiple values for same …_TOOL_PEN
lircd-0.9.4c[3841]: Notice: /etc/lirc/lircd.conf.d/devinput.lircd.conf: devinput: Multiple values for same …N_TRIGGER
lircd-0.9.4c[3841]: Notice: /etc/lirc/lircd.conf.d/devinput.lircd.conf: devinput: Multiple values for same …ER_HAPPY1
lircd-0.9.4c[3841]: Notice: /etc/lirc/lircd.conf.d/devinput.lircd.conf: devinput: Multiple values for same …BTN_WHEEL
lircd-0.9.4c[3841]: Warning: Duplicate remotes "devinput" found, problems ahead
lircd-0.9.4c[3841]: Notice: lircd(default) ready, using /var/run/lirc/lircd

Hello there !
thanks for your share !!!
Do you know how to configure the pi to command 2 IR séparately ???
thanks for you help...

hi
thank you for this explanation
but i have a problem
when " backup the original lircd.conf"
pi@raspberrypi:~ $ sudo mv /etc/lirc/lircd.conf /etc/lirc/lircd_original.conf
mv: cannot stat '/etc/lirc/lircd.conf': No such file or directory
and my remote name is x.lircd.conf
can you help me please

@prasanthj

Can you go a step further and try to get lirc_web working as well? I am trying to get it working, but right now, it's not finding my remote.

I need to use it to send the IR commands to my A/C. lirc is working and I can use irsend SEND_ONCE to send a keypress, but lirc_web doesn't find my remote.

Any help is appreciated.

@unnamalai-kb
Does a button has a gap value, or a whole remote control has a gap value?
I had tested that every button had different gap value, so how can I write the /etc/lirc/lirc.conf ?

thank you for doing this - i appreciate it.

If anyone is having trouble with this guide as I have since it seems to be more suited to ver 0.9.0. I have found another guide that is intended to help you setup lirc's latest version(0.9.4c) with raspbian stretch. Here is the link https://github.com/mtraver/rpi-ir-remote. It worked for me hopefully it'll clarify some of your problems.

In case some run into same problems with new Stretch and LIRC 0.9.4c. This is how I have made work

Above LIRC setup was not working for me.
Im using Stretch and LICR 0.9.4.c

Some helpful tips I have found in first post
but on this https://raspberrypi.stackexchange.com/questions/81876/raspberry-pi-3-not-lirc-not-running-working
I found solution

I run setup as explained and it worked.
for example
instead of mode2 -d /dev/lirc0 for me worked sudo mode2 --driver default --device /dev/lirc0
after that II pointed remote and get pulse on the list.

RECORD
Also to record the buttons I have done as per bellow because irrecord didnt work for me with command
sudo irrecord -d /dev/lirc0 ~/lircd.conf
I got

Could not open new config file /home/user/lircd.conf
Could not init hardware (lircd running ? --> close it, check permissions)

in order to solve this I used sudo irrecord --driver default --device /dev/lirc0 ~/lircd.conf

so steps are

sudo /etc/init.d/lircd stop
sudo irrecord --driver default --device /dev/lirc0 ~/lircd.conf

follow steps
then
sudo /etc/init.d/lircd start

Check your remote with command
irw

here it should recognise your buttons and file name
and to send command
irsend SEND_ONCE KEY_POWER

In case some run into same problems with new Stretch and LIRC 0.9.4c. This is how I have made work

Above LIRC setup was not working for me.
Im using Stretch and LICR 0.9.4.c

Some helpful tips I have found in first post
but on this https://raspberrypi.stackexchange.com/questions/81876/raspberry-pi-3-not-lirc-not-running-working
I found solution

I run setup as explained and it worked.
for example
instead of mode2 -d /dev/lirc0 for me worked sudo mode2 --driver default --device /dev/lirc0
after that II pointed remote and get pulse on the list.

RECORD
Also to record the buttons I have done as per bellow because irrecord didnt work for me with command
sudo irrecord -d /dev/lirc0 ~/lircd.conf
I got

Could not open new config file /home/user/lircd.conf
Could not init hardware (lircd running ? --> close it, check permissions)

in order to solve this I used sudo irrecord --driver default --device /dev/lirc0 ~/lircd.conf

so steps are

sudo /etc/init.d/lircd stop
sudo irrecord --driver default --device /dev/lirc0 ~/lircd.conf

follow steps
then
sudo /etc/init.d/lircd start

Check your remote with command
irw

here it should recognise your buttons and file name
and to send command
irsend SEND_ONCE KEY_POWER

Thanks man! Setting this up drove me crazy.

Hello, i want to use lirc with a raspberry BUT not with the gpio.
I want to use an uart /dev/ttyACM1
Is this possible?

mine still no luck...
tail -f /var/log/messages | grep lirc
Feb 24 17:51:54 raspberrypi lircd-0.9.4c[1221]: Notice: Using systemd fd
Feb 24 17:51:54 raspberrypi lircd-0.9.4c[1221]: Warning: Running as root
Feb 24 17:51:54 raspberrypi lircd-0.9.4c[1221]: Warning: config file /etc/lirc/lircd.conf contains no valid remote control definition
Feb 24 17:51:54 raspberrypi lircd-0.9.4c[1221]: Notice: lircd(default) ready, using /var/run/lirc/lircd
Feb 24 17:51:54 raspberrypi lircd-0.9.4c[1221]: Notice: accepted new client on /var/run/lirc/lircd
Feb 24 17:51:54 raspberrypi lircd-0.9.4c[1221]: Info: Cannot configure the rc device for /dev/lirc0
Feb 24 17:52:59 raspberrypi lircd-0.9.4c[1221]: Info: removed client
Feb 24 17:53:17 raspberrypi lircd-0.9.4c[1221]: Notice: accepted new client on /var/run/lirc/lircd
Feb 24 17:53:17 raspberrypi lircd-0.9.4c[1221]: Info: Cannot configure the rc device for /dev/lirc0
Feb 24 17:53:27 raspberrypi lircd-0.9.4c[1221]: Info: removed client

Thanks! This was a super helpful reference.

Great! Worked at my old Pi A (Stretch) too.

Thank you for this nice reference!

I'm using a Raspberry PI 3 and set up everything as written above. I'm using a TSOP34836 IR receiver. When I start receiving data with "mode2 -d /dev/lirc0" I got a lot of data input:
pulse 405
space 362
pulse 10150
pulse 383
even if the IR receiver is completely covered or even if the receiver ist not connected at all. Seems that there is unspecific input.
I just tested and set ground at GPIO 18, then input is changing, there are now only pulses but no spaces anymore. So it seems that the correct GPIO is set.
Still tested another GPIO and same result.

Do you have any idea what could be wrong or what I cloud try? Do you need more information?

Thank you for your help and best!