<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p><br>
</p>
<p> </p>
<p style="margin-bottom: 0in; line-height: 100%">Hi Stephen!</p>
<p style="margin-bottom: 0in; line-height: 100%"><br>
</p>
<pre class="western" style="margin-left: 0.39in; margin-right: 0.39in"><blockquote type="cite"><pre class="western" style="margin-left: 0.39in; margin-right: 0.39in"><font color="#000000">The Seiki configuration file - - the one I found at </font>
<font color="#000000"><a href="https://gist.github.com/gisikw/a2ffa7f45efa0d9c3bee">https://gist.github.com/gisikw/a2ffa7f45efa0d9c3bee</a> ? is at </font>
<font color="#000000">/etc/lirc/lircd.conf.d/Seiki_LIRC.conf . Good news is it is found/listed </font>
<font color="#000000">by <b>*systemctl status lircd.socket lircd.service*</b>.</font>
Good, that is the right place for it.
</pre></blockquote></pre>
<p style="margin-bottom: 0in; line-height: 100%">Figured it was in
the correct subdir, just nice to have verified and that being in
the
wrong place wasn’t the problem.</p>
<p style="margin-bottom: 0in; line-height: 100%"><br>
</p>
<br>
<pre class="western"><blockquote type="cite"><pre class="western">What is the output of: sudo ir-keytable
(without the -t). It should list your IR receiver(s).
</pre></blockquote>
pi@RPi-MythFE:~ $ sudo ir-keytable
Found /sys/class/rc/rc0/ (/dev/input/event4) with:
Name: gpio_ir_recv
Driver: gpio_ir_recv, table: rc-rc6-mce
LIRC device: /dev/lirc0
Attached BPF protocols: Operation not supported
Supported kernel protocols: lirc rc-5 rc-5-sz jvc sony nec sanyo mce_kbd rc-6 sharp xmp imon
Enabled kernel protocols: lirc
bus: 25, vendor/product: 0001:0001, version: 0x0100
Repeat delay = 500 ms, repeat period = 125 ms
pi@RPi-MythFE:~ $
</pre>
<p style="margin-bottom: 0in; line-height: 100%">
<br>
</p>
<p style="margin-bottom: 0in; line-height: 100%"><br>
</p>
<p style="margin-bottom: 0in; line-height: 100%">
<blockquote type="cite">
<pre class="western">I do not know how your remote works, just that it clearly does. IR
remotes need IR receiver hardware, which can be included in or with
tuners or as a separate device. The actual receiver is typically an
IR photo-diode, and in less naked devices than an RPi it is usually
hidden behind a small hole or transparent plastic window. So when you
are using your remote, what are you pointing it at? Does the RPi4
have a builtin IR receiver, or have you added one?</pre>
</blockquote>
I added the IR
detector from a Hauppage tuner. According to on-line information
for
an after-market replacement uses a TSOP 2238 IR Receiver.
Information from PiHut says they sell the TSOP3802. AFAICT
equivalent for my usage. (PiHut seemed to indicate an IR detector
was fine, just the pinouts could differ.)</p>
<p style="margin-bottom: 0in; line-height: 100%"><br>
</p>
<p style="margin-bottom: 0in; line-height: 100%">As for directing
the
remote control’s head, yes, directly to the opening in the
Hauppauge sensor – it’s hard to miss! <g> When nothing is
indicated on the screen the remote is closer and with grit – you
know that joke about how one presses the buttons harder on a
remote
control with dead batteries?! Yup! <g></p>
<p style="margin-bottom: 0in; line-height: 100%"><br>
</p>
<p style="margin-bottom: 0in; line-height: 100%"><br>
</p>
<p style="margin-bottom: 0in; line-height: 100%">You had a question
on the version: <i>sudo lircd -v </i></p>
<p style="margin-bottom: 0in; line-height: 100%"><br>
</p>
<p style="margin-bottom: 0in; line-height: 100%">pi@RPi-MythFE:~ $
sudo lircd -v</p>
<p style="margin-bottom: 0in; line-height: 100%">lircd 0.10.1</p>
<p style="margin-bottom: 0in; line-height: 100%"><br>
</p>
<p style="margin-bottom: 0in; line-height: 100%"><br>
</p>
<p style="margin-bottom: 0in; line-height: 100%">Thanks!</p>
<p style="margin-bottom: 0in; line-height: 100%">Barry</p>
<p>
<style type="text/css">
pre.cjk { font-family: "Courier New", monospace }
p { margin-bottom: 0.1in; line-height: 115% }
a:link { so-language: zxx }</style></p>
<p><br>
</p>
</body>
</html>