-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Auto detect scale and add to scales.h #19
Comments
I guess you can make a PR, what do you think? Should be as simple as this. (I'm not a maintainer here fwiw.) |
Auto-detection of USB scales would mean that there'd be no need for scales.h. It's a cool idea but I don't know how to implement it right now. Specifically, I don't know how to determine which USB devices are USB scales. Open to suggestions and/or PRs. |
This isn't really a solution for auto-detecting scales, but what if a flag were added for specifying a USB vendor and product at runtime? If the user-specified device is attached, the list in It also occurs to me that a crude autodetection could be accomplished easily. If no USB scale is recognized, the program could prompt the user to plug in the scale, and wait for a new USB device to show up. The new device would then be assumed to be a scale. Moving the content of |
Taking in a USB vendor and product ID on the CLI sounds like a great addition. It would be nice, of course, to figure out if there's a way to find any USB scale based on reported capability. The scale's report descriptor should contain this info, but it seems like the device needs to be unbound before it can be read and it's not realistic to unbind all your HIDs to find a scale. |
Maybe the easiest solution would be to parse scales.h at launch, if it exists; otherwise use the internal table. |
Is it possible when plugging in a new scale to add it to scales.h so there is no manual interference? Thanks!
The text was updated successfully, but these errors were encountered: