Jump to content
Flirc Forums
Adri

Flirc not working after upgrade to 3.25

Recommended Posts

Well that didn't work. Installed linux on a laptop and then installed flirc software. Still can't get past 3.11 on software. Does anyone have any suggestions to try on a gen 1 flirc? My problem is that I can not get the simplest of controls (minimalist) to work on the flirc. Some keys will function but others don't. Up arrow goes up, down arrow goes up, right arrow goes right, left arrow does nothing, return makes a noise.

I have tried to manually install 3.12 using the method outlined in the forum and it does not seem to take. I have updated the drivers and it does not seem to make a difference. I am using 3.25.2 on the software. I've tried both windows and linux on this gen 1 flirc.

Thanks in advance for any help you can give me. I have attached a log file of the upgrade. Hope that will help.

flirc_log.txt

Edited by Daddis

Share this post


Link to post
Share on other sites

Hi @jason

are there any news?

With 4.9.3 Pause Button is not working - Rest is OK. (4.7.0 works fine)

Are there any Firmware version between 4.7.0 and 4.9.3 (Dori) which i can test?

Edited by JohnWayne

Share this post


Link to post
Share on other sites
On 12/20/2019 at 9:28 PM, jason said:

Okay, I think I got it. Everyone was using windows, and there was something that needed to be fixed in my report descriptor and it looks like other OS's were more lenient. Sorry, please try the attached.  File->advanced to get your sku, and then do file->upgrade ,and upload one of the attached.

gen 1 devices can use the flirc-gen1v3.12.bin file

 

nemo.release-4.9.1.bin 60.63 kB · 4 downloads dori.release-4.9.1.bin 60.5 kB · 10 downloads

flirc-gen1-v3.12.bin 12 kB · 16 downloads

EDIT: found the other post saying 3.11 is latest now, FLIRC wasn't successful at working when I was remote logged into the machine, but recording the activity I wanted worked directly on the machine itself.

Edited by ncer

Share this post


Link to post
Share on other sites
On 12/21/2019 at 3:15 AM, jason said:

Oh I'm so sorry, I modified the content and forgot to update the CRC. Try the attached.

Sunrise_Flirc_updated.fcfg 348 B · 5 downloads

Hi Jason,

it works mostly now, but there are still some issues controlling the Sunrise box with Flirc after firmware upgrade.

  • DVR button is not working anymore
  • Back button is not working anymore (not sure if it was before though)
  • Forward/rewind are behaving differently than before
  • all the virtual buttons programmed on the touch screen of the Harmony Ultimate One do not work anymore (they did work after firmware upgrade before loading quoted file, but all physical buttons did not work anymore)

I attached you config file that has been working flawlessly with previous firmwares for the last few years with Gen2 version of the IR receiver.

Can you probably help with this?

Am on a Windows 10 x64 machine using newest versions of Flirc GUI and firmware.

 

Sunrise_Flirc.fcfg

Share this post


Link to post
Share on other sites

If you upgraded to the latest firmware, you'll have re-pair many of these keys. I changed the way the report ID's work in USB to be more compatible with other devices, and the way the old config sent them up doesn't work with newer firmware. So what I'd recommend is loading this file. Hit delete in the GUI, and re-record the button / function again. Let me know if that helps.

There is a ton of work I want to do with Flirc that's in the pipeline. I am at a standstill with my employees at home, the virus disruption in life and my supply chain (since january), and all the stress that comes with this. I'm really sorry. Still alive, working just as hard.

Let me know how this goes.

Share this post


Link to post
Share on other sites
5 hours ago, jason said:

If you upgraded to the latest firmware, you'll have re-pair many of these keys. I changed the way the report ID's work in USB to be more compatible with other devices, and the way the old config sent them up doesn't work with newer firmware. So what I'd recommend is loading this file. Hit delete in the GUI, and re-record the button / function again. Let me know if that helps.

Hi Jason,

unfortunately there is no way to re-record the buttons since the original remote supports bluetooth only. 
The codes were taken from here, the thread starter found them by trial and error method I guess.

Is there an easy and supported way to downgrade to previous firmware probably in the mean time?

Share this post


Link to post
Share on other sites
On 3/27/2020 at 2:19 PM, dude said:

Hi Jason,

unfortunately there is no way to re-record the buttons since the original remote supports bluetooth only. 
The codes were taken from here, the thread starter found them by trial and error method I guess.

Is there an easy and supported way to downgrade to previous firmware probably in the mean time?

What version did you need?

 

Share this post


Link to post
Share on other sites
7 hours ago, jason said:

What version did you need?

 

Hi Jason,

quite frankly I do not remember the last working FW I used. 
In the change logs you do not mention FW version, only GUI version.

But I updated Flirc FW quite regularly, so a FW from late 2019 should do just well.

Thanks and best regards

Share this post


Link to post
Share on other sites

Hi there,

I am new to Flirc and I am in the process of upgrading 3 W7 HTPC's w/ MCE Remote receivers to W10 w/ Flirc's.

As a result I believe I have identified an issue similar to what has been described above regarding the functioning or not of a couple of the pre-defined controllers and associated buttons.

The function(s) in question are as follows:-

Controllers > Kodi > stop button & Controllers > Media Keys > wake/suspend button for some reason they seem to have some direct relationship.

The observed behaviour is as follows:-

When I program the Controllers > Media Keys > wake/suspend button to the Harmony 700 power button, the Controllers > Kodi > stop button exhibits the same behaviour. i.e When I press the stop button whilst watching a movie using Kodi the PC goes to sleep.

If I then change the configuration of the Controllers > Kodi > stop button to perform the stop function then then I can no longer put my PC to sleep or wake it up via the Controllers > Media Keys > wake/suspend function.

Hopefully I have made myself clear.

PC configuration looks a bit like this . . . .

Windows 10 Pro Version 2004 OS Build 19041.423 running Kodi v18.8 w/ Chrome & EventGhost

Flirc GUI is v3.25.3 with FW v4.9.3

I am using a Harmony 700 Remote with the Flirc profile from Harmony

Here are couple of files that may help . . .

Cheers

Flirc Config v3.25.3 v1.fcfg flirc_log1.txt

Share this post


Link to post
Share on other sites

Just got my FLIRC today. Was very excited to try it. Now, three hours later, pretty upset with it.

  1. After ignoring a virus warning (via Windows 10 Defender) in both Firefox and Edge, I installed the FLIRC gui.
  2. I launched the gui, the device was found as connected.
  3. The gui asked me to upgrade the firmware from my shipped firmware to 4.9.3. I did so.
  4. I programmed several buttons (via the Harmony Hub remote app on iOS) to test functionality. Simple stuff, just red button types 'a' on the keyboard.
  5. Nothing works. The debug log shows that IR commands are being received but no commands are recognized by Windows. E.g., pressing the red button in the Harmony app (which should type 'a' on the keyboard via the FLIRC gui mapping I've permed) does nothing.
  6. Read through the forums and reddit for about two hours or so looking for a solution.
  7. Uninstall, reboot, reinstall software twice, including manual deletion of Program Files dir for FLIRC.
  8. Nothing works. At one point, the FLIRC gui shows the FLIRC dongle as disconnected. After another reinstall, this was fixed.
  9. Create a forum account to download firmware 4.9.1.
  10. Install 4.9.1 firmware.
  11. Remap keys (e.g., 'a' to red button again).
  12. Still nothing.

Any suggestions? The fact I can't even get the FLIRC to do something as basic as push 'a' or the 'enter' key on command (despite IR logs in the app responding to those keypresses) is just about enough for me to be convinced my FLIRC is broken.

Log from FLIRC gui:

-------------------

Wed Sep 9 2020 17:43:08

Flirc GUI Version v3.25.3

Operating System: Windows

*** Device Disconnected ***

*** Device Connected ***

Firmware Version: v4.9.1

SKU: Flirc 2.0 [dori]

Git Hash: 0x24052832

:e:17441

0,4947,4793,909,1577,903,1583,899,1587,899,743,929,1557,903,1584,903,1583,904,4370,899,748,899,743,903,743,899,743,930,1557,903,744,899,743,1744,1583,904,743,899,743,878

:e:24

0,4950,4792,899,1587,924,1562,899,1587,898,744,903,1583,898,1588,898,1588,899,4370,903,743,899,748,898,743,903,744,898,1588,898,743,903,743,1743,1583,899,747,899,747,899

:e:24

0,4949,4792,903,1583,903,1583,899,1639,847,748,898,1588,898,1588,899,1587,899,4370,899,747,899,747,899,747,895,747,899,1587,899,747,899,769,1712,1592,894,748,898,769,877

-------------------

 

flirc_log.zip

Edited by justwantthistowork
add log

Share this post


Link to post
Share on other sites

The windows virus thing is a problem, I don’t know why it says that. I wrote all the code.  I didn’t write any viruses. Chrome/firefox upload the binary to a third party, and it passes 15 checks, and one fails. It’s stupid. I don’t know how to fix it. 

Everything looks like it’s working.


When you hit ‘record a’ it says successfully recorded?

It doesn’t always highlight on the virtual keyboard after you press it. It’s hit or miss.

Fire up a text editor, and press the button you paired on your remote to see if it’s sent to the text editor as ‘a’.

If you try to record the same button again on your remote, does it say, ‘error, already recorder?’

You haven’t done anything wrong.

 

Share this post


Link to post
Share on other sites
4 hours ago, jason said:

The windows virus thing is a problem, I don’t know why it says that. I wrote all the code.  I didn’t write any viruses. Chrome/firefox upload the binary to a third party, and it passes 15 checks, and one fails. It’s stupid. I don’t know how to fix it. 

Everything looks like it’s working.


When you hit ‘record a’ it says successfully recorded?

It doesn’t always highlight on the virtual keyboard after you press it. It’s hit or miss.

Fire up a text editor, and press the button you paired on your remote to see if it’s sent to the text editor as ‘a’.

If you try to record the same button again on your remote, does it say, ‘error, already recorder?’

You haven’t done anything wrong.

 

Yes, it does say successfully recorded. I actually never had any issues with the FLIRC software detecting key presses when it showed FLIRC in the connected state.

I tried text editors, multiple media applications, web browsers, etc. with the button and nothing was ever sent to any window.

Also yes as to it providing the "already recorded" error upon attempts to assign a second time.

I've also tried the up, down, left, right, enter, and backspace keys on a separate trial attempt. Same results -- nothing works.

Share this post


Link to post
Share on other sites
42 minutes ago, justwantthistowork said:

Yes, it does say successfully recorded. I actually never had any issues with the FLIRC software detecting key presses when it showed FLIRC in the connected state.

I tried text editors, multiple media applications, web browsers, etc. with the button and nothing was ever sent to any window.

Also yes as to it providing the "already recorded" error upon attempts to assign a second time.

I've also tried the up, down, left, right, enter, and backspace keys on a separate trial attempt. Same results -- nothing works.

Did you by any chance use the zadig driver utility?

Share this post


Link to post
Share on other sites
On 9/10/2020 at 3:37 PM, jason said:

Did you by any chance use the zadig driver utility?

I had not at the time of my posts. I took your question to be a suggestion of something else to try and I have now replaced the default hidusb driver with a libusbk driver (had to search the forums a bit to see what use of the zadig driver utility implied, so hopefully my conclusion to use libusbk is correct). However, after the libusbk install through zadig, my FLIRC dongle was no longer detected by the FLIRC software. I am planning on reverting to hidusb as of the moment.

update: After a few more days of wasting time trying to troubleshoot this, I'm giving up and just returning it. Disappointed overall.

Edited by justwantthistowork
progress update

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...