Strategus

I believe I've eliminated IR weirdness from the equation. I took the PC, my desktop monitor, and the keyboard/mouse into the room with the TV. First I powered on the PC and monitor (exactly as when on my desktop), and the remote control/Flirc worked perfectly. Next I powered on the TV and played with the TV remote. The PC/Flirc/remote continued to worked fine. This implies to me that the issue has something to do with the HDMI connection between the TV and the PC. Just to be clear, there was not a connection of any kind between the PC and the TV in this test. I wanted to see if there was IR coming from the TV perhaps.

I turned on the TV and took the TV remote out of the room completely, and blocked off the sides of the Flirc with a paper towel tube. After powering on the PC, the remote (a Harmony 880) worked for a few seconds (5 or 10?) and then quit. I don't know. Poltergeists? With the clarity of hindsight, I brought the TV remote to my desk. The Flirc works just fine with the TV remote sitting next to the PC. Maybe I'll try painter's tape over the IR sensor in the TV. I dunno. Do IR receivers ever transmit "junk"?

I appreciate your time and help. I'm anxious to get my hands on the Skip 1 myself. My Harmony is getting a bit dated. FYI. Just for grins I moved the Flirc over to a Pi 4 and tried the same experiment with the same result. I also tried different HDMI cables. I'd say just back-burner this for a while, maybe forever. If I have some epiphany I'll post back, but you needn't worry about it.

The TV has a setting named "CEC". If that is set to "disable", we get the "too many edges" message. If it's set to "enable", that message goes away. Unfortunately, the remote doesn't work with either setting.

Running Flirc connected to the desktop monitor does what I'd expect and key presses register: Tue Dec 13 2022 21:04:55 Flirc GUI Version v3.25.3 Operating System: Linux *** Device Disconnected *** *** Device Connected *** Firmware Version: v4.9.3 SKU: Flirc 2.0 [dori] Git Hash: 0xcb185bde <1>malloc_addblock(49): Heap Block: 0x20001A7C - 0x20003BFF (8k) :e:27665 ....remote key presses show.... But when attached to the TV: ue Dec 13 2022 21:11:13 Flirc GUI Version v3.25.3 Operating System: Linux *** Device Disconnected *** *** Device Connected *** Firmware Version: v4.9.3 SKU: Flirc 2.0 [dori] Git Hash: 0xcb185bde <1>malloc_addblock(49): Heap Block: 0x20001A7C - 0x20003BFF (8k) <3>ir_finished(63): too many edges Key presses don't show up (too many edges?) my_flirc_log-jvc-tv.txt my_flirc_log-desktop-monitor.txt

The attached keyboard works in both configurations. The Flirc shows up in both configs, but doesn't work connected to the TV. Bizarre! Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 0e8d:0608 MediaTek Inc. Wireless_Device Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 002: ID 20a0:0006 Clay Logic flirc Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub I'm using a wireless Logitech keyboard, but using a wired keyboard doesn't change things.

Flirc USB adapter works when computer is connected to old Samsung monitor via HDMI, but stops working when PC is connected to oldish (dumb) JVC TV via HDMI. I got everything setup the way I wanted using a monitor on my desk connected to a Linux PC running Kodi. However, when I connected the same setup to my JVC TV set, the remote stopped responding. I need some suggestions as to how to proceed debugging this issue. Thanks.