Connection Issues with Eve Motion and HomePod Mini over Thread

Configuration
1

Hi all,

I bought a new Eve Motion sensor and it is already working on Thread… hence, I tried to follow the instructions of HomeKit Controller. My setup is:

  • Home Assistant, latest version (2022.12.8)
  • HomePod mini (16.2)
  • Eve Motion Sensor, already using Thread/Matter Firmware

This is how I’ve tried it:

  1. I were able to pair it in Home app or Eve app with HomeKit. The eve app also confirmed, that the device is connected over Thread.

  2. I unpaired the Motion sensor in Home.

  3. It directly appeared in Home Assistant by autodiscovery.
    image

  4. Now the problem starts: The configuration wizard starts to run…
    image

    but ends with this error message:

    image
    image368×617 57.4 KB

Entering the code in XXX-XX-XXX format doesn’t work.

Here what the log file shows me:

Logger: homeassistant.components.homekit_controller.config_flow
Source: components/homekit_controller/config_flow.py:481
Integration: homekit_controller ([documentation](https://www.home-assistant.io/integrations/homekit_controller), [issues](https://github.com/home-assistant/home-assistant/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+homekit_controller%22))
First occurred: 14:05:37 (1 occurrences)
Last logged: 14:05:37

Pairing attempt failed with an unhandled exception

Traceback (most recent call last): File "/usr/local/lib/python3.10/site-packages/aiohomekit/controller/coap/connection.py", line 283, in do_pair_setup response = await self.pair_setup_client.request(request).response asyncio.exceptions.CancelledError During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/components/homekit_controller/config_flow.py", line 481, in async_step_pair self.finish_pairing = await discovery.async_start_pairing(self.hkid) File "/usr/local/lib/python3.10/site-packages/aiohomekit/controller/coap/discovery.py", line 57, in async_start_pairing salt, srpB = await self.connection.do_pair_setup( File "/usr/local/lib/python3.10/site-packages/aiohomekit/controller/coap/connection.py", line 282, in do_pair_setup async with asyncio_timeout(16.0): File "/usr/local/lib/python3.10/site-packages/async_timeout/__init__.py", line 129, in __aexit__ self._do_exit(exc_type) File "/usr/local/lib/python3.10/site-packages/async_timeout/__init__.py", line 212, in _do_exit raise asyncio.TimeoutError asyncio.exceptions.TimeoutError

.

I paired and unpaired the Motion Sensor several times to Home App and to Home Assistant back and forth, but it behaves always the same. Anybody else facing this issue? Any hints how to solve this are appreciated :slight_smile:

2

Ok, I don’t know why, but today I was successful. I paired, renamed and unpaired the device in Eve app. Not sure if it made a difference.

However, the status update of the motion sensor is really unreliable. It’s too slow or too late. Since it went really good in HomeKit, do you think it might be a bug in Home Assistant? Or do I need an active device in my Thread Network as well, like the Eve Energy?

Here seems to be the issue … 33 times in my log file since I added the device:

2022-12-26 14:25:17.310 WARNING (MainThread) [aiohomekit.controller.coap.connection] CoAP POST returned unexpected code <aiocoap.Message at 0x7f584c45e0: ACK 4.04 Not Found (MID 2352, token 5136) remote <UDP6EndpointAddress [fd5b:defd:3d24:0:84a6:7e8e:cc63:3d7f] (locally fdd8:184c:80eb:459c:d4f4:b8b3:a3d8:5116%eth0)>>
2022-12-26 14:25:17.317 ERROR (MainThread) [aiohomekit.controller.coap.connection] Decryption failed, desynchronized? Counter=13/14
2022-12-26 14:25:17.322 ERROR (MainThread) [aiohomekit.controller.coap.connection] Failed flailing attempts to resynchronize, self-destructing in 3, 2, 1...
2022-12-26 14:26:20.108 WARNING (MainThread) [aiohomekit.controller.coap.pdu] Transaction 0 failed with error 6 (Invalid request
2022-12-26 14:26:43.723 ERROR (MainThread) [coap-server] Error received and ignored in this codepath: [Errno 113] Host is unreachable
3

If anybody is still having problems with Matter and HomePod … use the official Matter integration instead of HomeKit-Controller, then it works.

4

I have Eve Motion upgraded to Matter. When connected to Home Assistant (via Matter) it is reporting motion 24/7. Tried removing and adding up to 100 times without any change. Somebody know how to solve?

5

@onkelfarmor same for me here. Updated one Eve Motion to Matter firmware.
In HA it is always stuck at one state.
In HomeKit motion sensor works but slow.
Lux sensor doesn’t work in HA or HomeKit with Matter FW. It always reports 1 lux.