diff --git a/source/_integrations/homekit.markdown b/source/_integrations/homekit.markdown
index 7963487d5d1..60db1f97b50 100644
--- a/source/_integrations/homekit.markdown
+++ b/source/_integrations/homekit.markdown
@@ -87,6 +87,11 @@ homekit:
         description: The local network IP address. Only necessary if the default from Home Assistant does not work.
         required: false
         type: string
+      mode:
+        description: HomeKit can expose an entity via a bridge, or a single entity as an accessory which is needed for Television Media Players. ([Accessory mode](#accessory-mode))
+        required: false
+        type: string
+        default: '`bridge`'
       safe_mode:
         description: Only set this parameter if you encounter issues during pairing. ([Safe Mode](#safe-mode))
         required: false
@@ -297,6 +302,16 @@ If you create a HomeKit integration via the UI (i.e., **Configuration** >> **Int
 
 It is recommended to only edit a HomeKit instance in the UI that was created in the UI, and likewise, only edit a HomeKit instance in YAML that was created in YAML.
 
+### Accessory mode
+
+When exposing a Television media player (a `media_player` with device class `tv`) to HomeKit, `mode` must be set to `accessory`, and the include filter should be setup to only include the `media_player` entity. This can be accomplished in the UI with the following steps.
+
+1. Create a new bridge via the UI (i.e., **Configuration** >> **Integrations**)
+2. Before pairing the bridge, access the options for the bridge.
+3. Change the mode to `accessory`
+4. Select the `media_player` entity with the `tv` device class.
+5. Complete the options flow and pair as normal.
+
 ## Disable Auto Start
 
 Depending on your setup, it might be necessary to disable `Auto Start` for all accessories to be available for `HomeKit`. Only those entities that are fully set up when the `HomeKit` integration is started, can be added. To start `HomeKit` when `auto_start: false`, you can call the service `homekit.start`.