Jump to content
Flirc Forums

PeterC

Members
  • Content Count

    12
  • Joined

  • Last visited

Community Reputation

0 Neutral

About PeterC

  • Rank
    Junior Flirc-er
  1. Hello! Any progress or status update on this? Since then I tried with another remote (Hauppauge) with the same problem.
  2. Hello! I use Flirc v2 together with a Logitech Harmony One+ on Debian Buster (10.4) and MythTV. On the Flirc I have selected a full keyboard layout. The problem is that I need to press every remote button twice for the command to work. Before I bought a Flirc I used ir-keytable and did not experience this problem. Any help or suggestion would be appreciated. Best regards, Peter
  3. The remote control is a Logitech Harmony One+. The problem is that the setup is very unreliable and I don't know if it is the Flirc, the remote control, Debian Buster or a combination. The remote control has worked without problem for several years together with Debian. But when Debian was upgraded from Stretch to Buster the drivers for my IR receiver stopped working. I then bought a Flirc. The problems are several: It sometimes output errors when using flirc_util as I have posted above. It sometimes deletes the recorded keys and I have to do the configuration again.
  4. Here is the output from DEBUG=true flirc_util settings. Hope you can get some info out of it. flirc_debug.txt
  5. Today when the PC started I got no response whatsoever from any commands from the remote control and when I tried with flirc_util I got: flirc_util unit_test Flirc Okay htpc:~# flirc_util settings 3.25.3 FW Version: v4.9.3 SKU: Flirc 2.0 [dori] Branch: master Config: release Hash: 0xCB185BDE Settings: sleep detection: always enabled noise canceler: always enabled inter-key delay: N/A for current firmware variant: Flirc builtin profiles: NA Memory Info: NA product sku: Flirc 2.0 [dori] Recorde
  6. I was trying to start logging to file by following the example of creating a configuration file (/usr/bin/flirc.ini) and start the GUI but I can not find the log file. Is it supposed to be stored in /usr/bin/ if I don't enter any path in the ini-file? Using for example 'flirc_util unit_test' it still spit out errors but it kind of work although it still need two key presses for every command. And thats why I wanted the log file. [E] lib/libtransport/transport.c _dev_send_cmd(223): Wrong response: 'getversion' [E] lib/libflirc/firmware/fw_4.2.c _fl_unit_test(132): error recording t
  7. OK, I will give it a try tomorrow. Thanks!
  8. Thanks for your quick response! It is directly on the PC and I have tried different ports. Both USB 2.0 and 3.0. I need to have a 0.5m cable since the ports are at the back of the PC. The Flirc and the remote has clear sight and the distance is approximately 3m. The double record was no issue before I bought the Flirc when I used ir-keytable but it had other issues.
  9. Hello again! Just after I posted the last reply, Debian released an update to Buster (10.3) so here is the output again: uname -a Linux htpc 4.19.0-8-686-pae #1 SMP Debian 4.19.98-1 (2020-01-26) i686 GNU/Linux flirc_util settings 3.25.3 FW Version: v4.9.3 [E] lib/libtransport/transport.c _dev_send_cmd(223): Wrong response: 'ir_state' [E] lib/libflirc/firmware/fw_4.0.c fl_ver4_header_peek(50): invalid address you idiot SKU: Flirc 2.0 [dori] [E] lib/libtransport/hid.c hid_recv_packet(161): Wrong response length = 33 [E] lib/libtransport/hid.c hid_recv_packet
  10. This time when booting the computer I got this: flirc_util unit_test Flirc Okay flirc_util settings 3.25.3 FW Version: v4.9.3 SKU: Flirc 2.0 [dori] Branch: master Config: release Hash: 0xCB185BDE Settings: sleep detection: always enabled noise canceler: always enabled inter-key delay: N/A for current firmware variant: Flirc builtin profiles: NA Memory Info: NA product sku: Flirc 2.0 [dori] Recorded Keys: Index hash IK ID key ----- -------- --- -- ------------ But th
  11. On Debian Buster 10.2 uname -a Linux htpc 4.19.0-6-686-pae #1 SMP Debian 4.19.67-2+deb10u2 (2019-11-11) i686 GNU/Linux
  12. Hello! I just recently bought a Flirc Gen 2 and it behaves very strange. Almost every time I boot my computer (Debian Buster) the Flirc device is not recognized and I see this in journalctl: kernel: usb 3-2: device descriptor read/64, error -110 kernel: usb 3-2: device descriptor read/64, error -110 kernel: usb usb3-port2: attempt power cycle kernel: usb 3-2: new full-speed USB device number 4 using uhci_hcd kernel: usb 3-2: device not accepting address 4, error -110 kernel: usb 3-2: new full-speed USB device number 5 using uhci_hcd systemd-udevd[307]: usb3: Worker [
×
×
  • Create New...