Skip to main content

nestor-reachy

Reachy Mini as a satellite of Nestor: the assistant speaks and listens through it, and its head and antennas follow the conversation: listening, thinking, speaking, nodding on each word, laughing when the voice laughs. Built on nestor-satellite.

Status: the MuJoCo twin only. A physical robot is refused until its safety policy is validated on hardware; the robot's own microphone and speaker come later.

pip install "nestor-reachy[reachy,audio]"
nestor-reachy twin --headless &                               # the simulated robot
nestor-reachy run --room salon --pairing-uri "nestor+http://nestor.local:8471/?code=K7QF2M9X"

Pairing

Reachy has a speaker and no screen. The simplest is an enrollment code: add a satellite in the Nestor admin with the provisioning method (enrollment.provisioning), and give the robot the pairing URI it returns, by flag or in its environment:

NESTOR_PAIRING_URI="nestor+http://nestor.local:8471/?code=K7QF2M9X" nestor-reachy run --room salon
nestor-reachy run --core http://nestor.local:8471 --room salon --pairing-code K7QF-2M9X

Without one, it says a six-digit device code on its speaker, twice, digit by digit, with the SDK's recorded voice (device_code.speech, offline), and logs it: type it in the admin. The token is then kept in ~/.config/nestor-reachy/reachy-<room>.json and later runs reconnect with it (nestor-reachy run --core http://nestor.local:8471 --room salon). To tell robots apart, the admin can ask one to identify itself: it wiggles its antennas for two seconds, while it waits to be paired or once connected.

Safety lives on the device: every target is clamped to the motion limits, and the robot returns to rest when the link to the core drops or nothing is heard from it for two seconds.

Development

The tests use the Nestor server's conformance suite (nestor-home, a pinned dev dependency) and the SDK, both from PyPI. To test against local checkouts instead: uv run --with-editable ../nestor-satellite-python --with-editable ../nestor pytest.

uv sync
uv run pre-commit install
uv run ruff check && uv run ruff format --check && uv run ty check && uv run pytest
uv run --no-dev --group live --extra reachy pytest -m live   # with `nestor-reachy twin` running

License

MIT

Metadata

Release files for nestor-reachy 0.3.0

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

Source distribution (sdist)

Source distribution for nestor-reachy 0.3.0
File Size Uploaded Provenance Actions
nestor_reachy-0.3.0.tar.gz 11.1 kB Without provenance Details for nestor_reachy-0.3.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for nestor-reachy 0.3.0
File Interpreter ABI Platform Actions
nestor_reachy-0.3.0-py3-none-any.whl Python 3 none any Details for nestor_reachy-0.3.0-py3-none-any.whl

Total release size: 23.7 kB

Release files / nestor_reachy-0.3.0.tar.gz

Download URL nestor_reachy-0.3.0.tar.gz
Size 11.1 kB
Tags Source
SHA-256 checksum
How to use checksums
2342f57bfe9a6192238edc917a59b7a245058d48072035fcd4e2d56d82f650f9
BLAKE2b-256 checksum
How to use checksums
9b21151a432714de9d38c02c595a4308454c0c07d064dae5d2942bf8efd85bb9
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.6 {"installer":{"name":"uv","version":"0.13.6","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Release files / nestor_reachy-0.3.0-py3-none-any.whl

Download URL nestor_reachy-0.3.0-py3-none-any.whl
Size 12.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
354bdcc76dc3881b0f444528e2658621a7fbe21d3691873d286bbeaa79785c27
BLAKE2b-256 checksum
How to use checksums
3411f07f0a560af5d007986e27311953cbe3540856f1e6d7fcc362199ccb7682
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.6 {"installer":{"name":"uv","version":"0.13.6","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Security for nestor-reachy 0.3.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.

No provenance found

None of the files in this release were uploaded with provenance metadata.

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.

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