You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
SageTV MiniClient v1.2.12
SheildTV 2017
FLIRC IR receiver
ProntoPro TSU-9600
Issue: The "Enter/OK" button from my IR remote does not get properly recognized by the SageTV Miniclient about 75% of the time.
The FLIRC "OK/Enter" button works perfectly fine with the ShieldTV for every other application except on the SageTV MiniClient. It would seem that the ShieldTV can read the OK button just fine from my remote on anything else.
It looks like the SageTV MiniClient isn't handling the Enter/OK button very well when it comes from the FLIRC/USB interface for some reason. The SageTV MiniClient handles a Bluetooth Keyboard Enter Key OK, and it also handles the OK key from the ShieldTV controller without any issues.
The text was updated successfully, but these errors were encountered:
have you tried a version 1.3.1+ (we are 1.3.5 right now). Also, if you enabled the show unmapped keys in the app configuration, what "key" does it show? If it doesn't show an umapped key, then, 1 of 2 of things is happening.
Flirc isn't sending the key
Flirc is sending it, and we are handling it, and sending it to sagetv
Configuration:
SageTV MiniClient v1.2.12
SheildTV 2017
FLIRC IR receiver
ProntoPro TSU-9600
Issue: The "Enter/OK" button from my IR remote does not get properly recognized by the SageTV Miniclient about 75% of the time.
The FLIRC "OK/Enter" button works perfectly fine with the ShieldTV for every other application except on the SageTV MiniClient. It would seem that the ShieldTV can read the OK button just fine from my remote on anything else.
It looks like the SageTV MiniClient isn't handling the Enter/OK button very well when it comes from the FLIRC/USB interface for some reason. The SageTV MiniClient handles a Bluetooth Keyboard Enter Key OK, and it also handles the OK key from the ShieldTV controller without any issues.
The text was updated successfully, but these errors were encountered: