History

Remotes

Version 11 (brfransen, 04/20/2017 02:47 pm)

1 9 brfransen 
{{toc}}
2 9 brfransen 






    3
    1
    
    
h1. Remotes






    4
    1
    
    






    5
    11
    brfransen
    
h2. [[Architecture_and_Customization|Architecture and Tools]]






    6
    7
    brfransen
    






    7
    1
    
    
h2. Setup






    8
    1
    
    






    9
    1
    
    
h3. Automatic






    10
    1
    
    






    11
    1
    
    
"Service Menu" --> "LinHES Configuration" --> "Remotes" then select your remote and press "Next" and "Finish".






    12
    1
    
    






    13
    1
    
    
If your remote is not listed in the menus you will have to set it up manually.






    14
    1
    
    






    15
    1
    
    
h3. Manual






    16
    1
    
    






    17
    11
    brfransen
    
h4. R7.3 & Later Releases






    18
    1
    
    






    19
    11
    brfransen
    
Beginning in R7.3 the "runit":http://smarden.org/runit/ lircd service has been replaced with the remotes service (/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.






    20
    1
    
    






    21
    11
    brfransen
    
h4. R7.2 & Earlier Releases






    22
    1
    
    






    23
    11
    brfransen
    
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 /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 /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.






    24
    1
    
    






    25
    1
    
    
h2. Tips






    26
    1
    
    






    27
    5
    brfransen
    
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 Services Menu.  The easiest way to avoid losing your modifications is to make your own remote in ~/remotes/YourRemoteName/ and copy in the lircrc, lircd.conf and picture 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.






    28
    11
    brfransen
    






    29
    11
    brfransen
    
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.






    30
    11
    brfransen
    






    31
    11
    brfransen
    
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