Open rodrigograca31 opened 4 years ago
@benburkhart1 Should I contribute the changes back or is this a dead project? I loved that it used JS, my favorite language and that allowed me to play with it and make it work.
Im just not sure about that ID..... mine was that one.... I can still contribute the rest of the changes....
For those interested here is my fork: https://github.com/rodrigograca31/lighting-node-pro
Also: had to run it using sudo
...
Im not sending a PR because Im not sure how that ID thing works. If only my ID was different or what...?
Hey Rodrigo, your change looks good but you need to make the ID check an OR, not replace what it was before.
On Wed, May 6, 2020 at 10:35 AM Rodrigo Graça notifications@github.com wrote:
Im not sending a PR because Im not sure how that ID thing works. If only my ID was different or what...?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/benburkhart1/lighting-node-pro/issues/6#issuecomment-624787496, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAGQXYNGUTMZ63CM25CD4J3RQGNUNANCNFSM4MSKKOBQ .
So does that mean both IDs are valid!? Like the company produced devices with both IDs? If thats the case yeah I can change it and send a PR back.
+1 for deleting package-lock.json, when doing npm install it couldn't compile some usb package binary
@rodrigograca31 Yes it means both IDs are valid, the old ones do not change, they are programmed into the hardware itself.
So really the package-lock.json should be committed, I agree it needs to be ran with an updated version of nodejs so proper versions can be selected (it was written against an older version of node)
@rodrigograca31
return d.deviceDescriptor.idVendor === 0x1b1c && (d.deviceDescriptor.idProduct === 0x0c0b || d.deviceDescriptor.idProduct === 0x0c1a)
i've changed this and it work for my controller which isn't 0x0c0b but 0x0c1a, so it work for both normally
So it seems theres 3 ids as of now.... 🤔
0x0c0b, 0x0c10, 0x0c1a
Ok, I will send a PR in a few minutes....
Steps:
package-lock.json
andnode_modules
and runnpm install
again to install updated dependencies