That’s phenomenal! Any chance you’ve tested whether it keeps working across power loss/reboots?
Any possibility of adding the function to change color?
That’s phenomenal! Any chance you’ve tested whether it keeps working across power loss/reboots?
Any possibility of adding the function to change color?
Awesome ![]()
Thank’s for sharing your work ![]()
Did you also try to get this working with(in) esphome or are there technical difficulties not allowing this (easily)? ![]()
It looks like esphome does not really have an implementation for BLE Mesh yet
https://github.com/esphome/feature-requests/issues/1671
If you mean restart of the ESP, that works fine. The state is stored in the flash of the ESP so it reconnects to the BLE Mesh network after a restart.
What is still not perfect is that if HA restarts, you have to manually send again the config mqtt message so that the entities appear in HA. I did not have time to code that part but it should be relatively easy as HA sends a message when the mqtt service is started
Hey. Could you explain how you did that?
I accidentally upgraded the firmware on my ledvance G50 globe, and after that it is no longer recognizable by apple homekit. Apparently it has upgraded from BLE to Sig Mesh. Now, I desperately wanna go back to the previous firmware. Looks like you have done this before and would appreciate it if you teach me how.
Did anyone get the colors working? Nordic devzone says the nrfmesh app doesn’t support all mesh models like HSL.
Wondering what the best approach is - the Sylvania app is OK but I don’t know if I can export keys and have it working in multiple devices + homeassistant.
I can export the nrfmesh setup and import it into another device but the new device doesn’t work until I plug/unplug the lamp. I don’t know if BLE mesh can work with multiple phones/servers controlling the same lamp or group.
Docker/Bluetooth mesh would be good but my server may be too far to work reliably.
@Ultraworg any idea if your code would be easy to port/add to esphome/Tasmota/OMG?
Hi guys,
I have two of the W27 filament bluetoth bulbs(https://www.ledvance.com/consumer/products/smart-home/smart-lamps/smart-bluetooth/smart-classic-filament-lamps-with-bluetooth-technology/classic-bulb-shape-with-filament-style-with-bluetooth-technology-c6328), but i guess the boxes went to trash, I didn’t realise i would need the qr code to add them to homekit. Does anyone have the qr code they can share to add them to homekit?
Thanks
What exactly do you need from the app? I have managed to reverse engineer the telink ble mesh app and also the NRF app.
Thanks you for the work, I also got it to work with this, after I added CONFIG_HTTPD_MAX_REQ_HDR_LEN=1024 to sdkconfig.
see Header fields are too long (fixed) · Issue #4 · Ultraworg/LEDVANCE_BLE_MESH · GitHub
I tried all of this but i still get
marshmallow.exceptions.ValidationError: {‘token’: [‘Field may not be null.’]}
and
ValueError: invalid literal for int() with base 16: ‘{“network”: {}, “token”: null, “acl”: {}}’
no matter how many times i restart
Same for me
marshmallow.exceptions.ValidationError: {‘token’: [‘Field may not be null.’]}
Any hints? Reboot doesn’t help
Hello ! If someone is still searching,
I made an integration for this bulb, where I can control this specific bulbs from my RPI, without needing an additional device.
I hope it will help !
Putting the code here : GitHub - ELO-I/ledvance-mesh: Local Bluetooth Mesh control of Ledvance / Sylvania SMART+ bulbs for Home Assistant · GitHub
Hi ELO!
I recently started using Home Assistant and found some old LEDVANCE SMART+ Bluetooth LED strips that still work perfectly in the original app.
I came across your project and installed Ledvance Mesh 0.3.0 on Home Assistant 2026.11.0 (Docker on Synology).
Good news: Home Assistant discovers the LEDVANCE device and adds it successfully!
Unfortunately, I can’t control it. All controls are greyed out.
I’m using an ESP32 Bluetooth Proxy, located about one meter from the LED strip.
These errors appear in my Home Assistant logs:
Connection request ignored, state: CONNECTING
Connection open failed, status=133
Ledvance Mesh also reports:
Lamp added but not configured yet
(no lamp of the network is reachable over Bluetooth)
The diagnostics show:
proxy: null
setup_version: 0
state: None
I’ve already restarted the ESP32 Bluetooth Proxy, but the issue persists.
Do you have any idea what might be causing this? Could it be related to using an ESPHome Bluetooth Proxy instead of a local Bluetooth adapter?
Thanks for your work on this integration!
Cheers,
Dimi