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

Hi,

I have latest version of HA (0.87.1) installed running HASS.IO.

I have enabled homekit controller and can see that is starts but none of my homekit stuff is detected.

2019-02-13 09:23:58 INFO (MainThread) [homeassistant.loader] Loaded homekit_controller from homeassistant.components.homekit_controller
2019-02-13 09:23:58 INFO (MainThread) [homeassistant.setup] Setting up homekit_controller
2019-02-13 09:23:58 INFO (MainThread) [homeassistant.setup] Setup of domain homekit_controller took 0.3 seconds.

I cannot however get HA to detect any of my Elgato Eve motion sensors not the Elgato Eve power switch.

I see in latest release notes (for .87) that this should be possible:

Anyone with pointers on how to get this correctly configured or if it is even possible to use these devices with HA?

Thank you in advance.

Eve use Bluetooth to work, which HA does not support at the moment for HomeKit components. If you have wifi devices you should see them however.

For now you have to be patient :frowning:

For switch (door/windows, powers, etc ā€¦), I have made a input_boolean in HA which I switch on or off with HomeKit based on the state of eve door or power. At least you could can some basic things working. For sensors no way around so far.

edit: just read your link ā€¦ interesting ā€¦ perhaps there is a way around, Iā€™ll try to dig in.

1 Like

Just stumbled on to this and though iā€™d post in case anyone else sees it and gets their hopes up.

BLE support is coming, but still a fair bit away.

Currently working to migrate homekit_controller to config entries and add automated tests to catch regressions. Most of that work has landed, 2 medium sized pull requests left.

After that - basic BLE discovery and pairing. This does work, i had it working with an Eve Energy a few months ago (when that PR was merged).

After that - events. Right now homekit_controller doesnā€™t support events. The underlying library does for IP, but not BLE. Iā€™ll fix that and plumb it through to homekit_controller. As Eve Motion is pretty useless without events.

But yes. Still some time away.

6 Likes

Eagerly waiting for BLE support, would be nice to have HA natively be the bridge to August bluetooth homekit without August connect or Apple TV.

2 Likes

I can fully second that! Would be really great to have this support.

3 Likes

BLE support would be really really great. I have an Elgato Eve Energy in the bedroom but it often disconnects from the Apple TV in the living room. Having my Rpi3B+ closer to the Eve Energy would eliminate this problem!

2 Likes

@Jc2k just wondering where BLE support is at this point.

Thanks

1 Like

Itā€™s still one of my personal priorities, but the clash between the GLib event loop running in one thread and the asyncio event loop running in the main thread, then trying to use threading primitives to mash them togetherā€¦ Itā€™s not exactly being very stable.

Currently working on an entirely asyncio native client. Starting with IP accessories and supporting local push notifications, but hope to start evaluating aioble soon.

4 Likes

@Jc2k Many thanks for the update. I am no programmer but I do work hard at testing and have enough understanding that I can provide feedback. Let me know if I can be of assistance.

I also have WIFI homekit devices (as koogeek WIFI plug) but I donā€™t see it in HAā€¦anyone can help me?

In configuration.yaml I have this line:
default_config:

but I don0t see any homekit devices in integration sectionā€¦

Still no progress on the BLE front - barely had any time for Home Assistant this last quarter. That said the plan is still the same - going native asyncio is still the priority. The asyncio IP client is working, but not yet stable enough to merge. This will allow event support, which is pretty much a requirement for BLE devices because they are so slow to poll.

I did try something people here might be interested in though.

I have quite a few test Eve devices that I want to use with Home Assistant, and I know itā€™s going to be a while before I can look at them. Soā€¦ I recently picked up an Eve Extend which is a HomeKit Wifi to Bluetooth bridge. Itā€™s meant to be used as a range extender, but I wanted to see if it could let us use Eve accessories with Home Assistant.

I used the Eve app on an iPhone to have it join my WiFi, then assigned all my Eve devices to it (Eve Thermo, Eve Motion, Eve Energy, Eve Smoke Detector). You can only do this with the official Eve app - itā€™s a vendor HomeKit extension rather than an implementation of the official spec. I found when everything is working in the Eve app on iOS you can unpair the bridge and all the accessories stay connected to the bridge, and it remains on your WiFi. Then you can pair with HASS. Seems to work!

Full disclosure - the first time i tried this it worked perfectly first time. I think at that point I was using a FRITZ!Box 7530 for WiFi. Getting it to work at home was more problematic. There I have UniFi. It did work, but I had to reset it and try a few times before I got it to join the WiFi network. It would join the WiFi (could only tell through router DHCP reservations) but then fail to pair. I think it went through on the third go.

There are of course limitations:

  • The bridge can only take up to 8 accessories.
  • homekit_controller is still a polling integration until I finish this. So there are delays of up to a minute on picking up changes. So whilst the Eve Motion is supported, itā€™s not its most useful.
  • The smoke alarm is detected enough to monitor its battery, but thats it so far.
  • To add more devices later you will need to unpair from HASS, repair with Eve iOS app, unpair, repair with HASS. Right now only an unpair with the homekit_python cli is good enough and HASS ā€œunpairā€ only breaks the connection on the HASS side. So this is something of a pain.

This should work for other Eve products too, although testing required. E.g. Eve Room 2 - I think the temperature and humidity sensors would work out of the box, and probably a battery reading too. But if memory serves weā€™ll need to add a bit of code to support for the VOC reading.

Native bluetooth support is still something I want to do, but realistically itā€™s a long way out.

5 Likes

Iā€™m looking forward to when it supports events. I recently purchased several Ecobee Smart Switch+ devices which have an integrated motion sensor. It is detected by Home Assistant but, like you said, its value is acquired via polling so the ā€˜time-to-detectionā€™ is usually too long for triggering automations.

The Switch+ also has a light sensor and temperature sensor. All are detected as HomeKit accessories. Whenever support for events is implemented, will light and temperature values also be handled as events or will they continue to be polled? If so, what is the threshold that will be used to report a state-change? For example, will it be 0.5 C for temperature and 1 lux for light intensity?

Or will temperature and light, which arenā€™t particularly ā€˜time criticalā€™, continue to be polled every minute?

This thread is about Bluetooth HomeKit devices, and in particular the Elgato Eve ones. AIUI the Ecebobee products are IP based so this is a bit off topic here?

Events are especially important for BLE devices as they are more likely to be battery powered and we donā€™t want to wake the device up once a minute to poll if we can help it.

I cannot say how particular devices will behave when we have event support in homekit_controller, a lot of it is up to the devices themselves. The current implementation will subscribe to events for any characteristic that it polls if the device supports it. So if your temperature sensor supported events then Home Assistant would be able to make use of them. For the temperature characteristic, this is optional for the accessory manufacturer though.

Itā€™s likely that polling will still be used in addition to events at first. We donā€™t know how reliable the new event code is, so weā€™ll keep the existing code in place while we see. Even if we relax this and poll event characteristics less often, weā€™ll of course still be polling characteristics that donā€™t support events.

Regarding the resolution of data collected - we support whatever the underlying device supports, and if the device reports a change we report the change to the HA state machine.

Yes, the Ecobee Switch+ is IP based. However, my understanding is that you plan to implement support for events so, unless the goal is to limit that support to Bluetooth devices only, I believe my questions were on-topic.

Thanks for your reply. I look forward to testing the new version whenever it is released.

Hoping you are making progress on BLE, I could use this for the Level Lock as well.

+1 canā€™t use my Eve motion sensors and Eve switches ā€¦

Cross-posting this from another thread as my Eve Motion, Eve Energy (switch), Eve Smoke and Eve Thermo are now working great with homekit_controller via an Eve Extend:

Just wanted to post an update about Eve Extend. My first Eve Extend had been really patchy with my home WiFi (Unifi). I recently resolved to reset it and try again. Unfortunately the usb socket came off the PCB. Not great.

2nd Eve Extend just arrived. I set it up exactly as before. Used the Eve app on iOS to pair each Eve device i have (the bridge itself + Eve Thermo, Eve Motion, Eve Smoke and Eve Energy) with my phone (not HA). Then used the Eve app to ā€œmoveā€ each of those devices to the Extend. (So phone then routes all requests to the devices using the Eve Extend as a bridge). Then i used the Eve app to unpair my phone from the Eve Extend. Made sure to patch all the firmware levels (v 1.1 of Eve Extend claims to improve Wifi connectivity). Finally I paired with HA. It worked first time. Event notifications not only work but the reaction from the Eve Motion are nearly as fast as my Hue motion sensors (normally within a second).

Given my chronic lack of time for HA at the moment this remains your best shot at ā€œgoodā€ integration of Eve accessories into HA, but I could do with more field reports from people using this sort of setup.

See here.

1 Like

was just offered an Eve Energy switch, but reading all of the above, I am not sure if this is already supported in HA now? Switching and energy metering.

Could anyone here point me to how to go from here. It is Homekit compatible and operation via Wifi and direct via Bluetooth

thanks for any info you can share. I would start with Homekit controller and then how to proceed? is this mainly the wifi (since BLE is not supported)

As my main experience with smart switches is over Mqtt for the sensors, and api calls in shell_commands for the switching, I hoped this integration creates these sensors and switches automatically? Or does it still require some manual configurations.

I ask without trying firstā€¦ as in: of course I tried to have a neek peek before this item arrives, but on installing the Homekit controller is starts scanning and doesnā€™t find any unpaired devices, so wont do anything.

Hello,

Most Eve products are based on BLE (which is the case of the Eve Energy Switch). Natively there is no solution for Home Assistant, as the Homekit controller is not supporting BLE at the moment.

There are some reports of success when adding a Eve bluethooth extender in the mix. (like the post above from jc2k)

Personally, I have stopped using Eve products for now. Maybe the new era of thread will open up new avenue to integrate with HA. Wait and see.

guess youā€™re rightā€¦ found out that the eve switch was installed in a snap, which made me hopeful for its usefulness. would have thought that some central configuration would have taken care of being able to use it in the whole house. But I need to be within 10 meter or so with my mobile device to be able to use it, which makes it perfectly useless of course.

unless I can make a spare Apple TV have something to do again, would that register the eve switch so I can see it everywhere?