Search the Community

Using flirc tools 3.26.9 installed from the deb package. Trying to record a pattern and send it I get: root@box:~# irtools sendir --pattern=0,153,1231,131 --repeat=3 --ik=32000 found it [E] fl_version_compare(286): Flirc iospirit found version: 4.6.5 0x18BBFCFA [release] [E] sendir(36): Error: version >= 4.7.x required Any suggestions on how to resolve? Thanks.

Thanks @jason its updated. This was my recording in the device log: *** Device Connected *** Firmware Version: v4.9.7 SKU: Flirc 2.0 [dori] Git Hash: 0x1de23eb8 -19275000 +9097 -4399 +643 -452 +643 -456 +638 -456 +639 -452 +643 -452 +643 -451 +639 -456 +639 -456 +638 -1589 +639 -1589 +639 -1584 +643 -1585 +638 -1585 +643 -1585 +643 -1584 +639 -1585 +659 -1568 +639 -1588 +639 -474 +621 -456 +639 -456 +639 -456 +639 -1585 +638 -457 +638 -456 +639 -456 +639 -1589 +682 -1542 +643 -1584 +639 -1588 +639 -458 +611 -1611 +639 -40000 +9095 -2169 +613 <3>record_hash(473): hash exists I believe I should be using the command to send the IR signal - can you please confirm pi@raspberrypi:~ $ flirc_util sendir --raw="+9097 -4399 +643 -452 +643 -456 +638 -456 +639 -452 +643 -452 +643 -451 +639 -456 +639 -456 +638 -1589 +639 -1589 +639 -1584 +643 -1585 +638 -1585 +643 -1585 +643 -1584 +639 -1585 +659 -1568 +639 -1588 +639 -474 +621 -456 +639 -456 +639 -456 +639 -1585 +638 -457 +638 -456 +639 -456 +639 -1589 +682 -1542 +643 -1584 +639 -1588 +639 -458 +611 -1611 +639" --repeat=1 Here is the output: [V] util/flirc_util/src/main.c main(123): Command: flirc_util [V] util/flirc_util/src/main.c main(127): running pre-command function 0 [D] lib/libflirc/common/flirc_transport.c fl_open_hid(124): trying to open bootloader device [D] lib/libtransport/hid.c list_devs(280): --------------------------------------------------------- [D] lib/libtransport/hid.c list_devs(281): -----------------------Device List----------------------- [D] lib/libtransport/hid.c list_devs(282): --------------------------------------------------------- [D] lib/libtransport/hid.c list_devs(292): Device Found type: 20a0 0006 path: /dev/hidraw0 serial_number: E7A3ABA25050323431202020FF101122 [D] lib/libtransport/hid.c list_devs(294): [D] lib/libtransport/hid.c list_devs(295): Manufacturer: flirc.tv [D] lib/libtransport/hid.c list_devs(296): Product: flirc [D] lib/libtransport/hid.c list_devs(297): Release: 200 [D] lib/libtransport/hid.c list_devs(298): Interface: 0 [D] lib/libtransport/hid.c list_devs(299): Usage Page: 65280 [D] lib/libtransport/hid.c list_devs(300): Usage: 1 [D] lib/libtransport/hid.c list_devs(292): Device Found type: 20a0 0006 path: /dev/hidraw1 serial_number: E7A3ABA25050323431202020FF101122 [D] lib/libtransport/hid.c list_devs(294): [D] lib/libtransport/hid.c list_devs(295): Manufacturer: flirc.tv [D] lib/libtransport/hid.c list_devs(296): Product: flirc [D] lib/libtransport/hid.c list_devs(297): Release: 200 [D] lib/libtransport/hid.c list_devs(298): Interface: 1 [D] lib/libtransport/hid.c list_devs(299): Usage Page: 1 [D] lib/libtransport/hid.c list_devs(300): Usage: 6 [D] lib/libtransport/hid.c list_devs(292): Device Found type: 20a0 0006 path: /dev/hidraw1 serial_number: E7A3ABA25050323431202020FF101122 [D] lib/libtransport/hid.c list_devs(294): [D] lib/libtransport/hid.c list_devs(295): Manufacturer: flirc.tv [D] lib/libtransport/hid.c list_devs(296): Product: flirc [D] lib/libtransport/hid.c list_devs(297): Release: 200 [D] lib/libtransport/hid.c list_devs(298): Interface: 1 [D] lib/libtransport/hid.c list_devs(299): Usage Page: 12 [D] lib/libtransport/hid.c list_devs(300): Usage: 1 [D] lib/libtransport/hid.c list_devs(292): Device Found type: 20a0 0006 path: /dev/hidraw1 serial_number: E7A3ABA25050323431202020FF101122 [D] lib/libtransport/hid.c list_devs(294): [D] lib/libtransport/hid.c list_devs(295): Manufacturer: flirc.tv [D] lib/libtransport/hid.c list_devs(296): Product: flirc [D] lib/libtransport/hid.c list_devs(297): Release: 200 [D] lib/libtransport/hid.c list_devs(298): Interface: 1 [D] lib/libtransport/hid.c list_devs(299): Usage Page: 1 [D] lib/libtransport/hid.c list_devs(300): Usage: 128 [D] lib/libtransport/hid.c list_devs(292): Device Found type: 20a0 0006 path: /dev/hidraw1 serial_number: E7A3ABA25050323431202020FF101122 [D] lib/libtransport/hid.c list_devs(294): [D] lib/libtransport/hid.c list_devs(295): Manufacturer: flirc.tv [D] lib/libtransport/hid.c list_devs(296): Product: flirc [D] lib/libtransport/hid.c list_devs(297): Release: 200 [D] lib/libtransport/hid.c list_devs(298): Interface: 1 [D] lib/libtransport/hid.c list_devs(299): Usage Page: 12 [D] lib/libtransport/hid.c list_devs(300): Usage: 1 [D] lib/libtransport/hid.c list_devs(292): Device Found type: 20a0 0006 path: /dev/hidraw2 serial_number: E7A3ABA25050323431202020FF101122 [D] lib/libtransport/hid.c list_devs(294): [D] lib/libtransport/hid.c list_devs(295): Manufacturer: flirc.tv [D] lib/libtransport/hid.c list_devs(296): Product: flirc [D] lib/libtransport/hid.c list_devs(297): Release: 200 [D] lib/libtransport/hid.c list_devs(298): Interface: 2 [D] lib/libtransport/hid.c list_devs(299): Usage Page: 65280 [D] lib/libtransport/hid.c list_devs(300): Usage: 1 [D] lib/libtransport/hid.c list_devs(306): --------------------------------------------------------- [V] lib/libtransport/hid.c hid_dev_open(329): Device 20A0:5 not found [V] lib/libtransport/transport.c dev_open(88): no device found [V] lib/libflirc/common/flirc_transport.c _fl_open_libhid_btldr(56): no hid device found [D] lib/libflirc/common/flirc_transport.c fl_open_hid(130): trying to open main device [D] lib/libflirc/common/flirc_transport.c _fl_open_libhid_app(92): trying to open 0x20A0, 0x0006 [D] lib/libtransport/hid.c list_devs(280): --------------------------------------------------------- [D] lib/libtransport/hid.c list_devs(281): -----------------------Device List----------------------- [D] lib/libtransport/hid.c list_devs(282): --------------------------------------------------------- [D] lib/libtransport/hid.c list_devs(292): Device Found type: 20a0 0006 path: /dev/hidraw0 serial_number: E7A3ABA25050323431202020FF101122 [D] lib/libtransport/hid.c list_devs(294): [D] lib/libtransport/hid.c list_devs(295): Manufacturer: flirc.tv [D] lib/libtransport/hid.c list_devs(296): Product: flirc [D] lib/libtransport/hid.c list_devs(297): Release: 200 [D] lib/libtransport/hid.c list_devs(298): Interface: 0 [D] lib/libtransport/hid.c list_devs(299): Usage Page: 65280 [D] lib/libtransport/hid.c list_devs(300): Usage: 1 [D] lib/libtransport/hid.c list_devs(292): Device Found type: 20a0 0006 path: /dev/hidraw1 serial_number: E7A3ABA25050323431202020FF101122 [D] lib/libtransport/hid.c list_devs(294): [D] lib/libtransport/hid.c list_devs(295): Manufacturer: flirc.tv [D] lib/libtransport/hid.c list_devs(296): Product: flirc [D] lib/libtransport/hid.c list_devs(297): Release: 200 [D] lib/libtransport/hid.c list_devs(298): Interface: 1 [D] lib/libtransport/hid.c list_devs(299): Usage Page: 1 [D] lib/libtransport/hid.c list_devs(300): Usage: 6 [D] lib/libtransport/hid.c list_devs(292): Device Found type: 20a0 0006 path: /dev/hidraw1 serial_number: E7A3ABA25050323431202020FF101122 [D] lib/libtransport/hid.c list_devs(294): [D] lib/libtransport/hid.c list_devs(295): Manufacturer: flirc.tv [D] lib/libtransport/hid.c list_devs(296): Product: flirc [D] lib/libtransport/hid.c list_devs(297): Release: 200 [D] lib/libtransport/hid.c list_devs(298): Interface: 1 [D] lib/libtransport/hid.c list_devs(299): Usage Page: 12 [D] lib/libtransport/hid.c list_devs(300): Usage: 1 [D] lib/libtransport/hid.c list_devs(292): Device Found type: 20a0 0006 path: /dev/hidraw1 serial_number: E7A3ABA25050323431202020FF101122 [D] lib/libtransport/hid.c list_devs(294): [D] lib/libtransport/hid.c list_devs(295): Manufacturer: flirc.tv [D] lib/libtransport/hid.c list_devs(296): Product: flirc [D] lib/libtransport/hid.c list_devs(297): Release: 200 [D] lib/libtransport/hid.c list_devs(298): Interface: 1 [D] lib/libtransport/hid.c list_devs(299): Usage Page: 1 [D] lib/libtransport/hid.c list_devs(300): Usage: 128 [D] lib/libtransport/hid.c list_devs(292): Device Found type: 20a0 0006 path: /dev/hidraw1 serial_number: E7A3ABA25050323431202020FF101122 [D] lib/libtransport/hid.c list_devs(294): [D] lib/libtransport/hid.c list_devs(295): Manufacturer: flirc.tv [D] lib/libtransport/hid.c list_devs(296): Product: flirc [D] lib/libtransport/hid.c list_devs(297): Release: 200 [D] lib/libtransport/hid.c list_devs(298): Interface: 1 [D] lib/libtransport/hid.c list_devs(299): Usage Page: 12 [D] lib/libtransport/hid.c list_devs(300): Usage: 1 [D] lib/libtransport/hid.c list_devs(292): Device Found type: 20a0 0006 path: /dev/hidraw2 serial_number: E7A3ABA25050323431202020FF101122 [D] lib/libtransport/hid.c list_devs(294): [D] lib/libtransport/hid.c list_devs(295): Manufacturer: flirc.tv [D] lib/libtransport/hid.c list_devs(296): Product: flirc [D] lib/libtransport/hid.c list_devs(297): Release: 200 [D] lib/libtransport/hid.c list_devs(298): Interface: 2 [D] lib/libtransport/hid.c list_devs(299): Usage Page: 65280 [D] lib/libtransport/hid.c list_devs(300): Usage: 1 [D] lib/libtransport/hid.c list_devs(306): --------------------------------------------------------- [D] lib/libtransport/hid.c hid_find(254): Device Used type: 20a0 0006 path: /dev/hidraw0 serial_number: E7A3ABA25050323431202020FF101122[D] lib/libtransport/hid.c hid_find(256): Manufacturer: flirc.tv [D] lib/libtransport/hid.c hid_find(257): Product: flirc [D] lib/libtransport/hid.c hid_find(258): Release: 200 [D] lib/libtransport/hid.c hid_find(259): Interface: 0 [D] lib/libtransport/hid.c hid_find(260): Usage Page: 65280 [D] lib/libtransport/hid.c hid_find(261): Usage: 1 [V] lib/libtransport/hid.c hid_dev_open(336): Manufacturer String: flirc.tv [V] lib/libtransport/hid.c hid_dev_open(341): Product String: flirc [V] lib/libtransport/hid.c hid_dev_open(346): Serial Number String: E7A3ABA25050323431202020FF101122 [V] lib/libtransport/hid.c hid_dev_open(347): [V] lib/libtransport/hid.c hid_send_packet(79): Report ID: 2 [V] lib/libtransport/hid.c hid_send_packet(80): Report len: 33 00: 02 67 65 74 76 65 72 73 69 6f 6e 00 00 b4 79 03 .getversion...y. 10: 00 d4 ea 8f ff 04 00 00 00 00 00 00 00 78 ea 8f .............x.. 20: ff . [V] lib/libtransport/hid.c hid_send_packet(91): hid_write = 33 [V] lib/libtransport/hid.c hid_recv_packet(144): Report ID: 1 [V] lib/libtransport/hid.c hid_recv_packet(145): Report len: 33 [V] lib/libtransport/hid.c hid_recv_packet(156): retval = 33 00: 01 67 65 74 76 65 72 73 69 6f 6e 00 00 04 00 09 .getversion..... 10: 00 07 00 b8 3e e2 1d 72 65 6c 65 61 73 65 00 00 ....>..release.. 20: 00 . [V] lib/libflirc/common/flirc_transport.c transport_new_get_version(35): Version: 4.9.7 0x1DE23EB8 [release] [D] lib/libflirc/flirc_driver.c determine_iface(116): fw_state: firmware [D] lib/libflirc/flirc_driver.c determine_iface(118): version: 4.9 [D] lib/libflirc/flirc_driver.c determine_iface(256): initializing fw ver4.9 [D] lib/libflirc/common/flirc_transport.c _fl_open_libhid_app(113): [Device Found] [V] lib/libflirc/common/flirc_transport.c _fl_open_libhid_app(114): FIRMWARE: 2 [V] lib/libflirc/common/flirc_transport.c fl_open_hid(132): application found [D] lib/libflirc/flirc_driver.c fl_open_device(285): device found, state: 2 [V] lib/libcmds/cmds.c run_cmds(251): running command: sendir [V] lib/libcmds/cmds.c cmd_getopt(223): opt: --raw=+9097 -4399 +643 -452 +643 -456 +638 -456 +639 -452 +643 -452 +643 -451 +639 -456 +639 -456 +638 -1589 +639 -1589 +639 -1584 +643 -1585 +638 -1585 +643 -1585 +643 -1584 +639 -1585 +659 -1568 +639 -1588 +639 -474 +621 -456 +639 -456 +639 -456 +639 -1585 +638 -457 +638 -456 +639 -456 +639 -1589 +682 -1542 +643 -1584 +639 -1588 +639 -458 +611 -1611 +639, carg = 1 [V] lib/libcmds/cmds.c cmd_getopt(223): opt: --repeat=1, carg = 2 Transmitting IR Pattern... [V] lib/libtransport/hid.c hid_send_packet(79): Report ID: 6 [V] lib/libtransport/hid.c hid_send_packet(80): Report len: 65 00: 06 69 72 74 72 61 6e 73 65 74 00 00 00 44 00 98 .irtranset...D.. 10: 3a 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 :............... 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 30: 00 ff ff ff ff 00 00 00 00 dc 99 61 f7 c8 fb 80 ...........a.... 40: f7 . [V] lib/libtransport/hid.c hid_send_packet(91): hid_write = 65 [V] lib/libtransport/hid.c hid_recv_packet(144): Report ID: 5 [V] lib/libtransport/hid.c hid_recv_packet(145): Report len: 65 [V] lib/libtransport/hid.c hid_recv_packet(156): retval = 65 00: 05 69 72 74 72 61 6e 73 65 74 00 00 00 00 00 00 .irtranset...... 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 40: 00 . 00: 00 00 89 23 2f 11 83 02 c4 01 83 02 c8 01 7e 02 ...#/.........~. 10: c8 01 7f 02 c4 01 83 02 c4 01 83 02 c3 01 7f 02 ................ 20: c8 01 7f 02 c8 01 7e 02 35 06 7f 02 35 06 7f 02 ......~.5...5... 30: 30 06 83 02 0... [V] lib/libtransport/hid.c hid_send_packet(79): Report ID: 6 [V] lib/libtransport/hid.c hid_send_packet(80): Report len: 65 00: 06 69 72 74 72 61 6e 73 72 61 77 00 00 00 00 89 .irtransraw..... 10: 23 2f 11 83 02 c4 01 83 02 c8 01 7e 02 c8 01 7f #/.........~.... 20: 02 c4 01 83 02 c4 01 83 02 c3 01 7f 02 c8 01 7f ................ 30: 02 c8 01 7e 02 35 06 7f 02 35 06 7f 02 30 06 83 ...~.5...5...0.. 40: 02 . [V] lib/libtransport/hid.c hid_send_packet(91): hid_write = 65 [V] lib/libtransport/hid.c hid_recv_packet(144): Report ID: 5 [V] lib/libtransport/hid.c hid_recv_packet(145): Report len: 65 [V] lib/libtransport/hid.c hid_recv_packet(156): retval = 65 00: 05 69 72 74 72 61 6e 73 72 61 77 00 00 00 00 00 .irtransraw..... 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 40: 00 . 00: 31 06 7e 02 31 06 83 02 31 06 83 02 30 06 7f 02 1.~.1...1...0... 10: 31 06 93 02 20 06 7f 02 34 06 7f 02 da 01 6d 02 1... ...4.....m. 20: c8 01 7f 02 c8 01 7f 02 c8 01 7f 02 31 06 7e 02 ............1.~. 30: c9 01 7e 02 ..~. [V] lib/libtransport/hid.c hid_send_packet(79): Report ID: 6 [V] lib/libtransport/hid.c hid_send_packet(80): Report len: 65 00: 06 69 72 74 72 61 6e 73 72 61 77 00 00 31 06 7e .irtransraw..1.~ 10: 02 31 06 83 02 31 06 83 02 30 06 7f 02 31 06 93 .1...1...0...1.. 20: 02 20 06 7f 02 34 06 7f 02 da 01 6d 02 c8 01 7f . ...4.....m.... 30: 02 c8 01 7f 02 c8 01 7f 02 31 06 7e 02 c9 01 7e .........1.~...~ 40: 02 . [V] lib/libtransport/hid.c hid_send_packet(91): hid_write = 65 [V] lib/libtransport/hid.c hid_recv_packet(144): Report ID: 5 [V] lib/libtransport/hid.c hid_recv_packet(145): Report len: 65 [V] lib/libtransport/hid.c hid_recv_packet(156): retval = 65 00: 05 69 72 74 72 61 6e 73 72 61 77 00 00 00 00 00 .irtransraw..... 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 40: 00 . 00: c8 01 7f 02 c8 01 7f 02 35 06 aa 02 06 06 83 02 ........5....... 10: 30 06 7f 02 34 06 7f 02 ca 01 63 02 4b 06 7f 02 0...4.....c.K... [V] lib/libtransport/hid.c hid_send_packet(79): Report ID: 6 [V] lib/libtransport/hid.c hid_send_packet(80): Report len: 65 00: 06 69 72 74 72 61 6e 73 72 61 77 00 00 c8 01 7f .irtransraw..... 10: 02 c8 01 7f 02 35 06 aa 02 06 06 83 02 30 06 7f .....5.......0.. 20: 02 34 06 7f 02 ca 01 63 02 4b 06 7f 02 00 00 00 .4.....c.K...... 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 40: 00 . [V] lib/libtransport/hid.c hid_send_packet(91): hid_write = 65 [V] lib/libtransport/hid.c hid_recv_packet(144): Report ID: 5 [V] lib/libtransport/hid.c hid_recv_packet(145): Report len: 65 [V] lib/libtransport/hid.c hid_recv_packet(156): retval = 65 00: 05 69 72 74 72 61 6e 73 72 61 77 00 00 00 00 00 .irtransraw..... 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 40: 00 . +9097 -4399 +643 -452 +643 -456 +638 -456 +639 -452 +643 -452 +643 -451 +639 -456 +639 -456 +638 -1589 +639 -1589 +639 -1584 +643 -1585 +638 -1585 +643 -1585 +643 -1584 +639 -1585 +659 -1568 +639 -1588 +639 -474 +621 -456 +639 -456 +639 -456 +639 -1585 +638 -457 +638 -456 +639 -456 +639 -1589 +682 -1542 +643 -1584 +639 -1588 +639 -458 +611 -1611 +639 -15000 Done! [V] util/flirc_util/src/main.c main(173): running post-command function 0 [V] util/flirc_util/src/prepost.c flirc_deinit(39): closing device [D] lib/libflirc/flirc_driver.c fl_close_device(443): closing device [D] lib/libflirc/flirc_driver.c fl_close_device(454): freeing iface pi@raspberrypi:~ $

The sound bar is in the database and all other commands work - volume and mute. I have another remote that correctly controls the power on this unit but I don't know what the commands are specifically. I have tried both the toggle command and the on / off commands separately and together - no luck. Do you have way forward in this situation currently or will I be able to "transfer" the IR command to the skip 1s in the future through the app?

Also, when --repeat is omitted when running flirc_util.exe sendir --pronto="<pronto hex code>", flirc_util.exe defaults to 1 repeat. Not really a problem (you can specify --repeat=0), just slightly confusing.

Is it possible to parse the raw data to match it with a protocol, address and command code? I guess it should be doable especially if you can take an informed guess about the protocol being used. Is the raw data format documented somewhere?

Since we're all just kind of waiting for the next shipment of remotes, I thought I may as well revisit this in the meantime. It was over two months ago that you mentioned officially adding the missing "Back" command to the Roku Streambar, so that I wouldn't have to add it manually every time I make a new activity. I've checked the nightly updates various times since then, but see that it's still not there. Since there's not a whole lot going on right now, could you maybe get that added? As a reminder, the Back command from the "Roku 2" device is identical to that of the Roku Streambar, so the code can be taken directly from that. Should be pretty simple for you, I'm guessing. Get back to me about this when you can. Thanks!

Dragging the POWER OFF command list from a device onto the remote device made added it to the remote device, but removed it from the command list, preventing the command from being assigned to multiple buttons OR the POWER UP/POWER ON. Not sure what the expected behavior is. The UI is so bad on this I fired a UX designer on my team out of spite.

Try flirc_util.exe sendir --pattern=0,8834,4157,509,1534,510,494,509,493,507,495,508,1536,509,494,509,493,509,494,508,495,509,493,535,469,508,495,506,495,510,493,507,496,508,496,508,1534,509,495,522,480,507,496,508,494,508,495,509,494,509,493,508,1534,509,494,508,495,507,495,508 --repeat=0 Close Flirc GUI before running the command. --raw and --pronto arguments are not available before version 3.26.8.

I have a batch script that utilizes flirc_util.exe to send IR commands with Flirc USB. After upgrading Flirc (by replacing Flirc.exe & flirc_util.exe in the install dir) from 3.26.5 to 3.26.8 (because I need support for Pronto IR codes), I am having the following issue. If flirc_util.exe command is inside a for /f loop, for example: for /f "delims=" %%a in ('""C:\Program Files (x86^)\Flirc\flirc_util.exe" sendir --pronto="0000 006d 0022 0002 0156 00ab 0015 0040 0015 0040 0015 0040 0015 0015 0015 0015 0015 0015 0015 0015 0015 0040 0015 0015 0015 0015 0015 0040 0015 0040 0015 0040 0015 0040 0015 0040 0015 0015 0015 0015 0015 0015 0015 0040 0015 0015 0015 0040 0015 0015 0015 0015 0015 0040 0015 0040 0015 0040 0015 0015 0015 0040 0015 0015 0015 0040 0015 0040 0015 0015 0015 05d8 0156 0055 0015 0e48" 2>&1"') do echo %%a the IR signal is NOT being sent anymore. flirc_util.exe command output is still displayed though: Transmitting IR Pattern... +8892 -4446 +546 -1664 +546 -1664 +546 -1664 +546 -546 +546 -546 +546 -546 +546 -546 +546 -1664 +546 -546 +546 -546 +546 -1664 +546 -1664 +546 -1664 +546 -1664 +546 -1664 +546 -546 +546 -546 +546 -546 +546 -1664 +546 -546 +546 -1664 +546 -5 46 +546 -546 +546 -1664 +546 -1664 +546 -1664 +546 -546 +546 -1664 +546 -546 +54 6 -1664 +546 -1664 +546 -546 +546 -38000 +8892 -2210 +546 -95000 Done! If flirc_util.exe command is called directly, for example: "C:\Program Files (x86)\Flirc\flirc_util.exe" sendir --pronto="0000 006d 0022 0002 0156 00ab 0015 0040 0015 0040 0015 0040 0015 0015 0015 0015 0015 0015 0015 0015 0015 0040 0015 0015 0015 0015 0015 0040 0015 0040 0015 0040 0015 0040 0015 0040 0015 0015 0015 0015 0015 0015 0015 0040 0015 0015 0015 0040 0015 0015 0015 0015 0015 0040 0015 0040 0015 0040 0015 0015 0015 0040 0015 0015 0015 0040 0015 0040 0015 0015 0015 05d8 0156 0055 0015 0e48" 2>&1 the IR signal is still being sent (most of the time anyway*). (both examples can also be verified directly in cmd.exe if you replace %%a with %a) Can somebody please help. Thank you in advance. Regards, Franc * After some experimenting it seems like the longer (more complicated) the command line is, the less likely the IR signal will be sent. Very strange.

A forum member asked how I converted a CSV file I had created originally into a JSON file and I figured I would share with everyone. I pulled my codes from here https://www.remotecentral.com/cgi-bin/codes/yamaha/rx-v1000/ Here is how I got my json file. I am familiar with the Linux command line so I performed the following steps. Before I show these let me say that an easier way could be to open a spreadsheet program and copy the button name into one column and the code for the button into another column. The second column needs to have the spaces between the numeric codes replaced with commas. You should then be able to save to the CSV file. It is possible you spreadsheet program may be able to save the file to JSON. If not, you may be able to use an online tool to do that basic work. I followed the following steps to dump the html page into a bit more of a manageable file. The steps below have been modified from the blog post. lynx -dump 'https://www.remotecentral.com/cgi-bin/codes/yamaha/rx-v1000/' | sed -e 's/^ *//' | tr -s ' ' ',' | sed 's/$/,/' > dumped_page.txt I then ran the following commands to strip out more of what I did not need. sed -i '/\[filler\.gif\]/d' dumped_page.txt sed -i '/\(Copy,to,Clipboard\)/d' dumped_page.txt sed -i '/\[filler\.gif\]/d' dumped_page.txt I then opened the dumped_page.txt file into a text editor and removed all the text I did not need. How I found that was by looking for these couple of lines of text Remote Model: RAV222 [filler.gif] Power ([23]Copy to Clipboard) Power is where my first button started so I removed every line above Power in the file. I then looked for the equivalent of the bottom the button codes. [filler.gif] [ < Back | Page: 1 [43]2 | [44]Next > ] [filler.gif] I removed everything starting from the first filler.gif line to the bottom of the file. I then combined all the codes for each button onto one line. BEFORE Stadium, 0000,006b,0022,0002,0156,00ad,0015,0015,0015,0041,0015,0015,0015,0041, 0015,0041,0015,0041,0015,0041,0015,0015,0015,0041,0015,0015,0015,0041, 0015,0015,0015,0015,0015,0015,0015,0015,0015,0041,0015,0041,0015,0015, 0015,0041,0015,0041,0015,0015,0015,0015,0015,0015,0015,0041,0015,0015, 0015,0041,0015,0015,0015,0015,0015,0041,0015,0041,0015,0041,0015,0015, 0015,05f8,0156,0057,0015,0e57, AFTER Stadium,0000,006b,0022,0002,0156,00ad,0015,0015,0015,0041,0015,0015,0015,0041,0015,0041,0015,0041,0015,0041,0015,0015,0015,0041,0015,0015,0015,0041,0015,0015,0015,0015,0015,0015,0015,0015,0015,0041,0015,0041,0015,0015,0015,0041,0015,0041,0015,0015,0015,0015,0015,0015,0015,0041,0015,0015,0015,0041,0015,0015,0015,0015,0015,0041,0015,0041,0015,0041,0015,0015,0015,05f8,0156,0057,0015,0e57 Since I know I am working with a CSV file I removed the last comma from each line since I do not need it and it could cause problems when creating the JSON file I saved that file which now gives me 20 lines for my remote and then i ran another script to convert the CSV into a JSON file. Notice that I filled in the "types", "brand", and "model" with what was relevant to me. I redirected the output of the script to a file. #!/usr/bin/env bash cat << EOF { "header": { "version": "2.0" }, "types": [ "devices.audio" ], "brand": "Yamaha", "model": "RX V-1000", "signals": [ EOF while read -r line; do _label=$(echo "${line}" | cut -d ',' -f 1) _code=$(echo "${line}" | cut -d ',' -f 2- | tr '[:lower:]' '[:upper:]') cat << EOF { "label": "${_label}", "code": "${_code}", "protocol": "PRONTO" }, EOF done < dumped_page.txt cat << EOF ] } EOF One thing to keep on mind is that JSON is picky about commas and where then end up and the end of blocks. I will show what I mean with the last two entries of my JSON file. { "label": "RO Concert", "code": "0000,006B,0022,0002,0156,00AD,0015,0015,0015,0041,0015,0015,0015,0041,0015,0041,0015,0041,0015,0041,0015,0015,0015,0041,0015,0015,0015,0041,0015,0015,0015,0015,0015,0015,0015,0015,001 5,0041,0015,0015,0015,0015,0015,0041,0015,0041,0015,0015,0015,0015,0015,0015,0015,0041,0015,0041,0015,0041,0015,0015,0015,0015,0015,0041,0015,0041,0015,0041,0015,0015,0015,05F8,0156,0057,0015,0E57", "protocol": "PRONTO" }, <----- NOTICE THIS COMMA { "label": "Stadium", "code": "0000,006B,0022,0002,0156,00AD,0015,0015,0015,0041,0015,0015,0015,0041,0015,0041,0015,0041,0015,0041,0015,0015,0015,0041,0015,0015,0015,0041,0015,0015,0015,0015,0015,0015,0015,0015,001 5,0041,0015,0041,0015,0015,0015,0041,0015,0041,0015,0015,0015,0015,0015,0015,0015,0041,0015,0015,0015,0041,0015,0015,0015,0015,0015,0041,0015,0041,0015,0041,0015,0015,0015,05F8,0156,0057,0015,0E57", "protocol": "PRONTO" } <----- IT CANNOT EXIST AT THE END ] }

Most devices come with a toggle button for power. It tells the device to go to the opposite state that it is currently in. So if the device is in an on state, the toggle command turns it off. If it's off, the toggle command turns it on. The problem is when you have multiple devices in your entertainment center and they are told to toggle. If one isn't in the same state as the others, the devices won't end up in the same state. This can happen if something interferes with the IR signal to the device. Discrete Power, on the other hand, has separate commands for On and Off. If the device is off, it will turn on, but if the device is already on, sending the Power On doesn't do anything (well sometimes it does). Same with off. As for CEC, I avoid it at all costs. It's a pain to use for anything other then a basic setup. It might be appropriate for your configuration, but as you noted it can take time. You could try like I show in the image below, just remove the existing toggle and then drag the power off commands to the macro.

So the reason I have the TV power toggle option set on "power down" is because I have CEC enabled so the AVR is turned off when the TV is powered down. I set up my "power on" options to have the TV and AVR come on at the same time because CEC would take up to 15 seconds to tell the AVR to power on as well. Could you explain what you mean by the discrete power off codes? Do you just mean the power off command that's associated with the TV and AVR config? I think you're right in going the route of just using one of the color buttons to say "send the power off command regardless of current power state."

I came back to the TV tonight after the remote was sitting for about 24 hours. I was able to turn the TV on, switch activities, etc. But then when trying to turn on and then off my B activity, the remote wouldn't respond. I then just kept trying to power B on and off and on and off (I'd wait about 20 seconds between each power on/off attempt). It would sometimes respond, but more often than not, I wouldn't get a response (either on or off). Very inconsistent. I'm not sure how helpful this log is going to be. I don't see much here aside from power button presses. The remote logs that power is pressed and then released, but that doesn't always translate to the TV turning on or off. I don't know if it's a weak signal coming from the remote or not. The IR lights when viewing through a cell phone camera turn on, so I can see that a command is actually sent. The original remotes for each device work fine, so I know it's not related to that or environment. It'd be helpful in the logging to see when A, B, or C is pressed, followed by if the power button is turning on or off an activity, followed by the devices that the remote is sending an IR command for and any delay or repeats that the remote is doing. flirc-remote-control20230504.log

I've installed it in two distros. PCLinuxOS: It's in their repositories, but the rules file I mentioned above isn't there. So you'll have to add it physically as above. MX Linux: This will install from the "curl" command mentioned above, but you'll have to locate libreadline.so.8 and create a symlink to libreadline.so.6 — I just found it again, it's in /lib/x86_64-linux-gnu/ As your distro is Ubuntu-based, I don't see why the curl command won't work, but Ubuntu has moved away from Debian so maybe that's why. If you're new to Linux, the two I mentioned are easy for beginners. I could never get on with Ubuntu and gave it up as a bad job years ago. Never could understand the fuss, apart from the fact that the distro was headed by someone with a huge amount of money who could buy publicity. But believe me, MX and PCLOS are good!

Hello, I'm trying to replicate my AC remote using Flirc. I did it a few months ago, but I can't seem to get it back. I captured this log using Flirc GUI: Firmware Version: v4.9.61 SKU: Flirc 2.0 [dori] Git Hash: 0x4b35b711 <3>record_hash(473): hash exists -40481 +8834 -4157 +509 -1534 +510 -494 +509 -493 +507 -495 +508 -1536 +509 -494 +509 -493 +509 -494 +508 -495 +509 -493 +535 -469 +508 -495 +506 -495 +510 -493 +507 -496 +508 -496 +508 -1534 +509 -495 +522 -480 +507 -496 +508 -494 +508 -495 +509 -494 +509 -493 +508 -1534 +509 -494 +508 -495 +507 -495 +508 I'm trying to replicate this command using flirc_util, but I can't get it to work: flirc_util.exe sendir --raw="-40481 +8834 -4157 +509 -1534 +510 -494 +509 -493 +507 -495 +508 -1536 +509 -494 +509 -493 +509 -494 +508 -495 +509 -493 +535 -469 +508 -495 +506 -495 +510 -493 +507 -496 +508 -496 +508 -1534 +509 -495 +522 -480 +507 -496 +508 -494 +508 -495 +509 -494 +509 -493 +508 -1534 +509 -494 +508 -495 +507 -495 +508" [W] lib/libcmds/cmds.c handle_longopt(182): `sendir' doesn not take '--raw' option Error: must specify an option flirc_util.exe sendir --pronto="-40481 +8834 -4157 +509 -1534 +510 -494 +509 -493 +507 -495 +508 -1536 +509 -494 +509 -493 +509 -494 +508 -495 +509 -493 +535 -469 +508 -495 +506 -495 +510 -493 +507 -496 +508 -496 +508 -1534 +509 -495 +522 -480 +507 -496 +508 -494 +508 -495 +509 -494 +509 -493 +508 -1534 +509 -494 +508 -495 +507 -495 +508" Transmitting IR Pattern... (but doesn't work) flirc_util.exe sendir --pronto="0,40481,8834,4157,509,1534,510,494,509,493,507,495,508,1536,509,494,509,493,509,494,508,495,509,493,535,469,508,495,506,495,510,493,507,496,508,496,508,1534,509,495,522,480,507,496,508,494,508,495,509,494,509,493,508,1534,509,494,508,495,507,495,508" [E] lib/libtransport/transport.c _dev_send_cmd(223): Wrong response: 'ir_state' Error getting version device disconnected, can't run command ¿Any idea? Thanks!

I'm assuming that you ran Flirc (capital F) and flirc_util (small F) from the command line? This may give an indication of missing dependencies. Without a .desktop file, Flirc won't appear in your menus. Without the rules file, Flirc will run, but won't find your flirc and will report that it's disconnected. I had another problem when I installed it on MX Linux, where you can use the "curl" command. It complained that libreadline.so.6 was not present. You'd have to check a number of folders, starting from /lib, /usr/lib or /usr/lib64 (there could be others in your distro, or further subfolders). I found libreadline.so.8, and made a symlink to libreadline.so.6 — this worked for me. Other than that, I have no idea whatsoever.

The B activity light does light up, but in some cases if I hit the power button multiple times, sometimes the B button light is delayed in responding. The remote will queue up the commands and the B light will light up even if I am not currently hitting the power button. In some cases the TV will turn on or off (depending on whatever command actually made it to the TV), but often the remote is just in a bad state.

I'm finding the software side of things a little sloppy. In the archive for non-Debian users, there are only two files: Flirc and flirc_util. The reason that the flirc wasn't detected on my other partition running PCLinuxOS is that they forgot to include the Udev Rules file /etc/udev/rules.d/99-flirc.rules. That had been installed by the curl command, so I copied the file from my MXLinux installation to my PCLinuxOS installation and now it's all working! It's a great invention but they need to keep the software up to date!

Ok, yeah. I did see those instructions as well. That's going back a little bit for me, but I believe I ran into a different error altogether with that one. I use Zoran OS which is Ubuntu based. I can't remember if it was the curl command itself or something else. But for your effort, I will definitely try it when I get home from work so I can let you know what it tells me. Maybe you can help me with that when I post it. I'm glad you were able to get something of it working on your and. Hopefully I'm not far behind you either. There are a couple of functions on the remote that still aren't working for me. Like, stop. I can play a video but I can't stop it. Little things like that. So I would very much like to get the flirc utility working so I can remap the buttons to work properly lol I'll update after work today. Thanks!

I just found the page you tried to work from, which mentioned repositories. Wow. Glad that's not the one I found else I'd still be struggling with it. I found a different page which gave the following command line you have to put in, in a terminal to install Flirc: curl apt.flirc.tv/install.sh | sudo bash After that, you should check whether your distro has libreadline.so.6 available. This is because whoever programmed flirc_util marked it to require libreadline.so.6 "only" instead of "or later". If it's not there, in my case in the folder /lib/x86_64-linux-gnu but your distro may be different. What I had to do, was to go to the folder: cd /lib/x86_64-linux-gnu/ (or wherever you find libreadline.so.<number> Assuming it's 8 ... ) sudo ln -sf libreadline.so.8 libreadline.so.6 This worked on MX Linux. I'm actually struggling to get it to work on PCLinuxOS at the moment.

I've got it working on MX-Linux-KDE version, but I had to symlink libreadline.so.6 to libreadline.so.8 in order to use the command line flirc_utils. MX is directly Debian based (not via Ubuntu).

pi@raspberrypi:~ $ curl apt.flirc.tv/install.sh | sudo bash % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 8266 100 8266 0 0 15450 0 --:--:-- --:--:-- --:--:-- 15479 `..-:://++ooossyyyyhhhhhhhhhhhhhhhhyyysso++/:-.` `.:/+oosyhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhyo:` -/oyhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhy /hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhh- hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhh: yhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhh: ohhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhh- -hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhh` yhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhs /hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhh/ yhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhho:-:+hhhhhhhhhhhh. /hhhhhhhhhhhs- -shhhhhhhhhhhhhhhhhhhhhhhhhhhhhhh. `hhhhhhhhhhs yhhhhhhhhhh` .hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhh yhhhhhhhhh- :hhhhhhhhhho` `ohhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhs:` `-shhhhhhhhho shhhhhhhhhhhssshhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhh` .hhhhhhhhhhhhhhysso++///:::-----........-----:://+oshhhhhhhhhhh: :hhhhhhhhhhhs/:---......```````````.......---:::/+ohhhhhhhhhho +hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhs ohhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhy` +hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhs` -shhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhys: `.-://++oosssyyyyyhhhhhhhhhhhhhyyyssoo++//:--.` Distribution: debian Checking for curl... Detected curl... Installing flirc deb-repo... Running apt-get update... done. Installing apt-transport-https... done. Installing /etc/apt/sources.list.d/flirc_fury.list...done. Running apt-get update... done. Do you want to install the flirc utilities? [Y/n] Installing flirc utilities...done. pi@raspberrypi:~ $ flirc_util sendir --raw="+9092 -4403 +638 -456 +639 -456 +638 -456 +639 -456 +638 -456 +635 -456 +638 -456 +639 -456 +638 -1589 +638 -1585 +638 -1589 +638 -1584 +643 -1585 +638 -1584 +617 -1610 +639 -1584 +642 -452 +643 -1584 +638 -456 +639 -1584 +642 -1585 +638 -456 +613 -1610 +643 -451 +643 -1584 +638 -456 +639 -1588 +639 -451 +643 -452 +617 -1610 +639 -456 +638 -1584 +643" --repeat=1 [W] lib/libcmds/cmds.c handle_longopt(182): `sendir' doesn not take '--raw' option

Hi, I have captured the following IR codes in the device log. I would like to send them using flirc_util sendir could you please convert them. Thanks my_flirc_log.txt

I just received my Flirc Gen 2, and so far it's been a breeze to set up. I'm using the full keyboard option to control the audio output of a Raspberry Pi, using alsamixer commands... "Q"= left channel+, "Z"= left channel-, "E"= right channel+, "C" right channel-, "B"= balance equal, "W"= volume+, and "X"= volume-. But I also want to map the mute button... that requires an actual command: "amixer -D hw:CARD=audioinjector set 'Output Mixer Line Bypass' toggle". Is this possible?

Hi, That would be great! No support (for comma delimited sendir) required since I can roll back the GUI software to 3.26.0 Our use case for FLIRC is programatically sending IR codes. These IR codes are a large variety of TV codes which depends on which TV(s) the customer has installed. On a lot of TVs that we dont have in our database, or for some reasone they dont work, we have to capture the IR codes, assemble them into a group/database, and then we are able to use these programatically with flirc_util -sendir as needed. We need to improve the current capture process, opening the FLIRC GUI Device Log IR Debugging, pressing the remote, copying the captured ir code, pasting into a database/file, verifying operation by replay, and adding meta data .... it is not automated at the customer end currently. As a result we cannot scale product sales due to tech support hours required (not all tech support hours are for this process but it would signifcantly help) Is it possible to extend flirc_util record (or record_api) to produce the captured codes either in a file or as console output? Or there is a better way that we are just not seeing?