Hi
This might be a silly answer for you and might not help you at all.
But on my RPi5 with the latest software
(LibreELEC-RPi5.aarch64-13.0-nightly-20260924-1fca19c.img), the FLIRc works perfectly.
Regards, jd
(translated with DeepL)
Wenn du auch mit Deepl übersetzt kann ich auch gleich auf deutsch schreiben 
Wenn es Libreelec nicht ist, deins funktioniert ja und der FLIRC es nicht ist, muss es etwas dazwischen sein. Und dazwischen war nur ein Hub an welchem eine Maus und eine Bluetooth Tastatur stecken. Jetzt habe ich den FLIRC direkt am Raspi angesteckt, Maus und Tastatur hängen noch am Hub und dieser an einem anderen Raspi USB Port. Nun geht es. Mir erschließt sich nur nicht, warum es die ganze Zeit so ging und jetzt auf einmal nicht mehr. Aber danke für deine Hilfe, der Hinweis war gut. Brauchte ich nicht mehr da suchen wo ich die ganze Zeit gesucht hatte.
Vielen Dank und schöne Grüße
Für alle anderen die dieselbe Konstellation haben.
Hello
If it’s not LibreELEC — yours is working, after all — and it’s not the FLIRC either, then there must be something in between causing the problem. The only thing in between was a USB hub with a mouse and a Bluetooth keyboard connected to it.
I’ve now plugged the FLIRC directly into the Raspberry Pi. The mouse and keyboard are still connected to the hub, and the hub is plugged into a different USB port on the Raspberry Pi. Now it works.
I just don’t understand why it worked like that all the time and suddenly stopped working. But thanks for your help — that was a really good hint. It saved me from continuing to look in the wrong place, which is where I’d been looking the whole time.
Many thanks and best regards
Hi,
I switched to 13.0 Nightly, too, because I was having sound issues.
LibreELEC-RPi5.aarch64-13.0-nightly-20261023-3a28f2c.img.gz
Those are gone, but now I'm having a problem with my Flirc .
The mouse and the Ritek keyboard always work reliably.
The Flirc only works sporadically, and when it does, it’s always different keys. Sometimes these, other times those, but never all of them as programmed. They all work on the PC.
If I unplug the mouse and keyboard receiver and reboot the Raspberry Pi, the Flirc works too.
If I then plug the mouse and keyboard receiver back in, all three devices work perfectly.
But after a reboot, the Flirc stops working again 
I didn’t have these problems with LibreELEC 12.
Thank you very much, and best regards.
maranzon what has your RPi5 problem got to do with Amlogic?
I've moved the posts into the right spot.
maranzon what has your RPi5 problem got to do with Amlogic?
Well, that's not an RPi5 issue, but a problem with LE13.
Since we were talking about the nightly builds here, it's possible that someone might know something about it. Something must have changed in LE13 if it works in LE12.
Well, that's not an RPi5 issue, but a problem with LE13.
Since we were talking about the nightly builds here, it's possible that someone might know something about it. Something must have changed in LE13 if it works in LE12.
If you want people to help you, you do need to provide the necessary information. Run this in SSH:
lsusb -t -vHow to post a log (wiki)
1. Enable debugging in Settings>System Settings>Logging
2. Restart Kodi
3. Replicate the problem
4. Generate a log URL (do not post/upload logs to the forum)
5. Use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link here
Salute.
Don’t assume that AI has the answer to your problem; generally speaking, AI gets it wrong and offers options that are completely off the mark. It’s based on what it’s gathered from the internet, and there’s so much data online that’s utter nonsense.
And even if you want to report a ‘bug’, you’ll need to provide detailed information about it so that the error(s) can be rectified. That’s why I asked you to use the command lsusb -t -v to see which USB port you’re using for what, as USB ports share the same main channels. So the location could be a possible cause.
Salute.
Good to hear you got it sorted, and thanks for confirming the cause.
For what it's worth: this matches what lsusb -t -v was hinting at — the Flirc
was sitting behind a hub that also carried a mouse and a Bluetooth keyboard,
so all three shared the same upstream channel and power budget. That kind of
setup can work fine for months and then break after a firmware/kernel update,
because even a small change in USB enumeration timing or power draw on the
hub can upset a HID-only device like the Flirc.
Two suggestions if you want to close this out properly:
1. To confirm the hub is really the culprit, plug the Flirc back into the hub
and reboot a few times — if the problem returns, you've reproduced it.
2. If you'd rather keep everything on the hub, try an externally powered one,
or at least one that doesn't share its port with two other devices.
Either way, your workaround (Flirc directly on the Pi, peripherals on the hub)
is perfectly valid — that's how I'd leave it too.
Either way, your workaround (Flirc directly on the Pi, peripherals on the hub)
is perfectly valid — that's how I'd leave it too.
Yes, unfortunately, it’s stopped working again. Without changing anything, it works sometimes and then stops working again. The strange thing is that the volume up/down and mute commands work through the Flirc.
The AI had also flagged the hub as a possible issue. But if I disconnect it completely and leave only the Flirc plugged in, I have exactly the same problem.
And even when I connect all three dongles directly to the Raspberry Pi, the problem persists. However, the whole setup worked flawlessly under LE 12, even with the same hub, because I also had two SSDs connected to the Raspberry Pi’s USB 3.0 ports at the time. I never experienced these intermittent failures back then.
But I don’t want to go back to LE 12 because I had audio issues with it.
You can't expect people on this forum to go through such a lengthy troubleshooting process. Nobody has that much time.
And yet you expect people to help you.
For free, on their own time, without all the relevant information.
Isn't this sort of a nonsense?
