Sayyid Sofwan

@claudiocn this looks like a different error. Please [enable debugging](https://github.com/sysofwan/ha-triones#debugging) for full error trace.

@claudiocn this is common. See [this issue](https://github.com/sysofwan/ha-triones/issues/5). It is a BLE connection issue that will self recover. The debug log “cc 23 e3” shows that it successfully recovered and sent...

Oh, so it never finish setup. The library you tested is using your browser’s (local) Bluetooth hardware, not Home Assistant’s. For troubleshooting: 1. Make sure no other device is connected...

Thanks, this is have better logs and is the same issue here. `No supported read/write UUIDs found` means that the read UUID for your device is not known. Unfortunately, Triones...

Yeah, it’s weird. I’ll add some more debug logs later to figure this out.

Can you add logs to the triones.py:72 uuid detection code to see why it’s not finding the uuid? You can modify the code inside `config/custom_components/triones` folder, and restart HA afterwards.

Try logging `self._device.services.characteristics.values()` instead

Not sure why the library is not detecting any characteristics. You can check if it detects it if we go through each service. Sample code [here](https://github.com/hbldh/bleak/blob/develop/examples/service_explorer.py). Meanwhile, you can hardcode...

Another guess is we need to call `await self._device.get_services()` explicitly before querying the services in some implementation. Example [here](https://github.com/hbldh/bleak/blob/4adf5d5b6ef7dd2642b6e71a2fa4e913a85d077a/examples/connect_by_bledevice.py). Can you try it?

I think that’s a good idea. The integration is using the [bleak](https://bleak.readthedocs.io/en/latest/) library internally, probably need to lookup if they expose this information. Feel free to make a pull request...