Closed mrose17 closed 10 years ago
Thanks, I've picked up a couple of these fixes. For now I don't want to clutter the module with the auto-detection stuff, I'd rather see that as part of an end-user application, wrapper or separate module, and keep the openzwave module itself focused solely on wrapping libopenzwave.
understood. how about if we put that functionality in a different .js file - i'd rather keep it with the node-openzwave repo because it's encapsulating knowledge about which sticks work with openzwave. does that make sense?