[PLUGIN] IR Remote Controller feedback thread

[michel8166]

who has managed to get the infrared working with an allo isolator with the hifiberry digi + pro on top?

I have the 5 volts and the minus of the hifiberry plus the pin 4 for data (the value I changed in the lirc file to pin 4) but unfortunately I do not get it working that way.

I also get no response from the remote with the command {/etc/init.d/lirc stop} {mode2 -d /dev/lirc0}

or do I have to solder everything on the PCB of the raspberry pi? because you can not reach if the allo is on top.

thanks!

[ArturC]

Hello,
another one here that is almost giving up with this IR remote plugin for raspberry.
I’m a happy user of Volumio, I have a RPI2 with a IqAudio DAC Pro.
I have checked that the IR receiver is working, by checkin the output signal. Tried both GPIO18 with an Apple Remote but no results.
Connecting to GPIO18 makes some interference inthe sound when I press any remote button, aparently because this port is used by the DAC.
Which is the correct one after all? Is there any update for the plugin where we can select the input port?
Any help would be good.
Thanks.

[lev11]

Just wondering why the power button isn’t supported by default for the Justboom pre-configured setting in this plugin?

[gvolt]

Hello,

I am running version 2.362 on RPI3. After the installation of the IR remote controller plugin an update as of 14.11.2017 is shown. I tried to update but the old version (1.0.0) and the indicator that an update is available remains. I had a look on github and saw the last version is 1.2.0. To me it seems the ir.zip file the plugin manager downloads just has not been updated to this version.

It would be very nice if this could be solved as the new version not only brings more configurations for remote controls but also checks if a lirc-rpi overlay has already been loaded. This is very important for hardware which requires another gpio_in_pin than GPIO25 and has already loaded a dtoverlay.

E.g. the RemotePi board (https://volumio.org/forum/remotepi-board-for-t6600.html) has an IR receiver using GPIO18 or (after hardware modification) GPIO17. I am nearly done writing a plugin for the RemotePi which provides a switch on the configuration page to choose between GPIO18 and GPIO17. According to this setting a lirc-rpi dtoverlay entry gets added to the /boot/config.txt file. But this overlay gets overridden by the IR remote controller plugin version 1.0.0 by loading a dtoverlay with gpio_in_pin=25 without checking for a previously loaded overlay.

Thanks for this great piece of software. Keep up the good work!

[dyno]

@gvolt

I am running version 2.362 on RPI3. After the installation of the IR remote controller plugin an update as of 14.11.2017 is shown. I tried to update but the old version (1.0.0) and the indicator that an update is available remains. I had a look on github and saw the last version is 1.2.0. To me it seems the ir.zip file the plugin manager downloads just has not been updated to this version.

Same trouble… 2.378 RPI3 B

[michel8166]

@michel8166

who has managed to get the infrared working with an allo isolator with the hifiberry digi + pro on top?

I have the 5 volts and the minus of the hifiberry plus the pin 4 for data (the value I changed in the lirc file to pin 4) but unfortunately I do not get it working that way.

I also get no response from the remote with the command {/etc/init.d/lirc stop} {mode2 -d /dev/lirc0}

or do I have to solder everything on the PCB of the raspberry pi? because you can not reach if the allo is on top.

thanks!

someone has the solution to the problem with the allo isolator.

I have also tried the unisolated pin conectors at the bottom of the raspberry pi and at the top of the isolator and it still does not work.
So if someone here has the solution to this problem, I would appreciate it.

[Saiyato]

Hi all,

I’m not too familiar with lirc, so I might be interpreting stuff wrong.

I can’t seem to get the plugin to work on my Pi 3B running volumio 2.348. Since the Pi resides in the RaspDac case I amended the index.js and edited the gpio_in_pin to match my pin number (26).

Basically what I did:

1. Install the plugin
2. Amend the index.js
3. Copy over the A1156 configs from the repo
4. Saved the config
5. Rebooted (just in case)

Then I figured it wasn’t working at all, even mode2 didn’t do anything. So, I started questioning the battery, tested the remote (A1156), tested it on the Mac and it’s alive.

So, back to troubleshooting I went. This time I dug a bit deeper, I copied over the plugin from the repo and installed the latest version (1.2.0) instead.

1. Copy over plugin
2. Install plugin
3. Check the category (this had changed), and make sure everything adds up
4. Amend the index.js
5. Save the config (A1156)
6. Edit the lircrc file (UNIX EOL)
   Still nothing…

The logs showed the following:

Apr 12 08:50:22 volumiomain systemd[1]: Started LSB: Starts LIRC daemon.. Apr 12 08:50:22 volumiomain lirc[1842]: . Apr 12 08:50:22 volumiomain lirc[1842]: Starting execution daemon: irexec: failed!

I had no idea what irexec did, still only have a basic understanding, but it appears this maps a button code (not the signal code) to an action to be executed under irexec context.

Starting irexec was problematic due to the lircrc files having Windows EOL signs as opposed to UNIX. This was the first hurdle, I just cloned the volumio-plugins repo, so I think it’s already a problem there, or it was caused by someones merge. At any rate, this can be a problem for some people.

When I figured out the EOL problem the next problem arose, irexec couldn’t connect.

volumio@volumiomain:~$ sudo irexec /etc/lirc/lircrc irexec: could not connect to socket irexec: No such file or directory

Weird, so a little bit of searching gave me that irexec connects to lircd, which is the uniform interface between the pulses and other software. Shouldn’t be hard to run lircd right?

pstree from before the actions:

volumio@volumiomain:~$ pstree systemd-+-agetty |-avahi-daemon---avahi-daemon |-bash-+-avahi-publish-s | `-spotify-connect---spotify-connect---2*[{spotify-connect}] |-dbus-daemon |-dhcpcd |-dhcpd |-dnsmasq |-docker---10*[{docker}] |-dockerd-+-docker-containe-+-docker-containe-+-python---4*[{python}] | | | `-6*[{docker-containe}] | | `-12*[{docker-containe}] | `-129*[{dockerd}] |-haveged |-hotspot.sh---hostapd |-mpd-+-{decoder} | |-{io} | |-{output:alsa} | `-{player} |-netplugd |-nmbd---nmbd |-node-+-sh---node-+-2*[node-+-4*[{V8 WorkerThread}]] | | | `-{node}] | | |-4*[{V8 WorkerThread}] | | `-{node} | |-4*[{V8 WorkerThread}] | `-8*[{node}] |-ntpd |-polkitd-+-{gdbus} | `-{gmain} |-rpc.idmapd |-rpc.statd |-rpcbind |-shairport-sync---2*[{shairport-sync}] |-smbd---smbd |-sshd---sshd---sshd---bash---pstree |-systemd---(sd-pam) |-systemd-journal |-systemd-logind |-systemd-udevd |-udisks-daemon-+-udisks-daemon | `-{gdbus} |-udisks-glue |-upmpdcli---7*[{upmpdcli}] |-volumio-remote----2*[{volumio-remote-}] `-winbindd---3*[winbindd]

I was able to start mode2 to capture the pulses, so I can pretty much rule out hardware.

mode2 -d /dev/lirc0

I then started lircd, irexec and the lirc.service; but I still can’t control Volumio. Also I don’t know how to check whether everything is sent to the correct process (irexec?).

volumio@volumiomain:~$ sudo lircd volumio@volumiomain:~$ sudo irexec -d /etc/lirc/lircrc volumio@volumiomain:~$ sudo /etc/init.d/lirc start [ ok ] Starting lirc (via systemctl): lirc.service.

Now everything is running I guess… but still no working remote

volumio@volumiomain:~$ pstree systemd-+-agetty |-avahi-daemon---avahi-daemon |-bash-+-avahi-publish-s | `-spotify-connect---spotify-connect---2*[{spotify-connect}] |-dbus-daemon |-dhcpcd |-dhcpd |-dnsmasq |-docker---10*[{docker}] |-dockerd-+-docker-containe-+-docker-containe-+-python---4*[{python}] | | | `-6*[{docker-containe}] | | `-13*[{docker-containe}] | `-129*[{dockerd}] |-haveged |-hotspot.sh---hostapd |-irexec |-lircd |-mpd-+-{decoder} | |-{io} | |-{output:alsa} | `-{player} |-netplugd |-nmbd---nmbd |-node-+-sh---node-+-2*[node-+-4*[{V8 WorkerThread}]] | | | `-{node}] | | |-4*[{V8 WorkerThread}] | | `-{node} | |-4*[{V8 WorkerThread}] | `-8*[{node}] |-ntpd |-polkitd-+-{gdbus} | `-{gmain} |-rpc.idmapd |-rpc.statd |-rpcbind |-shairport-sync---2*[{shairport-sync}] |-smbd---smbd |-sshd-+-sshd---sshd---bash---pstree | `-2*[sshd---sshd---sftp-server] |-systemd---(sd-pam) |-systemd-journal |-systemd-logind |-systemd-udevd |-udisks-daemon-+-udisks-daemon | `-{gdbus} |-udisks-glue |-upmpdcli---7*[{upmpdcli}] |-volumio-remote----2*[{volumio-remote-}] `-winbindd---3*[winbindd]

I have no idea where to go next… is all software supported on the Pi 3B? Can someone help me out debug this issue.

[gvolt]

@Saiyato

Hi all,
…
I was able to start mode2 to capture the pulses, so I can pretty much rule out hardware.

mode2 -d /dev/lirc0

Ok, then you can check if the received pulses are mapped to key commands running

irw

Have a look at section “Examples” on http://www.lirc.org/html/irw.html how the ouput should look like. If you do not see a mapped key I guess the /etc/lirc/lircd.conf file is missing, damaged or not appropriate for your remote control.

Just in case: You can create your own lircd.conf running

irrecord -n -d /dev/lirc0  /path/<remote_name>.conf

If you should create your own lircd.conf you may copy it to /data/plugins/system_controller/ir_controller/configurations/<remote_name>/ so the IR Remote Controller plugin can install it to /etc/lirc/ when you choose the remote through the UI.

I then started lircd, irexec and the lirc.service; but I still can’t control Volumio. Also I don’t know how to check whether everything is sent to the correct process (irexec?).

volumio@volumiomain:~$ sudo lircd volumio@volumiomain:~$ sudo irexec -d /etc/lirc/lircrc volumio@volumiomain:~$ sudo /etc/init.d/lirc start [ ok ] Starting lirc (via systemctl): lirc.service.

To start lirc it should be sufficient to run

systemctl start lirc.service

But this should happen by enabling the IR Remote Controller plugin (which I assume you have still installed).

[Saiyato]

Good evening,

Thanks for the quick reply, I forgot to mention that irw gives me nothing, either normal or sudo run.
The same applies with my newly recorded lircd.conf, which is almost the same as the supplied template. Which I think means that the receiver works as intended, since the timings (?) are only a few off.

And yes I still have the plugin installed, I did change the EOL in the lircrc template file, because irexec failed after every reboot due to a parsing error.

So irrecord works, mode2 works, but irexec and/or irw seem to fail.

Forgot to mention that I’m using a TSOP38238 receiver, maybe that one is not fully supported?

[gvolt]

Sorry for asking the obvious: Has your lircd.conf been copied into /etc/lirc/?

Could you post the content of /etc/lirc/hardware.conf?

What does the log say when you execute irw and press some buttons on your remote?

Regarding the receiver: I have no experience of my own with this type but according to various web sites I would assume it should not be the issue.

[Saiyato]

@gvolt

Sorry for asking the obvious: Has your lircd.conf been copied into /etc/lirc/?

Could you post the content of /etc/lirc/hardware.conf?

You are absolutely correct to ask, I would’ve asked the same question.
I copied the new file over the existing one in /etc/lirc/ prior to rebooting.

The contents are:

# Please make this file available to others
# by sending it to <lirc@bartelmus.de>
#
# this config file was automatically generated
# using lirc-0.9.0-pre1(default) on Thu Apr 12 19:37:49 2018
#
# contributed by 
#
# brand:                       /home/volumio/test.conf
# model no. of remote control: 
# devices being controlled by this remote:
#

begin remote

  name  /home/volumio/test.conf
  bits            8
  flags SPACE_ENC|CONST_LENGTH
  eps            30
  aeps          100

  header       9191  4554
  one           619  1694
  zero          619   559
  ptrail        618
  repeat       9190  2247
  pre_data_bits   16
  pre_data       0x77E1
  post_data_bits  8
  post_data      0xC2
  gap          109814
  toggle_bit_mask 0x0

      begin codes
          PLAY                     0xA0
          UP                       0x50
          DOWN                     0x30
          LEFT                     0x90
          RIGHT                    0x60
          ENTER                    0xC0
      end codes

end remote

@gvolt

What does the log say when you execute irw and press some buttons on your remote?

Regarding the receiver: I have no experience of my own with this type but according to various web sites I would assume it should not be the issue.

irw does ‘nothing’ really:

volumio@volumiomain:~$ sudo irw ^Cvolumio@volumiomain:~$
I have pressed and held many times, but there’s no output whatsoever.

As for the support of the module, I couldn’t find any known issues with lirc as well.

[gvolt]

Thanks for clarifying

Could you post the content of your /etc/lirc/hardware.conf? We should especially check the entries for device, driver and modules.

As the console shows nothing when you run irw. Do have a log file we could have a look at? I don’t know if you will see anything but maybe watch

journalctl -f

while irw starts and you send RC commands.

According to http://www.lirc.org/html/irw.html instead of irw you could also use

ncat -U /usr/var/run/lirc/lircd

Does that show anything?

[Saiyato]

I will try the commands tonight, as I’m in the office right now, thanks for the quick reply, really appreciated!

The contents of /etc/lirc/hardware.conf is:

[code]# Arguments which will be used when launching lircd
LIRCD_ARGS="–uinput"

#Don’t start lircmd even if there seems to be a good config file
#START_LIRCMD=false

#Don’t start irexec, even if a good config file seems to exist.
#START_IREXEC=false

#Try to load appropriate kernel modules
LOAD_MODULES=true

Run “lircd --driver=help” for a list of supported drivers.

DRIVER=“default”

usually /dev/lirc0 is the correct setting for systems using udev

DEVICE="/dev/lirc0"
MODULES=“lirc_rpi”

Default configuration files for your hardware if any

LIRCD_CONF=""
LIRCMD_CONF=""[/code]

[Saiyato]

Just ran a journalctl -f when starting irw, prior to the test I confirmed the reception of pulses in mode2. I can’t see any weird log entries, but here it is (including the moment I SIGKILL’ed the irw).

Apr 13 15:14:29 volumiomain sudo[1968]: volumio : TTY=pts/1 ; PWD=/home/volumio ; USER=root ; COMMAND=/usr/bin/mode2 -d /dev/lirc0 Apr 13 15:14:29 volumiomain sudo[1968]: pam_unix(sudo:session): session opened for user root by volumio(uid=0) Apr 13 15:14:39 volumiomain sudo[1968]: pam_unix(sudo:session): session closed for user root Apr 13 15:14:46 volumiomain sudo[1995]: volumio : TTY=pts/1 ; PWD=/home/volumio ; USER=root ; COMMAND=/usr/bin/irw Apr 13 15:14:46 volumiomain sudo[1995]: pam_unix(sudo:session): session opened for user root by volumio(uid=0) Apr 13 15:14:46 volumiomain lircd-0.9.0-pre1[1782]: accepted new client on /var/run/lirc/lircd Apr 13 15:14:48 volumiomain volumio[1155]: info: CoreCommandRouter::volumioGetQueue Apr 13 15:14:48 volumiomain volumio[1155]: info: [1523632488054] CoreStateMachine::getQueue Apr 13 15:14:48 volumiomain volumio[1155]: info: [1523632488057] CorePlayQueue::getQueue Apr 13 15:14:48 volumiomain volumio[1155]: info: Apr 13 15:14:48 volumiomain volumio[1155]: [1523632488060] ---------------------------- Client requests Volumio queue Apr 13 15:14:48 volumiomain volumio[1155]: info: [1523632488065] InterfaceWebUI::pushQueue Apr 13 15:14:48 volumiomain volumio[1155]: info: [1523632488075] ------------------------------ 24ms Apr 13 15:14:48 volumiomain volumio[1155]: info: CoreCommandRouter::volumioGetState Apr 13 15:14:48 volumiomain volumio[1155]: info: [1523632488093] CoreStateMachine::getState Apr 13 15:14:48 volumiomain volumio[1155]: info: [1523632488094] CorePlayQueue::getTrack 0 Apr 13 15:14:48 volumiomain volumio[1155]: info: Apr 13 15:14:48 volumiomain volumio[1155]: [1523632488095] ---------------------------- Client requests Volumio state Apr 13 15:14:48 volumiomain volumio[1155]: info: [1523632488096] InterfaceWebUI::pushState Apr 13 15:14:48 volumiomain volumio[1155]: info: [1523632488127] ------------------------------ 48ms Apr 13 15:15:08 volumiomain volumio[1155]: info: CoreCommandRouter::volumioGetQueue Apr 13 15:15:08 volumiomain volumio[1155]: info: [1523632508346] CoreStateMachine::getQueue Apr 13 15:15:08 volumiomain volumio[1155]: info: [1523632508347] CorePlayQueue::getQueue Apr 13 15:15:08 volumiomain volumio[1155]: info: Apr 13 15:15:08 volumiomain volumio[1155]: [1523632508351] ---------------------------- Client requests Volumio queue Apr 13 15:15:08 volumiomain volumio[1155]: info: [1523632508353] InterfaceWebUI::pushQueue Apr 13 15:15:08 volumiomain volumio[1155]: info: [1523632508369] ------------------------------ 24ms Apr 13 15:15:08 volumiomain volumio[1155]: info: CoreCommandRouter::volumioGetState Apr 13 15:15:08 volumiomain volumio[1155]: info: [1523632508373] CoreStateMachine::getState Apr 13 15:15:08 volumiomain volumio[1155]: info: [1523632508374] CorePlayQueue::getTrack 0 Apr 13 15:15:08 volumiomain volumio[1155]: info: Apr 13 15:15:08 volumiomain volumio[1155]: [1523632508375] ---------------------------- Client requests Volumio state Apr 13 15:15:08 volumiomain volumio[1155]: info: [1523632508377] InterfaceWebUI::pushState Apr 13 15:15:08 volumiomain volumio[1155]: info: [1523632508421] ------------------------------ 49ms Apr 13 15:15:16 volumiomain lircd-0.9.0-pre1[1782]: removed client Apr 13 15:15:16 volumiomain sudo[1995]: pam_unix(sudo:session): session closed for user root

Unfortunately also the ncat gives me nothing, so I’m starting to think lircd is the culprit. I mean lircd is supposed to feed irw, irexec and ncat right?

Apr 13 15:26:33 volumiomain sudo[3067]: volumio : TTY=pts/1 ; PWD=/home/volumio ; USER=root ; COMMAND=/usr/bin/ncat -U /usr/var/run/lirc/lircd Apr 13 15:26:33 volumiomain sudo[3067]: pam_unix(sudo:session): session opened for user root by volumio(uid=0) Apr 13 15:26:38 volumiomain volumio[1155]: info: CoreCommandRouter::volumioGetQueue Apr 13 15:26:38 volumiomain volumio[1155]: info: [1523633198244] CoreStateMachine::getQueue Apr 13 15:26:38 volumiomain volumio[1155]: info: [1523633198245] CorePlayQueue::getQueue Apr 13 15:26:38 volumiomain volumio[1155]: info: Apr 13 15:26:38 volumiomain volumio[1155]: [1523633198246] ---------------------------- Client requests Volumio queue Apr 13 15:26:38 volumiomain volumio[1155]: info: [1523633198247] InterfaceWebUI::pushQueue Apr 13 15:26:38 volumiomain volumio[1155]: info: [1523633198255] ------------------------------ 12ms Apr 13 15:26:38 volumiomain volumio[1155]: info: CoreCommandRouter::volumioGetState Apr 13 15:26:38 volumiomain volumio[1155]: info: [1523633198258] CoreStateMachine::getState Apr 13 15:26:38 volumiomain volumio[1155]: info: [1523633198259] CorePlayQueue::getTrack 0 Apr 13 15:26:38 volumiomain volumio[1155]: info: Apr 13 15:26:38 volumiomain volumio[1155]: [1523633198259] ---------------------------- Client requests Volumio state Apr 13 15:26:38 volumiomain volumio[1155]: info: [1523633198260] InterfaceWebUI::pushState Apr 13 15:26:38 volumiomain volumio[1155]: info: [1523633198291] ------------------------------ 34ms Apr 13 15:26:53 volumiomain sudo[3067]: pam_unix(sudo:session): session closed for user root Apr 13 15:26:58 volumiomain volumio[1155]: info: CoreCommandRouter::volumioGetQueue Apr 13 15:26:58 volumiomain volumio[1155]: info: [1523633218521] CoreStateMachine::getQueue Apr 13 15:26:58 volumiomain volumio[1155]: info: [1523633218522] CorePlayQueue::getQueue Apr 13 15:26:58 volumiomain volumio[1155]: info: Apr 13 15:26:58 volumiomain volumio[1155]: [1523633218523] ---------------------------- Client requests Volumio queue Apr 13 15:26:58 volumiomain volumio[1155]: info: [1523633218524] InterfaceWebUI::pushQueue Apr 13 15:26:58 volumiomain volumio[1155]: info: [1523633218546] ------------------------------ 26ms Apr 13 15:26:58 volumiomain volumio[1155]: info: CoreCommandRouter::volumioGetState Apr 13 15:26:58 volumiomain volumio[1155]: info: [1523633218551] CoreStateMachine::getState Apr 13 15:26:58 volumiomain volumio[1155]: info: [1523633218552] CorePlayQueue::getTrack 0 Apr 13 15:26:58 volumiomain volumio[1155]: info: Apr 13 15:26:58 volumiomain volumio[1155]: [1523633218552] ---------------------------- Client requests Volumio state Apr 13 15:26:58 volumiomain volumio[1155]: info: [1523633218554] InterfaceWebUI::pushState Apr 13 15:26:58 volumiomain volumio[1155]: info: [1523633218583] ------------------------------ 34ms Apr 13 15:26:59 volumiomain sudo[3106]: volumio : TTY=pts/1 ; PWD=/home/volumio ; USER=root ; COMMAND=/usr/bin/mode2 -d /dev/lirc0 Apr 13 15:26:59 volumiomain sudo[3106]: pam_unix(sudo:session): session opened for user root by volumio(uid=0)

[gvolt]

Ok, nothing eye-catching for me

I am suspecting something wrong with either lircd or lircd.conf, too. Did you already check the permissions?

Could you additionally post the results of

systemctl status lirc

and

dmesg

please?

[Saiyato]

lirc itself doesn’t appear to be able to run, something’s off with the script I think.

Status:

[code]volumio@volumiomain:~$ systemctl status lirc
● lirc.service - LSB: Starts LIRC daemon.
Loaded: loaded (/etc/init.d/lirc)
Active: active (exited) since Fri 2018-04-13 15:10:27 UTC; 4h 27min ago
Process: 1577 ExecStart=/etc/init.d/lirc start (code=exited, status=0/SUCCESS)

Apr 13 15:10:27 volumiomain lirc[1577]: tira
Apr 13 15:10:27 volumiomain lirc[1577]: tira_raw
Apr 13 15:10:27 volumiomain lirc[1577]: udp
Apr 13 15:10:27 volumiomain lirc[1577]: uirt2
Apr 13 15:10:27 volumiomain lirc[1577]: uirt2_raw
Apr 13 15:10:27 volumiomain lirc[1577]: usb_uirt_raw
Apr 13 15:10:27 volumiomain lirc[1577]: usbx
Apr 13 15:10:27 volumiomain lirc[1577]: .
Apr 13 15:10:27 volumiomain lirc[1577]: Starting execution daemon: irexec: failed!
Apr 13 19:38:04 volumiomain systemd[1]: Started LSB: Starts LIRC daemon…
[/code]

dmesg doesn’t show any lirc errors:

volumio@volumiomain:~$ dmesg [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 4.9.65-v7+ (dc4@dc4-XPS13-9333) (gcc version 4.9.3 (crosstool-NG crosstool-ng-1.22.0-88-g8460611) ) #1056 SMP Fri Nov 24 13:58:07 GMT 2017 [ 0.000000] CPU: ARMv7 Processor [410fd034] revision 4 (ARMv7), cr=10c5383d [ 0.000000] CPU: div instructions available: patching division code [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache [ 0.000000] OF: fdt:Machine model: Raspberry Pi 3 Model B Rev 1.2 [ 0.000000] cma: Reserved 8 MiB at 0x3dc00000 [ 0.000000] Memory policy: Data cache writealloc [ 0.000000] On node 0 totalpages: 255488 [ 0.000000] free_area_init_node: node 0, pgdat 80c6f380, node_mem_map bd336000 [ 0.000000] Normal zone: 2246 pages used for memmap [ 0.000000] Normal zone: 0 pages reserved [ 0.000000] Normal zone: 255488 pages, LIFO batch:31 [ 0.000000] percpu: Embedded 14 pages/cpu @be5b0000 s25600 r8192 d23552 u57344 [ 0.000000] pcpu-alloc: s25600 r8192 d23552 u57344 alloc=14*4096 [ 0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 253242 [ 0.000000] Kernel command line: 8250.nr_uarts=0 bcm2708_fb.fbwidth=640 bcm2708_fb.fbheight=480 bcm2708_fb.fbdepth=16 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3f000000 vc_mem.mem_size=0x3f600000 splash quiet plymouth.ignore-serial-consoles dwc_otg.fiq_enable=1 dwc_otg.fiq_fsm_enable=1 dwc_otg.fiq_fsm_mask=0xF dwc_otg.nak_holdoff=1 console=ttyS0,115200 kgdboc=ttyS0,115200 console=tty1 imgpart=/dev/mmcblk0p2 imgfile=/volumio_current.sqsh elevator=noop rootwait bootdelay=5 logo.nologo vt.global_cursor_default=0 loglevel=0 [ 0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes) [ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) [ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) [ 0.000000] Memory: 977292K/1021952K available (7168K kernel code, 486K rwdata, 2012K rodata, 1024K init, 770K bss, 36468K reserved, 8192K cma-reserved) [ 0.000000] Virtual kernel memory layout: vector : 0xffff0000 - 0xffff1000 ( 4 kB) fixmap : 0xffc00000 - 0xfff00000 (3072 kB) vmalloc : 0xbe800000 - 0xff800000 (1040 MB) lowmem : 0x80000000 - 0xbe600000 ( 998 MB) modules : 0x7f000000 - 0x80000000 ( 16 MB) .text : 0x80008000 - 0x80800000 (8160 kB) .init : 0x80b00000 - 0x80c00000 (1024 kB) .data : 0x80c00000 - 0x80c79834 ( 487 kB) .bss : 0x80c7b000 - 0x80d3b964 ( 771 kB) [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 [ 0.000000] Hierarchical RCU implementation. [ 0.000000] Build-time adjustment of leaf fanout to 32. [ 0.000000] NR_IRQS:16 nr_irqs:16 16 [ 0.000000] arm_arch_timer: Architected cp15 timer(s) running at 19.20MHz (phys). [ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x46d987e47, max_idle_ns: 440795202767 ns [ 0.000007] sched_clock: 56 bits at 19MHz, resolution 52ns, wraps every 4398046511078ns [ 0.000019] Switching to timer-based delay loop, resolution 52ns [ 0.000297] Console: colour dummy device 80x30 [ 0.000312] console [tty1] enabled [ 0.000332] Calibrating delay loop (skipped), value calculated using timer frequency.. 38.40 BogoMIPS (lpj=192000) [ 0.000347] pid_max: default: 32768 minimum: 301 [ 0.000655] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes) [ 0.000665] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes) [ 0.001733] Disabling memory control group subsystem [ 0.001806] CPU: Testing write buffer coherency: ok [ 0.001843] ftrace: allocating 22397 entries in 66 pages [ 0.048969] CPU0: update cpu_capacity 1024 [ 0.048983] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000 [ 0.049019] Setting up static identity map for 0x100000 - 0x100034 [ 0.050891] CPU1: update cpu_capacity 1024 [ 0.050899] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001 [ 0.051588] CPU2: update cpu_capacity 1024 [ 0.051595] CPU2: thread -1, cpu 2, socket 0, mpidr 80000002 [ 0.052269] CPU3: update cpu_capacity 1024 [ 0.052275] CPU3: thread -1, cpu 3, socket 0, mpidr 80000003 [ 0.052365] Brought up 4 CPUs [ 0.052375] SMP: Total of 4 processors activated (153.60 BogoMIPS). [ 0.052380] CPU: All CPU(s) started in HYP mode. [ 0.052383] CPU: Virtualization extensions available. [ 0.053116] devtmpfs: initialized [ 0.064974] VFP support v0.3: implementor 41 architecture 3 part 40 variant 3 rev 4 [ 0.065254] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns [ 0.065270] futex hash table entries: 1024 (order: 4, 65536 bytes) [ 0.065806] pinctrl core: initialized pinctrl subsystem [ 0.066716] NET: Registered protocol family 16 [ 0.069209] DMA: preallocated 1024 KiB pool for atomic coherent allocations [ 0.078348] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers. [ 0.078354] hw-breakpoint: maximum watchpoint size is 8 bytes. [ 0.078499] Serial: AMBA PL011 UART driver [ 0.080564] bcm2835-mbox 3f00b880.mailbox: mailbox enabled [ 0.081100] uart-pl011 3f201000.serial: could not find pctldev for node /soc/gpio@7e200000/uart0_pins, deferring probe [ 0.149813] bcm2835-dma 3f007000.dma: DMA legacy API manager at be80f000, dmachans=0x1 [ 0.151665] SCSI subsystem initialized [ 0.151820] usbcore: registered new interface driver usbfs [ 0.151903] usbcore: registered new interface driver hub [ 0.151995] usbcore: registered new device driver usb [ 0.158770] raspberrypi-firmware soc:firmware: Attached to firmware from 2017-11-17 15:20 [ 0.160423] clocksource: Switched to clocksource arch_sys_counter [ 0.207450] VFS: Disk quotas dquot_6.6.0 [ 0.207527] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) [ 0.207736] FS-Cache: Loaded [ 0.207985] CacheFiles: Loaded [ 0.220235] NET: Registered protocol family 2 [ 0.221145] TCP established hash table entries: 8192 (order: 3, 32768 bytes) [ 0.221253] TCP bind hash table entries: 8192 (order: 4, 65536 bytes) [ 0.221438] TCP: Hash tables configured (established 8192 bind 8192) [ 0.221525] UDP hash table entries: 512 (order: 2, 16384 bytes) [ 0.221567] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes) [ 0.221773] NET: Registered protocol family 1 [ 0.222179] RPC: Registered named UNIX socket transport module. [ 0.222185] RPC: Registered udp transport module. [ 0.222189] RPC: Registered tcp transport module. [ 0.222194] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 0.222438] Trying to unpack rootfs image as initramfs... [ 1.390112] Freeing initrd memory: 13804K [ 1.396581] hw perfevents: enabled with armv7_cortex_a7 PMU driver, 7 counters available [ 1.398954] workingset: timestamp_bits=14 max_order=18 bucket_order=4 [ 1.415060] FS-Cache: Netfs 'nfs' registered for caching [ 1.416046] NFS: Registering the id_resolver key type [ 1.416073] Key type id_resolver registered [ 1.416078] Key type id_legacy registered [ 1.418410] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251) [ 1.418529] io scheduler noop registered (default) [ 1.418535] io scheduler deadline registered [ 1.418797] io scheduler cfq registered [ 1.424676] BCM2708FB: allocated DMA memory fdd10000 [ 1.424700] BCM2708FB: allocated DMA channel 0 @ be80f000 [ 1.430292] Console: switching to colour frame buffer device 80x30 [ 1.435165] bcm2835-rng 3f104000.rng: hwrng registered [ 1.435289] vc-mem: phys_addr:0x00000000 mem_base=0x3f000000 mem_size:0x3f600000(1014 MiB) [ 1.435805] vc-sm: Videocore shared memory driver [ 1.450791] brd: module loaded [ 1.459567] loop: module loaded [ 1.459579] Loading iSCSI transport class v2.0-870. [ 1.460123] usbcore: registered new interface driver smsc95xx [ 1.460138] dwc_otg: version 3.00a 10-AUG-2012 (platform bus) [ 1.688185] Core Release: 2.80a [ 1.688193] Setting default values for core params [ 1.688222] Finished setting default values for core params [ 1.888611] Using Buffer DMA mode [ 1.888617] Periodic Transfer Interrupt Enhancement - disabled [ 1.888621] Multiprocessor Interrupt Enhancement - disabled [ 1.888627] OTG VER PARAM: 0, OTG VER FLAG: 0 [ 1.888641] Dedicated Tx FIFOs mode [ 1.888996] WARN::dwc_otg_hcd_init:1032: FIQ DMA bounce buffers: virt = 0xbdd04000 dma = 0xfdd04000 len=9024 [ 1.889019] FIQ FSM acceleration enabled for : Non-periodic Split Transactions Periodic Split Transactions High-Speed Isochronous Endpoints Interrupt/Control Split Transaction hack enabled [ 1.889026] dwc_otg: Microframe scheduler enabled [ 1.889073] WARN::hcd_init_fiq:459: FIQ on core 1 at 0x805909a0 [ 1.889082] WARN::hcd_init_fiq:460: FIQ ASM at 0x80590d10 length 36 [ 1.889093] WARN::hcd_init_fiq:486: MPHI regs_base at 0xbe87a000 [ 1.889150] dwc_otg 3f980000.usb: DWC OTG Controller [ 1.889184] dwc_otg 3f980000.usb: new USB bus registered, assigned bus number 1 [ 1.889214] dwc_otg 3f980000.usb: irq 62, io mem 0x00000000 [ 1.889260] Init: Port Power? op_state=1 [ 1.889264] Init: Power Port (0) [ 1.889465] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 [ 1.889475] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 1.889483] usb usb1: Product: DWC OTG Controller [ 1.889491] usb usb1: Manufacturer: Linux 4.9.65-v7+ dwc_otg_hcd [ 1.889498] usb usb1: SerialNumber: 3f980000.usb [ 1.890318] hub 1-0:1.0: USB hub found [ 1.890357] hub 1-0:1.0: 1 port detected [ 1.891055] dwc_otg: FIQ enabled [ 1.891059] dwc_otg: NAK holdoff enabled [ 1.891063] dwc_otg: FIQ split-transaction FSM enabled [ 1.891076] Module dwc_common_port init [ 1.891304] usbcore: registered new interface driver usb-storage [ 1.891532] mousedev: PS/2 mouse device common for all mice [ 1.892488] bcm2835-wdt 3f100000.watchdog: Broadcom BCM2835 watchdog timer [ 1.892768] bcm2835-cpufreq: min=600000 max=1200000 [ 1.893164] sdhci: Secure Digital Host Controller Interface driver [ 1.893168] sdhci: Copyright(c) Pierre Ossman [ 1.893442] sdhost-bcm2835 3f202000.sdhost: could not get clk, deferring probe [ 1.895621] mmc-bcm2835 3f300000.mmc: could not get clk, deferring probe [ 1.895724] sdhci-pltfm: SDHCI platform and OF driver helper [ 1.898340] ledtrig-cpu: registered to indicate activity on CPUs [ 1.898528] hidraw: raw HID events driver (C) Jiri Kosina [ 1.898718] usbcore: registered new interface driver usbhid [ 1.898722] usbhid: USB HID core driver [ 1.899489] vchiq: vchiq_init_state: slot_zero = 0xbdd80000, is_master = 0 [ 1.901116] [vc_sm_connected_init]: start [ 1.904498] vc_vchi_sm_init: failed to open VCHI service (-1) [ 1.904505] [vc_sm_connected_init]: failed to initialize shared memory service [ 1.904513] [vc_sm_connected_init]: end - returning -1 [ 1.904871] Initializing XFRM netlink socket [ 1.904892] NET: Registered protocol family 17 [ 1.905004] Key type dns_resolver registered [ 1.905651] Registering SWP/SWPB emulation handler [ 1.906347] registered taskstats version 1 [ 1.912529] uart-pl011 3f201000.serial: cts_event_workaround enabled [ 1.912588] 3f201000.serial: ttyAMA0 at MMIO 0x3f201000 (irq = 87, base_baud = 0) is a PL011 rev2 [ 1.914135] sdhost: log_buf @ bdd07000 (fdd07000) [ 1.990455] mmc0: sdhost-bcm2835 loaded - DMA enabled (>1) [ 1.992660] mmc-bcm2835 3f300000.mmc: mmc_debug:0 mmc_debug2:0 [ 1.992668] mmc-bcm2835 3f300000.mmc: DMA channel allocated [ 2.057540] mmc0: host does not support reading read-only switch, assuming write-enable [ 2.059486] mmc0: new high speed SDHC card at address b368 [ 2.060141] mmcblk0: mmc0:b368 7.46 GiB [ 2.061669] mmcblk0: p1 p2 p3 [ 2.070560] of_cfs_init [ 2.070641] of_cfs_init: OK [ 2.074559] Freeing unused kernel memory: 1024K [ 2.088298] mmc1: queuing unknown CIS tuple 0x80 (2 bytes) [ 2.089937] mmc1: queuing unknown CIS tuple 0x80 (3 bytes) [ 2.091599] mmc1: queuing unknown CIS tuple 0x80 (3 bytes) [ 2.094462] mmc1: queuing unknown CIS tuple 0x80 (7 bytes) [ 2.120579] Indeed it is in host mode hprt0 = 00021501 [ 2.187374] random: fast init done [ 2.222723] initramfs: Booting Volumio for for BCM2835 [ 2.222892] initramfs: This script mounts rootfs RO with an overlay RW layer. [ 2.239624] squashfs: version 4.0 (2009/01/31) Phillip Lougher [ 2.245333] initramfs: IMGPART=/dev/mmcblk0p2 [ 2.245473] initramfs: IMGFILE=/volumio_current.sqsh [ 2.245681] initramfs: Boot delay (except first time) will be 5 seconds [ 2.246983] mmc1: new high speed SDIO card at address 0001 [ 2.299534] initramfs: /dev/mmcblk0p2: [ 2.320468] usb 1-1: new high-speed USB device number 2 using dwc_otg [ 2.320603] Indeed it is in host mode hprt0 = 00001101 [ 2.550705] usb 1-1: New USB device found, idVendor=0424, idProduct=9514 [ 2.550715] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 2.551525] hub 1-1:1.0: USB hub found [ 2.551615] hub 1-1:1.0: 5 ports detected [ 2.870454] usb 1-1.1: new high-speed USB device number 3 using dwc_otg [ 3.000693] usb 1-1.1: New USB device found, idVendor=0424, idProduct=ec00 [ 3.000704] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 3.003452] smsc95xx v1.0.5 [ 3.094150] smsc95xx 1-1.1:1.0 eth0: register 'smsc95xx' at usb-3f980000.usb-1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:20:27:4b [ 3.816316] EXT4-fs (mmcblk0p2): recovery complete [ 3.819854] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null) [ 3.821948] initramfs: Doing a 5 second delay here to give kernel load a headstart [ 8.825720] initramfs: Checking for USB updates [ 8.915907] initramfs: No USB device detected (when incorrect, try adding 'bootdelay=5' to your boot cmdline) [ 10.564052] EXT4-fs (mmcblk0p3): recovery complete [ 10.565972] EXT4-fs (mmcblk0p3): mounted filesystem with ordered data mode. Opts: (null) [ 10.576181] initramfs: With Option: [ 10.702970] initramfs: VOLUMIO_VERSION="2.348" [ 10.703127] initramfs: Finish initramfs, continue booting Volumio [ 11.128094] systemd[1]: systemd 215 running in system mode. (+PAM +AUDIT +SELINUX +IMA +SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ -SECCOMP -APPARMOR) [ 11.128413] systemd[1]: Detected architecture 'arm'. [ 11.265621] NET: Registered protocol family 10 [ 11.267158] systemd[1]: Inserted module 'ipv6' [ 11.270690] systemd[1]: Set hostname to <volumiomain>. [ 11.529994] systemd[1]: [/lib/systemd/system/docker.service:25] Unknown lvalue 'Delegate' in section 'Service' [ 11.531462] systemd[1]: [/lib/systemd/system/mpd.service:18] Unknown lvalue 'ProtectKernelTunables' in section 'Service' [ 11.531523] systemd[1]: [/lib/systemd/system/mpd.service:19] Unknown lvalue 'ProtectControlGroups' in section 'Service' [ 11.531581] systemd[1]: [/lib/systemd/system/mpd.service:20] Unknown lvalue 'ProtectKernelModules' in section 'Service' [ 11.531653] systemd[1]: [/lib/systemd/system/mpd.service:23] Unknown lvalue 'RestrictNamespaces' in section 'Service' [ 11.597484] systemd[1]: Cannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service failed to load: No such file or directory. [ 11.940836] systemd-udevd[198]: starting version 215 [ 11.941791] fuse init (API version 7.26) [ 12.020906] i2c /dev entries driver [ 12.423933] gpiomem-bcm2835 3f200000.gpiomem: Initialised: Registers at 0x3f200000 [ 12.729194] snd_bcm2835: unknown parameter 'index' ignored [ 12.787757] snd-hifiberry-dac soc:sound: ASoC: CPU DAI (null) not registered - will retry [ 12.793350] snd-hifiberry-dac soc:sound: pcm5102a-hifi <-> 3f203000.i2s mapping ok [ 13.239346] brcmfmac: F1 signature read @0x18000000=0x1541a9a6 [ 13.245729] usbcore: registered new interface driver brcmfmac [ 13.564108] brcmfmac: Firmware version = wl0: Aug 7 2017 00:46:29 version 7.45.41.46 (r666254 CY) FWID 01-f8a78378 [ 13.571000] brcmfmac: brcmf_c_preinit_dcmds: CLM version = API: 12.2 Data: 7.11.15 Compiler: 1.24.2 ClmImport: 1.24.1 Creation: 2014-05-26 10:53:55 Inc Data: 9.10.41 Inc Compiler: 1.29.4 Inc ClmImport: 1.36.3 Creation: 2017-08-07 00:37:47 [ 13.631036] systemd-journald[189]: Received request to flush runtime journal from PID 1 [ 15.061455] brcmfmac: power management disabled [ 15.462574] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup [ 15.514767] brcmfmac: power management disabled [ 17.065915] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1 [ 20.061765] Installing knfsd (copyright (C) 1996 okir@monad.swb.de). [ 20.709198] ip_tables: (C) 2000-2006 Netfilter Core Team [ 21.002982] nf_conntrack version 0.5.0 (16384 buckets, 65536 max) [ 23.009167] random: crng init done [ 27.587852] device-mapper: ioctl: 4.35.0-ioctl (2016-06-23) initialised: dm-devel@redhat.com [ 34.167628] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this. [ 34.217005] Bridge firewalling registered [ 35.011434] Netfilter messages via NETLINK v0.30. [ 35.027087] ctnetlink v0.93: registering with nfnetlink. [ 42.240594] brcmfmac: brcmf_cfg80211_stop_ap: SET SSID error (-110) [ 42.240606] brcmfmac: brcmf_cfg80211_stop_ap: BRCMF_C_DOWN error -110 [ 42.240616] brcmfmac: brcmf_cfg80211_stop_ap: setting INFRA mode failed -110 [ 42.240625] brcmfmac: brcmf_cfg80211_stop_ap: setting AP mode failed -110 [ 42.240638] brcmfmac: brcmf_cfg80211_stop_ap: BRCMF_C_UP error -110 [ 42.240648] brcmfmac: brcmf_set_mpc: fail to set mpc [ 42.864206] brcmfmac: brcmf_cfg80211_stop_ap: setting INFRA mode failed -7 [ 49.326776] EXT4-fs (dm-1): mounted filesystem with ordered data mode. Opts: (null) [ 51.930855] EXT4-fs (dm-1): mounted filesystem with ordered data mode. Opts: (null) [ 52.475442] EXT4-fs (dm-1): mounted filesystem with ordered data mode. Opts: (null) [ 65.467923] FS-Cache: Netfs 'cifs' registered for caching [ 65.468823] Key type cifs.spnego registered [ 65.468846] Key type cifs.idmap registered [ 84.016279] lirc_dev: IR Remote Control driver registered, major 244 [ 84.023847] lirc_rpi: module is from the staging directory, the quality is unknown, you have been warned. [ 85.080860] lirc_rpi: auto-detected active low receiver on GPIO pin 26 [ 85.081156] lirc_rpi lirc_rpi: lirc_dev: driver lirc_rpi registered at minor = 0 [ 85.081161] lirc_rpi: driver registered! [ 86.996260] input: lircd as /devices/virtual/input/input0 [ 3086.258738] EXT4-fs (dm-1): mounted filesystem with ordered data mode. Opts: (null) [ 3086.961784] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null) [ 3107.989264] EXT4-fs (dm-1): mounted filesystem with ordered data mode. Opts: (null) [ 3122.345784] EXT4-fs (dm-1): mounted filesystem with ordered data mode. Opts: (null) [ 3123.083781] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null) [ 3139.832060] EXT4-fs (dm-1): mounted filesystem with ordered data mode. Opts: (null) [ 3155.124145] EXT4-fs (dm-1): mounted filesystem with ordered data mode. Opts: (null) [ 3155.858662] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null) [ 3171.986550] EXT4-fs (dm-1): mounted filesystem with ordered data mode. Opts: (null) [ 3187.789290] EXT4-fs (dm-1): mounted filesystem with ordered data mode. Opts: (null) [ 3189.040762] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null) [ 3210.073639] EXT4-fs (dm-1): mounted filesystem with ordered data mode. Opts: (null)

See LIRC from 84.

the rights of the config files are (they all have UNIX EOL now):

volumio@volumiomain:~$ ls -al /etc/lirc/ total 24 drwxr-xr-x 2 volumio volumio 4096 Apr 12 19:39 . drwxr-xr-x 1 volumio volumio 4096 Apr 13 15:23 .. -rwxrwxrwx 1 volumio volumio 593 Apr 13 15:10 hardware.conf -rwxrwxrwx 1 root root 1019 Apr 13 15:10 lircd.conf -rwxrwxrwx 1 volumio volumio 121 Jan 26 2015 lircmd.conf -rwxrwxrwx 1 volumio volumio 492 Apr 13 15:10 lircrc

I will try to edit the script tomorrow, I mean /etc/init.d/lirc
Because the irexec part gives me:

volumio@volumiomain:~$ irexec -- -d /etc/lirc/lircrc < /dev/null irexec 0.9.0-pre1: too many arguments

[gvolt]

Just for comparison systemctl status lirc shows here (with version 1.2.0 of the IR Remote Controller plugin installed)

[code]systemctl status lirc -l
● lirc.service - LSB: Starts LIRC daemon.
Loaded: loaded (/etc/init.d/lirc)
Active: active (running) since Fri 2018-04-13 20:42:15 CEST; 1h 7min ago
Process: 1281 ExecStart=/etc/init.d/lirc start (code=exited, status=0/SUCCESS)
CGroup: /system.slice/lirc.service
├─1295 /usr/sbin/lircd --driver=default --device=/dev/lirc0 --uinput
└─1298 /usr/bin/irexec -d /etc/lirc/lircrc

Apr 13 20:42:15 volumio lirc[1281]: Loading LIRC modules:.
Apr 13 20:42:15 volumio lircd-0.9.0-pre1[1295]: lircd(default) ready, using /var/run/lirc/lircd
Apr 13 20:42:15 volumio lirc[1281]: Starting remote control daemon(s) : LIRC :.
Apr 13 20:42:15 volumio lircd-0.9.0-pre1[1295]: accepted new client on /var/run/lirc/lircd
Apr 13 20:42:15 volumio lirc[1281]: Starting execution daemon: irexec:.
Apr 13 20:42:15 volumio systemd[1]: Started LSB: Starts LIRC daemon…
Apr 13 20:46:50 volumio lircd-0.9.0-pre1[1295]: accepted new client on /var/run/lirc/lircd
Apr 13 20:48:30 volumio lircd-0.9.0-pre1[1295]: removed client
Apr 13 20:48:34 volumio lircd-0.9.0-pre1[1295]: accepted new client on /var/run/lirc/lircd
Apr 13 20:48:45 volumio lircd-0.9.0-pre1[1295]: removed client
[/code]
Regarding the permissions:

ls -al /etc/lirc/ total 24 drwxr-xr-x 2 root root 4096 Mar 22 22:24 . drwxr-xr-x 1 volumio volumio 4096 Apr 1 21:53 .. -rwxrwxrwx 1 root root 573 Apr 13 20:42 hardware.conf -rwxrwxrwx 1 root root 3049 Apr 13 20:42 lircd.conf -rwxrwxrwx 1 root root 121 Jan 26 2015 lircmd.conf -rwxrwxrwx 1 root root 3159 Apr 13 20:42 lircrc
Before putting too much time into editing the script file I would consider to uninstall the plugin and make sure all files from lirc are actually removed before starting over.

[Saiyato]

Removing all files and the plugin didn’t seem to help. I have another Pi, however a 2, not a 3, lying around; so I will try the plugin with a fresh image. I am a bit reluctant to re-image my main music Pi, so all in good time.

To be continued.

[gvolt]

Bummer! I also have a Pi 3 and lirc, installed through the IR Controller plugin, worked out of the box. So it’s good you have a second Pi to test with a fresh image. Good luck!

[Jonesy_sa]

Hi
I have a Pi1 B with Dac connected via the P5 header:
what-the-correct-connection-for-es9023-dac-t8765.html
I would like to buy a cheap IR receiver of eBay to try with my apple remote. I believe the P5 is already using Pin 18 from the GPIO. How would I wire it up with my set-up? I searched online but everyone is using pin 18. Can I still use 22 with my older DAC and where should the other two go?
Thank you