Eve Motion Sensor (Matter) stops detecting occupancy

I have repeated problems with my Eve Motion sensors running under Matter, and I’d appreciate any advice.

The latest problem is a sensor that is not marked as unavailable in HASS, but will not detect occupancy. It works fine in Apple Home and in the Eve app, and I can ping it from HASS and even make use of the Identify action to make it blink from HASS. At some random point it comes back and seems to function ok, but then drops occupancy detection again. It’s been rock solid for over a year until about 3 days ago, when this trouble with occupancy detection started.

This kind of thing has happened to two other Eve motion sensors, one of which I describe below. I’m using HomePod minis for my primary Thread network, and it seems to be ok. Matter logs don’t have anything about the sensor.

Another Eve Motion sensor has stopped completely. It is on node 15, and the Matter server logs do have the following:

2024-11-13 16:50:03.648 (MainThread) WARNING [matter_server.server.device_controller] <Node:15> Setup for node failed: Unable to establish CASE session with Node 15

2024-11-13 16:50:03.649 (MainThread) INFO [matter_server.server.device_controller] <Node:15> Retrying node setup in 60 seconds...

2024-11-13 16:51:03.650 (MainThread) INFO [matter_server.server.device_controller] <Node:15> Setting-up node...

2024-11-13 16:51:43.925 (Dummy-2) CHIP_ERROR [chip.native.EM] Failed to Send CHIP MessageCounter:209581643 on exchange 26068i with Node: <0000000000000000, 0> sendCount: 4 max retries: 4

2024-11-13 16:51:52.365 (Dummy-2) CHIP_ERROR [chip.native.SC] CASESession timed out while waiting for a response from the peer. Current state was 1

2024-11-13 16:51:55.368 (MainThread) INFO [matter_server.server.sdk] <Node:15> Attempting to establish CASE session... (attempt 2 of 2)

2024-11-13 16:52:34.930 (Dummy-2) CHIP_ERROR [chip.native.EM] Failed to Send CHIP MessageCounter:209581644 on exchange 26069i with Node: <0000000000000000, 0> sendCount: 4 max retries: 4

2024-11-13 16:52:44.085 (Dummy-2) CHIP_ERROR [chip.native.SC] CASESession timed out while waiting for a response from the peer. Current state was 1

2024-11-13 16:53:26.629 (Dummy-2) CHIP_ERROR [chip.native.EM] Failed to Send CHIP MessageCounter:209581645 on exchange 26070i with Node: <0000000000000000, 0> sendCount: 4 max retries: 4

2024-11-13 16:53:32.602 (Dummy-2) CHIP_ERROR [chip.native.SC] CASESession timed out while waiting for a response from the peer. Current state was 1

2024-11-13 16:53:32.604 (MainThread) WARNING [matter_server.server.device_controller] <Node:15> Setup for node failed: Unable to establish CASE session with Node 15

Again, that sensor is functional in Apple Home and Eve, with 45% battery level.

Below is my system info. Thanks in advance for any suggestions on how to wake up these lazy sensors.

System Information

version core-2024.11.1
installation_type Home Assistant OS
dev false
hassio true
docker true
user root
virtualenv false
python_version 3.12.4
os_name Linux
os_version 6.6.54-haos
arch aarch64
timezone America/Los_Angeles
config_dir /config
Home Assistant Community Store
GitHub API ok
GitHub Content ok
GitHub Web ok
HACS Data ok
GitHub API Calls Remaining 5000
Installed Version 2.0.1
Stage running
Available Repositories 1466
Downloaded Repositories 47
Home Assistant Cloud
logged_in true
subscription_expiration February 13, 2025 at 4:00 PM
relayer_connected true
relayer_region us-east-1
remote_enabled true
remote_connected true
alexa_enabled false
google_enabled false
cloud_ice_servers_enabled true
remote_server us-east-1-7.ui.nabu.casa
certificate_status ready
instance_id 20f527728e59431f99c2e6d578aad19c
can_reach_cert_server ok
can_reach_cloud_auth ok
can_reach_cloud ok
Home Assistant Supervisor
host_os Home Assistant OS 13.2
update_channel stable
supervisor_version supervisor-2024.11.2
agent_version 1.6.0
docker_version 27.2.0
disk_total 56.6 GB
disk_used 15.8 GB
healthy true
supported true
host_connectivity true
supervisor_connectivity true
ntp_synchronized true
virtualization
board odroid-n2
supervisor_api ok
version_api ok
installed_addons Z-Wave JS UI (3.17.0), File editor (5.8.0), Matter Server (6.6.0), Advanced SSH & Web Terminal (19.0.0), Home Assistant Google Drive Backup (0.112.1), Mosquitto broker (6.4.1), ESPHome (2024.10.0), Samba share (12.3.2), Auto Guest Login (1.4.0), Z-Wave JS (0.9.0)
Dashboards
dashboards 7
resources 35
views 15
mode storage
Recorder
oldest_recorder_run November 4, 2024 at 10:27 AM
current_recorder_run November 11, 2024 at 7:09 AM
estimated_db_size 565.71 MiB
database_engine sqlite
database_version 3.45.3

This very much sounds like the issue we are tracking at Matter over Thread Devices unavailable - Home Assistant Only · Issue #123835 · home-assistant/core · GitHub.

I assume you have multiple Apple Border Router devices?

Currently, we don’t have solution unfortunately. The problem seems to be that some of the Apple Border Router suddenly don’t forward packets properly. Home Assistant doesn’t know which one to prefer. However, Apple preferes the one you select as primary Home Hub.

Thanks so much for the helpful post and the link. I only have two Apple border routers (Minis) which I designated as my Preferred Network, running on channel 25 (automatically set). I have 4 Eeros, which HASS designates as “Other”.

The only Matter devices I have currently are 3 Eve Motion Sensors. All 3 have dropped at one time or another. One I could never get back, despite restarting the Matter server, changing the batteries, resetting the sensor repeatedly. I replaced it with a new device, which worked for a few weeks, until it too failed. The only way I was able to get it back was to delete it from Apple, Eve, and HASS, and re-commission it. The second one, which I posted about, seems to come in and out of HASS by itself. The third one has been out for a couple of weeks, but it’s in my workshop so I haven’t bothered to try and revive it yet, and it certainly hasn’t done so on its own.

Not sure any of this is helpful to you, other than to describe another case. If so, and you would like me to move the discussion to the thread you indicated, I can do so. Thanks again for the info. I’m sure it will get worked out in the end. Life on the edge….