<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">On Sep 2, 2015, at 7:42 AM, Alec Leamas <<a href="mailto:leamas.alec@gmail.com" class="">leamas.alec@gmail.com</a>> wrote:<br class=""><div><blockquote type="cite" class=""><br class="Apple-interchange-newline"><div class=""><span style="font-family: Helvetica; font-size: 14px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">However, a raw config file could be used exactly as a normal one. If you take your file with just a few buttons, copies it to /etc/lirc/lircd.conf</span></div></blockquote></div><br class=""><div class="">I’m curious why you wouldn’t take one of the irrecorded codes and search the remotes database for it. Something like:</div><div class=""><br class=""></div><div class=""><div class=""> find /usr/share/lirc/remotes -type f -exec grep -H -i 17FD {} \;</div><div class=""><br class=""></div><div class="">where 17FD represents a code from the irrecord file. It could be that irrecord is supposed to do this out of the box but I don’t remember it doing that when I was setting up my remotes.</div><div class=""><br class=""></div><div class="">Of course no match means you’ve got a never-before-seen remote and would have to do your own lircd.conf as Alec says.</div><div class=""><br class=""></div><div class="">- George</div></div><div class=""><br class=""></div></body></html>