Causes
- Unsupported browser — Firefox and Safari are not supported — The LYCAN 8K is configured entirely through the browser-based web driver at mouse.xyz (alternate link: mouse.fit). The driver page itself states plainly: "Please use Microsoft Edge or Google Chrome browser (Firefox is not supported)". The web app uses the WebHID API, which Firefox does not implement for this purpose and Safari does not support on macOS/iOS — so opening mouse.xyz in Firefox or Safari always results in "Device not found" or a page that never sees the mouse.
- WebHID permission not granted or previously denied — mouse.xyz needs the browser's WebHID permission to talk to the mouse. The first time you connect, Chrome/Edge shows a permission prompt asking which HID device to pair. If you dismissed it, denied it, or the prompt never appeared (some browser policies block WebHID by default), the driver cannot enumerate the mouse and shows "Device not found? please click to another Web Driver Link." A previously denied permission persists until you clear it in the browser's site settings.
- Mouse not actually connected in a detectable mode — The web driver only sees the mouse when it is actively connected. If the mouse is in wireless mode and the 2.4GHz receiver is unplugged, or the mouse is off (power switch on the underside in the off position), or the USB-C cable is a charge-only cable, the driver has nothing to enumerate. The LYCAN 8K ships with two USB-C cables that are data-capable, but third-party cables may be charge-only.
- Wrong driver link or browser version — G-Wolves maintains two web driver endpoints (mouse.xyz and mouse.fit) and the software version shown on the page has changed over time (1.0.0.41 → 1.0.0.44). An outdated cached version of the page, an old browser without WebHID support, or corporate browser policies that disable the WebHID API (a documented Edge/Chrome enterprise policy) can all make the driver fail to connect even on a supported browser.
- Extension conflicts or browser privacy settings — Ad-blockers, privacy extensions, or strict site-data settings can block the WebHID prompt or the driver's handshake. Some users on r/MouseReview also reported G-Wolves software/web pages failing to load entirely due to network or region issues, which produces the same "cannot connect to the driver" experience from a different angle.
How to Fix
- Use Google Chrome or Microsoft Edge — never Firefox or Safari — Open mouse.xyz (or the alternate link mouse.fit) in Chrome or Edge on Windows or macOS. Update the browser to the latest version first so WebHID is fully supported. If the page loads but never finds the mouse, this browser check is the most common root cause — the driver's own warning about Firefox is displayed right on the connect page.
- Connect the mouse by USB-C cable (wired mode) before opening the driver — Plug one of the two included data-capable USB-C cables into the mouse and the PC, and make sure the mouse's power switch is on. Wired mode is the most reliable connection for the web driver: the Nordic 54L MCU enumerates over the cable, and the driver can immediately see it. If the mouse only connects wirelessly, confirm the 2.4GHz receiver is plugged in and the mouse is switched to wireless before loading the page.
- Grant the WebHID permission when prompted — When Chrome/Edge asks "mouse.xyz wants to connect to a HID device," click the paired device (it should list the LYCAN 8K) and allow it. If no prompt appears, click the page's connect/refresh button again. If you previously denied it, open Chrome/Edge settings → Privacy and security → Site settings → HID devices (or search "HID" in settings), find mouse.xyz, and reset/remove the blocked entry, then reload the page and accept the prompt.
- Try the alternate web driver link — The mouse.xyz connect page itself suggests this: "Device not found? please click to another Web Driver Link (https://www.mouse.fit)". Open mouse.fit in the same browser with the mouse connected by cable and attempt the connection there. One of the two endpoints usually enumerates the device even when the other fails, since they are maintained as separate deployments.
- Disable interfering extensions and try incognito/private mode — Open a normal window, disable ad-blockers and privacy extensions for the mouse.xyz domain, then reload. If it still fails, open a Chrome/Edge incognito window (which loads without extensions) and try the connection there. If the driver connects in incognito, an extension or cached state was the culprit — whitelist mouse.xyz in your extensions and clear the site's cached data.
- Check OS/device level: unplug other HID devices and reseat the connection — Unplug other gaming mice, keyboards with HID passthrough, and USB hubs; then unplug and replug the LYCAN 8K's cable, or switch the mouse off and on. On Windows, verify the mouse appears in Device Manager under "Mice and other pointing devices" or as a HID device. On macOS, check System Information → USB. If the OS doesn't see the mouse at all, the cable, port, or mouse is at fault — test another port and the second included cable.
- Contact G-Wolves support with your browser, OS, and driver version — If the driver still reports "Device not found" with a supported browser, wired connection, and permission granted, email [email protected] (or reach their Discord) and include your OS version, browser name/version, the software version shown on the mouse.xyz page, and what you tried. G-Wolves has walked users through pairing/software issues on a per-model basis — for their wireless mice they also maintain pairing tools and alternate driver builds, which they will point you to.