Spec-first async Python client for madVR Envy IP Control.
This project intentionally does not inherit implementation patterns from existing community libraries. It is being built from the official Envy IP Control specification and protocol captures.
- Typed command helpers in
madvr_envy.commands - High-level async client in
madvr_envy.client.MadvrEnvyClient - Typed protocol parser in
madvr_envy.protocol
Example:
import asyncio
from madvr_envy.client import MadvrEnvyClient
async def main() -> None:
client = MadvrEnvyClient(host="192.168.1.100")
await client.start()
await client.wait_synced(timeout=10)
snapshot = await client.refresh_device()
print(snapshot.power_state, snapshot.incoming_signal, snapshot.aspect_ratio)
await client.get_mac_address(wait_for_ack=True)
await client.display_message(3, "Hello from py-madvr-envy")
await client.change_option("temporary\\hdrNits", 120)
groups = await client.enum_profile_groups_collect()
for group in groups:
print(group.group_id, group.name)
await client.stop()
asyncio.run(main())- Source:
https://madvrenvy.com/wp-content/uploads/EnvyIpControl.pdf - Document title:
madVR Envy IP Control revision 1.1.3 - Retrieved: 2026-02-27
- HTTP metadata observed during retrieval:
Last-Modified: Mon, 20 May 2024 02:40:13 GMT
uv sync --group dev
uv run ruff check .
uv run ruff format --check .
uv run ty check madvr_envy
uv run pytest -vSee docs/PROTOCOL_COVERAGE.md for implemented command and notification coverage.
For stream enumerations, use typed collectors:
enum_profile_groups_collect()enum_profiles_collect(profile_group)enum_setting_pages_collect()enum_config_pages_collect()enum_options_collect(page_or_path)
These helpers wait for protocol end markers and raise EnumerationTimeoutError if an end marker is not observed in time.
Use client.refresh_device() when an integration needs a complete, typed view of the device. The client owns the protocol request sequence for runtime telemetry, video geometry, temperatures, and profiles, then returns an EnvyDeviceSnapshot.
Use EnvyRuntime for long-running control-system integrations that need reliable video geometry:
from madvr_envy import EnvyRuntime, MadvrEnvyClient, RefreshPolicy
client = MadvrEnvyClient(host="192.168.1.100")
runtime = EnvyRuntime(
client,
policy=RefreshPolicy(
volatile_video_interval=5.0,
geometry_debounce=0.75,
stale_after=15.0,
),
)
runtime.subscribe(lambda snapshot: print(snapshot.video.trusted, snapshot.video.masking_ratio))
await runtime.start()EnvyRuntime keeps volatile video state fresh without continuously refreshing static catalogs. It reacts to push notifications, debounces display changes, polls signal/geometry while awake, clears geometry on NoSignal, and marks stale geometry untrusted.
For lower-level streaming consumers, madvr_envy.adapter.EnvyStateAdapter converts mutable runtime state into immutable snapshots plus typed deltas/events:
You can wire this directly through the client:
from madvr_envy.adapter import EnvyStateAdapter
adapter = EnvyStateAdapter()
def on_update(snapshot, deltas, events):
...
handle = client.register_adapter_callback(adapter, on_update)
# later: client.deregister_adapter_callback(handle)