-
Notifications
You must be signed in to change notification settings - Fork 0
Troubleshooting
Common issues, roughly in the order people hit them.
Brand-new boards sometimes need to be put into download mode manually (the USB port is wired straight to the ESP32 — there's no USB-to-UART bridge): hold BOOT, tap RESET, release BOOT, then retry at web.esphome.io. After one successful flash this becomes automatic. Also try a different USB-C cable — charge-only cables have no data lines.
The coil pairs are mixed up. A bipolar stepper has two coils; each must connect to one pair of driver outputs (coil A on connector pins 1–2, coil B on pins 3–4). Find the pairs with a multimeter: the two wires of a coil have low resistance (a few ohms) between them; across coils is open circuit. No multimeter? Touch two loose wires together and spin the shaft by hand — if it drags, those two are a pair.
Motor spins the wrong way? Don't rewire — flip Motor Direction in the web UI (Setup group).
Almost always heat: the TMC2209 hit its over-temperature limit and is cycling. Lower IRUN, raise the supply voltage (24 V runs cooler than 12 V for the same mechanical power), or add cooling. See Power Requirements.
If the log says Stall detected, StallGuard fired a false positive — and note the firmware zeroes the position counter on stall, so your position reference just moved. Lower SGTHRS (less sensitive), or check that TCOOLTHRS isn't arming detection during slow ramps. See StallGuard Tuning.
mDNS is blocked on some networks (guest Wi-Fi, some routers, some corporate networks). Find the board's IP in your router's client list and browse to http://<ip> directly. Once in, the IP is shown under Diagnostics — consider giving the board a DHCP reservation.
When the board can't connect, it automatically brings back its setup hotspot (same name as the device) after a while — connect to it and enter the new credentials in the captive portal. You can also re-provision over USB-C at web.esphome.io (Configure Wi-Fi), which works regardless of what's saved.
Note: in the generic board firmware the third button is labeled "Wi-Fi reset" but has no action attached — button behaviour is defined by product firmware (e.g. the Ropener's gestures). Use the hotspot or USB methods above.
The firmware boots new OTA images in a verify-first mode and rolls back automatically if the new image doesn't boot cleanly. If you end up on the old version after an update, the new image likely failed on your board — check Diagnostics → Firmware Version, and try updating over USB instead. Don't power-cycle during the first minute after an OTA update; that's when the image is validated. See OTA Updates.
- The I2C scan on boot logs what it finds — the AS5600 should appear at address 0x36.
- The AS5600 needs a diametric magnet (magnetized across the diameter) centered on the shaft end, a few millimetres from the chip. Axial ring magnets from the junk drawer won't work.
- Plain VAL3100s ship with the encoder footprint unpopulated — see the encoder section.
Check the live logs (connect USB-C at web.esphome.io → Logs), then open an issue with the log output and your board type.