openvibers/openvibe.link Commits

Follow-up to merged PR 3 (#9)

OP OpenVibers committed 2 Oct 2026 · 744b3ef848 · 2 files, +14 −11

local checks ✗ 0/2 · CI ✓ 9/9 · review SHIP by DeepSeek harness

https://github.com/OpenVibers/OpenVibe.Node/pull/9

Changes

ddiff --git a/docs/install.md b/docs/install.md
iindex 8ad0bdd..aabf7f7 100644
---- a/docs/install.md
++++ b/docs/install.md
@@@ -117,11 +117,13 @@ Raspberry Pi OS Bookworm (64-bit recommended). Enable I²C and SPI: `sudo raspi-
  `--driver adeept` (or `adeept-mecanum`).
  
  The kit's own software (`Adeept_Robot.service`, `WebServer.py` on `0.0.0.0:8888` with the fixed login
--`admin:123456`, MJPEG on `:5000`) must not run: anyone on the network could drive the car. The installer disables it,
--including autostart lines in root's and the invoking user's crontabs and `/etc/rc.local`. From a root shell, it checks
--`pi`'s crontab when that account exists. It comments out the kit's lines with the marker
--`#openvibe-node-disabled:` and keeps the original text, so running the installer again changes nothing. Check with
--`systemctl status Adeept_Robot.service`, `crontab -l` (and `sudo crontab -l -u pi` for a root-shell install) and
++`admin:123456`, MJPEG on `:5000`) must not run: anyone on the network could drive the car. The installer
++(`install/install.sh`) now does this automatically: it stops and disables `Adeept_Robot.service` and comments out the
++kit's autostart lines in the invoking user's crontab, root's crontab and `/etc/rc.local`, prefixing each with the
++marker `#openvibe-node-disabled:` and keeping the original text, so undoing it is removing the marker and a second
++run changes nothing. From a root shell, it checks `pi`'s crontab when that account exists. Verify with
++`systemctl status Adeept_Robot.service`, `crontab -l | grep openvibe-node-disabled` (and
++`sudo crontab -l -u pi | grep openvibe-node-disabled` for a root-shell install) and
  `grep openvibe-node-disabled /etc/rc.local`. The Node replaces it.
  
  If a direction is wrong on your car, fix it in `config.json` → `plugins[0].config`: `motors.<wheel>.direction`,
ddiff --git a/plugins/adeept_adr036/README.md b/plugins/adeept_adr036/README.md
iindex 7a8ed6b..a61a973 100644
---- a/plugins/adeept_adr036/README.md
++++ b/plugins/adeept_adr036/README.md
@@@ -8,12 +8,13 @@ kit's code is imported.
  ## Keep the kit's stock server disabled
  
  The kit's own server listens on `0.0.0.0:8888` with the fixed login `admin` / `123456` and streams MJPEG on `:5000`.
--Anyone on the network could drive the car with it. The installer disables its autostart in root's and the invoking
--user's crontabs and `/etc/rc.local`. From a root shell, it checks `pi`'s crontab when that account exists. It comments
--out the kit's lines with the marker `#openvibe-node-disabled:` and keeps the original text, so running the installer
--again changes nothing. Check with `systemctl status Adeept_Robot.service`, `crontab -l` (and
--`sudo crontab -l -u pi` for a root-shell install) and
--`grep openvibe-node-disabled /etc/rc.local`. Do not run it next to the Node. This plugin never starts it.
++Anyone on the network could drive the car with it. The installer (`install/install.sh`) now does this automatically:
++it stops and disables `Adeept_Robot.service` and comments out the kit's autostart lines in the invoking user's
++crontab, root's crontab and `/etc/rc.local`, prefixing each with the marker `#openvibe-node-disabled:` and keeping the
++original text, so undoing it is removing the marker and a second run changes nothing. From a root shell, it checks
++`pi`'s crontab when that account exists. Verify with `systemctl status Adeept_Robot.service`,
++`crontab -l | grep openvibe-node-disabled` (and `sudo crontab -l -u pi | grep openvibe-node-disabled` for a root-shell
++install) and `grep openvibe-node-disabled /etc/rc.local`. Do not run it next to the Node. This plugin never starts it.
  
  ## Wiring (kit defaults)