-
Notifications
You must be signed in to change notification settings - Fork 12
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
USB Auto discovery detects every FTDI device as an USB300 gateway #38
Comments
I am working on this. |
pushed directly to master to ease the testing |
@bodiroga, @dominikkv could you do me favor and test this commit with your USB300 devices. I already tested it with a FTDI serial programmer. This device was not recognized as an USB300 gateway. However my EnOcean stick got recognized as expected. |
I'll test it tomorrow. |
Auto discovery does not work with rfc2217, right? I'll have to change my docker config to expose USB to OpenHAB again, that's why I haven't tested yet. Plans are to do it on Thursday :-) |
Test was not successful. Manufacturer name and product name do not match! Here is my UsbSerialDeviceInformation:
|
Hi @dominikkv, thanks a lot for your test. What kind of USB dongle do you own. Really interesting that your dongles does not have EnOcean as manufacturer. |
https://www.amazon.de/d/B01DRO7B2U |
Hi @dominikkv, as your stick just provides generic FTDI information and nothing specific about EnOcean, I would like to stick with the current solution. Drawback: Auto discovery of these sticks is not working. |
Hi @fruggy83! Excuse me for being so late, I don't know if this issue is resolved or I can do anything to fix it. And sorry for not checking the manufacturer ID in the USBDiscovery part of the code, my check was too generic 😢 Thanks for your work! |
That's fine, but then we should mention it in the docu with a guide to add them manually. |
The USB dicovery just checks the vendor and product id => each FTDI device is detected as an USB300 gateway. The manufacturer should be added to this check.
The text was updated successfully, but these errors were encountered: