How to configure Atric IR-WakeupUSB with RPi4

JurKub · August 16, 2021 at 2:46 PM

Hi all,

I need some help how to configure Atric IR-WakeupUSB with LibreELEC-RPi4.arm-9.97.1

Thx

JurKub · August 17, 2021 at 10:16 AM

I made a bit progress but it's not working at all.

I put atric.rules to Configfiles\udev.rules.d

and hardware.conf & lircd.conf to Configfiles

when I do a

killall -9 eventlircd

killall -9 lircd

lircd --output /run/lirc/lircd --device=/dev/ttyatric --driver=irman /etc/lirc/lircd.conf

irw tells

ffff560400000000 00 KEY_RIGHT URC-8040

ffff550400000000 00 KEY_LEFT URC-8040

but nothing happens inside Kodi

**mglae** · August 17, 2021 at 4:01 PM

atric.rules.txt and lircd.conf.txt are using DOS line endings and do likely not work in LE.

JurKub · August 17, 2021 at 8:05 PM

on the Raspi the files are in the right format !

JurKub · August 18, 2021 at 7:06 AM

got it working using this 3 files

but the autostart.sh feels like a dirty hack

any suggestions how to make it better ?

**Klojum** · August 18, 2021 at 7:09 AM Official Post

Quote from JurKub

but the autostart.sh feels like a dirty hack

"If it looks stupid but it works, then it ain't stupid..."

**chewitt** · August 18, 2021 at 12:51 PM Official Post

If autostart.sh feels like a hack you can always convert things to a systemd service

**mglae** · August 18, 2021 at 4:11 PM

Code

killall -9 eventlircd
killall -9 lircd

killall is not working as expected, systemd will restart the services. Use systemd stop eventlircd;systemd stop lircd if really needed.

Did you read https://wiki.libreelec.tv/configuration/ir-remotes? Although it is outdated in the point that lircd today is only enabled by the existence of lircd.conf.

As usual providing logs via pastekodi may produce more feedback.

JurKub · August 19, 2021 at 8:12 AM

did some changes to autostart.sh in the meantime and added lirc_options.conf

yes I've read it but did not understood this part:

https://wiki.libreelec.tv/configuration/…es#lirc-support

Log:

**mglae** · August 19, 2021 at 10:29 PM

Is the autostart still needed? There is no real difference to the service.

Quote from JurKub

es I've read it but did not understood this part:

As said, the wiki is outdated. lircd is started by the existence of /storage.config/lircd.conf. The remaining

looks OK although I've never used lircd.

The log shows issues in the lircd.conf:

Code

Aug 19 08:25:27.807773 LibreELEC lircd-0.10.1[885]: Notice: /storage/.config/lircd.conf: devinput: Multiple definitions of: KEY_PAUSE
Aug 19 08:25:27.807894 LibreELEC lircd-0.10.1[885]: Notice: /storage/.config/lircd.conf: devinput: Multiple values for same code: KEY_PAUSE
Aug 19 08:25:27.808011 LibreELEC lircd-0.10.1[885]: Notice: /storage/.config/lircd.conf: devinput: Multiple values for same code: KEY_RECORD
[...]

and remote.xml:

Code

2021-08-19 08:25:32.546 T:925      INFO <general>: Loading special://masterprofile/keymaps/remote.xml
2021-08-19 08:25:32.549 T:925     ERROR <general>: Keymapping error: no such action 'xbmc.quit()' defined
2021-08-19 08:25:32.549 T:925     ERROR <general>: Keymapping error: no such action 'xbmc.activatewindow(myvideos)' defined
2021-08-19 08:25:32.549 T:925     ERROR <general>: Keymapping error: no such action 'xbmc.activatewindow(mymusic)' defined
[...]

JurKub · August 23, 2021 at 10:15 AM

Is the autostart still needed? There is no real difference

normal startup:

/usr/lib/libreelec/lircd_helper --nodaemon

which is not working

my version:

/usr/lib/libreelec/lircd_helper

which is working

lircd.conf and remote.xml updated

errors in kodi.log are gone now

**mglae** · August 23, 2021 at 3:56 PM

systemctl restart lircd should do the same in autostart.

As a wild guess that is needed because you did change the lircd output socket. May be related to:

Quote from JurKub

yes I've read it but did not understood this part:
https://wiki.libreelec.tv/configuration/…es#lirc-support

JurKub · August 24, 2021 at 12:20 PM

Quote from mglae

As a wild guess that is needed because you did change the lircd output socket. May be related to:

You are absolutely right changing lirc_options.conf solved the issue

autostart.sh is not needed anymore

and name set to devinput inside lircd.conf no longer needed

Thx a lot for your help

JurKub · November 18, 2024 at 9:52 AM New

Hi all,

need to come back to this old thread because of issue when upgrading from LibreELEC 10.0.4 to 12.0.1.

The driver tries to creates lock files in /var/lock/lockdev which is not existing.

In LibreELEC 10.0.4 the drives uses /var/lock

Workaround is to create it using autostart.sh.

Any ideas how to fix it without workaround using autostart.sh ?

Thx
JurKur

**chewitt** · November 18, 2024 at 2:34 PM New

If you're already using the autostart.sh file, you might as well add the workaround there too, no?

JurKub · November 18, 2024 at 2:36 PM New

Quote from chewitt

If you're already using the autostart.sh file, you might as well add the workaround there too, no?

I'm only using it to create the missing folder

lwing · November 19, 2024 at 1:10 AM New

Quote from JurKub

Hi all,
need to come back to this old thread because of issue when upgrading from LibreELEC 10.0.4 to 12.0.1.
The driver tries to creates lock files in /var/lock/lockdev which is not existing.
In LibreELEC 10.0.4 the drives uses /var/lock
Workaround is to create it using autostart.sh.
Any ideas how to fix it without workaround using autostart.sh ?

Thx
JurKur

Display More

Hi JurKur,

first, i don't have a better solution for the problem, except maybe creating a service instead of using autostart.sh. I think it is an issue for the devs of the irman driver.

I did an update myself to LE 12 just yesterday and had the same issue with my Atric device. Thank you very much for the solution, it saved me a lot of time!! How did you find out, that the lock file is missing, are there any logs for lirc in libreelec?

thx lwing

JurKub · November 19, 2024 at 6:00 AM New

Quote from lwing

How did you find out, that the lock file is missing, are there any logs for lirc in libreelec?

Hi lwing

good to hear my investigations helped to get your system working.

I opened a PuTTY session:

Code

killall -9 eventlircd
killall -9 lircd
/usr/sbin/lircd -O /storage/.config/lirc_options.conf --nodaemon /storage/.config/lircd.conf

In another PuTTY session I'ved started:

Code

/usr/sbin/lircd-uinput -O /storage/.config/lirc_options.conf --add-release-events

After that I got an error message about the lock file in the first PuTTY session.

Cheers
JurKub