I have a bluetooth ceiling lamp from Leroy Merlin. they can be controlled by their ENKI application, I would like to add it to the home assistant somehow, but I have a very big problem because I don’t know how to do it. If someone has already done it or also has the same problem, write everything here.
Same here Inspire Gdansk ENKI
Bought some ENKI lights at a sale as well. Very disappointed about the app and the requirements to register to some cloud service. Did some BT HCI sniffing and identified the chip, the lamps use die BT mesh from Silicon Laboratories. In the “Simplicity Connect” app the lights show up and can be controlled, so it should not be hard to integrate them.
I wrote a small integration for enki app (cloud mode) to support my Eglo v-link tunable white, you can give it a try : GitHub - CyrilP/hass-enki-component: Enki custom component for Home Assistant
maybe it will also work for your lamp
Hello,
I try to your integration in HA. I see also one entry : my address mail. But nothing of my modules evology for a roller shutter. Could you help me, please.
Only lights are supported as this is the only thing I have.
I need an access to an account with more modules to implement them
try these changes with your HA and propose a merge request
I don’t know to adapt your code and I’m not confortable with that. And You, it’s not possible to change your code with an information go ChatGPT and then I could test ?
I created a PR to add support for fans and lights with more than one endpoint. I don't know if you wants to accept PRs. If not, please close it without problem:
@nicok modify by others and test by you is a bit difficult, because normally there are a lot of bugs that need to be fixed while testing, so it's interactive.
If you are able to test python things, start if you want downloading my code from this branch GitHub - McGiverGim/hass-enki-component at add_inspire_radix · GitHub . In the tools folder there is a script (look at the README.md file for instructions) that you can use to connect with Enki and download meta-info for your device.
If you publish this info here (remove identifiers before if you want), I can try to adapt the code for it, but I can't promise anything. I do it with IA too and this month I don't have too much free credits.
Regards!
Hi @CyrilP I own a Lexman solar kit plug&play (flexible) which uses Enki; I might try to add support for it in your project (I'm not a developer but I do understand how these things work, hoping it's not too complicated...).
Anyway, first question is: which repo should I start from?
or
Looks like the first is the "new" one, but the second had a release 4 days ago...
Thanks for clarification.
Also, if you have any input to get me started, it's more than welcome... 
Hi @McGiverGim, I involve you also as it seems you know what you are doing 
I've run the enki_api_live.py script for my device; at first I got the error
Error running live diagnostics: 'NoneType' object has no attribute 'get'
but after correcting a few things (with the help of AI, I can share git diff if you wish) I obtained this output (I substituted IDs and names with $variables):
Devices found: 1
1. $LABEL_NAME | type=inverters | deviceType=inverters | node=$uuid_node
raw-json:
{
"apis": [
"envertech-001"
],
"capabilities": [
"check_energy_production",
"check_power_production"
],
"countries": [
"FR",
"ES",
"IT",
"PT",
"PL",
"GR",
"RO",
"CY"
],
"creationDate": "2026-05-31T09:12:43.822Z",
"defaultPictogram": "ic_64_object_lexman_envertech_inverter",
"deviceId": "$uuid",
"deviceName": "$LABEL_NAME",
"deviceType": "inverters",
"eans": [
"$somenumbers"
],
"homeId": "$myhomeID",
"i18n": "tr_device_lexman_envertech_flexible_inverter_label",
"icon": "inverters",
"imagePaths": [
"01.jpeg",
"02.jpeg"
],
"isEnabled": true,
"label": "$LABEL_NAME",
"mainChangeCapabilityEndpoints": [],
"mainChangeCapabilityId": null,
"mainCheckCapabilityId": "check_power_production",
"manufacturerId": "Lexman",
"nodeId": "$uuid_node",
"overrideCommandCapabilities": [],
"pairingState": "PAIRING_DONE",
"possibleValues": {},
"protocols": [
"lexman_envertech"
],
"searchTags": [
"tr_searchtag_solar_panels_label"
],
"services": [
"NOTIFICATION",
"ENERGY_PRICE_PRODUCTION"
],
"state": "DEFAULT",
"type": "inverters",
"updateDate": "2026-05-31T09:13:24.559Z",
"version": "2.9.0"
}
If you can instruct me further what to do with this data, I'm more than willing to cooperate and improve the integration. Thanks!
I also made a PR with code that works with my device (already tested, the instantaneous power is correctly read from my device) against both repos yours and @CyrilP.
Sorry for bothering, I want to help but I'm not sure of how these things work. Thanks for any response. Hope it's helpful and accepted.
I'm not too sure what I'm doing 
it's more the IA because Python is not my language but I think your PR against the original repo it's ok. I don't think it's needed against my repo because the original developer @CyrilP it's maintaining the original one, so no fork needed.
@CyrilP what is your intention with your repo? Are you willing to make it bigger accepting PRs with new features and devices?
I say that because in the past you accepted some PR, but in the latest days the PRs have been forgotten/ignored. Maybe you simply not have time this days for it, but it will be good to know what is your opinion about it.
No poblem if we need to wait some days more, only to know if your repo is the correct one to push the PRs for a "general" Enki integration.
Regards!
Hello
Given that Cyril's activity on GitHub seems to be very sporadic, I'm working on another version of the Enki integration for Hass. My goal is to integrate, at a minimum, all the accessories I have (light bulbs, outlets, sirens, door/window and motion sensors, thermometers, etc.).
Here's the link if anyone would like to check out the repository.
I'm taking this opportunity to gradually review the code architecture to make it cleaner.
Please feel free to contribute; I'll do my best to incorporate your pull requests.
Hi @bbird,
Good question… the confusion probably comes from two repos and two Cyrils 
(I’m not @CyrilP, same first name, different people).
I opened CyrilP/hass-enki-component#78 to align with him: broader device support, unify the differences between codebases, stop duplicating fixes across two trackers. He confirmed he’s fine pointing to one canonical repo and archiving his when ready.
For your Lexman solar inverter, cyrilcolinet/enki-integration-hass is where that work lives — check_power_production / check_energy_production are supported, regular releases (latest v1.6.14), HACS custom repo.
If something’s missing on your setup, opt-in telemetry can send an anonymized device profile (no account IDs) and pre-fill a GitHub issue — straightforward way to add hardware not covered yet.
Your PR is welcome there if you still have it.
Hi @McGiverGim,
You were right on the Radix endpoint layout: motor on endpoint 2, lights on 1 and 3, not the Siroco+ pattern (motor on 1).
That’s fixed in cyrilcolinet/enki-integration-hass#61, shipped in v1.6.15.
After update via HACS (cyrilcolinet/enki-integration-hass) and a restart, the fan entity should target the motor only and the light entities the LED kit; no cross-control between fan and lights.
If anything’s still wrong on your setup, ping me here or open an issue.
Hi again @bbird,
Your Lexman / Envertech inverter feedback helped: check_power_production and check_energy_production are now wired through api-enki-lexman-envertech-prod, not only the BFF dashboard tile.
In v1.6.15 (cyrilcolinet/enki-integration-hass#61) you should get:
- instant production (W)
- cumulative energy (kWh)
- discovery without needing a live BFF value at setup
HACS custom repo: cyrilcolinet/enki-integration-hass. Update, restart, reload the integration if sensors don’t show up.
Still missing something? Open an issue! Anonymized device profile welcome.