Ryan Malloy
df8b6128ea
Pytest harness (in-process HA + MockPanel)
==========================================
pyproject.toml — bumps requires-python to 3.14.2 to align with HA 2026.5.x
which is what pytest-homeassistant-custom-component pins. Dev group 'ha'
pulls the harness; .python-version updated to 3.14.
src/omni_pca/mock_panel.py — Thermostat (6) and Button (3) RequestProperties
handlers added (previous commit). Without these the HA coordinator's
discovery walk produced empty thermostat/button dicts.
custom_components/omni_pca/services.py — fix CONF_ENTRY_ID import: HA
exports it as ATTR_CONFIG_ENTRY_ID, not CONF_ENTRY_ID. Aliased on import.
tests/conftest.py — re-enables sockets globally (the HA harness installs
pytest_socket which otherwise blocks our network e2e tests).
tests/ha_integration/ — new directory with full HA boot harness:
conftest.py:
- autouse enable_custom_integrations so HA loads our component
- autouse expected_lingering_tasks=True (background event listener)
- autouse _short_scan_interval (1s instead of 30s for fast tests)
- panel fixture: MockPanel on a random localhost port for each test
- configured_panel fixture: builds a MockConfigEntry, runs setup,
yields, then unloads on teardown so the coordinator's reader task
and OmniClient socket close cleanly (otherwise verify_cleanup hangs)
test_setup.py — 12 tests:
- integration loads + system_info populated
- alarm_control_panel/light/switch/climate/button/event/binary_sensor
entities materialise per platform
- unload_entry tears down cleanly
- turning a light on via HA service updates the mock state
- arming via HA service with the right code transitions the area
- arming with wrong code keeps the area disarmed and surfaces error
Total: 351 passed, 1 skipped (PCA fixture). Ruff clean across src/ tests/
custom_components/. The 12 HA integration tests run in <1s end-to-end —
they boot HA in-process, drive the config flow, exercise services, and
verify state mutations on the mock side.
Docker dev stack (manual smoke / screenshots)
=============================================
dev/docker-compose.yml — HA 2026.5 container + MockPanel sidecar.
dev/run_mock_panel.py — long-running mock with a populated state
(5 zones, 4 units, 2 areas, 2 thermostats, 3 buttons, codes 1234/5678).
dev/Makefile — make dev-up / dev-logs / dev-down / dev-mock / dev-reset.
dev/README.md — onboarding walkthrough (host=host.docker.internal,
port=14369, controller_key=000102030405060708090a0b0c0d0e0f).
.gitignore — adds ha-config/ so the persisted HA state from the dev
stack doesn't get committed.
55 lines
1.8 KiB
Markdown
55 lines
1.8 KiB
Markdown
# Dev stack
|
|
|
|
Local Home Assistant + MockPanel for clicking around the integration without a
|
|
real Omni controller. Useful for screenshots, manual smoke tests, and seeing
|
|
what the entity layout looks like.
|
|
|
|
## Quick start
|
|
|
|
```bash
|
|
cd dev/
|
|
make dev-up # docker compose up -d
|
|
# wait ~30s for HA to boot
|
|
open http://localhost:8123
|
|
```
|
|
|
|
First time: HA onboarding wizard (any name / location works). Then:
|
|
|
|
1. **Settings → Devices & Services → Add Integration**
|
|
2. Search for **HAI/Leviton Omni Panel**
|
|
3. Fill in:
|
|
- host: `host.docker.internal`
|
|
- port: `14369`
|
|
- controller key: `000102030405060708090a0b0c0d0e0f`
|
|
4. Submit. Within a few seconds you should see the Omni Pro II device with
|
|
~25 entities (binary sensors, lights, alarm panel, climate, sensors,
|
|
buttons, switches, the events entity).
|
|
|
|
## What the mock simulates
|
|
|
|
Five named zones, four units, two areas, two thermostats, three button
|
|
macros. User codes `1234` (master, code index 1) and `5678` (code index 2).
|
|
|
|
Arming the alarm with code `1234` will succeed and the
|
|
`alarm_control_panel` entity transitions through ARMING → ARMED_AWAY in
|
|
real time via the panel's push-event simulation. Wrong code → HA error
|
|
toast, panel stays disarmed.
|
|
|
|
## Other targets
|
|
|
|
```bash
|
|
make dev-logs # tail HA + mock logs
|
|
make dev-mock # run only the mock on the host (no docker)
|
|
make dev-down # stop the stack
|
|
make dev-reset # wipe HA config and start fresh
|
|
```
|
|
|
|
## Notes
|
|
|
|
- The HA container mounts `../custom_components/omni_pca/` read-only, so
|
|
edits to the integration need a restart (`docker compose restart
|
|
homeassistant`) to take effect.
|
|
- The mock panel binds `0.0.0.0:14369` inside the container. If you
|
|
prefer to talk to it from the host directly (e.g. with `omni-pca`
|
|
CLI), use `make dev-mock` to run it natively.
|