Formerly known as Magic Hue utility

This repository includes two scripts:

The setup.py script allows the user to connect the "Zengge" lightbulb to their Wi-Fi. The control.py script provides an easy API for the "Zengge" lightbulbs.

1. Plug in your Zengge lightbulb and turn it on. It will start flashing different colors.

2. Connect to its Wi-Fi (something like LEDnetE1234B).

3. Run the setup.py script, providing your SSID and your Wi-Fi password:

   python3 setup.py -ssid MyWifiEndpoint -pswd MyAwesomePassword
   

If the script worked, your lightbulb will turn green within a few seconds.

Note: Currently, the script is automated for WPA2PSK / AES only. Modify it if your Wi-Fi uses a different mode and encryption.

Once your lightbulb is on your network, you can use the zengge.py script with the following arguments:

  -h, --help  show help message and exit
  -ip         provide the IP for the lightbulb; i.e. -ip 192.168.2.2
  -raw        accept colon-separated raw hex string; i.e. -raw 71:23:0f
  -rgb        accept comma-separated RGB values; i.e. -rgb 100,155,75
  -white      accept value of white temperature and brightness (0-255); i.e. -white 150,255
  -warm       accept value of warm white (0-255); i.e. -warm 150
  -cool       accept value of cool white (0-255); i.e. -cool 150
  -power      accept 'on' or 'off'; i.e. -power on
  -status     get the bulb's status
  -version    get the bulb's version

The user must provide the lightbulb's IP address and either RGB values, HEX values, or a white setting. An updated list of known combinations and rules for HEX values can be found below.

This will set the lightbulb to red:

python3 control.py -ip 192.168.2.2 -rgb 200,0,0

This will set the lightbulb to a specific white temperature and brightness:

python3 control.py -ip 192.168.2.2 -white 150,255

This will set the lightbulb to half power of warm white:

python3 control.py -ip 192.168.2.2 -warm 123

This will turn the lightbulb on with its last setting:

python3 control.py -ip 192.168.2.2 -raw 71:23:0f

I've been able to sniff a few codes that the app sends to the lightbulb. The structure of the hex list follows a pattern. The first bit defines the type of action. Then follow informational bits that define colors, brightness, etc. The entire list is followed by a checksum bit, masked by 255. For example, this is the broken-down list for turning the bulb on:

And here is how the data looks for magenta/purple color:

It's important to note that this script will calculate the checksum bit. You MUST NOT include it in the -raw argument.

There are several different types of commands (Action Bits) that the bulb accepts:

• 31 - Color options
• 61 - Pulse/gradual options
• 71 - Power options
• 81 - Status options

The 31 and 61 action bit commands follow this structure in the body bit list:

31:RR:GG:BB:?BRIGHTNESS?:?COLORTYPE?:0f
61:COLOR(S):BRIGHTNESS:0f

The following examples can help you further understand the structure of the body bit list:

Note that the final checksum bit is not included here. The script will add it automatically.

Firmware 11 has a very different signature and uses 23 bytes instead of 8 (or 9). Here are some parts I've been able to decipher:

b0b1b2b3000102 -- header, always the same
34 -- counter, keeps ticking up
000ee00100 -- filler ??
b1 - white / a1 - color
000000 - white, HEX values for Hue / 2, Saturation , Value if color (ie 006464)
00 -- warm / 64 cool
64 -- brightness for white
0000140000 -- filler?
24 -- checksum