Skip to content

Troubleshooting#

No USB devices found#

Run:

enody list

If the device is attached but not listed:

  • Try a known data-capable USB cable.
  • Try another USB port.
  • On Linux, install the udev rule in USB Setup.
  • Close other tools that may have the serial or USB interface open.

Permission errors on Linux#

Verify the rule exists:

ls /etc/udev/rules.d/99-enody-esp32.rules

Then reload udev and reconnect EP01:

sudo udevadm control --reload-rules
sudo udevadm trigger

WiFi setup fails#

Start from USB:

enody wifi-scan
enody wifi-setup

If network joining succeeds but WiFi discovery fails:

  • Confirm the computer and EP01 are on the same local network.
  • Confirm the network allows mDNS / local discovery.
  • Re-run enody wifi-generate-token to refresh the saved token.

Token verification fails#

Generate a new token:

enody wifi-generate-token

If multiple EP01 devices are visible, select the intended device by endpoint and host identifier.

Update target does not identify itself#

The update command may warn when an attached device can be seen at the USB update layer but does not respond to host identification. Before using enody update --force, disconnect unrelated USB development boards and confirm the only matching device attached is the EP01 you intend to update.

More diagnostics#

Use Rust log output through the CLI:

RUST_LOG=debug enody info