What version of WinBoat are you running?

v0.9.0

Your Environment

Linux Mint 22.2
KDE
Most recent Flatpak as of current date, not sure which that is tbh

Steps to Reproduce / Context

For context, I enjoy the pastime of training Figure Players in Super Smash Bros Ultimate using Nintendo's Amiibo Toys-to-Life figurines. On Windows, I used an app known as Powersaves for Amiibo. To use this software, it requires reading from a specific NFC Reader device, in this case the Powersaves Portal. It is a USB device, however when plugging it in to my computer, it is read through Linux but not through WinBoat, reading No Hardware Found on the application.

I would love if you could look into figuring this out, as it would help me SO much. I would be willing to work directly with you about this given I feel it's very unlikely that anyone working directly on this project would have a Powersaves Portal, and thus I can test any changes made to support it. Just message me here, and if it were better, I can send my Discord username there to discuss further on a platform I am more used to and active on.

Logs

container.log
install.log
migrations.log
winboat.log

Expected Behavior

Powersaves for AMIIBO, and the VM as a whole, should recognize the Powersaves Portal device when plugged in. It would then progress to a menu allowing me to save the data from the NFC chips in the figures' bases.

Current Behavior

It does not, despite recognizing my keyboard and mouse, other USB devices. The VM doesn't recognize it at all.

Possible Solution

I would suggest that, however the USB passthrough is programmed, to add this as a possible device, like adding it to a whitelist. I'd assume that the specific device number to recognize it would be needed, and here is that:

Manufacturer: Datel
Serial #: [REDACTED]

Class | 0 | ((Defined at Interface level))
Subclass | 0
Protocol | 0
USB Version | 2.00

Vendor ID | 0x1c1a | (Datel Electronics Ltd.)
Product ID | 0x03d9

Speed | 12 Mbit/s

Quality Notice

• I have checked the issue tracker and verified that this bug is a unique case.