ISP-7532FE (32FE) shows up, but fails to add to HA

[kbalint]

Hi, I've just bought this aforementioned ISP-7532FE (32FE) lights, and I can use it with Bluetooth on my phone. I've added your integration as well. For some time it just asked for a MAC address, after it identified the lights on it's own, but can not add it to HA (says unknown error occured) In the logs I see the following:

Logger: custom_components.ideal_led.idealled
Source: custom_components/ideal_led/idealled.py:362
integration: ideal_led (documentation, issues)
First occurred: 18:33:46 (1 occurrences)
Last logged: 18:33:46

Error getting status: ISP-7532FE - A6:0E:44:75:32:FE: Failed to connect after 9 attempt(s): No backend with an available connection slot that can reach address A6:0E:44:75:32:FE was found: The proxy/adapter is out of connection slots or the device is no longer reachable; Add additional proxies (https://esphome.github.io/bluetooth-proxies/) near this device

The Raspberry PI running the HA and the Ligh dongle is ~ 3m in distance but on different levels in the house (there's a floor between). Can't really move any of them; but it keeps popping up when I restart HA. All together there are 17 other BT LE devices are in the house, and HA can pick up all of them without any problem here in a ~30m radius.

[8none1]

I don't think this is a problem with the integration itself. The integration relies on HA to do all the actual low-level Bluetooth comms. This error is coming from HA itself.

The number of simultaneous connections is limited by the hardware. You can read more about that here: https://www.home-assistant.io/integrations/bluetooth/

However, BT LE devices are "connectionless" (kinda) so that shouldn't really be a problem. It's possible that your lights have a slightly different controller and there is a problem with the handshake, but I don't think it's that.

I'd suggest getting hold of a cheap ESP32 dev board and flashing it with ESPhome and setting up a Bluetooth proxy. It's really easy and will probably solve your problem.

Also it's worth looking at the stand-along controller here

You can run that on the Pi when HA is not running (you need to install simplepyble too) and if that doesn't work either then it's likely that the controller is subtly different.

[ops244]

hi, I have the same problem ...
at the same time, he connects the lamps (blinks several times), does not react to anything else...

Error getting status: IDL-F7EEFF - 36:C5:87:F7:EE:FF: Failed to connect after 11 attempt(s): No backend with an available connection slot that can reach address 36:C5:87:F7:EE:FF was found: The proxy/adapter is out of connection slots or the device is no longer reachable; Add additional proxies (https://esphome.github.io/bluetooth-proxies/) near this device

[8none1]

It's possible you both have newer hardware/firmware than I have on my devices and that they changed the protocol. Perhaps you are running a newer version on HA than me.

I'll upgrade to the latest version of HA and see if that makes any difference. But right now I can't reproduce this problem.

[8none1]

I built a dev container off the bleeding edge of Home Assistant and I'm sorry to report that everything works fine here. I was even passing the Bluetooth device on my laptop through to a docker container in order to control the lights.

So I strongly suspect that this is because you have lights which have a later hardware/software revision than the version I have and that they changed the protocol.

Really the only option is to reverse engineering the new devices and decode the new protocol.

[ops244]

Thank you, unfortunately I can't do that (

[8none1]

Can you share a link to where you bought your device. Maybe I can get one and take a look.

[ops244]

this is a Christmas garland on the Christmas tree, it's unlikely that you have such a thing for sale, the era brand

erasg-03