-
-
Notifications
You must be signed in to change notification settings - Fork 630
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for channel up and down tv remote #941
Comments
I think this layout is only for apple tv (and maybe official certified tvs with siri?) and not for tv accessories |
It’s AppleTV only. The Remote widget shows my new Sony TV with native HomeKit support just like the Homebridge TV accessories. |
Thanks for clearing this out. |
For Homebridge TVs, you can map these to the up and down, or to the left and right “buttons”. |
Is that a HAP-NodJS based TV you are showing? We have lost if known Keys/Buttons here
there are some blanks we don’t know yet about (12-14) this defines which keys are supported
|
Do we have any update here? |
Following. Be interested to see an update that might allow leveraging these newly exposed items |
I did set the Accessibility setting and am now seeing channel buttons for my Sonos TV as well as for the TVs from Homebriige ZP. They don't seem to do anything, though (iOS 17.6.1 on my iPad). When pressing the Channel Up button, the Arrow Down button activates (which it also does when pressing that area on the widget without the accessibility area. When pressing the Channel Down button, nothing happens. |
FYI to all: from iOS 18, the Mute and Power buttons in the iOS Remote for non-Apple-TVs now work and trigger changes in Characteristic.Mute and Characteristic.Active |
Current Situation
The channel up/down buttons for the tv remote are not available.
This is new in ios 15 for the apple tv remote in the control centre.
Proposed Change
Support for the channel up/down buttons in the new ios 15 remote.
An addition of a Buttontype.
Additional Context
No response
The text was updated successfully, but these errors were encountered: