-
Notifications
You must be signed in to change notification settings - Fork 92
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
Search for connected interfaces #95
Comments
Sounds good. The RDM Spec calls this functionality "discovery", so maybe I'm unsure how much hardware actually supports this. I know the Enttec USB DMX Pro does but many other devices probaby don't. |
I'm sorry, I was talking about searching for interfaces, not the actual lights... |
I see. That's going to be hard on the per driver level. Most would just report the same serial ports. The serialport package has a serialport-list command - is that something similar to what you had in mind? |
Yes. I'll look into that. |
So my original idea was to find a connected device using Any more thoughts on that? |
Yeah I'm not sure we can create a reliable way to discover all possible devices and make correct driver suggestions. :/ Maybe the best we can do is add some documentation about For artnet other stuff on the networking side needs to be configured as well so I'd hope people setting this up know what they are doing. Maybe more documentation could also help here - like a guide on the wiki or something. |
The library is working great. A nice-to-have feature would be the ability to search for connected devices. Happy to implement that, but what would be the best approach? Should we add a
search
function to each driver and call them one after each other / simultaneously?The text was updated successfully, but these errors were encountered: