Remotes
Version 11 (brfransen, 04/20/2017 02:47 pm) → Version 12/13 (brfransen, 04/20/2017 02:47 pm)
{{toc}}
h1. Remotes
h2. [[Architecture_and_Customization|Architecture and Tools]]
h2. Setup
h3. Automatic
"Service Menu" --> "LinHES Configuration" --> "Remotes" then select your remote and press "Next" and "Finish".
If your remote is not listed in the menus you will have to set it up manually.
h3. Manual
h4. R7.3 & Later Releases
Beginning in R7.3 the "runit":http://smarden.org/runit/ lircd service has been replaced with the remotes service ([[Architecture_and_Customization#etcsvremotesrun|/etc/sv/remotes]]). (/etc/sv/remotes). With [[Architecture_and_Customization#In-Kernel-Remote-Driver|in kernel remote drivers]] "LIRC":http://www.lirc.org/ is no longer the only way for LinHES to work with remotes. The remotes service allows for remotes to be started using in kernel remote drivers, LIRC, or any other commands that may be needed.
h4. R7.2 & Earlier Releases
In LinHES R7.2 & earlier "LIRC":http://www.lirc.org/ is started by "runit":http://smarden.org/runit/. LinHES does not have a hardware.conf file for LIRC but instead uses the runit script at [[Architecture_and_Customization#etcsvlircdrun|/etc/sv/lircd/run]] /etc/sv/lircd/run to configure and start LIRC. If your remote is not starting you can put the commands to start your remote in [[Architecture_and_Customization#etcrunitlircsh|/etc/runit/lirc.sh]] /etc/runit/lirc.sh and the runit script at /etc/sv/lircd/run will be ignored. Make sure to use the "lircd -n switch":http://www.lirc.org/html/lircd.html to keep lircd in the foreground as runit requires the processes it manages be in the foreground.
h2. Tips
h3. Custom Remote Templates
If your remote is included with LinHES and you have modified either the /etc/lircd.conf or /etc/lircrc files your changes will be overwritten the next time the LIRC templates are updated or a different remote is selected from the Service Services Menu. The easiest way to avoid losing your modifications is to make your own custom remote template in ~/remotes/YourRemoteName/ and copy in the custom lircrc, lircd.conf, remote lircd.conf and picture and remote.run files. file of the remote. Your remote will be available as an option in "Service Menu" --> "LinHES Configuration" --> "Remotes". and it will not be overwritten by any updates. If your remote has the same name as a remote in /usr/MythVantage/templates/remotes/ both will show in the UI. However, when either UI item is selected only the files in ~/remotes/ will used.
See also: [[Architecture_and_Customization#remotes|remotes]].
h3. Miscellaneous
If your remote is not included with LinHES please open a "ticket":http://linhes.org/bugs/projects/linhes/issues/new and attach the files you created to make it work so that it can be included in a future version of LinHES.
A very detailed guide filled with lots of information to help you debug your remote under LIRC >= 0.9.0 is posted "here.":http://forum.xbmc.org/showthread.php?t=104541
h1. Remotes
h2. [[Architecture_and_Customization|Architecture and Tools]]
h2. Setup
h3. Automatic
"Service Menu" --> "LinHES Configuration" --> "Remotes" then select your remote and press "Next" and "Finish".
If your remote is not listed in the menus you will have to set it up manually.
h3. Manual
h4. R7.3 & Later Releases
Beginning in R7.3 the "runit":http://smarden.org/runit/ lircd service has been replaced with the remotes service ([[Architecture_and_Customization#etcsvremotesrun|/etc/sv/remotes]]). (/etc/sv/remotes). With [[Architecture_and_Customization#In-Kernel-Remote-Driver|in kernel remote drivers]] "LIRC":http://www.lirc.org/ is no longer the only way for LinHES to work with remotes. The remotes service allows for remotes to be started using in kernel remote drivers, LIRC, or any other commands that may be needed.
h4. R7.2 & Earlier Releases
In LinHES R7.2 & earlier "LIRC":http://www.lirc.org/ is started by "runit":http://smarden.org/runit/. LinHES does not have a hardware.conf file for LIRC but instead uses the runit script at [[Architecture_and_Customization#etcsvlircdrun|/etc/sv/lircd/run]] /etc/sv/lircd/run to configure and start LIRC. If your remote is not starting you can put the commands to start your remote in [[Architecture_and_Customization#etcrunitlircsh|/etc/runit/lirc.sh]] /etc/runit/lirc.sh and the runit script at /etc/sv/lircd/run will be ignored. Make sure to use the "lircd -n switch":http://www.lirc.org/html/lircd.html to keep lircd in the foreground as runit requires the processes it manages be in the foreground.
h2. Tips
h3. Custom Remote Templates
If your remote is included with LinHES and you have modified either the /etc/lircd.conf or /etc/lircrc files your changes will be overwritten the next time the LIRC templates are updated or a different remote is selected from the Service Services Menu. The easiest way to avoid losing your modifications is to make your own custom remote template in ~/remotes/YourRemoteName/ and copy in the custom lircrc, lircd.conf, remote lircd.conf and picture and remote.run files. file of the remote. Your remote will be available as an option in "Service Menu" --> "LinHES Configuration" --> "Remotes". and it will not be overwritten by any updates. If your remote has the same name as a remote in /usr/MythVantage/templates/remotes/ both will show in the UI. However, when either UI item is selected only the files in ~/remotes/ will used.
See also: [[Architecture_and_Customization#remotes|remotes]].
h3. Miscellaneous
If your remote is not included with LinHES please open a "ticket":http://linhes.org/bugs/projects/linhes/issues/new and attach the files you created to make it work so that it can be included in a future version of LinHES.
A very detailed guide filled with lots of information to help you debug your remote under LIRC >= 0.9.0 is posted "here.":http://forum.xbmc.org/showthread.php?t=104541