Replies: 8 comments 8 replies
-
|
Greetings @efiniste! You are absolutely right. A longer press on a virtual button in the Firemote card is not something that's easily detected. Since I can't properly detect them, a long or short press is processed the same way as regular click. I've looked into detecting a long press event a few times, but I haven't yet pursued it. Maybe it's time I look at it again? In the meantime, perhaps I can help you with a launcher button customization to give you a working solution while you wait. What kind of device are you using? |
Beta Was this translation helpful? Give feedback.
-
|
Please God do this! Especially for the firemote, I have to tap like 100 times to rewind sometimes, or switch to the official app, or there are buttons that don't work at all because of this, like the 1 and 2 button on the Amazon Fire Style 6, you need to press and hold to program these. Or holding the home button can direct you to a menu for your smart home which can be nice w/Alexa. That said holding the select button is pretty frequently used as well, at least on youtube to add to playlists. Even if there was just a way to do it once through a service call or something so that I could program those 2 buttons on Style Six. Either way the firemote is probably one of my favorite parts of my HASS dash ever, so whatever you do I'm still incredibly grateful, it just feels like the only glaring hole in the setup. |
Beta Was this translation helpful? Give feedback.
-
|
@mizuxe ~ My apologies, I know it's an inconvenience and I'd like to get it working exactly like the physical remote, but I haven't had the time to focus and solve that issue yet. I am VERY happy to read that Firemote is one of your favorite parts of your Home Assistant dashboard! That made my day! 😄 Happily, there ARE solutions to most of the things you listed: 1 and 2 buttons on the Amazon Fire Style 6: Holding the Select Button: Holding the Home Button (or any others): If you need help making these things work, please let me know and I will be glad to help. I just need to know specifically what you are hoping to accomplish, and what kind of device you are controlling. |
Beta Was this translation helpful? Give feedback.
-
|
I'll give this all a go! programming 1 and 2 buttons is such a W, Thank you so much! |
Beta Was this translation helpful? Give feedback.
-
|
HI @PRProd, thanks very much for the quick response. A launcher button would be great. I'm using a Fire TV, device type fire_tv_4_series Steve |
Beta Was this translation helpful? Give feedback.
-
|
Good news @efiniste! I have a Fire TV 4 Series in front of me right now, so I put this simple YAML config together, tested it in YouTube, and it works! type: custom:firemote-card
entity: media_player.fire_tv_192_168_107_88
device_family: amazon-fire
device_type: fire_tv_4_series
compatibility_mode: default
custom_launchers:
- friendly_name: Longpress Select
label: L Select
color: red
background: white
service: androidtv.adb_command
target:
entity_id: media_player.fire_tv_192_168_107_88
data:
command: >-
sendevent /dev/input/event0 1 28 1 && sendevent /dev/input/event0 0 0 0
&& sleep 1 && sendevent /dev/input/event0 1 28 0 && sendevent
/dev/input/event0 0 0 0
app_launch_1: customlauncher Longpress SelectPLEASE REMEMBER to replace my TV's entity ID with yours in both places. |
Beta Was this translation helpful? Give feedback.
-
|
@PRProd Thanks Doug. I'm sorry, I made a mistake on the device type. It's actually a fire_stick_4k in the device type, Fire TV Stick 4k (1st Gen - 2018) on the drop down chooser. The button shows fine in my test card but doesn't have any effect on-screen when pressed. All the other buttons work fine so it's got the correct entity configured. |
Beta Was this translation helpful? Give feedback.
-
|
No problem! Try it this way instead: type: custom:firemote-card
entity: {YOUR ENTITY ID HERE}
device_family: amazon-fire
device_type: fire_stick_4k
compatibility_mode: default
custom_launchers:
- friendly_name: Longpress Select
label: L Select
color: red
background: white
service: androidtv.adb_command
target:
entity_id: {YOUR ENTITY ID HERE}
data:
command: >-
sendevent /dev/input/event4 1 28 1 && sendevent /dev/input/event4 0 0 0
&& sleep 1 && sendevent /dev/input/event4 1 28 0 && sendevent
/dev/input/event4 0 0 0
app_launch_1: customlauncher Longpress Select |
Beta Was this translation helpful? Give feedback.
-
|
Works perfectly. Thanks very much, Doug. Steve |
Beta Was this translation helpful? Give feedback.
-
|
That's great news! Thanks for letting me know! |
Beta Was this translation helpful? Give feedback.
-
|
Hello again Steve! Congrats on getting a NVIDIA Shield! I hope you love it! I know It is my favorite of all of the devices I've owned and tested. In response to your question in the home assistant community discussion board:
You are absolutely right, the command is different. Because of the way the Shield is designed, you will need to use both the ADB integration and the Android TV Remote integration for this solution to work. I assume you've already set your system up that way, otherwise the lag would be unbearable. type: custom:firemote-card
entity: {YOUR SHIELD ENTITY ID HERE}
android_tv_remote_entity: {YOUR SHIELD REMOTE ENTITY ID HERE}
device_family: nvidia-shield
device_type: shield-tv-pro-2019
compatibility_mode: default
custom_launchers:
- friendly_name: Longpress Select
label: L Select
color: red
background: white
service: remote.send_command
target:
entity_id: {YOUR SHIELD REMOTE ENTITY ID HERE}
data:
num_repeats: 1
delay_secs: 0
command: KEYCODE_DPAD_CENTER
hold_secs: 1
app_launch_1: customlauncher Longpress Select
app_launch_2: youtube |
Beta Was this translation helpful? Give feedback.
-
|
Hi Doug. Yes, very impressed with the Shield. Far better to use than the Fire TV, although that may be influenced slightly by the lack of lag now. :) My wife is certainly happier with it! The code above works great with a minor tweak. Hold_secs: 0.5 worked like a standard press of the centre button so I changed the 0.5 to 1 and now it works perfectly. Thanks again, Doug. Really appreciate your work on this. Steve |
Beta Was this translation helpful? Give feedback.
-
|
Excellent! I've updated my YAML from 0.5 to 1 for future visitors to this discussion. On that topic, 0.5 seemed to be the lowest I could go on my end without it behaving like a simple button press, and your experience got me to thinking. Do you have your shield plugged directly into your network through a physical cable, or is it connected over wi-fi? I'm just curious if that might be the difference maker. (honestly not a big deal at all, I'm just curious by nature) |
Beta Was this translation helpful? Give feedback.
-
|
(example added to the wiki) |
Beta Was this translation helpful? Give feedback.
-
|
Yes, my shield is connected over gigabit Ethernet. |
Beta Was this translation helpful? Give feedback.
-
|
Interesting... oh well. Note to self: "Don't try to optimize button hold time" 😄 |
Beta Was this translation helpful? Give feedback.
-
I don't seem to be able to do a "long" press of the ok/centre button when using Firemote. I use this, for example, to bring up context menus in the YouTube app. Is this not working because it's a "virtual" button now? Is it possible to program one of the app buttons to do a long press?
Thanks,
Steve
Beta Was this translation helpful? Give feedback.
All reactions