Button backlight times out while still using the remote

@David Li So are you saying that if you pick up the remote, the physical button lights come on and if you continuously hit the physical buttons(like searching through a long list of media using the directional arrows) for more than 15 seconds(or whatever your timeout is set to) the physical button lights stay on as long as you're clicking the physical buttons?

I think it's more about if that happens, it doesn't bother me. I haven't ever noticed it happening. Generally, I don't look at the buttons "at all". I look at the TV (like to navigate Roku / Shield / FireTV etc on screen menus). The button illumination provides a bit of focus when the remote is first picked up (and it wakes and lights), but after my hand is on the D Pad, all rest is muscle memory (volume, channel, mute, Left / right / up / down / select).

The primary benefit of a "TV remote control" hardware vs. a smartphone touchscreen is you don't need to look at the most commonly used buttons. One uses muscle memory for repetitive tasks.

Expected is that everyone has their unique needs / uses of a remote control, and Allonis has made it as flexible as possible. I can't believe that the default Channel page scroll isn't a wanted feature by all that use streaming boxes. I use it more than any other function of the remote to go through on TV guides to pick something to watch quickly. Once on that page, I use the up / down to hone in, and then Select.

We are working on a bunch of product features that will be available soon and we can look at the timeout to make that more configurable for the unique needs.

A bit of a counterpoint. For me, the true test of the system is handing the remote to someone who has not used the system at all and they can operate it. So the backlight staying on is key, why? because if they are trying to figure something out or choose something, the remote going dark is an issue.

FYI - the reason I like the Allonis model is that it closely matched my URC system where I could fully automate functions.

I have what I want with Cable TV, hit power, and everything is setup and the right stuff is selected. My next revision will be creating a logical activity start page with the simple on/off and specific activities (Watch Netflix, Watch Amazon Prime, Listen to Music, Play DVD, etc....). What is tripping me up currently is determining the language to use that is both screen-efficient and understandable to the non-user.

From a HW side, the two issues that impact usage are the backlighting (somewhat fixed with the solution you suggested), and the problem where the command is not sent when you pick up the remote (it's not fully awake yet). The second one requires a press...then a second press to get the function to work.

I'm looking forward to the changes coming. You have a very active group here, would it be possible to vet some of the future changes with the group to help you chart a direction forward (priority setting)?

Hi,
Allonis is by far mostly weighed by paying customers needs to set new feature direction.  Many features are directly paid for by someone who wants the capability.
For example, at Infocomm we will show the new "KissCam" and "Look Alike" features that a client wanted.

And, by far, most of that is in the commercial space, not residential.
Many of those wants serve both markets.
The best thing SmartRemote users can do for high priority is to spread the word and help Allonis increase residential business. If you like what you have and want to see more, then, let others know.

thanx for the interest!!!!!T

bowlingbeeg wrote:

@David Li So are you saying that if you pick up the remote, the physical button lights come on and if you continuously hit the physical buttons(like searching through a long list of media using the directional arrows) for more than 15 seconds(or whatever your timeout is set to) the physical button lights stay on as long as you're clicking the physical buttons?
 

This is exactly what happens when you convert the hard buttons to macros that include the WakeUpMyRemote command. To the letter.

It's kind of a janky way to go about implementing it but the bottom line is that it makes the backlight behave exactly how I've envisioned since pretty much day one. It no longer matters if I'm looking through my movie library for 5 seconds or 5 minutes. From a practical perspective when I pick up the remote the backlight turns on and stays on until I'm done with it and then turns off when I set it down. If the backlight does shut off because I haven't pressed a button during the timeout interval the next button press immediately wakes the backlight again regardless of whether the screen is still on or off.

Overall I'm very pleased by how this worked out. I suspect you will be as well. 

bitzerjd wrote:

A bit of a counterpoint. For me, the true test of the system is handing the remote to someone who has not used the system at all and they can operate it. So the backlight staying on is key, why? because if they are trying to figure something out or choose something, the remote going dark is an issue.

FYI - the reason I like the Allonis model is that it closely matched my URC system where I could fully automate functions.

I have what I want with Cable TV, hit power, and everything is setup and the right stuff is selected. My next revision will be creating a logical activity start page with the simple on/off and specific activities (Watch Netflix, Watch Amazon Prime, Listen to Music, Play DVD, etc....). What is tripping me up currently is determining the language to use that is both screen-efficient and understandable to the non-user.

From a HW side, the two issues that impact usage are the backlighting (somewhat fixed with the solution you suggested), and the problem where the command is not sent when you pick up the remote (it's not fully awake yet). The second one requires a press...then a second press to get the function to work.

I'm looking forward to the changes coming. You have a very active group here, would it be possible to vet some of the future changes with the group to help you chart a direction forward (priority setting)?
 

I'm with you here. 100%