dave-code-ruiz / elkbledom Goto Github PK

Home Assistant custom component for LED STRIP NAME ELK BLEDOM

License: MIT License

Python 100.00%

hacs-custom hacs-integration home-assistant home-automation led-controller ledstrips light

elkbledom's Introduction

elkbledom HA Integration

Home Assistant integration for LED STRIP or LED Desktop light (lightbar) NAME ELK BLEDOM with android/iphone mobile app duoCo Strip (https://play.google.com/store/apps/details?id=shy.smartled&hl=es&gl=US) or mobile app Lantern Lotus (https://play.google.com/store/apps/details?id=wl.smartled&hl=es&gl=US).

I buy it in amazon spain (https://www.amazon.es/gp/product/B00VFME0Q2)

Or lightbar like this (https://www.amazon.es/bedee-Regulable-Inteligente-Bluetooth-Dormitorio/dp/B0BNPMGR1H)

New support for MELK strip, you can buy it in amazon spain (https://www.amazon.es/distancia-Bluetooth-aplicaci%C3%B3n-sincronizaci%C3%B3n-habitaci%C3%B3n/dp/B09VC77GCZ) or search "B09VC77GCZ" in your amazon country shop. MELK device confirmed working: https://www.amazon.com/dp/B07R7NTX6D

Supported strips

You can scan BT device with BTScan.py in my repository exec: sudo python3 BTScan.py, code supports led strips whose name begins with "ELK-BLE" or "MELK" or "ELK-BULB".

Code supports controlling lights in HA with write uuid: 0000fff3-0000-1000-8000-00805f9b34fb or 0000ffe1-0000-1000-8000-00805f9b34fb

You can know your uuid with gatttool:


gatttool -I

[be:59:7a:00:08:xx][LE]> connect be:59:7a:00:08:xx

Attempting to connect to be:59:7a:00:08:xx

Connection successful

[be:59:7a:00:08:xx][LE]> primary
attr handle: 0x0001, end grp handle: 0x0003 uuid: 00001800-0000-1000-8000-00805f9b34fb
attr handle: 0x0004, end grp handle: 0x0009 uuid: 0000fff0-0000-1000-8000-00805f9b34fb

[be:59:7a:00:08:xx][LE]> Characteristics
handle: 0x0002, char properties: 0x12, char value handle: 0x0003, uuid: 00002a00-0000-1000-8000-00805f9b34fb
handle: 0x0005, char properties: 0x10, char value handle: 0x0006, uuid: 0000fff4-0000-1000-8000-00805f9b34fb
handle: 0x0008, char properties: 0x06, char value handle: 0x0009, uuid: 0000fff3-0000-1000-8000-00805f9b34fb

If your strip show some uuid like "0000fff3-0000-1000-8000-00805f9b34fb" , your strip it is supported

If your strip show some uuid like "0000ffe1-0000-1000-8000-00805f9b34fb" , your strip it is supported

If your strip show some uuid like "0000ff01-0000-1000-8000-00805f9b34fb", go to your correct repository: https://github.com/raulgbcr/lednetwf_ble

If your strip show some uuid like:

"0000xxxx-0000-1000-8000-00805f9b34fb"
xxxx can be one of these values ("ff01", "ffd5", "ffd9", "ffe5", "ffe9", "ff02", "ffd0", "ffd4", "ffe0", "ffe4")

Go to your correct repository: https://www.home-assistant.io/integrations/led_ble/

If your uuid is none of the above, create issue with: 1- strip name 2- your results uuid 3- handle information

You can use gatttool to try discover your turn on/off command with:

sudo gatttool -i hci0 -b be:59:7a:00:08:xx --char-write-req -a 0x0009 -n 7e00040100000000ef # POWERON
sudo gatttool -i hci0 -b be:59:7a:00:08:xx --char-write-req -a 0x0009 -n 7e0004000000ff00ef # POWEROFF

sudo gatttool -b be:59:7a:00:08:xx --char-write-req -a 0x0009 -n 7e0004f00001ff00ef # POWER ON
sudo gatttool -b be:59:7a:00:08:xx --char-write-req -a 0x0009 -n 7e000503ff000000ef # RED
sudo gatttool -b be:59:7a:00:08:xx --char-write-req -a 0x0009 -n 7e0005030000ff00ef # BLUE
sudo gatttool -b be:59:7a:00:08:xx --char-write-req -a 0x0009 -n 7e00050300ff0000ef # GREEN
sudo gatttool -b be:59:7a:00:08:xx --char-write-req -a 0x0009 -n 7e0004000000ff00ef # POWER OFF

Installation

HACS (recommended)

Installation can be done through HACS , search "elkbledom" and download it

Manual installation

You can manually clone this repository inside config/custom_components/ HA folder.

Setup

After installation, you should find elkbledom under the Settings -> Integrations -> Add integration -> search elkbledom integration -> follow instructions.

The setup step includes discovery which will list out all ELK BLEDOM lights discovered. The setup will validate connection by toggling the selected light. Make sure your light is in-sight to validate this.

The setup needs to be repeated for each light.

Config

After Setup, you can config two elkbledom params under Settings -> Integrations -> search elkbledom integration -> Config.

Reset color when led turn on: When led strip turn on, led reset to color white or not. This is needed if you want because i don´t know led strip state and is needed a reset.

Disconnect delay or timeout: You can configure time led strip disconnected from HA (0 equal never disconnect).

Features

Discovery: Automatically discover ELK BLEDOM based lights without manually hunting for Bluetooth MAC address

On/Off/RGB/Brightness support

Emulated RGB brightness: Supports adjusting brightness of RGB lights

Multiple light support

Not supported

Live state polling: External control (i.e. IR remote) state changes NO reflect in Home Assistant and NO updated.

[Light modes] (blinking, fading, etc) is not yet supported.

enable debug mode

Use debug log to see more information of posible errors and post it in your issue description

In configuration.yaml:

logger:
  default: info
  logs:
    custom_components.elkbledom: debug

Examples

Create button to turn on:

show_name: true
show_icon: true
name: turn on
type: button
tap_action:
  action: toggle
entity: light.tiraled

Create button to set color:

show_name: true
show_icon: true
name: Red
type: button
tap_action:
  action: call-service
  service: light.turn_on
  target:
    entity_id: light.test
  data:
    rgb_color:
      - 255
      - 0
      - 0
    brightness: 255

Known issues

If you use mobile app to connect to strip, you need to disconnect it first, only one device can be connected over bluetooth to led strip.
Live state polling dont work.

I am waiting for read status value:

     ```
     
     future = asyncio.get_event_loop().create_future()
     await self._device.start_notify(self._read_uuid, create_status_callback(future))
     # PROBLEMS WITH STATUS VALUE, I HAVE NOT VALUE TO WRITE AND GET STATUS
     await self._write(bytearray([0xEF, 0x01, 0x77]))
     await asyncio.wait_for(future, 5.0)
     await self._device.stop_notify(self._read_uuid)
     
     ```

Credits

This integration will not be possible without the awesome work of this github repositories:

https://www.home-assistant.io/integrations/led_ble/

https://github.com/sysofwan/ha-triones

https://github.com/TheSylex/ELK-BLEDOM-bluetooth-led-strip-controller/

https://github.com/FreekBes/bledom_controller/

https://github.com/FergusInLondon/ELK-BLEDOM/

https://github.com/arduino12/ble_rgb_led_strip_controller

https://github.com/lilgallon/DynamicLedStrips

https://github.com/kquinsland/JACKYLED-BLE-RGB-LED-Strip-controller

https://linuxthings.co.uk/blog/control-an-elk-bledom-bluetooth-led-strip

elkbledom's People

Contributors

Stargazers

Watchers

Forkers

rondoval soska12 ferehcarb gormya double-a-92 ynsgnr tishkoff14433 loopy321 misa1515 modelstudent101 whizkid123 teagan42 amirlanesman

elkbledom's Issues

Don't connect with uuid 0x0003 uuid: 00001800-0000-1000-8000-00805f9b34fb

Hello, I'm trying to connect to my bluetooth led lampshade, but it doesn't work. Its native program is ilink. What data do you need to provide in order to add support for my device in your integration?
char-desc
handle: 0x0001, uuid: 00002800-0000-1000-8000-00805f9b34fb
handle: 0x0002, uuid: 00002803-0000-1000-8000-00805f9b34fb
handle: 0x0003, uuid: 00002a00-0000-1000-8000-00805f9b34fb
handle: 0x0004, uuid: 00002800-0000-1000-8000-00805f9b34fb
handle: 0x0005, uuid: 00002803-0000-1000-8000-00805f9b34fb
handle: 0x0006, uuid: 00002a05-0000-1000-8000-00805f9b34fb
handle: 0x0007, uuid: 00002800-0000-1000-8000-00805f9b34fb
handle: 0x0008, uuid: 00002803-0000-1000-8000-00805f9b34fb
handle: 0x0009, uuid: 0000a042-0000-1000-8000-00805f9b34fb
handle: 0x000a, uuid: 00002902-0000-1000-8000-00805f9b34fb
handle: 0x000b, uuid: 00002803-0000-1000-8000-00805f9b34fb
handle: 0x000c, uuid: 0000a040-0000-1000-8000-00805f9b34fb
handle: 0x000d, uuid: 00002803-0000-1000-8000-00805f9b34fb
handle: 0x000e, uuid: 0000a041-0000-1000-8000-00805f9b34fb
handle: 0x000f, uuid: 00002803-0000-1000-8000-00805f9b34fb
handle: 0x0010, uuid: 0000a043-0000-1000-8000-00805f9b34fb
handle: 0x0011, uuid: 00002902-0000-1000-8000-00805f9b34fb

characteristics
handle: 0x0002, char properties: 0x02, char value handle: 0x0003, uuid: 00002a00-0000-1000-8000-00805f9b34fb
handle: 0x0005, char properties: 0x02, char value handle: 0x0006, uuid: 00002a05-0000-1000-8000-00805f9b34fb
handle: 0x0008, char properties: 0x10, char value handle: 0x0009, uuid: 0000a042-0000-1000-8000-00805f9b34fb
handle: 0x000b, char properties: 0x08, char value handle: 0x000c, uuid: 0000a040-0000-1000-8000-00805f9b34fb
handle: 0x000d, char properties: 0x02, char value handle: 0x000e, uuid: 0000a041-0000-1000-8000-00805f9b34fb
handle: 0x000f, char properties: 0x10, char value handle: 0x0010, uuid: 0000a043-0000-1000-8000-00805f9b34fb

primary
attr handle: 0x0001, end grp handle: 0x0003 uuid: 00001800-0000-1000-8000-00805f9b34fb
attr handle: 0x0004, end grp handle: 0x0006 uuid: 00001801-0000-1000-8000-00805f9b34fb
attr handle: 0x0007, end grp handle: 0x0011 uuid: 0000a032-0000-1000-8000-00805f9b34fb

Light strip fails to add

Hi. I decided to try this project as I have an ELKBLEDOM Strip in my kitchen. I set up Bluetooth on my server (generic-x86) and installed the integration. The integration finds my light strip but when I try to go add it i get an endless spinning circle.

If i leave the app, I get an unknown error. Nothings shows up in the logs, just a warning saying that this is a custom integration. I'm pretty new to bluetooth Hass devices as i just got the Bluetooth integration working on my server.

More than 1 light

Is it possible to have more than 1 light on HA? I have one all set up and working fine and it keeps popping up that it finds the second but fails to connect.

Another LED driver

Hello,

I have a LED driver which uses the same Android app (duoCo Strip), but is not recognized by HA.
It is a brand new installation of HA - it seems that gatttool is no longer available.

After giving the command at the terminal: "bluetoothctl info MAC_address"
I get following result:
Device BE:FF:50:00:92:A4 (public)
Name: ELK-BLEDOM
Alias: ELK-BLEDOM
...
UUID: Human Interface Device (00001812-0000-1000-8000-00805f9b34fb)

Please guide me thru on how to use bluetoothctl if anything more is needed to add that strip to the list.

Automation and Home Assistant

I ran into a HA problem when creating automation.
It is only possible to turn on/off/switch the state.
Is it possible to change the color and launch the effect through automation?

Device becomes unresponsive

Hi there. First let me thank you for the work you have put into this integration. I found a cheap LED set on Temu and was excited to get it to work with your integration. Everything appeared to be working but it seems that after a while it stops being responsive. A restart oF HA brings it back to a working state for some unknown amount of time but after a while it stops working again. I have found that if I use the gatttool I can again interact with the device though it is slow to respond initially. I do not see any errors in my HA logs.

For reference, this is the device I am using:

gapplication gatttool
bash-5.1# gatttool -I
[ ][LE]> connect be:96:19:00:1e:d3
Attempting to connect to be:96:19:00:1e:d3
Connection successful
[be:96:19:00:1e:d3][LE]> primary
attr handle: 0x0001, end grp handle: 0x0007 uuid: 00001800-0000-1000-8000-00805f9b34fb
attr handle: 0x0008, end grp handle: 0x000b uuid: 00001801-0000-1000-8000-00805f9b34fb
attr handle: 0x000c, end grp handle: 0xffff uuid: 0000fff0-0000-1000-8000-00805f9b34fb
[be:96:19:00:1e:d3][LE]> Characteristics
handle: 0x0002, char properties: 0x02, char value handle: 0x0003, uuid: 00002a00-0000-1000-8000-00805f9b34fb
handle: 0x0004, char properties: 0x02, char value handle: 0x0005, uuid: 00002a01-0000-1000-8000-00805f9b34fb
handle: 0x0006, char properties: 0x02, char value handle: 0x0007, uuid: 00002a04-0000-1000-8000-00805f9b34fb
handle: 0x0009, char properties: 0x20, char value handle: 0x000a, uuid: 00002a05-0000-1000-8000-00805f9b34fb
handle: 0x000d, char properties: 0x06, char value handle: 0x000e, uuid: 0000fff3-0000-1000-8000-00805f9b34fb
handle: 0x000f, char properties: 0x10, char value handle: 0x0010, uuid: 0000fff4-0000-1000-8000-00805f9b34fb

Any idea on what may be causing the device to become unresponsive?

Is there any chance you could post a sample of what it would take to turn the strip on/off using gatttool interactive? I'd like to see if I can do it from there without problem to try and troubleshoot further.

Any help you can provide is most appreciated!

FutureWarning: BLEDevice.rssi is deprecated and will be removed in a future version of Bleak, use AdvertisementData.rssi instead return self._device.rssi

Logger: py.warnings
Source: custom_components/elkbledom/elkbledom.py:186
Integration: Elkbledom (documentation, issues)
First occurred: 20:13:21 (3 occurrences)
Last logged: 20:14:49

/config/custom_components/elkbledom/elkbledom.py:186: FutureWarning: BLEDevice.rssi is deprecated and will be removed in a future version of Bleak, use AdvertisementData.rssi instead return self._device.rssi

Any way to also control with App (I have Magic Lantern)?

I see you mentioned below that there can only be one connection at a time. Is it possible to allow the app to connect while HA integration is loaded?
Right now the effect is wrong and there is now way for me to change it to the desired value.
This is on a MELK with character 0000FFF3-0000-1000-8000-00805F9B34FB

==========================

There are only one connection to led strip, if HA is connected to strip, gatttool not work.

1- You need to delete HA integration with elkbledom strip.
2- restart strip
3- send commands with gatttool, first 7e0783 and second 7e0404 in this order.

Finally connect HA integration again

good luck

Originally posted by @dave-code-ruiz in #45 (comment)

Can't set up device within HA integration settings

As explained in the title, I did install this project, made sure that my strip led is compatible with this plugin on my Raspberry Pi 4 (with manual HA install). However, when I try to add the strip led in HA, I end up with the error message Config flow could not be loaded: {"message":"Invalid handler specified"}...

Steps to reproduce :

Install elkbledom with HACS
Go to Settings > Integration > Add Integration
See error message flashing

While watching the HA's log, I see this error line :

$  tail -f ./home-assistant.log

2023-09-01 14:45:22.717 WARNING (SyncWorker_2) [homeassistant.loader] We found a custom integration elkbledom which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2023-09-01 14:45:46.340 ERROR (MainThread) [homeassistant.config_entries] Error occurred loading flow for integration elkbledom: No module named 'bluetooth_sensor_state_data'

But I do already have this lib installed :

$ python3 -m pip install bluetooth-sensor-state-data
Defaulting to user installation because normal site-packages is not writeable
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Requirement already satisfied: bluetooth-sensor-state-data in /usr/local/lib/python3.11/dist-packages (1.6.2)
Requirement already satisfied: home-assistant-bluetooth>=1.3.0 in /usr/local/lib/python3.11/dist-packages (from bluetooth-sensor-state-data) (1.10.3)
Requirement already satisfied: sensor-state-data>=2.0 in /usr/local/lib/python3.11/dist-packages (from bluetooth-sensor-state-data) (2.17.1)

BLEDOM device no longer being detected

I have a cheap BLEDOM device that was working.
I though it may be someone the recent updates but I downgraded to version 0.0.4 which I was sure was working but the device was not detected by the plugin.
Was there a recent change in HA that limited this addon?

The specific device seems to be detailed on this Github page https://github.com/arduino12/ble_rgb_led_strip_controller

Does not connect to the device

It finds it instantly, but when trying to connect, it constantly turns and cannot connect in any way. As a result, it issues a message to reconnect.
In HA 2023.07, the tape was installed at least every other time. Then I was constantly buggy and passed out, But sometimes it worked. After updating this integration, nothing has changed.
If you update HA from ,07 to ,08, then the device remained, but there was not a single object, and if you install it immediately on ,08, it does not connect.

Находит мгновенно, но при попытке соединиться постоянно крутит и никак не может соединиться. В итоге выдает сообщение на повторное соединение.
В HA 2023.07 лента хоть через раз, но устанавливалась. Потом глючила постоянно и отрубалась, Но иногда работала. После обновления этой интеграции ничего не изменилось.
Если обновить HA с ,07 на ,08 то устройство оставалось, но ни одного объекта не было, а если установить сразу на ,08 то не подключается.

Effect reset when changing brightness

If i set en effect (eg: blink_green), the led are starting linking green. nice. But if i change brightness the effect is stopped and led are back in "full green".
So impossible to change brightness when using effects
Using this Led strip:

20MAC864WB BLK

anyway to add music sync support?

i was thinking of adding music sync support using something like appdeamon and python, is there a way to integrate them with the already working integration or would need a custom one? Thanks again

Color temperature widget has too high values

In this view to set the color temperature the values range from 10000K to 999999K, which is too much.

A reasonable range would maybe be 1000K to 9999K. I assume there is maybe some wrong decimal offset..?

Also the color for me does not work properly. It's either green-ish at around 10000K, and everywhere else it's a white-blue.
I don't know if it's just my LED strip not supporting it, or if it's because of the high values,

Bledom device not working

I am unable to add 2 devices to this integration. I can connect to both through phone app Lotus Lantern and can see MAC codes but get an error when trying to connect stating unable to connect to Elkbledom

Unable to connect to Elkbledom 1.0.1

Not connected on version 1.0.1 (1.0.0 also), but connected on version 0.0.4.

Device:

root@orangepi3-lts:~# gatttool -I
[                 ][LE]> connect BE:58:A5:00:00:36
Attempting to connect to BE:58:A5:00:00:36
Connection successful
[BE:58:A5:00:00:36][LE]> primary
attr handle: 0x0001, end grp handle: 0x0003 uuid: 00001800-0000-1000-8000-00805f9b34fb
attr handle: 0x0004, end grp handle: 0x0009 uuid: 0000fff0-0000-1000-8000-00805f9b34fb
[BE:58:A5:00:00:36][LE]> Characteristics
handle: 0x0002, char properties: 0x12, char value handle: 0x0003, uuid: 00002a00-0000-1000-8000-00805f9b34fb
handle: 0x0005, char properties: 0x10, char value handle: 0x0006, uuid: 0000fff4-0000-1000-8000-00805f9b34fb
handle: 0x0008, char properties: 0x06, char value handle: 0x0009, uuid: 0000fff3-0000-1000-8000-00805f9b34fb

In DEBUG bluetooth:

2023-04-24 00:30:40.445 DEBUG (MainThread) [bleak_retry_connector] ELK-BULB5       - BE:58:A5:00:00:36: Connection attempt: 1
2023-04-24 00:30:40.450 DEBUG (MainThread) [homeassistant.components.bluetooth.wrappers] BE:58:A5:00:00:36 - ELK-BULB5       -> /org/bluez/hci0: Connecting (last rssi: -83)
2023-04-24 00:30:41.283 DEBUG (MainThread) [homeassistant.components.bluetooth.wrappers] BE:58:A5:00:00:36 - ELK-BULB5       -> /org/bluez/hci0: Connected (last rssi: -83)
2023-04-24 00:30:52.395 DEBUG (MainThread) [homeassistant.components.bluetooth.base_scanner] hci0 (4F:E6:AC:D6:ED:89): Scanner watchdog time_since_last_detection: 0.3000001499985956

The lamp is plugged in 220v. Distance 1.5 meters.

When the lamp is disconnected from 220v:

2023-04-24 00:58:06.562 DEBUG (MainThread) [bleak_retry_connector] ELK-BULB5       - BE:58:A5:00:00:36: Connection attempt: 1
2023-04-24 00:58:06.564 DEBUG (MainThread) [bleak_retry_connector] ELK-BULB5       - BE:58:A5:00:00:36: Failed to connect: No backend with an available connection slot that can reach address BE:58:A5:00:00:36 was found, backing off: 4.0 (attempt: 1, last rssi: None)
2023-04-24 00:58:06.565 DEBUG (MainThread) [bleak_retry_connector.bluez] ELK-BULB5       - BE:58:A5:00:00:36: Device was removed from bus, waiting 4.0 for it to re-appear: 'org.bluez.Device1'
x10

On version 0.0.4 bluetooth debug:

2023-04-24 01:32:24.359 DEBUG (MainThread) [bleak_retry_connector] ELK-BULB5       - BE:58:A5:00:00:36: Connection attempt: 1
2023-04-24 01:32:24.366 DEBUG (MainThread) [homeassistant.components.bluetooth.wrappers] BE:58:A5:00:00:36 - ELK-BULB5       -> /org/bluez/hci0: Connecting (last rssi: -85)
2023-04-24 01:32:28.917 DEBUG (MainThread) [homeassistant.components.bluetooth.base_scanner] hci0 (4F:E6:AC:D6:ED:89): Scanner watchdog time_since_last_detection: 2.5600013210005272
2023-04-24 01:32:31.057 DEBUG (MainThread) [homeassistant.components.bluetooth.manager] hci0 (4F:E6:AC:D6:ED:89) [connectable]: BE:58:A5:00:00:36 AdvertisementData(local_name='ELK-BULB5      ', service_uuids=['00001800-0000-1000-8000-00805f9b34fb', '0000fff0-0000-1000-8000-00805f9b34fb'], rssi=-84) match: set()
2023-04-24 01:32:31.060 DEBUG (MainThread) [homeassistant.components.bluetooth.wrappers] BE:58:A5:00:00:36 - ELK-BULB5       -> /org/bluez/hci0: Connected (last rssi: -85)
2023-04-24 01:32:50.903 DEBUG (MainThread) [bleak_retry_connector] ELK-BULB5       - BE:58:A5:00:00:36: Connection attempt: 1
2023-04-24 01:32:50.904 DEBUG (MainThread) [homeassistant.components.bluetooth.wrappers] BE:58:A5:00:00:36 - ELK-BULB5       -> /org/bluez/hci0: Connecting (last rssi: -85)
2023-04-24 01:32:51.659 DEBUG (MainThread) [homeassistant.components.bluetooth.wrappers] BE:58:A5:00:00:36 - ELK-BULB5       -> /org/bluez/hci0: Connected (last rssi: -85)

On version 0.0.4 it connects well, but there are problems with white light.
I don't know what to do...

wrong behavior detected by @diandr6 94% brightness

In #22 the user @diandr6 detected wrong behavior, she explain it :

The lamp works and connects, but the white color does not behave as usual. For the interface, the lamp is always at 94% brightness (even if the HA interface is set to 1%) and the selected color mode. Warm white and cool white modes do not work correctly. Warm white = 10,000K and cool white = 1,000,000K when the actual range is 3000K to 6500K. When the lamp is turned on in white mode, the interface is displayed as in color mode (blue or light yellow) and turning off / on the lamp switches it to color mode.

And with video

I think the video will make it clearer what's going on.
https://youtu.be/AtCGdVATMDE

Version | core-2022.8.0 got this error but it is working

This error originated from a custom integration.

Logger: custom_components.elkbledom.elkbledom
Source: custom_components/elkbledom/elkbledom.py:196
Integration: Elkbledom (documentation, issues)
First occurred: 14:52:30 (1 occurrences)
Last logged: 14:52:30

Error getting status: [org.freedesktop.DBus.Error.UnknownObject] Method "Connect" with signature "" on interface "org.bluez.Device1" doesn't exist

Version	core-2022.8.0
Installation Type	Home Assistant OS
Development	false
Supervisor	true
Docker	true
User	root
Virtual Environment	false
Python Version	3.10.5
Operating System Family	Linux
Operating System Version	5.10.17-v8
CPU Architecture	aarch64
Timezone	America/New_York
Configuration Directory	/config

Effect Speed LED

I have paired my two strip led and ON/OFF command works.
The integration have found Effect Speed LED, but nothig happens if I change that value (0-100 range).
The integration did not founf the RGB settings.

Error adding entities for domain light with platform elkbledom (Since HA 2023.8.0)

Logger: homeassistant.components.light
Source: helpers/entity_platform.py:619
Integration: Lumière (documentation, issues)
First occurred: 20:13:24 (2 occurrences)
Last logged: 20:13:24

Error adding entities for domain light with platform elkbledom
Error while setting up elkbledom platform for light
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 510, in async_add_entities
await asyncio.gather(*tasks)
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 619, in _async_add_entity
device = dev_reg.async_get(self.hass).async_get_or_create(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: homeassistant.helpers.device_registry.DeviceRegistry.async_get_or_create() got multiple values for keyword argument 'config_entry_id'

Live state polling dont work.

Hello,

I want to change color on my Led strip when my screen colors change. So I write a python script to get average color and send color to my Led strip through HA.
The color change in state but the LED Strip don't change.
I saw that this is a known issue.

Do you know when the issue will be resolved ?

Thank you

Pool Lights from amazon

There are a bunch of these on amazon, surprisingly they hit amazon before aliexpress, they are relatively new.

Here is some info from the one I bought, do you think these are fairly the same? I can try to test/debug when I get a chance

Logger: custom_components.elkbledom.elkbledom

Hello

Connection broke since the last release

https://www.home-assistant.io/blog/2022/07/06/release-20227/#breaking-changes

Error
Config flow could not be loaded: undefined

self.brightness value can be None, leading to a crash in _transform_color_brightness

In some cases, the function _transform_color_brightness crashes because it is given a None value for brightness by the upstream funnctions.

Error is:
unsupported operand type(s) for *: 'int' and 'NoneType'

Relevant part of the trace:

File "/usr/src/homeassistant/homeassistant/components/light/init.py", line 582, in async_handle_light_on_service
await light.async_turn_on(**filter_turn_on_params(light, params))
File "/config/custom_components/elkbledom/light.py", line 163, in async_turn_on
color = self._transform_color_brightness(color, self.brightness)
File "/config/custom_components/elkbledom/light.py", line 130, in _transform_color_brightness
res = tuple(color * set_brightness // 255 for color in rgb)
File "/config/custom_components/elkbledom/light.py", line 130, in
res = tuple(color * set_brightness // 255 for color in rgb)
TypeError: unsupported operand type(s) for *: 'int' and 'NoneType'

Context:
This seems to happen when self.brightness is None from a new/uninitialized/switched-off device, but I cannot say exactly

Workaround:
A workaround is a sanity check in _transform_color_brightness, e.g.
if set_brightens is None: set_brightness =0

but it would be better to find the root cause and fix the initialization, I guess.
Happy to help when I get the time, thanks so much for your great work!

set_effect_speed function

Hi.
First thank you for this great work!

I can't find how to change the speed of the effects. I can see the set_effect_speed function but I can't find anything on the HA side.

Thanks !

Cannot configure LotusLamp strip (worked before)

In September I bought a LED strip [https://www.amazon.de/gp/product/B0CBBLQ8WH/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1] and was happy when I found out, that it was controllable by Home Assistant through this HACS integration,
After an update it stopped working and I had to delete the integration, but downgrading did not help.
With latest version, configuring after installation of HACS integration and restart leads to:

2024-02-04 08:51:08.173 ERROR (MainThread) [root] A message handler raised an exception: Cannot convert home_assistant_bluetooth.models.BluetoothServiceInfoBleak to habluetooth.models.BluetoothServiceInfoBleak Traceback (most recent call last): File "src/dbus_fast/message_bus.py", line 798, in dbus_fast.message_bus.BaseMessageBus._process_message File "/home/homeassistant/.homeassistant/deps/lib/python3.11/site-packages/bleak/backends/bluezdbus/manager.py", line 979, in _parse_msg self._run_advertisement_callbacks( File "/home/homeassistant/.homeassistant/deps/lib/python3.11/site-packages/bleak/backends/bluezdbus/manager.py", line 1028, in _run_advertisement_callbacks callback(device_path, device.copy()) File "/home/homeassistant/.homeassistant/deps/lib/python3.11/site-packages/bleak/backends/bluezdbus/scanner.py", line 270, in _handle_advertising_data self.call_detection_callbacks(device, advertisement_data) File "/home/homeassistant/.homeassistant/deps/lib/python3.11/site-packages/bleak/backends/scanner.py", line 210, in call_detection_callbacks callback(device, advertisement_data) File "src/habluetooth/scanner.py", line 179, in habluetooth.scanner.HaScanner._async_detection_callback File "src/habluetooth/scanner.py", line 204, in habluetooth.scanner.HaScanner._async_detection_callback File "src/habluetooth/manager.py", line 398, in habluetooth.manager.BluetoothManager.scanner_adv_received File "src/habluetooth/manager.py", line 398, in habluetooth.manager.BluetoothManager.scanner_adv_received File "src/habluetooth/manager.py", line 437, in habluetooth.manager.BluetoothManager.scanner_adv_received TypeError: Cannot convert home_assistant_bluetooth.models.BluetoothServiceInfoBleak to habluetooth.models.BluetoothServiceInfoBleak

I guess I cannot work around any more :-(

Loght strip not connecting

As of yesterday the light strip imtegration has stopped working
It says "Retrying setup: Couldn't find a nearby device with address:"

Support for LED Desktop light (lighbar)

Hi there - reading through the instructions, it seems like this integration only supports LED light strips. Is it possible to use with lightbars as well?

LED strip not returning any data

My cheap LED strip from AliExpress is recognized automatically, but it throws an error when trying to configure it.

This error originated from a custom integration.

Logger: custom_components.elkbledom.elkbledom
Source: custom_components/elkbledom/elkbledom.py:547
Integration: elkbledom (documentation, issues)
First occurred: 11:17:10 PM (6 occurrences)
Last logged: 11:19:08 PM

ELK-BLEDOB: Device unexpectedly disconnected; RSSI: -68

This error originated from a custom integration.

Logger: custom_components.elkbledom.elkbledom
Source: custom_components/elkbledom/elkbledom.py:435
Integration: elkbledom (documentation, issues)
First occurred: 11:17:47 PM (1 occurrences)
Last logged: 11:17:47 PM

Error getting status: ELK-BLEDOB - BE:60:B0:00:88:21: Failed to connect after 4 attempt(s): failed to discover services, device disconnected

I can connect to it through gatttool. However, both primary and Characteristics commands return nothing:

$ gatttool -I
[                 ][LE]> connect be:60:b0:00:88:21
Attempting to connect to be:60:b0:00:88:21
Connection successful
[be:60:b0:00:88:21][LE]> primary
Error: Discover all primary services failed: Request attribute has encountered an unlikely error

Initial release observations

Thank you very much for your effort!
I can confirm that it connects automatically to the Bluetooth strip controller!

The only functionality that worked for me is turning it off. Everything else like turn on, color selection, brightness, status, is not working.

Thanks again for creating this. Hopefully the community will have something fully working at some point

ELK-BLE pattern support

Hello there,

I saw in the readme that setting the pattern is not yet supported, if you are interested I have it working. I only own "ELK-BLE" lights so I am unable to test on the other types you support.

The bytes are:

0x7E
0x05
0x03
(patternNumber + 0x80)
0x03
0xFF
0xFF
0x00
0xEF

If this doesn't work for you, or you already know this, please disregard this and sorry to waste your time.

Support for newer type

Hi,

I've got some strips that report as MELK (found device: BE:16:71:00:18:91 0 MELK-OA10 ) instead of ELK and they use the DuoCo StripX app from the play store. By default they don't seem to work. For what I can tell, it looks as if these are looking for some initial (auth?) packet before they accept commands.

After I send char-write-cmd 0x0009 7e0783 and then 7e0404 I got them to work. From then on they seem happy to accept all existing commands.

gattool reports:

[BE:16:71:00:18:91][LE]> primary 
attr handle: 0x0001, end grp handle: 0x0003 uuid: 00001800-0000-1000-8000-00805f9b34fb
attr handle: 0x0004, end grp handle: 0x0009 uuid: 0000fff0-0000-1000-8000-00805f9b34fb
[BE:16:71:00:18:91][LE]> characteristics 
handle: 0x0002, char properties: 0x12, char value handle: 0x0003, uuid: 00002a00-0000-1000-8000-00805f9b34fb
handle: 0x0005, char properties: 0x10, char value handle: 0x0006, uuid: 0000fff4-0000-1000-8000-00805f9b34fb
handle: 0x0008, char properties: 0x06, char value handle: 0x0009, uuid: 0000fff3-0000-1000-8000-00805f9b34fb

Here's the base64-encoded btsnoop log:

YnRzbm9vcAAAAAABAAAD6gAAAAwAAAAMAAAAAQAAAAAA4s3Mx5T8fAIKIAcAAwAEAALIAAAAAAwA
AAAMAAAAAAAAAAAA4s3Mx5UQTAIKAAcAAwAEAAPIAAAAABcAAAAPAAAAAQAAAAAA4s3Mx5XnHQIK
IBIADgAEABEGAQADAAAAAA4AAAAOAAAAAQAAAAAA4s3Mx5bSFwIKIAkABQAEAAEQCgAKAAAADgAA
AA4AAAABAAAAAADizczHmDCWAgogCQAFAAQAAQgBAAoAAAAOAAAADgAAAAEAAAAAAOLNzMeafMAC
CiAJAAUABAABCAMACgAAAA4AAAAOAAAAAQAAAAAA4s3Mx5tv3gIKIAkABQAEAAEIBAAKAAAAGQAA
AA8AAAABAAAAAADizczHm6kTAgogFAAQAAQACQcFABAGAAAADgAAAA4AAAABAAAAAADizczHm+NX
AgogCQAFAAQAAQgJAAoAAAAOAAAADgAAAAAAAAAAAOLNzMeb5OwCCgAJAAUABAAEBwAHAAAAAA8A
AAAPAAAAAQAAAAAA4s3Mx5w7gQIKIAoABgAEAAUBBwACKQAAAAwAAAAMAAAAAAAAAAAA4s3Mx6Gw
jwIKAAcAAwAEAAoJAAAAABoAAAAPAAAAAQAAAAAA4s3Mx6K3YAIKIBUAEQAEAAt+BATwAAAAABUA
AAAPAAAAAAAAAAAA4s3Mx6MSlQIKABAADAAEAFIJAH4HgwAAAA8AAAAPAAAAAAAAAAAA4s3Mx6vg
qQIKAAoABgAFABMCAgAAAAAAABUAAAAPAAAAAAAAAAAA4s3Mx7JSjAIKABAADAAEAFIJAH4EBAAA
ABUAAAAPAAAAAAAAAAAA4s3Mx7162wIKABAADAAEAFIJAH4EBAAAABUAAAAPAAAAAAAAAAAA4s3M
x8g/HAIKABAADAAEAFIJAH4EBA==

(save as melk.txt, then cat melk.txt | base64 -d > melk.log and open that in wireshark)

Any ideas what more you would need to support these?

ELK-BLEDOB

I have a ELK-BLEDOB and I can't connect the integration. Can someone help me?

UID Not shown

Hi i do have some uid which are not listed,

7579F3BF-064A-6559-852E-2CDB7D8A74D8

A3А680D5-9E15-CAA7-42E3-E71777F36314

also i attached a screenshot

Brightness and color selecting not working

//it shows when i try to select color
(Polish language)
I can't select color from wheel and can't adjust brightness.
Also can't find where i can switch back to solid mode.

Set Color

Thx for your integration. Works fine.
Is there a option to set the color via scripts using yaml code?
I've tried the rgb_color options from the light domain, but this does not work for me.

Always white when lighting up

Hey,

Thanks for your plugin, it was really what i was looking for !
But i would like to keep the same color every time i turn it on/off. Unfortunately, it always go white, is there any reason for that ?
Is there a way for me to keep the last used color ?

Thanks,

Lyliya

Error log timeout

Hi
happy to see that "ELKBLEDOM" is now integrated with HA

i have two ELKBLEDOM...

one is white.... this one is working
RGB.. this one is not working

===================

This error originated from a custom integration.

Error getting status: Device with address BE:FF:20:00:D8:C8 could not be found. Try increasing timeout value or moving the device closer.

ModuleNotFoundError: No module named 'custom_components.xiaomi_gateway3'

Hello, im getting the bellow error in the new version. The integration wont load.

File "/config/custom_components/elkbledom/init.py", line 8, in
from .elkbledom import BLEDOMInstance
File "/config/custom_components/elkbledom/elkbledom.py", line 8, in
from custom_components.xiaomi_gateway3.core.device import update
ModuleNotFoundError: No module named 'custom_components.xiaomi_gateway3'

Adding Light strip fails

Hi, i can not add the strip, it runs into a timeout while trying to connect.

Strip: https://amzn.eu/d/hCpoa3l (Ailbton 10m BT Neon Strip)
Home Assistant: Supervisor 2023.10.0 @os 10.5 running on x86 Intel NUC
BT: tried onboard BT, external USB BT 5.0 and 5.3 Adapters.

UUID:

The Integration does find the Strip:

But fails to connect:

Logs:
`2023-10-06 20:43:13.154 DEBUG (MainThread) [custom_components.elkbledom.config_flow] Discovered bluetooth devices, step bluetooth, : BE:67:00:25:6D:E0 , ELK-BLEDOM00
2023-10-06 20:43:13.154 DEBUG (MainThread) [custom_components.elkbledom.config_flow] Discovered bluetooth devices, step bluetooth confirm, : None
2023-10-06 20:43:13.154 DEBUG (MainThread) [custom_components.elkbledom.config_flow] Discovered supported devices: ELK-BLEDOM00 - BE:67:00:25:6D:E0 - -127
2023-10-06 20:44:12.750 DEBUG (MainThread) [custom_components.elkbledom.config_flow] Discovered supported devices: ELK-BLEDOM00 - BE:67:00:25:6D:E0 - -127
2023-10-06 20:44:22.550 DEBUG (MainThread) [custom_components.elkbledom.elkbledom] device ELK-BLEDOM00: BE:67:00:25:6D:E0 -46
2023-10-06 20:44:22.550 DEBUG (MainThread) [custom_components.elkbledom.elkbledom] Model information for device ELK-BLEDOM00 : ModelNo ELK-BLE, Turn on cmd [126, 0, 4, 240, 0, 1, 255, 0, 239], Turn off cmd [126, 0, 4, 0, 0, 0, 255, 0, 239], rssi -46
2023-10-06 20:44:22.550 DEBUG (MainThread) [custom_components.elkbledom.elkbledom] init command for: ELK-BLEDOM00 not needed; RSSI: -46
2023-10-06 20:43:13.154 DEBUG (MainThread) [custom_components.elkbledom.config_flow] Discovered bluetooth devices, step bluetooth, : BE:67:00:25:6D:E0 , ELK-BLEDOM00
2023-10-06 20:43:13.154 DEBUG (MainThread) [custom_components.elkbledom.config_flow] Discovered bluetooth devices, step bluetooth confirm, : None
2023-10-06 20:43:13.154 DEBUG (MainThread) [custom_components.elkbledom.config_flow] Discovered supported devices: ELK-BLEDOM00 - BE:67:00:25:6D:E0 - -127
2023-10-06 20:44:12.750 DEBUG (MainThread) [custom_components.elkbledom.config_flow] Discovered supported devices: ELK-BLEDOM00 - BE:67:00:25:6D:E0 - -127
2023-10-06 20:44:22.550 DEBUG (MainThread) [custom_components.elkbledom.elkbledom] device ELK-BLEDOM00: BE:67:00:25:6D:E0 -46
2023-10-06 20:44:22.550 DEBUG (MainThread) [custom_components.elkbledom.elkbledom] Model information for device ELK-BLEDOM00 : ModelNo ELK-BLE, Turn on cmd [126, 0, 4, 240, 0, 1, 255, 0, 239], Turn off cmd [126, 0, 4, 0, 0, 0, 255, 0, 239], rssi -46
2023-10-06 20:44:22.550 DEBUG (MainThread) [custom_components.elkbledom.elkbledom] init command for: ELK-BLEDOM00 not needed; RSSI: -46
2023-10-06 20:44:22.550 DEBUG (MainThread) [custom_components.elkbledom.elkbledom] ELK-BLEDOM00: Connecting; RSSI: -46
2023-10-06 20:45:43.602 ERROR (MainThread) [custom_components.elkbledom.elkbledom] Error getting status: ELK-BLEDOM00 - BE:67:00:25:6D:E0: Failed to connect after 4 attempt(s): TimeoutError

2023-10-06 20:45:43.616 DEBUG (MainThread) [custom_components.elkbledom.elkbledom] Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/bleak/backends/bluezdbus/client.py", line 209, in connect reply = await self.bus.call(
^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/dbus_fast/aio/message_bus.py", line 399, in call await future asyncio.exceptions.CancelledError
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/bleak_retry_connector/init.py", line 350, in establish_connection await client.connect(
File "/usr/src/homeassistant/homeassistant/components/bluetooth/wrappers.py", line 292, in connect connected = await super().connect(**kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/bleak/init.py", line 605, in connect return await self._backend.connect(**kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/bleak/backends/bluezdbus/client.py", line 146, in connect async with async_timeout(timeout):
File "/usr/local/lib/python3.11/asyncio/timeouts.py", line 111, in _aexit raise TimeoutError from exc_val
TimeoutError
The above exception was the direct cause of the following exception:

Traceback (most recent call last):
File "/config/custom_components/elkbledom/elkbledom.py", line 407, in update await self._ensure_connected()
File "/config/custom_components/elkbledom/elkbledom.py", line 455, in _ensure_connected
client = await establish_connection(
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/bleak_retry_connector/init.py", line 374, in establish_connection
_raise_if_needed(name, device.address, exc)
File "/usr/local/lib/python3.11/site-packages/bleak_retry_connector/init.py", line 314, in _raise_if_needed
raise BleakNotFoundError(msg) from exc bleak_retry_connector.BleakNotFoundError: ELK-BLEDOM00 - BE:67:00:25:6D:E0: Failed to connect after 4 attempt(s): TimeoutError
2023-10-06 20:45:43.617 DEBUG (MainThread) [custom_components.elkbledom.elkbledom] ELK-BLEDOM00: Connecting; RSSI: -46`

any idea?
regards,
Sven

Changing brightness slowly ruins the color

When I change the brightness with the "Light" panel on my home view, the set color slowly degrades towards pure Red, pure Blue or pure Green.

E.g.

Set a white-ish color at 100%
Change it to 1%
Change it back to 100%
Color becomes a bit more orange
Change it to 1% and back to 100%
Color becomes more red
Repeat a few times
Color is pure Red

In real life this color has become Red at 30%

Maybe some rounding or integer division error while calculating the new RGB value?

Integration error

running HAOS on virtual machine, everything else is working, but while integrating, it doesn't auto discover but asks for mac address directly, after adding the address but its giving me a unknown error

cant connect to UUID

my UUid is not on the ones you mentioned so
Device BE:58:60:05:AE:BB (public)
Name: ELK-BLEDOM
Alias: ELK-BLEDOM
Paired: no
Trusted: no
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
UUID: Unknown (0000fff0-0000-1000-8000-00805f9b34fb)

Light strip is not detected as a device

Home Assistant 2023.8.0
Supervisor 2023.07.1
Operating System 10.4
Frontend 20230802.0 - latest

Added integration via HACS with latest version, and when adding device, it finds the lights, blink test is successful, but the lights show as entity, unable to control.

HA OS

How can I use this in HAOS? I cant run the commands you list to get the uuid and stuff.

ELK-BLEDOM with different char value handle

Hi, I have a LED strip which seems to have a different char value handle and thus isn't supported.
Instead of 0x0009 like in the examples, I have 0x000e for the char properties: 0x06.

Those are the commands I could get to work:

sudo gatttool -b BE:96:50:00:00:23 --char-write-req -a 0x000e -n 7e00040100000000ef # POWER ON
sudo gatttool -b BE:96:50:00:00:23 --char-write-req -a 0x000e -n 7e00040000000000ef # POWER OFF

sudo gatttool -b BE:96:50:00:00:23 --char-write-req -a 0x000e -n 7e000503ff000000ef # RED
sudo gatttool -b BE:96:50:00:00:23 --char-write-req -a 0x000e -n 7e0005030000ff00ef # BLUE
sudo gatttool -b BE:96:50:00:00:23 --char-write-req -a 0x000e -n 7e00050300ff0000ef # GREEN

sudo gatttool -b BE:96:50:00:00:23 --char-write-req -a 0x000e -n 7e00010000000000ef # 0% Bightness
sudo gatttool -b BE:96:50:00:00:23 --char-write-req -a 0x000e -n 7e00013200000000ef # 50% Bightness
sudo gatttool -b BE:96:50:00:00:23 --char-write-req -a 0x000e -n 7e00016400000000ef # 100% Bightness

And here the full gatttool output in case it's also needed:

[BE:96:50:00:00:23][LE]> primary
attr handle: 0x0001, end grp handle: 0x0007 uuid: 00001800-0000-1000-8000-00805f9b34fb
attr handle: 0x0008, end grp handle: 0x000b uuid: 00001801-0000-1000-8000-00805f9b34fb
attr handle: 0x000c, end grp handle: 0xffff uuid: 0000fff0-0000-1000-8000-00805f9b34fb
[BE:96:50:00:00:23][LE]> Characteristics
handle: 0x0002, char properties: 0x02, char value handle: 0x0003, uuid: 00002a00-0000-1000-8000-00805f9b34fb
handle: 0x0004, char properties: 0x02, char value handle: 0x0005, uuid: 00002a01-0000-1000-8000-00805f9b34fb
handle: 0x0006, char properties: 0x02, char value handle: 0x0007, uuid: 00002a04-0000-1000-8000-00805f9b34fb
handle: 0x0009, char properties: 0x20, char value handle: 0x000a, uuid: 00002a05-0000-1000-8000-00805f9b34fb
handle: 0x000d, char properties: 0x06, char value handle: 0x000e, uuid: 0000fff3-0000-1000-8000-00805f9b34fb
handle: 0x000f, char properties: 0x10, char value handle: 0x0010, uuid: 0000fff4-0000-1000-8000-00805f9b34fb

Issue on Config / Setup - Missing Parameter

Hi,

Great integration, I encountered an issue when adding the integration for my device. I was getting "Unknown Error"

Log file pointed to a missing parameter on line 171 of config_flow.py.

Looking through history it appears that there is now a 'delay' parameter required for BLEDOMInstance - I noticed this has been updated elsewhere in the codebase but looks like config_flow.py was missing still.

I verified by passing a hard-coded parameter by directly editing the file and was then able to continue to with the setup and now the integration works well.

Error tryng to add lights

I've installed this integration from HACS but anytime I try to add from integration panel an error message (in italian) says me : "impossible to load configuration flow: {"message":"Invalid handler specified"}" with only an ok button that end the configuration process. What can I do?

UUID With errors

I recently bought a bluetooth adapter like UDUP EP-B3536 and a led strip of the type supported in Lotus Lanterne app. The adapter is regularly seen in my Home Assistant supervisrd on Debian 11, and in fact I added it in the Devices section and service, but after installing your elkbledom software via Hacs, i tried to add the led strip both like "ElkBLEDOM" sia come "Led-Ble" senza successo. In the first case I get an "Unknown error occurred" after entering the nane and the address in the format BE:89:E0:03:D0:09 because the strip is not automatically detected, in the second it tells me that it hasn't found anything. My UUIDs are as follows:

        "0000110e-0000-1000-8000-00805f9b34fb",
        "0000110a-0000-1000-8000-00805f9b34fb",
        "00001200-0000-1000-8000-00805f9b34fb",
        "0000110b-0000-1000-8000-00805f9b34fb",
        "00001108-0000-1000-8000-00805f9b34fb",
        "0000110c-0000-1000-8000-00805f9b34fb",
        "00001800-0000-1000-8000-00805f9b34fb",
        "00001801-0000-1000-8000-00805f9b34fb",
        "0000180a-0000-1000-8000-00805f9b34fb",
        "00001112-0000-1000-8000-00805f9b34fb"

I took them from the diagnostic file of the Devices and services section, which also shows the correct recognition of the Bluetooth, I attach it below. What am I missing? Where is wrong?
config_entry-bluetooth-aa74d345fb9124bd52c2c667ebbda5f8.txt

Lag

Huge lag like for 2 mins or so