Howto configure HomeKit Controller to detect Elgato Eve Motion or Switch?

Hello :wave:

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 :wink:

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.

Hi @Jc2k

Hope youā€™re doing well.
Can I kindly ask you about the progress of BLE support for HA?

Thanks
Pit

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).

1 Like

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.

Hi @Jc2k

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.

Have a great weekend

One question how can I unpair my IPhone in the Eve app or how could it done.

Thanks in advance

Hi @Marcel_Frenzel
Sorry for not answering sooner.
I just went into the APP on my iPhone and removed the Eve Extend device, I am not 100% sure where exactly it is, but it was straight forward.
Perhaps this could be useful for you:
https://help.evehome.com/hc/en-us/articles/360010226974-Remove-Accessories-or-delete-your-Home

Hi there,

That is understandable.
Would adding more sensor readings/control to already working devices fit that schedule?

In particular:

  • eve weather is missing the air pressure reading
  • eve Aqua is missing the ability to control the valve (flow rate)

Thanks,
mb

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

Hey Jc2k,

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ā€¦

What do you think?

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.

Thanks!

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.

Thank you!

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.

2 Likes

The day has come!

I was able to migrate my eve water guards with no issues to home assistant homekit controller ble.

Having trouble with my eve Motion and a Onelink device, but Iā€™m sure weā€™ll get there!

Thank you so much to Jc2k and all the other contributors for making this happen.

Let us know if there is a good place we can help report what works and what doesnā€™t work since Iā€™m sure not every homekit ble device is testable.

2 Likes

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 :heart: '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.