Skip to content

Support for channel up and down tv remote #941

Open

Description

@ferensw

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

Activity

  1. ferensw commented on Apr 15, 2022

    @ferensw
    Author

    Like this:

    image

  2. seydx commented on Apr 17, 2022

    @seydx
    Contributor

    I think this layout is only for apple tv (and maybe official certified tvs with siri?) and not for tv accessories

  3. ebaauw commented on Apr 17, 2022

    @ebaauw
    Contributor

    It’s AppleTV only. The Remote widget shows my new Sony TV with native HomeKit support just like the Homebridge TV accessories.

  4. ferensw commented on Apr 18, 2022

    @ferensw
    Author

    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...

  5. ebaauw commented on Apr 18, 2022

    @ebaauw
    Contributor

    For Homebridge TVs, you can map these to the up and down, or to the left and right “buttons”.

  6. thelofts commented on Jun 23, 2023

    @thelofts

    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?
    IMG_0168
    IMG_0167

  7. bauer-andreas commented on Jun 29, 2023

    @bauer-andreas
    Contributor

    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.

  8. tavicu commented on Oct 20, 2023

    @tavicu

    Do we have any update here?

  9. n0rt0nthec4t commented on Nov 23, 2023

    @n0rt0nthec4t
    Contributor

    Following. Be interested to see an update that might allow leveraging these newly exposed items

  10. ebaauw commented on Aug 14, 2024

    @ebaauw
    Contributor

    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.

  11. jsiegenthaler commented on Sep 22, 2024

    @jsiegenthaler

    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

  12. bwp91 commented on Jul 27, 2026

    @bwp91
    Contributor

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions