ladeak

Sorry, no issues with the devices in any other apps. Cool, thanks for the pointers, I will check the code in the next few days.

`HandleIncomingMessages` does not even hit from their IP addresses LIFX-Mini-xxxxx, which is weird given they are on the same network, same IP range etc. I don't see a reason for...

Port: 56700. I don't think 'Service' property does anything today in the library. I think you should be able to even skip the mac address if you manually create the...

As a quick update, discovery operation works with https://github.com/node-lifx/lifx-lan-client I am comparing the messages sent out and, I see that byte 4-7 is different in the Frame headers https://lan.developer.lifx.com/docs/packet-contents#frame-header This...

Solution seems really simple >The source identifier allows each client to provide a unique value, which will be included in the corresponding field in Acknowledgement (45) and State packets the...

This is where it is written in the FrameHeader: ```csharp //BinaryWriter bw = new BinaryWriter(ms); #region Frame //size uint16 dw.Write((UInt16)((payload != null ? payload.Length : 0) + 36)); //length //...

> This seems to be an important thing in the docs 'We recommend that your program has one source value and keeps incrementing sequence per device for each message you...

I think the fix might be even simpler. Sequence value should be incremented, and the Identifier shouldn't. All the code is already there, just the logic needs to be 'echanged'.

Both PR-s out there. Both finds and returns all lights now. @dotMorten please review when you have a chance :)

@dotMorten any chance to review the PR-s?