Project: re-pair Sengled Zigbee bulbs in Zigbee2MQTT and bring Wi-Fi bulbs back with SengledTools local UDP

Discuss the Sengled Smart Lighting Hubs
Post Reply
User avatar
ZerOne
Site Admin
Posts: 292
Joined: Sun Dec 13, 2020 8:21 am

A project post for Sengled bulbs that lost their cloud. Part 1 covers Zigbee bulbs with Zigbee2MQTT. Part 2 covers Wi-Fi bulbs using the community SengledTools Home Assistant integration. It is based on the Zigbee2MQTT device pages and the SengledTools README, as at October 2026. I have not run it, so check the current README and issues first.

Safety: switch the bulb off at the wall before changing it, use it only in a suitable enclosed-rated fitting, and do not flash firmware into a bulb you cannot afford to lose. Keep the bulbs on an IoT VLAN.

Part 1: Zigbee bulbs and Zigbee2MQTT
  1. Enable permit join in the Zigbee2MQTT frontend.
  2. Factory reset the bulb as the Zigbee2MQTT device page for your model says. For the E11-N1EA the page says: start with the bulb on, then quickly turn it off and on at least 10 times, ending in an ON state. If it worked, the bulb flashes five times, meaning it is in pairing mode. If it does not flash, try again.
  3. Watch the Zigbee2MQTT log for the device to be interviewed, then rename it.
  4. Remember Sengled bulbs are end devices, not routers, so add a few mains-powered routers elsewhere.
Part 2: Wi-Fi bulbs with SengledTools
  1. Factory reset the bulb. The README says to flick the power switch rapidly 5 or more times until it flashes, and it links a reset guide for other Sengled Wi-Fi products.
  2. On a PC on the same network, with Python 3.10 or later, clone the repository and run the wizard (run_wizard.sh on Linux or macOS, run_wizard.bat on Windows). Manual route:

Code: Select all

git clone https://github.com/HamzaETTH/SengledTools.git
cd SengledTools
pip install -r requirements.txt
python sengled_tool.py --setup-wifi
  1. When the wizard asks, switch the PC to the bulb's temporary Wi-Fi (named like Sengled_Wi-Fi Bulb_XXXXXX) and follow the prompts to give it your home Wi-Fi.
  2. Give the bulb a DHCP reservation on your router.
  3. Copy the project's custom_components/sengled_udp folder to config/custom_components/sengled_udp in Home Assistant, restart, then add the Sengled UDP integration under Devices & services. You can choose Discover or enter bulb IPs by hand.
Per the project's integration README, the bulbs are controlled over UDP port 9080, which means Home Assistant must be able to reach it, and you get light entities with on/off, brightness, RGB colour and colour temperature. If a bulb's IP changes, that bulb's entity will stop working until you update it.

Do not flash casually

The README says flashing open firmware (Tasmota, ESPHome or WLED) can permanently brick the bulb, and that it was tested with the W31-N15 and W31-N11 only. Other models use other modules and may not work. The UDP integration is the lower-risk path, and the README suggests trying it first.

Keep it safe
  • IoT VLAN, DHCP reservation, and a firewall rule letting only Home Assistant reach UDP 9080.
  • No port-forwarding and no internet access for the bulbs, now that the cloud is gone.
  • Do the Wi-Fi provisioning on a laptop you trust, and do not enter your main Wi-Fi password into anything you do not trust. Use a separate IoT Wi-Fi network if you can.
Discussion: which Sengled models have you got working this way? Did the wizard work first time, and did you need anything beyond the README?
Post Reply

Return to “Sengled Smart Hub Discussion”