You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Oct 12, 2023. It is now read-only.
In calling SetColor, no color changes are taking place for my bulb. Connectivity with the bulb has been verified as other methods like TurnOff work as intended.
I did some inspection of packets from the Magic Home android app and found some differences in the bytes being sent to the bulb. Changing the first parameter from 0x41 to 0x31 and the second to last parameter from 0x0f to 0xf0 of the SendData call in SetColor corrects the issue for me. SendData(new byte[] { 0x31, R, G, B, 0x00, 0xf0, 0x0f });
With these changes calls to SetColor work consistently for me. However, I only have one Magic Home light bulb. So, I don't have a way to broadly test this.
Looking in the device information screen on my android app, my bulb is listed with a firmware version of 44.v9.34.6887-a
In calling
SetColor, no color changes are taking place for my bulb. Connectivity with the bulb has been verified as other methods likeTurnOffwork as intended.I did some inspection of packets from the Magic Home android app and found some differences in the bytes being sent to the bulb. Changing the first parameter from
0x41to0x31and the second to last parameter from0x0fto0xf0of theSendDatacall inSetColorcorrects the issue for me.SendData(new byte[] { 0x31, R, G, B, 0x00, 0xf0, 0x0f });With these changes calls to
SetColorwork consistently for me. However, I only have one Magic Home light bulb. So, I don't have a way to broadly test this.Looking in the device information screen on my android app, my bulb is listed with a firmware version of 44.v9.34.6887-a