jason

Try this one.https://flirc.com/software/flirc-usb/firmware/flirc.marlin.release-v4.10.5.bin Can you also do one more smear after you plug it in?

We figured out the issue and pushed an update.

I have a mailing list, otherwise here is the best place to. I will start doing blog posts when I have an update as well.

Thank you, really means a lot. I was going to suggest this, I wasn’t sure how the GUI would react though. That’s great. Nice job! Yes, that was the plan. Even when it gets sent down to the device, it does it as a smaller form of JSON called CBOR. You can go back and forth. I don’t keep all the data though, just the buttons because I have bytes of memory.

It’s a soft limit. We just need to figure out how to handle the ux. I’ll prioritize this. No technical reason.

Can you ssh and type ‘dmesg’ and send the output? Yes, you can downgrade, figure out which SKU you have and then grab the one to try from here: https://flirc.com/software/flirc-usb/firmware/

Can you please attach your whole support file?

If you plug it into the machine you upgraded on, it works?

Version published! Thanks everyone for all the helpful feedback, support, and testing. I will post the next one relatively soon. I will lock the topic shortly as well since any feedback would be general. I will also post a feature request board soon so I can gather feedback on how to prioritize our long list of tasks.

It’s not supposed to come off. If it does, it will crack or break. What you are experiencing is expected.

I'll send another lid with the remote.

Yes, cheap batteries would do it. I use rechargeable. They don't last as long, but it prevents these issues.

I can probably repair it if you send it in. I caught a bug under extreme conditions. Low voltage, nominal temp, the voltage regulator would get stuck latched. It would only happen if you had batteries and plugged into a computer and unplugged the cable. It was rare where and you'd have to do it over and over to reproduce it. But that doesn't mean it wouldn't happen to yours 40% of the time. These things get multiplied when you mass produce or have subtle variations in chip manufacturing etc. One of the difficult things about hardware. It has to work 100% of the time under all conditions. Some of which you can't imagine to test under. It would leak current from the battery. Not a lot, but basically a constant drain that will never go away, even if it's asleep. The only remedy was removing the batteries and plugging them back in. It could have been the reason for the corrosion. I added a diode to the 6th version of the PCB. I would add one by hand to your board as well as try and replace the springs. But the plastic could get damaged, etc.

I've got to be honest, given the condition of the remote, being that it's an A05 model, ~2-3 years old, and it wont connect to either machine, I don't think it's worth either of our times trying to fix it. Can I send you a 50% off coupon for a new one?

Do you have another machine to test it on? You set it up at one point, when was the last time you set it up? (meaning it was configured on a machine)

Doesn't necessarily mean data is working. If it doesn't show anything in lsusb, it's not connected to the machine. Try another cable. Try reversing the USB-C connector on the remote side. Does it work in another machine with the same cable? This topic is specifically to help me focus on release candidate issues. I'll create a new thread with these posts and move them there since it's not specific to this release.

Remote is not showing up at all. Check in another PC. If it doesn't show up, replace the chord. Are you using a USB-C to A adapter, maybe it's not good. Try reversing the cable Check your steamdeck hub, or try without the hub. If it doesn't show up in linux, it's not going to show up in the app.

In the terminal, can you type in lsusb and paste the output?

@trogle. Let me know how this feels:

Yes, I'm going to take a look soon.

Thank you, I found the bug. Very upset with myself. I worked on this for months, tested so thoroughly, wrote simulations, and at the end, I optimized one small thing and created the bug. I'll have an update shortly.

I think the lib errors and warnings you can ignore, it's normal. Just to be clear, if you double click it, does it launch the GUI? If it does, can you attach the remote. Then create support files and attach them here. I'll look at the logs. It should have an error that will give us a clue.

My primary linux machine is a steamdeck. I don't have any issues. Did you change anything, are you running a a different desktop environment than the default KDE? etc.

Did the public version work and not this one? Are you on a steam deck?

Post the support file. I’ll take a look.