Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion majordom_zigbee/controller.py
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down
4 changes: 1 addition & 3 deletions majordom_zigbee/readme.md
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down
Loading