search

millskyle / BRMesh_homeassistant

ESP32 interface for interfacing BRMesh lights to HomeAssistant using MQTT
17 stars 1 forks source link

readme

BRMesh Home Assistant

Here in Canada, it seems like it's impossible to get outdoor floodlights that are compatible with Home Assistant. All the available options on Amazon employ the "BRMesh" app. The app admittedly works well, but of course I want Home Assistant integration, which this completely offline app does not support. The lights themselves are sold under several brand names, such as MELPO, SOLLA, Neliwo, but they seem to all be the same light.

This solves my problem and integrates the lights into HomeAssistant. This is firmware for an ESP32 that will allow control of "BRMesh" lights.

Requirements

Software Requirements

Hardware Requirements

Instructions

After making the modifications listed below, you should be able to flash an ESP with this firmware, and it will automatically talk to Home Assistant and announce the lights. They will appear in the MQTT integration as a "BRMesh" light. It seemed like magic to me when it happened. I was shocked it worked.

Modifications:

Several things must be modified in the sketch. You'll want to take a look at this section and modify it before flashing:

//IP Address of your MQTT Broker (probably your Home Assistant host)
#define MQTT_BROKER_ADDR IPAddress(192,168,0,100)
//Your MQTT UserName
#define MQTT_BROKER_USER "User123"
//Your MQTT Password
#define MQTT_BROKER_PASS "password1234"
//Your WiFi SSID
#define WIFI_SSID "MyWifi"
//Your Wifi Password
#define WIFI_PASS "wifipassword"

const uint8_t my_key[] = { 0x38, 0x35, 0x31, 0x33 }; //Unique key from BRMesh app (found using USB debugging and adb logcat)
byte mac[] = {0x14, 0x39, 0x28, 0x32, 0xa7, 0xb0}; // find in serial console upon reset, e.g. "start ESP32 DEVICEID - AABBCCDDEEFF"  (<-that's the MAC)

const int redundancy = 5;  // Repeats sending each command to the lights this many times; BLE broadcasting was flakey

Obtaining my_key from BRMesh

  1. Add the lights you wish to control to BRMesh app
  2. Plug your Android phone into your computer and run the command: 
    adb logcat  | grep getPayloadWithInner
  3. Accept the warning on your phone
  4. Change the color of your lights, turn them on and off, etc. You should see some things printed to your terminal like this: 
    11-27 21:25:23.309  7827  7827 I jyq_helper: getPayloadWithInnerRetry---> payload:22035b000000000000000000,  key: 31323334
11-27 21:25:23.309  7827  7827 I jyq_helper: getPayloadWithInnerRetry---> mSendCnt:95,  sSendSeq:243,  seq:243
11-27 21:25:28.338  7827  7827 I jyq_helper: getPayloadWithInnerRetry---> payload:22037f000000000000000000,  key: 31323334
11-27 21:25:28.338  7827  7827 I jyq_helper: getPayloadWithInnerRetry---> mSendCnt:96,  sSendSeq:244,  seq:244
11-27 21:25:29.567  7827  7827 I jyq_helper: getPayloadWithInnerRetry---> payload:7203ff00ff00000000000000,  key: 31323334
11-27 21:25:29.567  7827  7827 I jyq_helper: getPayloadWithInnerRetry---> mSendCnt:97,  sSendSeq:245,  seq:245
  5. Write down the "key". In this case, 31323334 means you'll input const uint8_t my_key[] = { 0x31, 0x32, 0x33, 0x34 }; in the Arduino sketch.

MQTT and Wifi Credentials

Set you MQTT and Wifi credentials. Nothing to really explain here. If you need to change your MQTT port, I've hardcoded that and you can find it in the code in the mqtt.begin() call.

Set the MAC address

If you don't know the MAC address of your ESP32, you can flash the firmware with the incorrect MAC address, and watch in the serial monitor. Upon boot, the ESP prints its true MAC address. Fill this in the sketch and re-flash.

Modify the number of lights

I bought a 4-pack of these lights, and thus wrote the code for 4 lights. It can be easily modified in the sketch by changing the numLights, mylights, and mylightnames declarations.

Flashing

I had an issue with flashing my ESP32 (I'm pretty new to Arduino IDE...maybe this is obvious), but I had to go to Tools > Partition Scheme and change it to "Huge APP (3MB...)" or I got a "sketch too large" error.

Known issues

White temperature

My light did not have color temperature, so I've omitted it as I could not decode the BRMesh payload for such commands without owning a compatible light. It should be possible to modify this if the payloads can be obtained.

Incorrect States

The ESP tries to keep track of and report the correct state of the lights to HomeAssistant, but since the lights don't communicate (only receive broadcast commands), there's no way to tell if a light received the command sent to it, or if it has been changed via another method (e.g. the BRMesh app). Thus the state reported in Home Assistant should not be taken as absolute truth about the state of the light.

Commands not received by light

Only about 80% of the commands that I sent to the lights actually were received. Thus I introduced the redundancy variable in the firmware. Each command is sent redundancy times (defaultt: 5) very quickly in series. This seems to solve almost all issues. If you're having problems with commands being flakey, try upping this.

Acknowledgements