Updated Firmware, no longer working with Moode/Raspberry Pi

Recommended Posts

Have been using your Flirc product for a while now and really enjoy the convenience it offers.

Rebuilt my system, which included new versions of Flirc software and answered yes to the "Update Firmware?" question on my WIndows 10 machine.
The upgrade appeared successful and tests on the Win 10 machine are successful. Config settings still there!

Load a fresh image of Moode 4.4 and the keystrokes no longer register on the Pi 3.
I have a Ver 2 (nemo) hardware dongle.
Have tried it in all 4 USB ports, rebooting each time.

It is definitely a Linux issue. I suspect the driver is not loading properly?
But it shows as loaded in 'dmesg' below.

The dongle works with Windows 10. The remote works with the dongle in Windows 10.
Transfer the dongle to a freshly written Moode 4.4 image and the key strokes are not sent.
It WAS working fine before the firmware update.

Share this post

Link to post

Share on other sites

With a fresh linux install on the RPI3, I was able to load Flirc and the flirc_util.

The status is ok (now). Prior to the firmware update it had some very "interesting" responses for flirc_util test
I can program the keys in Linux, so the flirc_util program is picking up the IR commands sent from the remote.

flirc_util keys shows the keys programmed to letters, e.g. play is mapped to w.

The problem is, pressing the play key is not generating a w and sending it to bash.
So no keystrokes are being translated and sent to the OS.

The Flirc driver must be working as the util program can read the commands sent and can tell when a remote button has already been programmed.

How do I get the keystrokes to be sent to the device, like a keyboard? (Like it used to...)

You go to your other PC, and ssh into it. When you press on your remote control buttons, they don't show up in your SSH remote session, is that right?

If so, that's actually expected. The SSH session is a virtual console into the machine. Your mouse and keyboard are plugged into the machine, and on another 'virtual console'. Actually the display manager. Whatever is showing up on the HDMI interface, is assigned to this same virtual console (display manager 0). You wont see keystrokes unless you are looking at the monitor.

You go to your other PC, and ssh into it. When you press on your remote control buttons, they don't show up in your SSH remote session, is that right?

If so, that's actually expected. The SSH session is a virtual console into the machine. Your mouse and keyboard are plugged into the machine, and on another 'virtual console'. Actually the display manager. Whatever is showing up on the HDMI interface, is assigned to this same virtual console (display manager 0). You wont see keystrokes unless you are looking at the monitor.

Thank you for the response.

The only challenge is that it USED to show up on logging in via SSH.
And I had/have a script that would then match those keystrokes to MPD commands.
That user would autologin on boot and the script would run, catching the keystrokes coming from the remote/Flirc.

Will check with the HDMI connected and see if it is showing up in that terminal session.

If it is a keyboard, why would it NOT be available in an SSH session as a "keyboard"?
And more importantly, why would it not be available after a firmware upgrade?