Uniled cannot connect to SP620E anymore

[dancom81]

Describe the bug

Uniled cannot connect aynmore to SP620E

Configuration

I'm using the addon on an Home Assistant docker install on a raspberry pi 4.
Core 2024.1.1, Frontend 20240104.0

Version of the custom_component

I also tried to downgrade from 2.2.5 to 2.2.1 but same issue.

Configuration

docker compose HA

    ...
    volumes:
        - /run/dbus:/run/dbus:ro
    privileged: true

    #command: /bin/bash -c "bluetoothctl power on && hass -c /config/"

    restart: unless-stopped
    devices:
        - /dev/ttyUSB0:/dev/ttyUSB0
        - /dev/ttyUSB1:/dev/ttyUSB1

only added this

          ...
          bluetooth:
          ...

Add your logs here.

log

here a part of the log

2024-02-28 20:17:28.642 DEBUG (MainThread) [custom_components.uniled.lib.ble.device] Checking support for: '34:00:00:00:0B:34' (SP620E)... AdvertisementData(local_name='SP620E', manufacturer_data={20563: b'\x1b\x104\x00\x00\x00\x0b4'}, service_uuids=['0000ffe0-0000-1000-8000-00805f9b34fb', '5833ff01-9b8b-5191-6142-22a4536ef123'], rssi=-70)
2024-02-28 20:17:28.642 DEBUG (MainThread) [custom_components.uniled.lib.ble.device] Device 'SP620E' (34:00:00:00:0B:34) is supported!
2024-02-28 20:17:28.644 DEBUG (MainThread) [custom_components.uniled] *** Setup UniLED BLE Device: 34:00:00:00:0B:34: SP620E v3 - {'transport': 'ble', 'address': '34:00:00:00:0B:34', 'model': 'SP620E'} AdvertisementData(local_name='SP620E', manufacturer_data={20563: b'\x1b\x104\x00\x00\x00\x0b4'}, service_uuids=['0000ffe0-0000-1000-8000-00805f9b34fb', '5833ff01-9b8b-5191-6142-22a4536ef123'], rssi=-50)
2024-02-28 20:17:28.645 DEBUG (MainThread) [custom_components.uniled.lib.ble.device] SP620E: Inititalizing (SP620E)...
2024-02-28 20:17:28.645 DEBUG (MainThread) [custom_components.uniled.lib.ble.device] SP620E: Set model as 'SP620E' by SPLED (BanlanX)
2024-02-28 20:17:28.645 DEBUG (MainThread) [custom_components.uniled.lib.channel] Inititalized: channel_0 (0x7f87d0fad0)
2024-02-28 20:17:28.645 DEBUG (MainThread) [custom_components.uniled.lib.ble.device] SP620E: Updated '34:00:00:00:0B:34' advertisement; RSSI: -50
AdvertisementData(local_name='SP620E', manufacturer_data={20563: b'\x1b\x104\x00\x00\x00\x0b4'}, service_uuids=['0000ffe0-0000-1000-8000-00805f9b34fb', '5833ff01-9b8b-5191-6142-22a4536ef123'], rssi=-50)
2024-02-28 20:17:28.645 DEBUG (MainThread) [custom_components.uniled] *** Awaiting UniLED Device: SP620E, first response...
2024-02-28 20:17:28.646 DEBUG (MainThread) [custom_components.uniled.lib.ble.device] SP620E: Update!
2024-02-28 20:17:28.646 DEBUG (MainThread) [custom_components.uniled.lib.ble.device] SP620E: Update - Send State Query... (retrys=0)
2024-02-28 20:17:28.646 DEBUG (MainThread) [custom_components.uniled.lib.ble.device] SP620E: Send 1 command(s), attempt 1 of 1...
2024-02-28 20:17:28.646 DEBUG (MainThread) [custom_components.uniled.lib.ble.device] SP620E: Connecting '34:00:00:00:0B:34'; RSSI: -50
2024-02-28 20:18:49.668 ERROR (MainThread) [custom_components.uniled.lib.ble.device] SP620E: Device not found, no longer in range, or poor RSSI: -50
2024-02-28 20:18:49.668 DEBUG (MainThread) [custom_components.uniled.lib.ble.device] SP620E: Send command failed!
2024-02-28 20:18:49.669 DEBUG (MainThread) [custom_components.uniled.coordinator] Finished fetching SP620E data in 81.023 seconds (success: False)
2024-02-28 20:18:49.669 WARNING (MainThread) [custom_components.uniled] SP620E: First update attempt failed!
2024-02-28 20:18:49.670 DEBUG (MainThread) [custom_components.uniled.lib.ble.device] SP620E: Stopped
2024-02-28 20:18:50.189 DEBUG (MainThread) [custom_components.uniled.coordinator] SP620E: Coordinator destroyed
2024-02-28 20:18:50.190 DEBUG (MainThread) [custom_components.uniled.lib.device] SP620E: Deleted Device
2024-02-28 20:18:50.190 DEBUG (MainThread) [custom_components.uniled.lib.channel] Deleted: channel_0

Text

after installing it through HACS I was able to detect and connect the SP620E and control it.
unfortunately in the coming days it started to disconnect regularly.
thought it was a problem with the rpi 4 and searched how to fix the bluetooth, made some change to the docker compile and the bluetooth seems to work.
but then the Uniled isn't able anymore to connect with the SP620E: it shows always Initializing status and then no success. if I try to configure I get the error 
"Config flow could not be loaded: 500 Internal Server Error Server got itself in trouble"
with the IOs app I can still control it, so the device is fine.

any idea what could be?

[Flatking]

Same Problem with SP602E :(

[dancom81]

after an update of the IOS app, now it started to work again in the uniled too.. hope it last

[dancom81]

it didn't. already impossible to connect to it via Uniled / HA. Still working on the app

[marcelloceschia]

Same with our SP620E.
It was working once, but since then no success.

[satvilla]

Same with SP630e, it seems that the integration doesn't use the bluettoth gateway and can't connect to the LED driver because is to far. Does it have sense?