Tourbox Neo - No TourBox device found

[Rallick-Jex]

Description

Following the standard instructions to install, using Garuda Linux KDE

During installation I get this, but it doesn't error out and apparently installs successfully

Installing TuxBox driver...
WARNING: Cache entry deserialization failed, entry ignored
WARNING: Cache entry deserialization failed, entry ignored
✓ Driver installed successfully

• systemctl --user status tuxbox shows the service is running

• user in both dialout and input groups

• verbose logging doesn't work ./venv/bin/python -m tuxbox -v
fish: Unknown command: ./venv/bin/python

• ls -la /dev/ttyACM* shows two devices ttyACM0 and ttyACM1. Going into the config file and setting usb_port, neither works

• noticed when i opened the config file under [device]: mac_address = XX:XX:XX:XX:XX:XX

• kdotool --version returns kdotool v0.2.3

TourBox Model

Neo

Connection Type

USB

Linux Distribution

Garuda Linux KDE Dr460nized

User Groups

games scanner openrazer docker realtime libvirt video uucp lp kvm input wheel dialout

USB Device Info (USB only)

crw-rw---- 166,0 root 13 Jun 21:55 󰡯 /dev/ttyACM0
crw-rw---- 166,1 root 13 Jun 22:33 󰡯 /dev/ttyACM1

Bus 003 Device 005: ID 1532:0520 Razer USA, Ltd Kraken Tournament Edition
Bus 003 Device 027: ID 2e3c:5740 ARTERY Technology TourBox

Bluetooth Info (BLE only)

Driver Logs

if bluetooth on PC is turned off:
`tuxbox.device_ble - ERROR - Connection error: ('No powered Bluetooth adapters found. Turn on Bluetooth and try again.', <BleakBluetoothNotAvailableReason.POWERED_OFF: 3>)`

if bluetooth is turned on (it's a Neo, shouldn't matter, but it actually changes!)
WARNING - Cannot send haptic config - not connected
`tuxbox.device_ble - WARNING - No TourBox device found during scan`
`tuxbox.device_ble - ERROR - No TourBox device found`

Udev Rules

no matches for tuxbox

[quinnvoker]

I experienced roughly the same issue with my Tourbox Neo. Everything installed and would run properly but the service would not detect any Tourbox. I updated my Tourbox firmware, no change. I only got it working after uninstalling and installing 3.1.3 instead, after which everything worked perfectly immediately.

Maybe the stricter auto-detection could be causing the issue in my case, because my Neo shows up as this in lsusb and might be getting skipped in v3.1.4 if it's not directly reporting itself as a tourbox:

Bus 001 Device 008: ID 2e3c:5740 ArteryTek AT32 Virtual ComPort in FS Mode

[AndyCappDev]

Hi @Rallick-Jex and @quinnvoker — this is fixed in v3.1.5, just released.

What was wrong: the VID:PID filter added in 3.1.4 only allowlisted the Elite / Elite Plus pair (c251:2005). The Neo enumerates as 2e3c:5740 (Artery AT32 generic CDC) with manufacturer string ARTERY Technology / ArteryTek, so it was getting silently filtered out before the probe even ran — exactly matching the symptoms you both described (downgrade to 3.1.3 worked, but 3.1.4 silently couldn't find the device).

To upgrade:

git pull && ./install.sh
systemctl --user restart tuxbox

Could you confirm it works for you on 3.1.5? If yes, I'll close this. Thanks for the detailed report — the lsusb output (and quinnvoker noting the AT32 enumeration) was what made the root cause obvious.