Skip to content

Latest commit

 

History

History
291 lines (224 loc) · 10.6 KB

H6127.md

File metadata and controls

291 lines (224 loc) · 10.6 KB
Raw

H6127

Contributors


BeauJBurroughs
Eric Golde
chvolkmann
Garrett Credi
philhzss

Checklist of packets

  • Keep alive
  • Change Color
  • Set global brightness
  • Change to music mode
  • Change music mode to cycle colors
  • Change Scenes
  • DIY Mode

How packets work

From my understanding, all packets are 20 bytes long. The first byte is a identifier, followed by 18 bytes of data, followed by an XOR of ALL the bytes. 0x33 seems to be a command indicator (the only alternatives value for the first byte is 0xaa, 0xa1)

0x33: Indicator
0xaa: keep alive
0xa1: DIY VALUES

The second byte seems identify the packet type

    0x01: Power
    0x04: Brightness
    0x05: Color

The third byte differs based on type.

For power packets, it's a boolean indicating the power state. (0x00, or 0x01)
For brightness packets, it corresponds to a uint8 brightness value, affecting lights at about 0x14 to 1% - 0xfe to 100%
For color packets, this indicates an operation mode.

0x33: Indicator
    0x01: Power
        0x00: Off
        0x01: On
    0x04: Brightness
        0x00: 0% (also Off)
        0x14: 1%
        0xfe: 100%
    0x05: Color
        0x02: Manual
        0x01: Music
        0x04: Scene
        0x0a: DIY

Color packets also carry an RGB value, followed by a boolean and a second RGB value. The boolean seems to switch the set of LEDs used within the bulb.

Have not verified this in the H6127 but the condition appears to exist. (from h6113)
There is one set for RGB values and one for warm/cold-white values, where True corresponds to the warm/cold-white LEDs. When the flag is set, the first RGB value seems to be ignored and vice-versa. The values for warm/cold-white LEDs cannot be set arbitrarily. The slider within the app UI uses a list of hardcoded color codes. (thanks Henje!)

Zeropadding follows. unless colors can be changed within mode. Finally, a checksum over the payload is calculated by XORing all bytes.

 0x33: Indicator
    0x01: power
        0x00: Off
        0x01: On
    0x04: brightness
        0x00: 0% (also Off)
        0x14: 1%
        0xfe: 100%
    0x05: color
        0x02: Manual
            0x000000: red, green, blue
            0xffffff: red, green, blue
        0x01: music
            0x00: Energic
            0x01: Spectrum(colors)
                0x000000: red, green, blue
                0xffffff: red, green, blue
            0x02: Rolling(colors)
                0x000000: red, green, blue
                0xffffff: red, green, blue
            0x03: Rhythm
        0x04: Scene
            0x00: Sunrise
            0x01: Sunset
            0x04: Move
            0x05: Dating
            0x07: Romantic
            0x08: Blinking
            0x09: Candlelight
            0x0f: Snowflake
        0x0a: DIY

IDENTIFIER, PACKETTYPE, MODE/DATA, MODEID, MODEDATA/DATA, DATA, DATA, DATA, DATA, DATA, DATA, DATA, DATA, DATA, DATA, DATA, DATA, DATA, DATA, XOR
Type Unformatted UUID Formatted UUID
Service 000102030405060708090a0b0c0d1910 00010203-0405-0607-0809-0a0b0c0d1910
Characteristic 000102030405060708090a0b0c0d2b11 00010203-0405-0607-0809-0a0b0c0d2b11

Keep Alive

It is always this, it never seems to change. This is sent every 2 seconds from the mobile app to the device.

0xAA, 0x01, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0xAB
aa010000000000000000000000000000000000ab

On/Off

0x33, 0x01, 0x01, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x33
3301010000000000000000000000000000000033 = on

0x33, 0x01, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x32
3301000000000000000000000000000000000032 = off

#Also setting brightness to 0% seems to turn it off
0x33, 0x04, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x37
330400000000000000000000000000000000037

Set Color

RED, GREEN, BLUE range is 0 - 255 or 0x00 - 0xFF

0x33, 0x05, 0x02, RED, GREEN, BLUE, 0x00, 0xFF, 0xAE, 0x54, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, XOR

#not sure what the middles section is for,(ffae54) but it is included in the XOR and is not always required. Above mentions may be for warm white colors etc

0x33, 0x05, 0x02, RED, GREEN, BLUE, 0X00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, XOR

Set Brightness

BRIGHTNESS range is 0 - 255 or 0x00 - 0xFF

0x33, 0x04, BRIGHTNESS, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, (0x33 ^ 0x04 ^ BRIGHTNESS)

Set Music Modes

3305010000000000000000000000000000000037 = music Energic
3305010100ff00000000000000000000000000c9 = music spectrum(red)
33050101000000ff0000000000000000000000c9 = music spectrum(blue)
3305010200ff00000000000000000000000000ca = music rolling (red)
33050102000000ff0000000000000000000000ca = music rolling (blue)
3305010300000000000000000000000000000034 = music Rhythm

Set Scene

3305040000000000000000000000000000000032 = Scene(Sunrise)
3305040100000000000000000000000000000033 = Scene(Sunset)
3305040400000000000000000000000000000036 = Scene(Movie)
3305040500000000000000000000000000000037 = Scene(Dating)
3305040700000000000000000000000000000035 = Scene(Romantic)
330504080000000000000000000000000000003a = Scene(Blinking)
330504090000000000000000000000000000003b = Scene(Candlelight)
3305040f0000000000000000000000000000003d = Scene(snowflake)```

DIY

DIY mode appears to start with a keep alive followed by a start data packet, followed by 1 to 3 packets of data, followed by an end data packet, followed by the DIY mode command.

The Start Packet consists of 0xa102, PACKET#(0x00), TOTAL PACKET#'S, PADDING, XOR

a102 00 02 000000000000000000000000000000a1 = Start

First 2 bytes are a1 and 02 sigaling a write

0xa102: Write Data

Third byte is the Number of the packet from 00-ff

0x00: Start
0x01: Number of packet
0x02: Number of packet
0x03: Number of packet
0xff: End

Fourth byte is the name of the DIY in the App

3b: Name

Fifth and Sixth bytes are the Style and the Style Mode

00:Fade               01:Jumping              02:Flicker             03:Marquee           04:Music           FF:combo
    00:Whole              00:whole                00:Whole               03:Straight          08:Rhythm          00:??
    01: N/A               01:subsection           01:subsection          04:Gathered          06:Spectrum
    02:Circulation        02:circulation          02:Circulation         05:Dispersive        07:Rolling

Seventh byte is the Speed of transitions 00 being no movement, and 64 appearing to be the fastest

00: No movement
64: Fastest movement

Eighth byte is unknown at this time:

18: PADDING?

Remaining bytes are the Colors limited to 8 colors total between (2 packets)

0xFFFFFF: Red, Green, Blue
0xFFFFFF: Red, Green, Blue
0xFFFFXX: Red, Green, XOR

Last byte is the XOR as shown above:

XX: XOR

0xa102, PACKET#, NAME, STYLE, MODE, SPEED, ??, RED, GREEN, BLUE, RED, GREEN, BLUE, RED, GREEN, BLUE, RED, GREEN, XOR
a102 01 0a 03 03 2b 18 ff0000 ff7f00 ffff00 00ff 1b

The Second packet is mostly only color data and is only necessary if there are more than 2 colors in the DIY:

First 2 bytes of 2nd Packet a102

0xa102: Write Data

Third bytes of 2nd Packet is the packet number

0x02: Packet number

Fourth byte of 2nd Packet is the Blue color data of the previous packet (if more than 2 colors)

0xFF: Blue

Remaining packets are color packets, adding and XOR

0xFFFFFF: Red, Green, Blue
0xFFFFFF: Red, Green, Blue
0xFFFFFF: Red, Green, Blue
0xFFFFFF: Red, Green, Blue
0x000000XX: Padding and XOR

0xa102, PACKET#, BLUE, RED, GREEN, BLUE, RED, GREEN, BLUE, RED, GREEN, BLUE, RED, GREEN, BLUE, 0x00, 0x00, 0x00, XOR
a102 02 00 0000ff 00ffff 8b00ff ffffff 000000d5 = Data

Third Packet Appears to be for Combo Style and Style mode data

a102 03 0100 0200 0303 00000000000000000000a3

End Packet appears to be 0xa102, 0xff, Padding, XOR

a102 ff 000000000000000000000000000000005c = End

DIY Mode command

33050a000000000000000000000000000000003c

Reading current values (seems to be broadcast by Govee device when you initially connect to it, WIP:

There has to be a way to read current status. So far I've discovered this. For brightness, it's aa04......... etc. :

On notification handle (0x0011):
aa04fe0000000000000000000000000000000050 seems to mean that brightness is 100%
aa041400000000000000000000000000000000ba seems to mean that brightness is 1%

It seems like those values are spat out by the bluetooth controller if you write this to the same handle as usual 0x0015:
aa040000000000000000000000000000000000ae

For colour, it's aa05......... etc:

On notification handle (0x0011):
aa050dff0000000000000000000000000000005d seems to mean that colour is 100% red (I have not tested other colours at this time)
We should be able to assume then that aa05 means colour, 0d = ?? (colour state??) and FF, 00 ,00 is the current colour)

It seems like those values are spat out by the bluetooth controller if you write this to the same handle as usual 0x0015:
aa050100000000000000000000000000000000ae

Original Repo

BeauJBurroughs/Govee-H6127-Reverse-Engineering