Skip to main content

La Marzocco Python Client

This is a library to interface with La Marzocco's Home machines.

workflow codecov

Installing this libary

This project is on pypi and can be installed using pip

pip install pylamarzocco

Libraries in this project

  • LaMarzoccoCloudClient interacts with La Marzocco's cloud API to send commands and retrieve machine information. It also supports WebSocket connections for real-time updates.
  • LaMarzoccoBluetoothClient provides a bluetooth client to send settings to the machine via bluetooth.
  • LaMarzoccoMachine provides a high-level interface for interacting with La Marzocco machines, combining both cloud and bluetooth clients.

Setup

LaMarzoccoCloudClient

You need username and password, which are the credentials you're using to sign into the La Marzocco Home app. Additionally, you need an InstallationKey for authentication.

Generating Installation Key

First, generate an installation key for your client:

import uuid
from pylamarzocco.util import generate_installation_key, InstallationKey

# Generate new key material
installation_key = generate_installation_key(str(uuid.uuid4()).lower())

# Save it for future use
with open("installation_key.json", "w", encoding="utf-8") as f:
    f.write(installation_key.to_json())

# Or load existing key material
with open("installation_key.json", "r", encoding="utf-8") as f:
    installation_key = InstallationKey.from_json(f.read())

Initializing the Client

from aiohttp import ClientSession
from pylamarzocco import LaMarzoccoCloudClient

async with ClientSession() as session:
    cloud_client = LaMarzoccoCloudClient(
        username=username,
        password=password,
        installation_key=installation_key,
        client=session,
    )
    
    # Register the client (only needed once for new installation keys)
    await cloud_client.async_register_client()

LaMarzoccoBluetoothClient

The LaMarzoccoBluetoothClient discovers bluetooth devices and connects to them to send local bluetooth commands. Some commands, like turning the machine on and off, can be sent through bluetooth.

Obtaining the Bluetooth Token

Before you can use the Bluetooth client, you need to obtain the Bluetooth authentication token. There are three ways to get this token:

Method 1: Through the Cloud Client

The easiest method is to retrieve the token from the cloud API after initializing the cloud client:

from pylamarzocco import LaMarzoccoCloudClient

# Initialize and authenticate with the cloud client
cloud_client = LaMarzoccoCloudClient(
    username=username,
    password=password,
    installation_key=installation_key,
    client=session,
)

# Get all machines associated with your account
things = await cloud_client.list_things()

# The token is available in the ble_auth_token field
ble_token = things[0].ble_auth_token

Method 2: Through the Static Method (Pairing Mode)

If you don't have cloud credentials or prefer to use Bluetooth directly, you can read the token from the machine when it's in pairing mode:

from pylamarzocco import LaMarzoccoBluetoothClient

# Discover available bluetooth devices
bluetooth_devices = await LaMarzoccoBluetoothClient.discover_devices()

if bluetooth_devices:
    # Put your machine in pairing mode first!
    # Then read the token directly from the machine
    ble_token = await LaMarzoccoBluetoothClient.read_token(bluetooth_devices[0])

Note: This method only works when the machine is in pairing mode. Consult your machine's manual for instructions on how to enable pairing mode.

Method 3: Scanning the QR Code

The Bluetooth token is printed as a QR code on a label inside the machine's chassis. You can scan this QR code with a standard QR code reader app to obtain the token string.

  1. Open the machine's chassis (consult your machine's manual for instructions)
  2. Locate the QR code label
  3. Scan the QR code with a QR code reader app
  4. The scanned value is your Bluetooth token

Using the Bluetooth Client

Once you have the token from any of the above methods, you can initialize the Bluetooth client:

from pylamarzocco import LaMarzoccoBluetoothClient

# Discover available bluetooth devices
if bluetooth_devices := await LaMarzoccoBluetoothClient.discover_devices():
    print("Found bluetooth device:", bluetooth_devices[0])
    
    bluetooth_client = LaMarzoccoBluetoothClient(
        ble_device=bluetooth_devices[0],
        ble_token=ble_token,  # Use the token from any of the three methods above
    )

LaMarzoccoMachine

Once you have any or all of the clients, you can initialize a machine object with:

from pylamarzocco import LaMarzoccoMachine

machine = LaMarzoccoMachine(
    serial_number=serial_number,
    cloud_client=cloud_client,
    bluetooth_client=bluetooth_client,  # Optional
)

You can then use the machine object to send commands to the machine, or to get the current status of the machine.

Getting Machine Information

# Get dashboard information
await machine.get_dashboard()

# Get firmware information
await machine.get_firmware()

# Get schedule settings
await machine.get_schedule()

# Get machine settings
await machine.get_settings()

# Get statistics
await machine.get_statistics()

# Get machine data as dictionary
machine_data = machine.to_dict()

Controlling the Machine

from pylamarzocco.const import SteamTargetLevel

# Turn machine on/off
await machine.set_power(True)  # Turn on
await machine.set_power(False)  # Turn off

# Control steam
await machine.set_steam(True)  # Enable steam
await machine.set_steam(False)  # Disable steam

# Set coffee target temperature
await machine.set_coffee_target_temperature(93.0)

# Set steam level (1-3)
await machine.set_steam_level(SteamTargetLevel.LEVEL_2)

WebSockets

The cloud client supports WebSocket connections for real-time updates from the machine dashboard.

To use WebSockets, start the connection with:

from pylamarzocco.models import ThingDashboardWebsocketConfig

def callback(config: ThingDashboardWebsocketConfig):
    """Callback function for websocket updates."""
    print(f"Received update: {config.to_dict()}")

# Connect to dashboard websocket with optional callback
await machine.connect_dashboard_websocket(callback)

# The websocket will receive real-time updates about the machine status
# To disconnect later:
await machine.websocket.disconnect()

Bluetooth Shot Counter

Newer firmware pushes brewing events over Bluetooth in real time. This removes the ~4 s delay of the cloud websocket for shot start/stop.

Requirements:

  • an ESP-gateway machine (Linea Micra, Linea Mini, Linea Mini R, GS3 AV/MP) with shot counter firmware; connect_bluetooth_shot_counter returns False otherwise. dashboard.shot_counter_supported tells whether the cloud reports support.
  • a Bluetooth client with a valid token
  • a free, persistent Bluetooth connection slot (the machine likely accepts only one central at a time)
from pylamarzocco.models import BluetoothShotCounterUpdate

def on_shot(update: BluetoothShotCounterUpdate | None):
    """Called on every brewing update, and with None when Bluetooth disconnects."""
    if update is not None:
        print(update.state, update.timer_value, update.final_shot_time)

await machine.get_dashboard()  # or get_dashboard_from_bluetooth()
if await machine.connect_bluetooth_shot_counter(on_shot):
    ...  # machine.dashboard is now updated in real time

# Later
await machine.disconnect_bluetooth_shot_counter()

While the shot counter is running:

  • The connection stays open and reconnects automatically. Idle disconnects are paused.
  • Reconnects back off up to 60 s. They stop after 3 failed logins in a row; bluetooth_client.authentication_failed then reports the likely wrong token.
  • A single failed command does not drop the connection.
  • The CMMachineStatus widget is overridden with the Bluetooth state (status and brewing_start_time), including after later cloud updates.
  • If no Bluetooth update arrives for 60 s, the cloud state is used again and the callback receives None.
  • machine.last_shot_time holds the duration of the last shot.
  • Bluetooth commands such as set_power share the same connection. Requests are serialized, so responses can't mix up.
  • If no callback is passed, the dashboard websocket update_callback is used instead.

For long-running hosts (e.g. Home Assistant with adapters or proxies), pass ble_device_callback to LaMarzoccoBluetoothClient so reconnects use the most recent BLEDevice.

Complete Example

Here's a complete example of using the library:

import asyncio
import uuid
from pathlib import Path
from aiohttp import ClientSession
from pylamarzocco import LaMarzoccoCloudClient, LaMarzoccoMachine
from pylamarzocco.util import InstallationKey, generate_installation_key

SERIAL = "your_serial_number"
USERNAME = "your_username"
PASSWORD = "your_password"

async def main():
    # Generate or load key material
    key_file = Path("installation_key.json")
    if not key_file.exists():
        installation_key = generate_installation_key(str(uuid.uuid4()).lower())
        with open(key_file, "w", encoding="utf-8") as f:
            f.write(installation_key.to_json())
        registration_required = True
    else:
        with open(key_file, "r", encoding="utf-8") as f:
            installation_key = InstallationKey.from_json(f.read())
        registration_required = False

    async with ClientSession() as session:
        # Initialize cloud client
        client = LaMarzoccoCloudClient(
            username=USERNAME,
            password=PASSWORD,
            installation_key=installation_key,
            client=session,
        )
        
        # Register device if needed
        if registration_required:
            await client.async_register_client()
        
        # Initialize machine
        machine = LaMarzoccoMachine(SERIAL, client)
        
        # Get machine information
        await machine.get_dashboard()
        await machine.get_firmware()
        await machine.get_settings()
        
        # Control the machine
        await machine.set_power(True)
        await asyncio.sleep(5)
        await machine.set_power(False)

asyncio.run(main())

Metadata

Release files for pylamarzocco 2.5.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for pylamarzocco 2.5.1
File Size Uploaded Provenance Actions
pylamarzocco-2.5.1.tar.gz 72.8 kB With provenance Details for pylamarzocco-2.5.1.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for pylamarzocco 2.5.1
File Interpreter ABI Platform Actions
pylamarzocco-2.5.1-py3-none-any.whl Python 3 none any Details for pylamarzocco-2.5.1-py3-none-any.whl

Total release size: 123.0 kB

Release files / pylamarzocco-2.5.1.tar.gz

Download URL pylamarzocco-2.5.1.tar.gz
Size 72.8 kB
Tags Source
SHA-256 checksum
How to use checksums
dd9b280f9a610d0ceb5f6ffb2e9b01a9b354ea759d09de941f359c6c46c1384f
BLAKE2b-256 checksum
How to use checksums
6a1f9d9a913425191624247b72e2b98740b305b6f90221b2b4713bb5ca82aa5e
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 4, 2026.

Transparency log

Release files / pylamarzocco-2.5.1-py3-none-any.whl

Download URL pylamarzocco-2.5.1-py3-none-any.whl
Size 50.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
bd3b8e9cf4c77bf03b14ec20336133342c820787f26239a8ab9f542611487eed
BLAKE2b-256 checksum
How to use checksums
53f40f20ccea36238cca060d02396a8c92819e12a61c5383ab51b2cd1ee5563e
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 4, 2026.

Transparency log

Security for pylamarzocco 2.5.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.

Select from 2 files

Attestation for pylamarzocco-2.5.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 4, 2026.

Transparency log

A 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.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

2.5.1 This release

2 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page