Getting started with the edelkrone SDK

What connect.edelkrone.com does

connect.edelkrone.com lets edelkrone owners build motion programs by talking to their AI assistant. You describe the motion you want, the assistant reads the SDK documentation from this site, writes a short Python program and runs it on your computer. Your computer talks to the device over Bluetooth; this site never controls your device directly.

What you need

An edelkrone device that the SDK supports. Ask your assistant to call get_sdk_info for the current list.
A computer (macOS, Windows or Linux) with Bluetooth switched on, near the device.
Python 3.11 or newer.
An AI assistant that supports MCP connectors, such as Claude or ChatGPT. Assistants that can run code on your computer (for example Claude Code or Cowork) can install the SDK and write programs for you; with other assistants you copy the code and run it yourself.

Installing the SDK

The SDK is a Python package named edelkrone on PyPI (https://pypi.org/project/edelkrone/):

python3 -m venv ~/edelkrone-env
~/edelkrone-env/bin/pip install edelkrone

The python3 that comes with macOS is version 3.9, which is too old. Install Python 3.11 or newer from python.org or with Homebrew (brew install python@3.12) and create the environment with that Python, for example python3.12 -m venv ~/edelkrone-env.

To check the installation and the connection without moving anything, run the official example:

~/edelkrone-env/bin/python -m edelkrone.examples.read_device

Running programs on macOS

macOS asks for permission before a program uses Bluetooth. Run programs that connect to your device in the Terminal app and choose Allow when macOS asks; you can change it later in System Settings → Privacy & Security → Bluetooth.

When an AI assistant app (Claude Code, Cowork or an editor) starts Python itself, macOS may stop the program as soon as it uses Bluetooth: Python exits with code 134 (SIGABRT) and a crash report says the app is missing a Bluetooth usage description. This is a macOS rule for the app, not a fault of your device or the SDK. Let the assistant write the program to a file and run it in Terminal, for example with a .command file opened by open -a Terminal program.command.

Your first motion program

Tell your assistant what you want in plain words, for example: "Turn my HeadONE 90 degrees to the right, slowly." The assistant describes the motion back to you and asks for confirmation before running anything. Read the safety rules before your first run.

Troubleshooting

No units found (not_found): the device is off, out of range, or connected to the edelkrone phone app or another program. A connected device stops advertising; close the other connection.
Python stops with exit code 134 on macOS: run the program in Terminal (see "Running programs on macOS").
The device does not move at low speed: some devices do not start below a minimum joystick speed. A DollyONE V2 did not move at 10-20 % and moved at 50 %.
firmware_ok is false: update the device firmware with the edelkrone app.
Every error carries a reason code; the SDK guide lists what each one means.