English | Русский

Local-only Homebridge plugin for BroadLink LB1 smart bulbs.

It controls compatible bulbs directly over the local network using the BroadLink UDP protocol. Normal operation does not require BroadLink Cloud, Magic Home, an account, or Python.

Python is used only by the optional helper scripts for initial Wi-Fi provisioning and LAN unlock.

The plugin was physically tested with the bulb shown above.

Confirmed device identification:

Packaging may vary between sellers. The definitive compatibility check is discovery reporting device class lb1 and devtype 0x60C8.

Other BroadLink bulb revisions are currently unverified and should not be considered supported until confirmed on real hardware.

• HomeKit Lightbulb accessory
• On / off
• Brightness
• Hue and saturation
• Color temperature
• Local state polling
• Automatic LAN discovery
• Manual device configuration
• Stable accessory identity based on MAC address
• Automatic re-authentication after connection/session failures
• Firmware watchdog keepalive ping
• Multiple bulbs supported
• No cloud dependency during normal operation

Install the plugin from the Homebridge UI by searching for:

homebridge-broadlink-lb1-local

or install it from the command line:

npm install -g homebridge-broadlink-lb1-local

Then restart Homebridge.

The bulb must be connected to your Wi-Fi and left LAN-unlocked before Homebridge can control it.

If your bulb is already connected to Wi-Fi and reports Locked: False, you can skip this section and continue with Homebridge Configuration.

The helper scripts in scripts/ use python-broadlink only for the initial preparation process. They are not used by Homebridge afterwards.

Clone this repository:

git clone https://github.com/IvanTroshka/homebridge-broadlink-lb1-local.git
cd homebridge-broadlink-lb1-local

Create a temporary Python virtual environment:

python3 -m venv .venv
. .venv/bin/activate
pip install -r scripts/requirements.txt

Factory-reset the bulb and put it into its Wi-Fi setup state.

On the tested LB1, setup mode is indicated by fast blinking.

If the bulb exposes a temporary setup Wi-Fi access point, connect the computer running the setup script to that network before continuing.

Avoid adding the bulb back to old third-party applications if your goal is direct LAN control. The tested bulb was previously provisioned by an old Magic Home application in a LAN-locked state.

Run:

python scripts/setup_bulb.py "Your Wi-Fi SSID"

The script prompts for the Wi-Fi password without echoing it.

You can also provide the password explicitly:

python scripts/setup_bulb.py "Your Wi-Fi SSID" --password "your-wifi-password"

For a different supported security mode:

python scripts/setup_bulb.py "Your Wi-Fi SSID" --security wpa1/2

After successful provisioning, the bulb should leave setup mode and join your normal Wi-Fi network.

Find the bulb in your router/DHCP leases or with your preferred LAN scanner.

The Homebridge accessory identity is based on the bulb MAC address, not its IP address, so later DHCP address changes do not create duplicate accessories.

Run:

python scripts/unlock_lb1.py --ip 192.168.1.50

Replace 192.168.1.50 with the bulb's actual address.

The helper:

• discovers the bulb;
• authenticates locally;
• calls set_lock(False);
• performs a fresh discovery;
• verifies that Locked is False;
• verifies that a fresh session can authenticate and read state.

The Homebridge plugin never intentionally sets the device lock to true.

Example:

{
  "platform": "BroadlinkLB1Local",
  "name": "BroadLink LB1 Local",
  "discovery": true,
  "pollInterval": 10,
  "keepAliveInterval": 90,
  "devices": [
    {
      "name": "LB1 Lamp",
      "host": "192.168.1.50",
      "mac": "aa:bb:cc:dd:ee:ff"
    }
  ]
}

Manual and discovered devices are de-duplicated by MAC address.

You can also use discovery only:

{
  "platform": "BroadlinkLB1Local",
  "name": "BroadLink LB1 Local",
  "discovery": true,
  "devices": []
}

Manual device entries support:

{
  "name": "LB1 Lamp",
  "host": "192.168.1.50",
  "mac": "aa:bb:cc:dd:ee:ff"
}

Optional device fields may include port and devtype.

The plugin cannot authenticate to a LAN-locked bulb.

Reset/re-provision the bulb and run:

python scripts/unlock_lb1.py --ip YOUR_BULB_IP

Check that Homebridge and the bulb are on the same LAN/VLAN and that UDP broadcast traffic is allowed.

You can also configure the bulb manually with its IP and MAC address.

The plugin automatically retries communication and re-authenticates when needed.

For firmware that uses the BroadLink watchdog, keepalive ping is enabled by default every 90 seconds.

HomeKit uses mired values while the LB1 protocol uses Kelvin. The plugin performs the conversion internally.

The current implementation clamps outgoing color temperature to 2700K..6500K.

The optional setup helpers use python-broadlink, an MIT-licensed project for local BroadLink device control.

The Homebridge plugin itself communicates with the bulb directly from Node.js/TypeScript and does not require python-broadlink at runtime.