Giters

DarthAffe / RGB.NET

The one-stop SDK for RGB-peripherals

Home Page:http://lib.arge.be

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Where can I find my Razer device ID?

Symbai opened this issue · comments

commented

The Guids in Devices.cs is incomplete and misses my keyboard. Where do you get these Guids from? And for some reason they are completely different than the IDs I can find in the Devices.xml file in the SDK folder:

    <keyboard pid="515" file="A83F96C8-1F78-465E-892B-ABE403760394.dll" />
    <keyboard pid="529" file="A83F96C8-1F78-465E-892B-ABE403760394.dll" />
    <keyboard pid="521" file="A83F96C8-1F78-465E-892B-ABE403760394.dll" />
    <keyboard pid="534" file="A83F96C8-1F78-465E-892B-ABE403760394.dll" />
    <keyboard pid="538" file="A83F96C8-1F78-465E-892B-ABE403760394.dll" />
    <keyboard pid="545" file="A83F96C8-1F78-465E-892B-ABE403760394.dll" />
    <keyboard pid="516" file="0B8959B5-5594-4761-9432-78ED542BAF42.dll" />
    <keyboard pid="542" file="704A4B8F-0CD6-4D79-BFE7-8B1190E4A85C.dll" />
    <keyboard pid="550" file="704A4B8F-0CD6-4D79-BFE7-8B1190E4A85C.dll" />
	<keyboard pid="551" file="704A4B8F-0CD6-4D79-BFE7-8B1190E4A85C.dll" />
	<keyboard pid="554" file="704A4B8F-0CD6-4D79-BFE7-8B1190E4A85C.dll" />
    <keyboard pid="556" file="704A4B8F-0CD6-4D79-BFE7-8B1190E4A85C.dll" />
	<keyboard pid="552" file="704A4B8F-0CD6-4D79-BFE7-8B1190E4A85C.dll" />
	<keyboard pid="574" file="704A4B8F-0CD6-4D79-BFE7-8B1190E4A85C.dll" />
	<keyboard pid="575" file="704A4B8F-0CD6-4D79-BFE7-8B1190E4A85C.dll" />
	<keyboard pid="577" file="704A4B8F-0CD6-4D79-BFE7-8B1190E4A85C.dll" />
	<keyboard pid="579" file="704A4B8F-0CD6-4D79-BFE7-8B1190E4A85C.dll" />
	<keyboard pid="590" file="704A4B8F-0CD6-4D79-BFE7-8B1190E4A85C.dll" />
	<keyboard pid="599" file="704A4B8F-0CD6-4D79-BFE7-8B1190E4A85C.dll" />
	<keyboard pid="600" file="704A4B8F-0CD6-4D79-BFE7-8B1190E4A85C.dll" />
	<keyboard pid="602" file="704A4B8F-0CD6-4D79-BFE7-8B1190E4A85C.dll" />
	<keyboard pid="604" file="4FE6D485-08A6-4C32-8484-2BD6A1451025.dll" />
	<keyboard pid="605" file="704A4B8F-0CD6-4D79-BFE7-8B1190E4A85C.dll" />
	<keyboard pid="606" file="704A4B8F-0CD6-4D79-BFE7-8B1190E4A85C.dll" />
	<keyboard pid="614" file="704A4B8F-0CD6-4D79-BFE7-8B1190E4A85C.dll" />
	<keyboard pid="617" file="704A4B8F-0CD6-4D79-BFE7-8B1190E4A85C.dll" />
	<keyboard pid="619" file="704A4B8F-0CD6-4D79-BFE7-8B1190E4A85C.dll" />
	<keyboard pid="625" file="4FE6D485-08A6-4C32-8484-2BD6A1451025.dll" />
	<keyboard pid="2308" file="BD6FFEFA-572B-480D-88D8-6E12A203736C.dll" />
	<keyboard pid="2593" file="BD6FFEFA-572B-480D-88D8-6E12A203736C.dll" />
	<keyboard pid="2595" file="704A4B8F-0CD6-4D79-BFE7-8B1190E4A85C.dll" />
	<keyboard pid="2596" file="704A4B8F-0CD6-4D79-BFE7-8B1190E4A85C.dll" />

For example you defined Black Window Chroma with ID 2EA1BB63-CA28-428D-9F06-196B88330BBB but this ID does not exist in the list.

commented

The GUIDs where part of the official SDK documentation.
But since the support for GUID-based device access seems to be not that good at the time, this is already changed to a different approach on the development branch.