Sayyid Sofwan

+1 this is going to be super useful for discovery

+1 I don't see the point of dependOn if this is not supported.

+1 happening to me too. Mostly triggered by P2P streaming.

I had the same issue. It was fixed by setting the camera’s streaming quality to low.

Make sure the recording quality is also low. Also I find that sometimes I have to reload the page for steaming to start.

This is probably caused by your Home Assistant not having access to BLE hardware. Try using [gatttool](https://cxiao.net/posts/2015-12-13-gatttool/) from your HA container and make sure it is working first.

Please share your log output, the issue may not be the same. I am using the [bleak](https://github.com/hbldh/bleak) library, so you can test if that works in containers or not too.

Thanks for reporting and the helpful error log. I have an idea on fixing this, but it might take some time. I assumed that the characteristic UUID is the same...

I did more digging into this. I think the implementation correctly follows [this protocol](https://github.com/madhead/saberlight/blob/master/protocols/Triones/protocol.md). It is possible that your device is using different UUIDs. Can you connect to your device...

Found more characteristic UUIDs from another open source [Triones implementation](https://github.com/pedasmith/BluetoothDeviceController/blob/5c6154794b9799d666448b24f57b2adf8ea60359/BluetoothDeviceController/BluetoothProtocols/Triones_LedLights_Custom.cs). Do try the latest code if it fixes the issue. Otherwise, I will need you to do BLE scanning of...