majordom-integration-sdk
Models, protocols, and tooling for building MajorDom integrations.
An integration bridges an external protocol or platform (Matter, Zigbee, HomeKit, a vendor
cloud, …) into the MajorDom language. This SDK is the contract: the schemas, the
AbstractController framework, the device-repository protocol, discovery services, and a
standalone dev runner so you can build and test an integration without a running Hub.
The Hub itself depends on this same package — first-party integrations use no private
shortcut.
Install
pip install majordom-integration-sdk
Requires Python 3.12+.
Also a standalone IoT toolkit
You don't need MajorDom to get value from this package. majordom_integration_sdk.discovery
ships three fully working, standardized device-discovery services you can drop into any
async Python project:
- Zeroconf / mDNS (
ZeroconfDiscoveryService) — browse Bonjour/mDNS services with a clean listener protocol, and — unusually — reliable disappearance tracking: it augments raw zeroconf with an active cache-poll + confirm-evict loop so you get accurate "device went away" events, not just arrivals. - SSDP / UPnP (
SSDPDiscoveryService) — flexible, per-listener configurable search targets and refresh behavior over raw sockets, without dragging in a full UPnP stack. - BLE (
BLEDiscoveryService) — a uniform listener interface over Bleak for advertisement scanning.
All three share one register(listener, …) → cancel shape, run standalone (each module has a
runnable __main__ demo), and are a solid reference for implementing standardized
interfaces over messy IoT protocols even if you never touch MajorDom. The
AbstractController framework and the DeviceRepositoryProtocol + in-memory/SQLite
implementations are equally reusable as a small, typed device-modelling toolkit.
Documentation
Full integration-author docs — models, the controller lifecycle, storing data, discovery, and a worked example — live at docs.majordom.io.
The fastest way to start a new integration is the integration-template repository (Use this template → Create a new repository).
License
See LICENSE. For commercial licensing or partnership inquiries, contact us via parker-industries.org/partnership.
Development
Setup:
poetry install && poetry run poe install
This installs dependencies and the pre-commit hook that runs poe check.
| Task | Description |
|---|---|
poe install |
Install deps and register the pre-commit hook |
poe check |
Full quality pipeline (ruff, ty, pytest, poetry build/check) |
poe check --ci |
Same, plus git diff --exit-code |
Two long-lived branches: develop (integration branch, all work lands here) and master
(protected, released). Releases are cut from develop via Actions → Release; see
ParkerIndustries/workflows for the CI/CD.
Metadata
Release files for majordom-integration-sdk 0.2.1
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 | |
|---|---|---|---|---|
| majordom_integration_sdk-0.2.1.tar.gz | 53.2 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| majordom_integration_sdk-0.2.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 117.7 kB
Release files / majordom_integration_sdk-0.2.1.tar.gz
| Download URL | majordom_integration_sdk-0.2.1.tar.gz |
|---|---|
| Size | 53.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d2da48c76d15b2e712fd7708e5413a549c67508d7c6a72d9c95282bc54f03ea6
|
|
BLAKE2b-256 checksum How to use checksums |
bf6bdb4a30a856d1262cddc2c94a09747eb7541fa7f690359851c62d02840d3a
|
| 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 / majordom_integration_sdk-0.2.1-py3-none-any.whl
| Download URL | majordom_integration_sdk-0.2.1-py3-none-any.whl |
|---|---|
| Size | 64.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2c05da5ea7de0933066a288f9f389161cf9ee4efb5ee4cddff87538e63ca4ed2
|
|
BLAKE2b-256 checksum How to use checksums |
921b827db384624ec4d3231e1cfd1b3f74c1dadc8176422ce47315ef794977a8
|
| 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 majordom-integration-sdk 0.2.1
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 majordom_integration_sdk-0.2.1.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.