Jump to content
Flirc Forums

jason

Administrators
  • Posts

    4,017
  • Joined

  • Last visited

  • Days Won

    256

Posts posted by jason

  1. On 7/3/2025 at 5:31 PM, Want_it_to_work said:

    The GUI cannot do macros to emulate a keyboard for a software music player.

    You can. First record the first key normally.

    Then go to the GUI. File->Advanced.

    Then change the recording mode to macro. Now record the same button on your remote. Rather than getting a 'key already exists' error, you should be able to keep recording on that key. Same goes for long press.

    Sorry, I just checked, I thought that was in the manual. It's going to get updated soon. I had to drop gitbook, they lost my manual, and I can't edit it. So I had to re-write it in docusaurus.

    On 7/3/2025 at 5:31 PM, Want_it_to_work said:

    I am happy with the results but not pleased with the effort, and lack of support, to get there.

    I'm really sorry, I fucked up and let you guys down. I'll do better.

    On 7/3/2025 at 5:31 PM, Want_it_to_work said:

    In your case, I suspect you have a faulty device, but it may be too late for you to try again? 

    Sounds like it was replaced. I heard of the 'memory' issue one other time. Waiting for a device to reproduce it. I was hoping @Brigitte still had it.

    image.png

    • Like 1
  2. 10 minutes ago, Kevin Cowans said:

    Hello Jason

    Correct, Harmony to turn everything Off then the Skip 1s to run Activity 1 where the Marantz AVR turns On and then Off.

    It may be getting Late here, however, there is no File / About in the SkipApp, that I can find, however, I clicked on the 3 Vertical Dots / About and took a Screenshot as it is not possible to Cut and Paste the Information in Windows 11, hopefully that is the Information that you meant.

    The Remote Firmware is Version 4.13.11.0.

    I am now going to Bed so if you Reply I will get your Message Tomorrow.

    Thanks in advance

    Kevin

    Screenshot 2025-07-05 225422.png

    Living Room.skip 117.77 kB · 0 downloads

    Perfect, thank you. I see the issue. It's a bug with the latest release candidate. You may need to delete the app and reset the remote and start over again (With the current PUBLIC beta or the website 0.9.993). Or, if you wait until monday, we can push a new release candidate to have this fixed.

  3. 4 hours ago, Kevin Cowans said:

    Hello Jason

    Thanks for the Reply.

    The AVR is the Device being Turned On and Off, not the TV, just for clarification.

    I have attached the Log to this Message.

    I think I may have misunderstood your Instructions, if that is so then Please let me know.

    The First Block is from the Harmony Elie Remote which I used to Turn everything Off, the Rest is from the Skip 1s where I used the Activity and the AVR switched On and then Off.

    Thanks

    Kevin

    my_flirc_log.txt 2.07 kB · 1 download

    So this is two button presses, correct ? First harmony, then the second one is the skip 1s pressed once, correct?

    Can you do me another favor. In the skipapp, can you go to file->About, copy and paste that text here. Also, go to remote manager, and save your configuraiton, and post it here, as shown here:
    image.png

    Can you also tell me what firmware version of the remote you see? Same screenshot as above.

    Thanks for the info. I'll figure it out

  4. 24 minutes ago, Kevin Cowans said:

    Hello Jason

    Thanks for the Reply.

    The AVR is the Device being Turned On and Off, not the TV, just for clarification.

    I have attached the Log to this Message.

    I think I may have misunderstood your Instructions, if that is so then Please let me know.

    The First Block is from the Harmony Elie Remote which I used to Turn everything Off, the Rest is from the Skip 1s where I used the Activity and the AVR switched On and then Off.

    Thanks

    Kevin

    my_flirc_log.txt 2.07 kB · 1 download

    Thank you. Can you also attach a picture of the Power button on your remote that's the problem. Both power-on/off toggles at the bottom. Similar to the attached, (but for both Up/Down.

    image.png

  5. 3 hours ago, Kevin Cowans said:

    Hello Jason

    I am having quite a few issues that I am unable to solve.

    I have Two Activities, 'Home Theatre PC' and 'Watch TV'.

    To keep things less complicated I will be using 'Home Theatre PC' in this example but Issue exists in the 'Watch TV' Activity too.

    I have the following Devices:

    LG 49SK8500PLA - Added as LG Type 1 TV

    Marantz NR1609 AVR - Added as NR/SR Series Main Zone, I have tried Essential Commands Only and also All Commands.

    Flirc - Added as Flirc (Plex), I use Plex HTPC.

    To have a Clean Start, I Turn Off the TV and Marantz AVR Manually, the PC stays On 24/7.

    When I Press 'A' on the Skip 1s Remote followed by the 'Power' Button, the TV Turns On, then the Marantz AVR Turns On and Immediately Turns Off.

    I have checked the Button Timings and Repeat is Set at 1.

    I would try Learning the Original Marantz Remote for the NR1609 but the Remote Learning feature does not work which I reported back in March.

    The Remote Learning will Learn the First, or sometimes the Second, Button but it will not progress any further so Learning a Full Remote is not possible.

    Any Help in solving these Issues would be appreciated as, unfortunately, the Skip 1s Remote is of no use to me as it is currently.

    Thanks in advance

    Kevin

    Can you grab your Flirc USB, Pop it in the computer. Open Up the Flirc USB pairing application. Go to File->Advanced, enable IR debugging. 

    Press once the SKIP Remote Power button in question that is turning off and on the TV.

     

    Wait a good five seconds. Grab the other remote, and Press the Power button once. Let go for 5 Seconds, press it again.

    Copy and paste the text in here. Let's get it fixed.

  6. On 6/26/2025 at 8:19 PM, Brigitte said:

    I’ve initiated an RMA request for the device. My Streacom case was sacrificed so I could use its SE and at least that unit works like it should. 
    On a personal note @jason, people pay hard earned money for your products, you can’t just leave them hanging like this without support. It’s not just me, most other forum threads go unresolved. Stand by your product or pull it off the market please. 

    Where did you initiate an RMA?

  7. Is this plugged directly into the computer or ina hub? What kind of computer? I’m really sorry about this. Can you save and share your configuration here. 
     

    can you also tell me what sku you have? I’ll generate some firmware to troubleshoot this 

  8. On 6/9/2025 at 8:18 AM, netflux said:

    Just posting to add that I've experienced exactly the same issue, again with an old Flirc 2.0 that I hadn't used for some time. Same unit test failure, exactly the same symptoms as above.

    I've already ordered a replacement from Amazon, just posting here in case the data point is useful.

    How long did you have the bad one?

  9. On 5/7/2025 at 5:03 AM, alexbk66 said:

    Not much activity here in the forum?

    I'll definitely return to this shortly when I get out our recent updates. I can't thank you enough for your efforts. Will connect with you outside the forums as welll.

  10. On 4/27/2025 at 12:08 PM, Deloran said:

    Just asking asking again.

    I really don't quite follow this particular setup. I asked a question but didn't get a response regarding the remote. Are you sending something from IP2IR and then the flirc usb is playing back 2 signals for every transmission?

    What is the log you attached? is this from the IP2IR device? 

    Can you clear the log, and send one signal to the flirc, and post those results? 

    - Hello, thank you for responding. How do i disable IR learning? 
    IR learning can't be "disabled" because it's only enabled during recording. Once a record is successful, it is played back and never enters this state again.

    - Is it possible to passthrough the codes from iTach through the Flirc? 
    I really don't understand what this means. In order for the codes to achieve their desired results on your PC, you need to record them with Flirc so they send the right USB signal on reception.

    My guess is that your IP2IR device is sending out two presses everytime you tell it to do it once. But I can't be for sure without more information of your setup and a new log.

  11. 2 hours ago, Borax6878 said:

    I'm looking to buy a mini PC that has a motherboard with wake (from hibernate) on USB capability that works with the Flirc USB.

    I have a Flirc USB in my desktop PC and waking from hibernate with my IR remote works fine. For the bedroom I'd like a mini PC that can also wake from an IR remote so I would buy a second Flirc USB for the bedroom. I'm replacing a raspberry pi 3 which is becoming too slow for modern versions of kodi. A raspberry pi 5 would do the job but a mini PC running linux or windows isn't much more expensive and is more flexible.

    Which mini PC can wake from hibernation with a Flirc USB?

    PS.

    I have a minisforum mini PC whose motherboard doesn't support wake on USB so don't say they all do.

    Almost all can. Just make sure it can supply power over usb. And it’s on suspend and not hibernate. 

  12. 16 minutes ago, Deloran said:

    I am using a Global Cache iTach IP2IR with the FLIRC on an Nvidia Shield PRO 2019. I can record from the remote with no problems. However commands are executing twice. Global Cache has their own library of IR Codes. Would this have anything to do with it? Is there a work around?

    Can you capture the code with the remote and from the ip2ir ?


    Use the flirc gui->advanced, enable IR debugging. press and hold the button once on the remote for about a second Then send the same button out once from the ip 2 ir.

  13. On 4/1/2025 at 8:52 AM, JeroenD said:

    @jason,

     

    This happens indeed every time I do a unit test.
    I just repeated again following commands: device_log, settings, unit_test, settings, device_log.
    As you can see below again my key recordings are lost.

    I am not doing anything custom at all. I am not using the utility, not in background and not in script. I am happy to install the special firmware to get the extra logs (however you have to tell me how to install it, because normally I do this only with the GUI).

    macmini2018:~ # flirc_util device_log
    <3>ir_finished(72): too many edges
    <3>ir_finished(72): too many edges
    <3>ir_finished(72): too many edges
    <3>ir_finished(72): too many edges
    macmini2018:~ #

    macmini2018:~ # flirc_util settings
    flirc_util version 8fa330dc8741f2014de7af7f0761abb35ddadb65 [8fa330d+]
     Firmware Detected
     FW Version: v4.10.5
        SKU:     Flirc 2.0 [dori]
        Branch:  release
        Config:  release
        Hash:    0xF7261C8C

    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
    -----  --------   ---  --  ------------
        0  7174CC7E   054  01  .
        1  C0FD707E   054  01  escape
        2  50DA027E   054  01  c
        3  BF513A7E   054  01  return
        4  35D85E7E   053  01  up
        5  E39DBA7E   054  01  right
        6  C5B4F07E   054  01  down
        7  53C1287E   054  01  left
        8  4F2DCC7E   054  01  backspace
        9  83B4CC7E   054  01  e
       10  338DA87E   130  01  =
       11  C36A3A7E   130  01  -
       12  686DCC7E   130  01  F8
       13  9F1DBA7E   130  01  pageup
       14  2EFA4C7E   130  01  pagedown
       15  87CDCC7E   054  01  r
       16  8C1D4C7E   054  02  play/pause
       17  F7F13A7E   054  01  f
       18  01515E7E   054  01  ,
       19  95C14C7E   054  01  x
       20  83164C7E   055  01  s
    macmini2018:~ #

    macmini2018:~ # flirc_util unit_test
    [E] lib/libflirc/firmware/fw_4.2.c _fl_unit_test(172): can't find hash: test2
    Flirc Not Okay
    macmini2018:~ #

    macmini2018:~ # flirc_util settings
    flirc_util version 8fa330dc8741f2014de7af7f0761abb35ddadb65 [8fa330d+]
     Firmware Detected
     FW Version: v4.10.5
        SKU:     Flirc 2.0 [dori]
        Branch:  release
        Config:  release
        Hash:    0xF7261C8C

    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
    -----  --------   ---  --  ------------
    macmini2018:~ #

    macmini2018:~ # flirc_util device_log
    macmini2018:~ #

     

    PM me your address, let's see if this is fixed in hardware, before we return this one.

  14. 1 hour ago, JeroenD said:

    @jason ,

    Any idea what might be causing the issue?

    Do you need more logs / info? If so then please let me know what more you need.

    Thanks.

    This is really crazy. Does this happen every time?

    I don’t see anything in dmesg. 

    Can you do a flirc_utility device log before this happens and after it happens. I may need to send you some special firmware to get more logs. The only way a device can lose its memory is if it’s sent a special command. Or memory gets corrupted, and the way that happens is if something writes to memory… But it would also say in the device log if it found corrupt memory.

    Are you doing anything custom like running the utility in the background or as a startup script, etc?

     

  15. On 3/27/2025 at 4:19 AM, JeroenD said:

    I have also enabled Kodi debugging.

    During normal operation when I press the play/pause button then the Kodi log file shows the following message:

    2025-03-27 12:06:31.164 T:631975   debug <general>: HandleKey: play_pause (0xf0bd) pressed, window 12005, action is PlayPause

    However when the video is in long pause (couple of minutes) then my Flirc is not responding anymore when I press a button and then this HandleKey debug message is NOT shown in the Kodi.log. 

    Therefore I think this issue is a bug in the Flirc firmware.

    What is the next step?

     

    When this happens, can you ssh into it and see if there are any logs?

    Do a `dmesg` paste that here.

    Also run a few commands and see what happens.
     

    flirc_util unit_test

    flirc_util settings

    Let me know. 

×
×
  • Create New...