From dbfdc5dd5bcf3cb7d7746b3ff15a5719f2fc323e Mon Sep 17 00:00:00 2001
From: Mark Parker <34688010+MarkParker5@users.noreply.github.com>
Date: Wed, 14 Oct 2026 14:40:29 +0200
Subject: [PATCH] Describe the hardware tests generically

---
 majordom_zigbee/controller.py | 2 +-
 majordom_zigbee/readme.md     | 4 +---
 2 files changed, 2 insertions(+), 4 deletions(-)

diff --git a/majordom_zigbee/controller.py b/majordom_zigbee/controller.py
index 906c01b..f7c4966 100644
--- a/majordom_zigbee/controller.py
+++ b/majordom_zigbee/controller.py
@@ -295,7 +295,7 @@ async def start(self):
         self._application.add_listener(self)
         log.debug("[READY] connected to %s", self._zigbee_device_path)
 
-        # Optionally cap the coordinator's TX power (e.g. RF-quiet cage/hardware testing). Unset =
+        # Optionally cap the coordinator's TX power (e.g. RF-quiet hardware testing). Unset =
         # radio default (full power, for a real home). The radio clamps to its floor.
         tx_dbm = os.environ.get("MAJORDOM_ZIGBEE_TX_DBM")
         if tx_dbm:
diff --git a/majordom_zigbee/readme.md b/majordom_zigbee/readme.md
index 4e3d622..de2eec4 100644
--- a/majordom_zigbee/readme.md
+++ b/majordom_zigbee/readme.md
@@ -48,9 +48,7 @@ id a parameter gets at pairing is identical to the one used on fetch and in live
 
 - `test_zigbee_controller_mocked.py` — an in-memory zigpy stub, no radio or devices needed
   (runs in CI).
-- `test_zigbee_controller_hardware.py` — a real device in the self-hosted IoT cage; manual
-  only. Its hardcoded device/parameter ids must be regenerated for your DUT (see the note
-  at the top of that file).
+- Real-device tests are kept in a private repository and run manually.
 
 ## Notes