You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for clearing this out.
It's just a pity that the most used function of a tv remote (channel up/down) is not available.
Or maybe I'm just to old-skool...
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
Updating this since it has been quiet for a long time, and the reason is worth stating plainly.
The blocker is not effort, it is evidence. RemoteKey currently defines values 0 to 11 plus 15 for Information, which leaves an unexplained gap at 12, 13 and 14. That gap is suggestive, and channel up and down would be a natural fit for it — but suggestive is not the same as known. Adding enum values on a guess would be worse than leaving the gap, because plugins would start sending numbers that HomeKit may simply ignore, and we would then be stuck supporting them.
What would move this forward is confirmation of the real values: either documentation of the HAP characteristic, or a capture from a certified accessory or the Home app showing what it actually sends when those buttons are pressed.
Leaving this open rather than closing it, since the interest here is genuine and the gap is real. If anyone can supply that evidence, it becomes a small change.
Activity
ferensw commentedon Apr 15, 2022
Like this:
seydx commentedon Apr 17, 2022
I think this layout is only for apple tv (and maybe official certified tvs with siri?) and not for tv accessories
ebaauw commentedon Apr 17, 2022
It’s AppleTV only. The Remote widget shows my new Sony TV with native HomeKit support just like the Homebridge TV accessories.
ferensw commentedon Apr 18, 2022
Thanks for clearing this out.
It's just a pity that the most used function of a tv remote (channel up/down) is not available.
Or maybe I'm just to old-skool...
ebaauw commentedon Apr 18, 2022
For Homebridge TVs, you can map these to the up and down, or to the left and right “buttons”.
thelofts commentedon Jun 23, 2023
iOS 17 - Channel Up/Down and Menu buttons are in all TVs now (i wish it isn’t just beta bug)


How to use HAP to catch the press of those?
bauer-andreas commentedon Jun 29, 2023
Is that a HAP-NodJS based TV you are showing?
We have lost if known Keys/Buttons here https://github.com/homebridge/HAP-NodeJS/blob/9c9bd7101b2ab520a237c09da8017d18a5c2c7cc/src/lib/definitions/CharacteristicDefinitions.ts#L3078
there are some blanks we don’t know yet about (12-14)
this defines which keys are supported https://github.com/homebridge/HAP-NodeJS/blob/9c9bd7101b2ab520a237c09da8017d18a5c2c7cc/src/lib/definitions/CharacteristicDefinitions.ts#L3088. If channel keys don’t show with current HAP-NodeJS versions they are maybe located at >15 key ids.
tavicu commentedon Oct 20, 2023
Do we have any update here?
n0rt0nthec4t commentedon Nov 23, 2023
Following. Be interested to see an update that might allow leveraging these newly exposed items
ebaauw commentedon Aug 14, 2024
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.
jsiegenthaler commentedon Sep 22, 2024
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
bwp91 commentedon Jul 27, 2026
Updating this since it has been quiet for a long time, and the reason is worth stating plainly.
The blocker is not effort, it is evidence.
RemoteKeycurrently defines values 0 to 11 plus 15 for Information, which leaves an unexplained gap at 12, 13 and 14. That gap is suggestive, and channel up and down would be a natural fit for it — but suggestive is not the same as known. Adding enum values on a guess would be worse than leaving the gap, because plugins would start sending numbers that HomeKit may simply ignore, and we would then be stuck supporting them.What would move this forward is confirmation of the real values: either documentation of the HAP characteristic, or a capture from a certified accessory or the Home app showing what it actually sends when those buttons are pressed.
Leaving this open rather than closing it, since the interest here is genuine and the gap is real. If anyone can supply that evidence, it becomes a small change.