Skip to main content

Pure Python implementation of the Matter IOT protocol.

Project description

CircuitMatter

CircuitMatter is a Python-only implementation of the Matter IOT specification. It is aimed at hobby use and hasn't been certified for commercial use.

The Matter spec originates out of the Connected Home over IP (CHIP) project and some resources still use this naming. Matter is the trademark associated with certification.

Get the Matter Specification

The Matter specification is behind a contact info wall here: https://csa-iot.org/developer-resource/specifications-download-request/ CircuitMatter code is based on version 1.3 and references sections from that version.

You do not need to pay anything or be a member organization.

Running CircuitMatter

CircuitMatter is currently developed in CPython 3.12, the de facto implementation written in C. It is designed with minimal dependencies so that it can also be used on CircuitPython on microcontrollers.

Requirements

After cloning the repo, install flit for packaging:

pip install flit

This project is based on avahi tools. It must therefore be installed for it to work properly.

sudo apt-get install avahi-utils

Do a dev install

flit install -s --deps develop

Running a CircuitMatter replay

CircuitMatter can capture and replay UDP packets and random numbers to ease development. You can test the start of the CircuitMatter process by using the replay file from the repo:

python examples/replay.py test_data/recorded_packets.jsonl

Running for real

To run CircuitMatter against a live Matter commissioner run:

python -m circuitmatter

This will start up MDNS via avahi for discovery by the commissioner and then reply to received UDP packets. CircuitMatter currently doesn't fully commission so it can't act as any specific type of device yet. When it can, there will be examples.

Running a Matter commissioner

chip-tool

The de facto standard implementation of Matter is open source as well. It is written in C++ and has many dependencies. It implements all of the different facets of the specification.

We use this implementation via ESP Matter (tested on commit 9350d9d5f948d3b7c61c8659c4d6990d0ff00ea4) to run an introspectable (aka debug printable) commissioner.

To setup esp-matter clone the repo and load submodules:

git clone -o espressif git@github.com:espressif/esp-matter.git
cd esp-matter
git submodule update --init --recursive .

This will pull down the ESP Matter wrapper code and the projectchip implementation into the connectedhomeip/connectedhomeip/ sub-directory.

To build all of the command line tools run

bash install.sh

(Or source it directly if you use bash.)

Now setup the environment using export.sh. (This depends on what shell you use.)

Next, run chip-tool to initiate the commissioning process:

chip-tool pairing code 1 67202583

This will look up commissionable devices on the network via MDNS and then start that process. 67202583 is the manual pairing code that matches the device state in test_data/device_state.json.

Logs can be added into the chip sources to understand what is happening on the commissioner side. To rebuild, I've had to run bash install.sh again.

Apple Home

The Apple Home app can also discover and (attempt to) commission the device. Tap Add Accessory.

  • By default this will pull up the camera to scan a QR Code. CircuitMatter will print the qrcode to the console to scan.
  • You can also use the passcode by clicking "More options" and the CircuitMatter device will show up as a nearby Matter Accessory. Tap it and then enter the setup code 67202583. This will start the commissioning process from Apple Home.

iOS Chip Tool

The connectedhomeip repo also has an iOS version of Chip Tool that can be helpful in debugging Apple Home. Installation instructions (requiring xcode) are here: https://github.com/project-chip/connectedhomeip/tree/master/src/darwin/CHIPTool

Generate a certificate declaration

Each Matter device has its own certificate to capture whether a device has been certified. (CircuitMatter declares itself as an uncertified test/development/hobby device.) This is referred to the Certificate Declaration (CD). CircuitMatter can generate a CD for you and the remaining certificates are loaded from the projectchip repositorry. The certificate generated by CircuitMatter is signed by a test private key.

To generate a CD run:

python -m circuitmatter.certificates

This will write the certificate_declaration.der file. (test_data/certificate_declaration.der is checked into the repo too and used by default.)

Publish

Use flit to publish to PyPI:

flit publish

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

circuitmatter-0.3.0.tar.gz (96.9 kB view details)

Uploaded Source

Built Distribution

circuitmatter-0.3.0-py3-none-any.whl (71.5 kB view details)

Uploaded Python 3

File details

Details for the file circuitmatter-0.3.0.tar.gz.

File metadata

  • Download URL: circuitmatter-0.3.0.tar.gz
  • Upload date:
  • Size: 96.9 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: python-requests/2.32.0

File hashes

Hashes for circuitmatter-0.3.0.tar.gz
Algorithm Hash digest
SHA256 f0f02b525a5523068ca79feb4ecbb9831ab5779c38879b7be2e9fa93c7bb4ee5
MD5 1300b81e8683271669bccff50260c651
BLAKE2b-256 696e5e603e6e491d1360c3499a08db4e0f1c5fb823e4ecd434df5b6324bbcbb8

See more details on using hashes here.

File details

Details for the file circuitmatter-0.3.0-py3-none-any.whl.

File metadata

File hashes

Hashes for circuitmatter-0.3.0-py3-none-any.whl
Algorithm Hash digest
SHA256 c90057f25f7280e5a6d438029079eadbea4b66e470b1e94a0c387742219cd693
MD5 d57e3adfdb604146df5f8d72780b56eb
BLAKE2b-256 860fe4904c85537517bb6e6202e90be78401b086361b8f3a6e425b148a18dbec

See more details on using hashes here.

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page