Troubleshooting

Troubleshooting

No device in discovery

Discovery requires an active interface, HTTP server, and _filelink._tcp.local. mDNS advertisement. Check Ethernet link/DHCP or Wi-Fi/provisioning. Windows firewall/network requirements are not established by the supplied evidence.

Wi-Fi does not connect

Boot and fallback use saved primary slot-0 credentials. Although storage supports five entries, automatic selection across them is not implemented. A failed primary connection leads to open provisioning AP mode.

SD download is not ready

The CRC cache must contain a ready checksum before download. Wait and retry; the device does not calculate that checksum synchronously for the request.

Transfer integrity failure

Keep the original local file and retry. Uploads and downloads use CRC32. Normal queue transfers have cancellation/recovery logic; direct editor transfers do not share every queue behavior.

OTA outcome is uncertain

The device may disconnect when rebooting. Rediscover it and check reported firmware information; a dropped connection alone is not confirmation.

Factory reset appears incomplete

Verify settings after restart. The reset handler sends success without checking all underlying reset-operation outcomes. It never erases SD content.