Is there a way we can record IR inputs and submit them to your database?

[Sotz]

I know that recording remote codes is currently in your to-do list, but for the technically minded among us, is there a way we can record the IR signals to submit to you for inclusion in the database?

I own the FLIRC USB dongle, and am Linux savvy if needed, so if there's any way I can record the IR signals for my unsupported devices, then I'd be happy to submit my findings to add to the app.

Edited March 7, 2023 by Sotz

[jason]

1 hour ago, Sotz said:

I know that recording remote codes is currently in your to-do list, but for the technically minded among us, is there a way we can record the IR signals to submit to you for inclusion in the database?

I own the FLIRC USB dongle, and am Linux savvy if needed, so if there's any way I can record the IR signals for my unsupported devices, then I'd be happy to submit my findings to add to the app.

Yes, I'm going to work on making this easier, unfortunately, it's a bit of a pain.

You can use Flirc in combination with irscrutinizer to get the pronto codes. I have a bunch of internal stuff I'm going to publish too. Then put the pronto codes in a comma delimited specified here:

 

[clmnt]

I successfully imported two devices that are not in the database following your procedure, thanks!

I got the raw IR timings for each button using a Flirc USB dongle and the Flirc app in IR debugging mode. I pasted the raw codes (without the first "0," string) into irscrutinizer using the button "Paste & Scrutinize" to convert them into PRONTO codes. With the PRONTO code for each button of the remote, I built a json file with the same structure as the files in the admin tab of the Skip App under Brands. Once done for a device or a remote, I was finally able to import this json file to the app by clicking Add on the admin tab.

One could probably build a community app using flirc_util and the irgen python module to speed up the procedure.

[jason]

1 hour ago, clmnt said:

I successfully imported two devices that are not in the database following your procedure, thanks!

I got the raw IR timings for each button using a Flirc USB dongle and the Flirc app in IR debugging mode. I pasted the raw codes (without the first "0," string) into irscrutinizer using the button "Paste & Scrutinize" to convert them into PRONTO codes. With the PRONTO code for each button of the remote, I built a json file with the same structure as the files in the admin tab of the Skip App under Brands. Once done for a device or a remote, I was finally able to import this json file to the app by clicking Add on the admin tab.

One could probably build a community app using flirc_util and the irgen python module to speed up the procedure.

Really great job. Here are some notes, and what I've been up to:

I reached out to irscrutinizer to see if we can get direct hardware support built in. I don't have time, I'm hoping I could get some help from them with my support.

I actually just pushed an update so flirc spits out better ir output +1231 -12132 etc, that can be directly imported into irscrutinizer 

I have a commandline app that will print out the pronto hex codes directly, I will share that in a second.

I would be happy to provide some source or a python wrapper for you to play around with a whip something up.

Can you share your files you created? For the benefit of the community, and I will include them in the next release.

We don't support only JSON importing, but will support a simple text file too, as outlined here: 

 

** Edit **

For some reason my app CI isn't auto updating, here is a copy until I figure out what's going on: https://flirc.io/nightly/Flirc GUI/mac/Flirc-3.26.5.dmg

[clmnt]

Of course I can share the files I created. I have an Haier TV that I couldn't control with the existing profiles (could be my mistake) and a Topping DX3Pro DAC for my audio. For anyone interested in the Topping codes, those should work for all Topping devices.

About simple text importing, I first created a .txt file with the syntax detailed in your linked post but on the Windows app, I couldn't import anything else than files with a .json extension. For this reason, i tried to mimic a json file already present on the Brands tab.

Haier - LDF40V280S.json Topping - DX3Pro.json

[jason]

18 hours ago, clmnt said:

Of course I can share the files I created. I have an Haier TV that I couldn't control with the existing profiles (could be my mistake) and a Topping DX3Pro DAC for my audio. For anyone interested in the Topping codes, those should work for all Topping devices.

About simple text importing, I first created a .txt file with the syntax detailed in your linked post but on the Windows app, I couldn't import anything else than files with a .json extension. For this reason, i tried to mimic a json file already present on the Brands tab.

Haier - LDF40V280S.json 7.89 kB · 1 download Topping - DX3Pro.json 2.83 kB · 2 downloads

Thanks so much for this, I'm going to review, and probably include them. Regarding text files, it was probably an error in the filename. The filename must be precise to describe the device, and categories, otherwise it will fail to import. I have python I through together to help convert to text to json, I'll publish that shortly.

[pro_info]

Hi,
I am also converting the codes of my devices that are not compatible.
Is it possible to know all enumerations for the field "signals"->"label" that are managed by the automapping?

Thx

Edit: Ok, after having a little fun retrieving some IR code, I have a bounce problem when sending the IR code.
Example with MUTE button:
From IR debug original remote 
-44137
+8986 -4466 +626 -468 +625 -1595 +625 -468 +624 -1596 +625 -1596 +623 -1598 +625 -1595 +626 -467 +626 -1595 +624 -469 +626 -1595 +625 -468 +625 -468 +624 -469 +625 -467 +626 -1595 +625 -468 +625 -468 +625 -1595 +625 -1596 +625 -1595 +626 -468 +624 -485 +608 -469 +624 -1596 +625 -1595 +625 -469 +624 -468 +625 -468 +624 -1597 +625 -1595 +625 -1597 +624

I convert the bold part in IrScrutinizer
0000 006B 0022 0000 015C 00AD 0016 0016 0016 003E 0016 0016 0016 003E 0016 003E 0016 003E 0016 003E 0016 0016 0016 003E 0016 0016 0016 003E 0016 0016 0016 0016 0016 0016 0016 0016 0016 003E 0016 0016 0016 0016 0016 003E 0016 003E 0016 003E 0016 0016 0016 0016 0016 0016 0016 003E 0016 003E 0016 0016 0016 0016 0016 0016 0016 003E 0016 003E 0016 003E 0016 0791

And when I press the button briefly on the Skip (in the same way as the original), I have this:
-9329
+9129 -4377 +653 -452 +653 -1491 +652 -452 +653 -1494 +650 -1489 +658 -1511 +625 -1492 +654 -452 +769 -1374 +653 -452 +652 -1491 +652 -494 +604 -459 +653 -452 +653 -452 +533 -1610 +653 -452 +670 -571 +509 -1497 +653 -1491 +652 -1490 +653 -453 +651 -453 +656 -449 +652 -1491 +652 -1491 +652 -453 +604 -500 +654 -451 +652 -1491 +652 -1491 +652 -1491 +653
-49
+9123 -4380 +653 -453 +652 -1490 +652 -463 +642 -1491 +652 -1491 +651 -1491 +652 -1491 +651 -463 +484 -1649 +651 -453 +606 -1536 +652 -453 +651 -453 +651 -454 +650 -454 +651 -1491 +652 -454 +558 -546 +651 -1492 +651 -1491 +651 -1492 +651 -453 +651 -453 +533 -572 +651 -1491 +651 -1492 +651 -454 +651 -453 +651 -454 +651 -1491 +651 -1492 +652 -1492 +650

How can I correct this problem?
Thank you

Edited March 25, 2023 by pro_info

[Nathan]

@pro_info Sorry, didn't notice your reply, as this thread was marked solved. If you are having a code issue with a device, can you create a thread for that device (if you haven't already)?