MX Remote - Python Client for Pulse-Eight MatrixOS devices
Python 3 library for discovering and controlling Pulse-Eight AV distribution hardware over a local network: video/audio matrices, HDMI-over-IP encoders/decoders, multiviewers, and audio amplifiers. Supports device discovery, video/audio routing, volume control, remote-control key passthrough, HDMI-over-IP streaming, multiviewer control, and more.
If you are looking to integrate Pulse-Eight neo, OneIP, or ProAmp8 devices into your own software or home-automation system, this is the library for it.
Documentation: opdenkamp.github.io/mx-remote
What is MX Remote?
MX Remote is the network protocol these Pulse-Eight devices use to discover and control one another over UDP (multicast or broadcast). All of them run the shared MatrixOS firmware, which speaks this protocol natively. This library is a client implementation of that protocol — its purpose is to expose the devices to third-party software.
Supported devices
All devices below run MatrixOS and are controlled through the same protocol:
- Pulse-Eight neo — HDBaseT video/audio matrices (neo:4, neo:8, neo:X, and splitters)
- Pulse-Eight OneIP — HDMI-over-IP units: Transmitter (TX), Receiver (RX), Transceiver (TZ), and Multiviewer
- Pulse-Eight ProAmp8 — 8-zone audio amplifier with Dolby support
Requirements
- Python 3.11 or later
- Network access to one or more of the Pulse-Eight devices above (multicast or broadcast)
Installation
pip install .
Quick Start
The minimum code to discover devices on the network:
import asyncio
import mx_remote
async def main():
mx = mx_remote.Remote()
await mx.start_async()
# wait for devices to be discovered
await asyncio.sleep(5)
for uid, device in mx.remotes.items():
print(f"{device.serial} ({device.name}) - {device.model_name} - {device.status}")
for port, bay in device.bays.items():
print(f" {bay.bay_label} [{bay.mode}] signal={bay.signal_detected}")
await mx.close()
asyncio.run(main())
Documentation
The guides below are published at opdenkamp.github.io/mx-remote alongside an API reference generated from the docstrings, and are readable here in docs/.
| Page | Covers |
|---|---|
| Configuration | Opening a connection and keeping it in step with the mesh. |
| Devices and bays | Naming, hiding, EDID and the device registry. |
| Routing | Selecting video and audio sources for an output. |
| Callbacks | Reacting to state changes rather than polling for them. |
| Audio | Volume, mute and remote-control passthrough. |
| OneIP | Streaming endpoints, stream sources and statistics. |
| Multiviewer | Layout, sources and output configuration. |
| Diagnostics | Network status, the mxr console app and capture replay. |
Other languages
The same protocol, implemented independently:
- Go — https://github.com/opdenkamp/mx-remote-golang
- Rust — https://github.com/opdenkamp/mx-remote-rust (also ships a C ABI, for C and C++)
Python is the oldest of the three and the one that still decodes what older
firmware sent: 0x06, 0x36 and 0x47 are superseded opcodes kept because a
unit on older firmware still emits them. So it decodes a slightly wider set than
the others, and the difference is deliberate rather than drift.
License
BSD 3-Clause License. See LICENSE for details.
1 maintainer
Metadata
1 maintainer
Release files for mx-remote 9.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| mx_remote-9.1.0.tar.gz | 380.9 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mx_remote-9.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 710.4 kB
Release files / mx_remote-9.1.0.tar.gz
| Download URL | mx_remote-9.1.0.tar.gz |
|---|---|
| Size | 380.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f01baa1001ede518dcd809e15e706cbd61292068420c98ff1119e4f265cc506c
|
|
BLAKE2b-256 checksum How to use checksums |
9947ec1027f396c768f5064a222d724165f7a3254faa9e477331709ef9a070ac
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logRelease files / mx_remote-9.1.0-py3-none-any.whl
| Download URL | mx_remote-9.1.0-py3-none-any.whl |
|---|---|
| Size | 329.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c778d4c814b2cf4f500bae3cc1d528b24180c78595ac2b4462bcf84ef39cd185
|
|
BLAKE2b-256 checksum How to use checksums |
15bb7b03e806436fe719404c5bafbaf9621497386ae56c686cf1a41f3dd20847
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logSecurity for mx-remote 9.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for mx_remote-9.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
