HomePod (original and mini) and Apple TV serve as HomeKit extension for BLE devices such as EVE so yes it will help you out. if you have a very recent Eve switch it will be compatible soon with thread protocol (which is akin to zigbee) -> with an HomePod Mini (not the original) youād probably see a near instant response time (letās wait for firmware update and review)
yeah, anxiously awaiting the release for the new HomePod Mini hereā¦ have a full set of Google home devices, so probably will end up doubling that with the Pods. O dear. Loved the intercom function of those as showed in the recent Apple Event. Have made that myself now in the HA interface of my GH devices, which was quite an effort tbh
Anyways, even thought the Eve energy switch is rather large, thereās a nice discount this weekend, so will probably grab a few extra and maybe even have a look at the Energy strip, which seems about the only strip around with individual smart sockets. Not sure if the energy metering on the strip is individual though.
What little time I have for HA these days is spent on support, code review or fixing bugs. Or very small features. So I havenāt even thought about BLE support in a year, unfortunately.
(It doesnāt help that the Eve Extend has been working so well for me).
Thank you for the quick reply.
In that case i am going to get one of the Eve Extend and try this out. Just wanted to know that, so that I donāt buy this for nothing.
Take care.
Just wanted to let you know the good news and my experience so far with the Eve Extend device.
I can truly understand now that you do not see the need for getting BLE implemented, because its just working great. I have 2x Eve Degree, 1x Eve Energy and 1x Eve Door.
Everything just works out of the box, with the installation description you gave here.
I am even considering buying the Eve Light Switch, since it would fit so well. The only downside are the costs of that thing.
I donāt have either of those devices so itās hard to speculate.
I believe Air Pressure is not a standard HomeKit value. This means a certain amout of reverse engineering will be needed to extract it. However on the HA side this should map cleanly to an ordinary sensor with a device class of DEVICE_CLASS_PRESSURE.
Flow rate also looks like it might not be a part of the HomeKit standard. It also looks like there isnāt a proper valve type in Home Assistant. Right now valves are modelled as switches, they can be on or off and thatās it. So we have to reverse engineer the custom HomeKit characteristic(s) used for flow rate, then figure out what to map that to on the Home Assistant side. There is a new number integration which would potentially allow us to control the flow rate, but it would be an independent entity to the on/off switch.
Iād need to see the .storage/homekit_controller-entity-map of someone with both of these devices already paired in order to progress further
Thanks so much for all your contributions on this. It really makes a difference.
I know you set up your Eve Extend Directly with HA, what are you doing for firmware updates? Thats my biggest concern with disconnecting the Eve products from IOS is that they wont get updates anymoreā¦
So regardless of how you connect an Eve device to Home Assistant you wonāt get firmware updates any more. Itās a choice between putting it in HA or having firmware updates.
Iām not too worried. Most of the devices are BLE devices, and none of them connect to the cloud. So from a security POV, theres no mass exploitation risk and iām too boring for a targetted attack and too out in the sticks for drive by to be a risk.
As for stability/bug fixes, i just havenāt needed them.
That said, I do unpair the Extend from HA, pair it with iOS, then do admin stuff, then unpair from iOS, and repair with HA. This does mean i could update the firmware. Though it might screw up device ids, so not sure how realistic it is if you have lots of UI based automations. (UPDATE: To be clear this should work and if it doesnt its a bug, but iāve not had time to explore).
I wonāt be supporting firmware updates via homekit_controller, iām too worried about bricking devices.
I will try and setup my eve extend through homekit as you suggested.
One thing I will note is that I found out today the extend has been discontinued, so if you have BLE only devices that you want to connect to Home Assistant, get your extend now before they are all goneā¦
Maybe someday the homekit integration will support bluetooth and it wont be an issue, but for now Iāll get my extend setup.
Funnily enough, I recently wrote a BLE backend for aiohomekit and Home Assistant, but iāve not had time to finish it. It came about because another contributor has added Thread support to aiohomekit, and there is some crossover in the protocols. Anyway all the work thats gone into homekit_controller over the past 2 years paid off, it was actually pretty easy to get working. Both of these are queued up in our aiohomekit dev branch and really just need polishing.
That said things are super hectic for me right now, and I have no idea how well the BLE client will work in āreal worldā conditions (e.g. have only tested on a Mac so far, and i donāt know what the range is like, etc). So I still suggest going with the Extend for now. But hopefully weāll be able to avoid it entirely in the future.
It wouldnāt have been possible without @bdraco who put my proof of concept code through hell and made it reliable enough to turn on by default. Big 's
You can expect things to get better and batter - HAOS 9 will massively improve dbus performance, which halves bluetooth read times. Other bluetooth work @bdraco is doing gets us wins all over the linux/python bluetooth stack. Pairing is faster. Wake up from sleep is faster. 2022.8 is really just the beginning.