jason

Just add another profile on the savant, panasonic or a samsung tv, and then map it to flirc to your liking. Also, tell me the name of the model you were using on savant to try and pair with flirc.

Also, please link a pic to your remote or the model.

What firmware is the old one running?

yeah, configuration files are stored completely differently, it's coming.

The new device has no advanced configuration yet. These will be added soon. What you are seeing looks good to me. Hang in there. I've had to split time between getting orders out and spending time with my family. 1. Sleep detection - Done, needs to be vetted before pushed 2. Noise Canceler - Not going to be added, algorithm will be improved until this feature is obsolete 3. Interkey delay - Not going to be used, this device uses different techniques that weren't possible on the original 4. Seq Modifiers - This should already be working and implemented, just can't be disabled yet The rest are setting information, and will be added.

Can we set up a team viewer session? v2.0.2 should have fixed this, can you confirm that's what you're using?

Okay, thanks for posting this, I appreciate it. I'll post an update soon. I think I know what's wrong. Older versions of software can't speak to newer versions of hardware, it's expected that v1.4.4 doesn't work.

If you have a harmony, there are some existing devices already that you can add to your harmony, and flirc support is built in for these devices. Right now, there is a kodi, and a firetv device. I'll be reaching out to them shortly to add some more.

Okay, I posted another update which fixed another crashing issue. We're on v2.0.2 right now. This was with older generation devices.

I'm working on this issue. Top priority.

Thanks for the kind feedback, makes all the hard work worth it. https://support.flirc.tv/hc/en-us/articles/203167509-Setting-up-Flirc-with-PS4 It's supported, just a bit of a manual process. I'll be getting this into the GUI shortly. Let us know if you need help with any of that.

Can you post a link to that remote you are using?

Here is a copy of v1.4.4: https://flirc.tv/software/release/gui/windows/Flirc.v1.4.4.exe I'm still working on a fix.

When you pair your remote make sure you aim your remote away from the device this can happen if it's too close.

Okay, Just to let other know, changing the USB position helped the crash. I've got a local repro here, and I'll be working on a fix today.

pm me a session ID and password.

Can we do a team viewer session?

Did it crash?

awesome. Okay, unplug the device, and fire up the GUI. Does it work? Plug in the device if the GUI loads with no device present, and let me know what happens. Log file should change.

I ask because the plastic sometimes doesn't look pristine. Surface isn't always perfect. Even so, I don't recycle products. However, the metal is newly released. It wouldn't even be possible to recycle material, your the first to ever receive it and see it. They just started shipping. I have super strict quality control this go around. I'm even opening up 50% of them and inspecting them myself to ensure they are adhering to my standards. I send them emails all the time telling them what is and what isn't okay. Your unit is not behaving correctly, let's get you a replacement. Send me an email at support@flirc.tv and I'll take care of everything.

Is this the new metal one? Or is it plastic?

I'll get that up tomorrow. Can you help me figure out what's going on? I can't reproduce this. In the Installation directory: c:\Program Files (x86)\Flirc there is a flirc.ini file. Can you change all the false words to true. Then can you change loglevel = 0 to loglevel 5 Run the app, there will be a log file put on your desktop. Throw that on here, I'll take a look at what's going on. Thank you and very sorry for the trouble.

I believe you have the older one, correct? The issue reported above is definitely different. Long story short, I created another sku for a huge company who was looking to partner, and they ended up not moving forward. I repurposed that sku, but gave them a different USB Product ID in the process. The new 2.0 software has a completely re-written driver model that handles all the device communication. I simply forgot to add the AZ product id when searching for the device. This is why some people have a 'disconnected' state when opening the GUI. There was a substantial amount out there. Completely forgot about it, was about a year and a half ago.

can we set up a team viewer session? If not, at your convenience; There is a flirc.ini in the installation directory. Can you change all the false to true, then set the loglevel = 0 ---> loglevel=5 Then can you post the log?