Separate efble lib from the repository as pip package

[f00b4r0]

Hi,

Is there any chance you could backport your changes from ha-ef-ble, or split out the ef-ble backend from ha-ef-ble to enable data collection without requiring HA? Would be very useful for other integrations.

Thanks!

[rabits]

Hi @f00b4r0 , it requires quite a bit of work - so anyone who interested please vote up for this feature request (or maybe help with execution?) and we will think about that.

[GnoX]

I actually structured ef_ble it in a way it can be used independently from HA so this is not that hard to do - in fact, few people are already using it outside of HA (including me for remote debugging), for example see #264.

The problem with splitting it is that it will probably slow down overall development of integration because we would have to manage two separate projects and can't do changes atomically. We might do it eventually - I was preparing it for this, but I don't think it's completely ready yet.

[f00b4r0]

I actually structured ef_ble it in a way it can be used independently from HA so this is not that hard to do - in fact, few people are already using it outside of HA (including me for remote debugging), for example see rabits/ha-ef-ble#264.

Thanks this is helpful already. You might want to "document" this a little more publicly (maybe in README?) so it's easily found 🙂

The problem with splitting it is that it will probably slow down overall development of integration because we would have to manage two separate projects and can't do changes atomically. We might do it eventually - I was preparing it for this, but I don't think it's completely ready yet.

I understand, but since ha-ef-ble essentially carries what is now the canonical (and best) implementation to interface with EcoFlow devices, you're bound to get more requests like mine 😉