NAO Fair autostart
Process that runs on a NAO v6 and performs the trigger assignment stored by the NAO Fair app. It starts at boot, in the robot's Python 2.7, the same way as the microphone bridge. The app is not required to be running.
While the NAO Fair app is connected it renews a lease through NAOqi about once a second, and this process ignores triggers. An explicit release, or 20 seconds without a renewal, hands the triggers back. The assignment itself is a JSON file under /home/nao/nao-fair-autostart/assignment.json, so it survives a reboot. ALMemory is only the live channel.
The process speaks with the robot's own TTS, stops speech, waves, nods, shakes, sits, stands, and stops a gesture. Gespräch beenden stops speech. Gespräch starten, Gespräch umschalten, and Gespräch beenden und Kontext löschen do nothing here.
Installing it from the NAO Fair app, and detecting that it is already present, comes later. Until then, copy a checkout by hand.
Install a local checkout
On Linux, or in WSL, from this directory:
sh packaging/install_on_nao.sh nao@ROBOT_IP
The script asks for the nao SSH password, copies the files to /home/nao/nao-fair-autostart/, registers /home/nao/nao-fair-autostart/run_forever.sh under [program] in /home/nao/naoqi/preferences/autoload.ini, and starts the process. Do not add it under [python]. That section runs inside NAOqi.
From a checkout already on the robot, as the nao user:
sh packaging/install_local.sh
A robot without this process still accepts a NAO Fair app connection. The app reports that the autostart assignment was not stored.
On the robot
Stop it:
ssh nao@ROBOT_IP /home/nao/nao-fair-autostart/run_forever.sh stop
Follow the log:
ssh nao@ROBOT_IP tail -f /home/nao/nao-fair-autostart/run_forever.log
ALMemory keys
| Key | Writer | Meaning |
|---|---|---|
NAOFair/Autostart/Assignment |
App | JSON assignment |
NAOFair/Autostart/AssignmentSeq |
App | Integer bumped on each push |
NAOFair/Autostart/AckSeq |
Robot | Sequence persisted to disk |
NAOFair/Autostart/LeaseCommand |
App | hold or release |
NAOFair/Autostart/LeaseSeq |
App | Integer bumped about once a second while connected |
NAOFair/Autostart/LeaseAckSeq |
Robot | Last hold sequence after speech and the current gesture were stopped |
There is no extra secret. Anyone who can already reach NAOqi can already make the robot speak.
Metadata
Release files for nao-fair-autostart 0.1.0
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 | Actions |
|---|---|---|---|---|
| nao_fair_autostart-0.1.0.tar.gz | 16.1 kB | Without provenance | Details for nao_fair_autostart-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| nao_fair_autostart-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for nao_fair_autostart-0.1.0-py3-none-any.whl |
Total release size: 29.0 kB
Release files / nao_fair_autostart-0.1.0.tar.gz
| Download URL | nao_fair_autostart-0.1.0.tar.gz |
|---|---|
| Size | 16.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5d410495ab40c8555de79e06c7b76f7741150247d4c4584a706c4067bb8c3edf
|
|
BLAKE2b-256 checksum How to use checksums |
0eb9e50a93029b096820dd5cf1e672ec2addffb549c68696ef8ffb4e54e9efce
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.15
|
Release files / nao_fair_autostart-0.1.0-py3-none-any.whl
| Download URL | nao_fair_autostart-0.1.0-py3-none-any.whl |
|---|---|
| Size | 12.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9d3d52b1568a929747eadcc259936a4a34622d838e0482740f49eaa888a76169
|
|
BLAKE2b-256 checksum How to use checksums |
88042055323ed64063ab2c4af1b4b51aadd968f3d0d9fafb593627b9c2c6f6c0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.15
|
Security for nao-fair-autostart 0.1.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.