#btle libs, issues
torn agate
Sure thing! I don't know how bluepy got popular, but I at least hope its not because of people taking example of eq3btsmart. FWIW, I created (I think at least?) that integration and its upstream lib to learn some python and play around with iot devices...
Anyway, the problem with btle devices is not just that the device accepts a single connection, but your host's bt chip may have similar limitation => you stay connected with a device, you may not be able to make requests on another. Some raspberry pis had that limitation, NUCs were more forgiving, iirc.
I'm not sure what's the state nowadays (no btle devices in my setup), but there are bt<->mqtt gateways that were (are?) more reliable than homeassistant. And I think their magic is related to how the device accesses are scheduled, but I hope someone corrects me 🙂
btle libs, issues
warped timber
Ahaha, and here I thought I had chosen something nice and simple to cut my teeth on. Thanks for all the advice, I've been wondering how I can build this in a way it can both be used directly or externally though another device if the home assistant host doesn't have bluetooth/is too far away/etc. The mqtt gateway looks like a perfect solution for that.
I've managed to map out the important endpoints and get state updating somewhat regularly, so I'll just have a play around and see what works best for this use case
Current attempt is up here but be warned ye who enter here, comments are unintelligible and it is not configured properly