From f5a8eaaf08884b2e0b360f775acb5ea5db55861e Mon Sep 17 00:00:00 2001
From: "J. Nick Koston" <nick@koston.org>
Date: Sun, 23 May 2021 15:30:40 -0500
Subject: [PATCH] Add Pairing with an insecure setup code section (#17937)

---
 source/_integrations/homekit_controller.markdown | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/source/_integrations/homekit_controller.markdown b/source/_integrations/homekit_controller.markdown
index e24876d3b2c..ef9e114aa22 100644
--- a/source/_integrations/homekit_controller.markdown
+++ b/source/_integrations/homekit_controller.markdown
@@ -103,6 +103,10 @@ When you have filled in the rest of the form to create your migration it will sh
 <img src='/images/integrations/homekit_controller/device_automation_finish.png' />
 </p>
 
+## Pairing with an insecure setup code
+
+Some device manufacturers do not follow the HomeKit spec and will use a fixed code or trivially guessable code such as `123-45-678` for pairing. HomeKit Controller will warn when pairing about the insecure nature of this configuration and require additional consent before pairing with the accessory. Consider finding a replacement device that implements code randomization.
+
 ## Troubleshooting
 
 ### I don't have a HomeKit PIN