I would like to know if it is possible to configure the Remote Two so that the ‘hardware’ buttons are always linked to the TV remote control?
This means that the screen can only be operated by touch, but the real buttons on the remote control are always linked to the TV, regardless of the screen and the status of the remote control.
I want to be able to pick up the Remote Two and operate the TV directly without having to switch to a special screen first.
Is there any way to do this?
No. Not even posible on any universal remote for that matter. Unless you’re talking like an old school analog universal remote. The Harmony can’t do this either. You have to either be inside of an activity or inside of a device. When running either of the latter, this is possible. You just need to map each button to the TV functions you want.
Hi,
perhaps something which is quite near. Configure a watch TV activity and map the power button to the Power Toggle of the TV and all other had keys to the TV as well. In early firmware versions remapping the power button had the effect that the activity could not be stopped with the power button. I do not know if it is still the case.
Ralf
Why not map buttons to same functions regardless what action is on?
As an example I have same buttons for subwoofer up/down, volume up/down, mute/subwoofer mute and so on. Yes, takes a few minutes to set up but also yes, works like a charm.
Some of the hardware buttons seem to stay as their last configured state when no activity is running.
For example, I have the hardware volume buttons configured to control a sonos soudbar via the integration. I don’t have any other activity where they are configured differently. So when the speaker is playing music from an external source and none of the activities are running on the remote. I can still pick up the remote and press the volume buttons to control the soundbar without starting and activity.
Interesting. I didn’t think any of the buttons worked outside of an activity or device. Guess I never tried though.
Configure the button mapping on normal pages outside of activities will be possible with the new web configurator. It’s mentioned at 8:15 in this longer video about the new configurator linked in one of the Kickstarter updates: https://www.youtube.com/watch?v=bcGJH8z9hM8&t=496s
The question is, when will we see the new configurator?
At least it could slowly appear in the beta firmware.
A beta was announced for Q3 and the Kickstarter update from Wednesday says infos will be released very soon. I suspect it will be at the announced Q&A on October 12th.
It is now mid-November and there is still no beta of the new configurator.
So the term ‘soon’ doesn’t quite fit here.
Q3 is also over.
I guess the release was shifted to November 2024. At least that’s what it says (quite hidden) in the core-simulator docs (core-simulator/docker at main · unfoldedcircle/core-simulator · GitHub).
Not sure why UC is so reserved with updating their software roadmap and inform the users. Maybe they’re in fear of a backlash when something gets shifted but they should have noticed by now that the current communication strategy can lead to the same problems.
1 Like
Or worse.
Honesty and openness is the best policy.
1 Like
November is over halfway gone.