Universal Light Controller

Version of the custom_component 2.2.3 --> Latest version ## Describe the bug Not supported after upgrade from 1.xxx version. I see that there are another issue with the same error (https://github.com/monty68/uniled/issues/47) but it was on 2.2.0 and solved on version 2.2.1. ## Debug log [code]

Excerpt saved from GitHub on 2026-10-23.

The original text was already deleted or overwritten when we archived it.

… initialization: Debug logs: ``` 2024-01-21 15:22:28.916 DEBUG (MainThread) [custom_components.uniled.lib.ble.device] Checking support for: '55:55:07:05:8A:6E' (SP601E)... AdvertisementData(local_name='SP601E', manufacturer_data={20563: b'\x01\x01UU\x07\x05\x8an'}, service_uuids=['00001800-0000-1000-8000-00805f9b34fb', '00001801-0000-1000-8000-00805f9b34fb', '0000ffe0-0000-1000-8000-00805f9b34fb'], rssi=-79) 2024-01-21 15:22:28.916 DEBUG (MainThread) [custom_components.uniled.lib.ble.device] Device 'SP601E' (55:55:07:05:8A:6E) is supported! 2024-01-21 15:22:28.919 DEBUG (MainThread) …

Excerpt saved from GitHub on 2026-10-23.

… 20260128.6 Installation method: HACS ## Configuration logger: default: warning logs: custom_components.uniled: debug ## Describe the bug I am trying to add a BanlanX SP538E controller via BLE. The device is detected during scanning and shows correct local_name as "SP538E", but UniLED reports the device as "not supported". The model SP538E is listed in the supported devices list in the documentation. The device is: Advertising with local_name = SP538E and SP548E Strong RSSI (-79 to -85) However UniLED still reports: Device 'XX:XX:XX:XX:XX:XX' (SP538E or SP548E) not supported! Please advise if …

Excerpt saved from GitHub on 2026-10-23.

Version of the custom_component 3.0.10-beta 11 ## Configuration [code] ## Describe the bug I have an SP548E model 148 that is currently not supported, is there anything I can do to help get it supported. ## Debug log [code]

Excerpt saved from GitHub on 2026-10-23.

Please add support for SP522E 2CH PWM CCT WiFi

Excerpt saved from GitHub on 2026-10-23.

Summary Adds network (WiFi) support for the BanlanX SP541E, a single-colour PWM (music) controller, and fixes two bugs that otherwise stop it from being set up on the `dev_v3` beta. Closes #141, closes #146. ## Changes ### 1. SP541E model signature (`lib/net/sp53x_54xe.py`) The SP541E answers network discovery with model code `0x5C`, which is not in any `SPTechSig.code` dict yet. As a result, `match_model_code()` returns `None` and the config flow reports "Device not supported". Its status response reports light type `0x01`. This matches `0x81` (PWM Mono) with the high bit cleared. The …

Excerpt saved from GitHub on 2026-10-23.

Is your feature request related to a problem? Please describe. BanlanX SP65X models are similar to SP63X, with addtional support for Mi Jia app. Please add support SP65X models as well as SP63X. Describe the solution you'd like Edit the banlanx_6xx.py, add those SP65X models. Additional context Currently, I've change the banlanx_6xx.py, and tested for SP659E, work as well as SP639E. I haven't tested for the other SP65X models, just guessed those ids.

Excerpt saved from GitHub on 2026-10-23.

Summary Adds support for the BanlanX SP661E (single colour PWM controller): power, brightness, three effects (Triangle, Strobe, Heart Beat) and effect speed. How this came about: I (@bartoszbielawski) bought a new LED strip with an SP661E controller and wanted to control it from Home Assistant. UniLED discovered it, but the config entry failed with `device update failed`. The code in this PR was written by Claude Code (an AI coding assistant) while I directed the work: it reverse-engineered the protocol from BLE captures against my real controller, found the cause of the failure, and wrote …

Excerpt saved from GitHub on 2026-10-23.

[code] Add support please.

Excerpt saved from GitHub on 2026-10-23.