Unfortunately not. I added valve support for an unrelated WiFi device, it’s just a bonus that it probably now works with Eve Extend too.
It does mean that when the BLE transport exists it will work as well, but such a transport is a significant amount of work.
I helped to write the BLE support in the blocking homekit client we used to use and had a working prototype for Eve Energy in Home Assistant, but as i’ve said before there were some severe limitations because of the interactions between asynchronous code running in HA, asynchronous code running in the Linux bluetooth stack and then trying to put a synchronous blocking code path in the middle of that with threads. With the HA homekit_controller code as it was when I started contributing it took 2 threads to get this working, per entity. I know there are users with 40+ homekit entities. Not only wasn’t it reliable, it wouldn’t have scaled.
Now we use a different homekit client that is entirely async. Unfortunately it’s IP only at the moment. That code landed in 0.107.0 and i’m spending this cycle mostly on support. But the hope is that now this foundational piece in place we can use
aioble and avoid the threading layer that was causing problems. But this is a massive piece of work so is still a good long while away.