Button Long Press - Beta Test Group #477
Replies: 6 comments 16 replies
-
|
Long press did not work for me. Let me know if there is something I need to change in the yaml if I use an existing Firemote remote setup. Media Player Device Type: Nvidia Sheild Pro (2019) |
Beta Was this translation helpful? Give feedback.
-
|
No problem! I REALLY appreciate that you took the time to try this beta! |
Beta Was this translation helpful? Give feedback.
-
|
@qwerty13547 ~ v4.0.0b3 was just released, and it has that DPad support you were looking for. 😄 |
Beta Was this translation helpful? Give feedback.
-
|
Sweet! Good work👍 It work, but may still need some tweaking. Setup as above. Nvidia shield remote in YouTube app.: Long press on center button on D pad open the action screen for the video. Firemote 4.0.03b in YouTube app: Long press on center button on D pad does not work as intended, it starts playing video as a single press would. I imagine that it takes longer time to engage long press then Shield need to get the instruction to open the action screen for the video. So it se it as a single press. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the detail @qwerty13547!
Based on what you've experienced, am I correct to assume that you haven't connected to your Shield with the Android TV Remote Integration as well? If that's true, what's happening "under the hood" in this type of configuration is that Firemote is actually repeatedly sending the ADB command "left", "right", "up", or "down" 4 times every second. (actual code here) No matter how fast or slow this command is repeated, it seems that the fastest response the Shield will provide is what you are seeing now. It's slow, but that's why we have the Android TV Remote Integration! Adding this to your Firemote configuration will drastically improve performance! help: Why do I still need the ADB integration when there is an Android remote integration?
When using both of them like this, the "long press" strategy changes. In this configuration, we have a new option. The Android TV Remote Integration allows us to specify a duration of how long to hold the button down. After detecting a "long press" on the dashboard, Firemote v4.0.0b3 sends the "up", "left", "right", or "down" command with a 0.5 second "hold down" time. After 0.5 seconds has passed, Firemote checks to see if you are still holding the button down. If so, it sends another 0.5 seconds hold down command to your Shield and will continue to check until you release the button. (actual code here) Summary:
This is part of what was documented in the chart above at id 07. When only an ADB entity is defined, there is no such thing as a "hold". All of the documentation and help threads say there should be, but for whatever reason it is ignored. So, as noted above, I've opted to do the only thing I could: repeat the button press command 4 times per second. This is why you saw your Shield behave as if the center button was just clicked. (actual code here) However, when adding the Android TV Remote Integration we gain the ability to tell the Shield that we want a long press. Pressing and holding the center button in Firemote with the Shield in my lab while using YouTube does work as expected. (actual code here) So @qwerty13547, I invite you to add the Android TV Remote Integration to your Home Assistant, configure your Shield, and test once again! THANKS AGAIN for your help with the testing here! I hope to hear from you again soon! -Doug |
Beta Was this translation helpful? Give feedback.
-
|
@qwerty13547 ~ I'm curious if you've given this a try yet. Do you have any updates? |
Beta Was this translation helpful? Give feedback.
-
|
Firemote beta version v4.0.0b2 was just released. Nothing from the chart above has been updated since beta 1, but I would prefer that you test against this new beta 2 version. |
Beta Was this translation helpful? Give feedback.
-
|
Firemote beta version v4.0.0b3 has just been released. This one has support for dpad longpress actions, as well as some important internal hints for your dashboard if you're experimenting with the new "sections" layouts. Please see the updated chart at the top of this discussion for additional details. I'd love to hear from you! |
Beta Was this translation helpful? Give feedback.
-
|
Hi, |
Beta Was this translation helpful? Give feedback.
-
|
Greetings @Christarr2308! The problem you are describing was already captured in the chart above at id 01. This is a known issue that was introduced with HA 2024.08.0 and it mostly affects iPads. The Firemote code isn't directly to blame for the change. The good news is that for the past week, a group of very smart people have been working to track down the problem, and a fix for this issue should be published very soon. For more information, take a look here #478 -Doug |
Beta Was this translation helpful? Give feedback.
-
|
As a followup, this rendering issue has been fixed in the latest iPad Companion app, version 2024.8. Simply download the latest version from the App Store if you haven't done so already, and you will be ready to go! |
Beta Was this translation helpful? Give feedback.
-
It's ready!!Good news everyone! Firemote beta version v4.0.0b4 has just been released. This latest beta contains all of the planned long press functionality, and completes the chart at the top! This IS the release candidate! Please download this new beta and let me know if you find anything wrong. If not, it will be published soon! Thanks in advance, everyone! |
Beta Was this translation helpful? Give feedback.
-
It's out!I decided to launch it today. 😄 Long press support is now available in the official release of Firemote version v4.0.0 |
Beta Was this translation helpful? Give feedback.
-
|
I first attmpted to long press the center button. This resulted in the TV registering multiple clicks of the center button (as if I was tapping it over and over in rapid succession) |
Beta Was this translation helpful? Give feedback.
-
|
Gotcha! I think what is happening is that you have your configuration set to Strong instead of the default for your device: If that's the case, then the repeating button press is the only method that will work to simulate a "hold". (ID 7 on the chart above) The good news is that Amazon Fire products are the ONLY ones right now with actual support for "button down command" (wait for USER to release Firemote button "button up command" With two exceptions, that family of devices actually has the BEST support for button hold! Give "Default" a try, and let me know if that works better for you. |
Beta Was this translation helpful? Give feedback.
-
|
Ahh that makes sense, I do have strong set but its intentional. On my firecube the default did not work. However following the instructions I found that "event 13" (iirc) worked. But then, as also mentioned in the documentation, when I would turn the tv on with the firemote, I would need to press a button on the physical remote before the dpad buttons would work. I found that when using "strong" it would alleviate this limitation. Albeit its a little slower as also indicated, but definitely still usable. So for my usecase I would rather sacrifice the speed over the need to press the physical remote when turning on. And even if the center press won't work on strong mode, I think for my usecase it still works better because then I don't have to try and find the remote =) Although now that makes me think, what if I had a single button that sent a command in strong mode, while the rest of the buttons are "event 13"...I wonder if that would wake up the firemote or does it have to be a physical remote button press? Either way thanks for your help, and please let me know if I misunderstood anything regarding the limitations and my preference |
Beta Was this translation helpful? Give feedback.
-
|
You understand fully! Firemote is bound by the capabilities of the Home Assistant integrations.
I wish... I tried and failed at that task |
Beta Was this translation helpful? Give feedback.
-
|
Ahh damn, thanks for the info! I'll take not having to wake up the remote over having long press. |
Beta Was this translation helpful? Give feedback.
-
🎉 Beta Testing For Button Long Press Has Arrived! 🥳
I have just published the first beta version of Firemote that supports button push and hold, also known as long press! Now, I need your help to test it all out before the official release!
How can you help?
After downloading the newest beta version, please compare the differences between how your physical remote reacts to long press events, and how Firemote reacts to those same events. If everything is working properly, or you find an issue that's not mentioned in the "Known Issues / Limitations" section below, please let me know in this discussion thread right away.
I request that your reports contain the following information:
Known issues / Limitations
This chart will be actively updated as testing continues.
01yesiPad OS Companion AppFiremote rendering is messed up / unusable - Follow the progress here #47805yesAllDPad direction buttons (up, right, down, left) do not have long press support07Chromecast, Onn, Shield, XiaomiDpad center/select button hold is not supported in "strong" mode unless an Android TV remote entity is definedCompromised with a simulated repeat press of the button08unknownRokuReplay button long press is not supported. Roku integration limitation - issue 123999 has been opened to address itCompromised with a simulated repeat press of the button09AllRewind & Fast Forward buttons do not have long press support10Most - Some Fire TV Devices gained support in beta 3Volume up and Volume down buttons do not have long press support11Amazon Fire, RokuChannel up and Channel down buttons do not have long press supportThank you all in advance for your help! I know that many of you have been waiting a long time for this, so I appreciate your continued patience and partnership with this update.
~ Tagging potentially interested users ~
@efiniste @mizuxe @electroflame @janstadt @dasadavid @darrenhomme
Sorry if I missed you and/or if I included you and you didn't want to be included
Beta Was this translation helpful? Give feedback.
All reactions