SDK issues

[blx]

Hello,

I just received a Blynclight Standard and started tinkering with the SDK to see what can be done with it.
The answer in my case is, apparently, not much.

I'm using Blynclight.dll in a C# project. While I can create the BlyncLightController instance correctly and retrieve the list and names of detected devices, the interesting API methods have no apparent effects on the lights.
Methods such as TurnOnRGBLights(0, 255, 0, 0) or TurnOnRedLight(0) return true but do not turn the light on.
Worse than that, GetDeviceUniqueId(0) returns a different UID every time I request a new color. Using TurnOnRGBLights(...) I noticed that the value returned as UID is actually a bitmap of the RGB values as well as the ON, flash, flash speed and dim flags.

I get the exact same behavior using the sample Windows Forms application provided with the SDK (BlyncLightTest). The light does not change, but the UID matches the RGB values and checkboxes' states.

Did I mess something up? Can I do a factory reset of my Blynclight?
The Blynclight still works as intended with Embrava Connect and Skype.

[blx]

Nevermind, the DLL provided with the SDK was out of date for my device (SKU: BLYNCUSB40). I used the one distributed with Embrava Connect with no issue.

[arsa]

@blx

Uh huh - thanks for the pointer!
This is super weird - none of the things in the current SDK that i just got work with USB40 version. Stealing dll from embrava connect unblocks - nice, thanks!

[JaredS]

I have the same problem. It seems none of the SDKs work with the USB40. Unfortunately I'm targeting Linux and Mac, so I can't simply grab the the latest dll.

[mgibson]

Working with the BlyncLight Mini.

SDK is as described by blx. Attempted blx's fix, copying the distributed blynclight.dll, and now all the controls are greyed out. So, nothing working so far.

[paddy]

Hi, I had the same issues.

It really seems the SDK is out of date. I was able to make it run in Windows with a few changes. I replaced all BlyncLight.DLL in the solution folder and subfolders with the newest version from Embrava Connect.
Then I had to change the Target SDK Version to 4.5.2, then recompiled and debugged. It seems the detected device ID (in my case 13 or 0x0D for a BlyncLight Plus) was not listed in their source code, hence the buttons are not enabled.
By changing one of the existing devices to match my device ID of 0x0D I was able to run and control the device.

I really hope Embrava will update their SDK soon!

Patrick

[hack the gibson]

I'm reverse engineering the software to create a linux opensource version. anyone interested?