Eve energy device is permanently offline

Describe the issue you are experiencing

Starting from version 6.0 or another one released from May my Eve Energy and door sensor devices are permanently offline. They work perfectly well in HomeKit and in Alexa. But stopped working in HA. I tried removing them and adding again. First it was not easy as by default adding them didn’t work and I had to do some unusually many trial and error to finally succeed. After adding them they worked for 10 mins or so and then went offline. With each full restart of HA server these devices appear for 10 mins and then go permanently offline.

As my thread border router I use AppleTV (latest firmware) that is connected using ethernet cable same as HA server (latest updates). Before release in May it used to work flawlessly. Though I found some threads of people with the same issues going earlier in the year.

What type of installation are you running?

Home Assistant OS

Which operating system are you running on?

Home Assistant Operating System

Which add-on are you reporting an issue with?

Matter Server

What is the version of the add-on?

6.1.2

Steps to reproduce the issue

Open list of Matter devices in HA and they all appear offline. Same if going to Matter Server web page.

System Health information

No repairs

Anything in the Supervisor logs that might be useful for us?

None

Anything in the add-on logs that might be useful for us?

or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
s6-rc: info: service banner successfully started
s6-rc: info: service matter-server: starting
s6-rc: info: service matter-server successfully started
s6-rc: info: service legacy-services: starting
[06:29:32] INFO: Starting Matter Server...
s6-rc: info: service legacy-services successfully started
[06:29:32] INFO: Using 'enp6s18' as primary network interface.
[06:29:32] INFO: Successfully send discovery information to Home Assistant.
2024-06-12 06:29:34.028 (MainThread) INFO [matter_server.server.stack] Initializing CHIP/Matter Logging...
2024-06-12 06:29:34.029 (MainThread) INFO [matter_server.server.stack] Initializing CHIP/Matter Controller Stack...
[1718166574.051127][126:126] CHIP:CTL: Setting attestation nonce to random value
[1718166574.051347][126:126] CHIP:CTL: Setting CSR nonce to random value
[1718166574.052159][126:126] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_kvs
[1718166574.052275][126:126] CHIP:DL: writing settings to file (/tmp/chip_kvs-THG8XI)
[1718166574.052347][126:126] CHIP:DL: renamed tmp file to file (/tmp/chip_kvs)
[1718166574.052536][126:126] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /data/chip_factory.ini
[1718166574.052664][126:126] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /data/chip_config.ini
[1718166574.052720][126:126] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /data/chip_counters.ini
[1718166574.052881][126:126] CHIP:DL: writing settings to file (/data/chip_counters.ini-K8nI9I)
[1718166574.053079][126:126] CHIP:DL: renamed tmp file to file (/data/chip_counters.ini)
[1718166574.053102][126:126] CHIP:DL: NVS set: chip-counters/reboot-count = 52 (0x34)
[1718166574.053400][126:126] CHIP:DL: Got Ethernet interface: enp6s18
[1718166574.053545][126:126] CHIP:DL: Found the primary Ethernet interface:enp6s18
[1718166574.053899][126:126] CHIP:DL: Failed to get WiFi interface
[1718166574.053911][126:126] CHIP:DL: Failed to reset WiFi statistic counts
2024-06-12 06:29:34.054 (MainThread) WARNING [PersistentStorage] Initializing persistent storage from file: /data/chip.json
2024-06-12 06:29:34.054 (MainThread) WARNING [PersistentStorage] Loading configuration from /data/chip.json...
2024-06-12 06:29:34.115 (MainThread) WARNING [CertificateAuthorityManager] Loading certificate authorities from storage...
2024-06-12 06:29:34.115 (MainThread) WARNING [CertificateAuthority] New CertificateAuthority at index 1
2024-06-12 06:29:34.116 (MainThread) WARNING [CertificateAuthority] Loading fabric admins from storage...
2024-06-12 06:29:34.116 (MainThread) WARNING [FabricAdmin] New FabricAdmin: FabricId: 0x0000000000000002, VendorId = 0x134B
2024-06-12 06:29:34.116 (MainThread) INFO [matter_server.server.stack] CHIP Controller Stack initialized.
2024-06-12 06:29:34.117 (MainThread) INFO [matter_server.server.server] Starting the Matter Server...
2024-06-12 06:29:34.119 (MainThread) INFO [matter_server.server.helpers.paa_certificates] Fetching the latest PAA root certificates from DCL.
2024-06-12 06:29:37.770 (MainThread) INFO [matter_server.server.helpers.paa_certificates] Fetched 58 PAA root certificates from DCL.
2024-06-12 06:29:46.063 (MainThread) INFO [matter_server.server.helpers.paa_certificates] Fetched 74 PAA root certificates from Test DCL.
2024-06-12 06:29:46.063 (MainThread) INFO [matter_server.server.helpers.paa_certificates] Fetching the latest PAA root certificates from Git.
2024-06-12 06:30:47.925 (MainThread) INFO [matter_server.server.helpers.paa_certificates] Fetched 5 PAA root certificates from Git.
2024-06-12 06:30:47.926 (MainThread) WARNING [FabricAdmin] Allocating new controller with CaIndex: 1, FabricId: 0x0000000000000002, NodeId: 0x000000000001B669, CatTags: []
2024-06-12 06:30:48.009 (MainThread) INFO [matter_server.server.device_controller] Loaded 3 nodes from stored configuration
2024-06-12 06:30:48.013 (MainThread) INFO [matter_server.server.vendor_info] Loading vendor info from storage.
2024-06-12 06:30:48.015 (MainThread) INFO [matter_server.server.vendor_info] Loaded 200 vendors from storage.
2024-06-12 06:30:48.016 (MainThread) INFO [matter_server.server.vendor_info] Fetching the latest vendor info from DCL.
2024-06-12 06:30:48.405 (MainThread) INFO [matter_server.server.vendor_info] Fetched 201 vendors from DCL.
2024-06-12 06:30:48.405 (MainThread) INFO [matter_server.server.vendor_info] Saving vendor info to storage.
2024-06-12 06:30:49.736 (MainThread) INFO [matter_server.server.device_controller.mdns] Node 40 discovered on MDNS
2024-06-12 06:30:49.736 (MainThread) INFO [matter_server.server.device_controller.mdns] Node 37 discovered on MDNS
2024-06-12 06:30:49.736 (MainThread) INFO [matter_server.server.device_controller.node_40] Setting-up node...
2024-06-12 06:30:49.737 (MainThread) INFO [matter_server.server.device_controller.node_37] Setting-up node...
2024-06-12 06:31:21.143 (MainThread) INFO [matter_server.server.device_controller] Interviewing node: 34
2024-06-12 06:31:32.773 (Dummy-2) CHIP_ERROR [chip.native.EM] Failed to Send CHIP MessageCounter:134707281 on exchange 42912i with Node: <0000000000000000, 0> sendCount: 4 max retries: 4
2024-06-12 06:31:32.803 (Dummy-2) CHIP_ERROR [chip.native.EM] Failed to Send CHIP MessageCounter:134707282 on exchange 42913i with Node: <0000000000000000, 0> sendCount: 4 max retries: 4
2024-06-12 06:31:38.448 (Dummy-2) CHIP_ERROR [chip.native.SC] CASESession timed out while waiting for a response from the peer. Current state was 1
2024-06-12 06:31:38.450 (Dummy-2) CHIP_ERROR [chip.native.SC] CASESession timed out while waiting for a response from the peer. Current state was 1
2024-06-12 06:31:49.147 (MainThread) INFO [matter_server.server.device_controller.node_34] Node could not be discovered on the network, returning cached IP's
2024-06-12 06:31:49.254 (MainThread) INFO [matter_server.server.device_controller.node_34] Node could not be discovered on the network, returning cached IP's
2024-06-12 06:31:52.144 (Dummy-2) CHIP_ERROR [chip.native.DIS] Timeout waiting for mDNS resolution.
2024-06-12 06:32:06.143 (Dummy-2) CHIP_ERROR [chip.native.DIS] OperationalSessionSetup[1:0000000000000022]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:119: CHIP Error 0x00000032: Timeout
2024-06-12 06:32:06.144 (MainThread) ERROR [matter_server.server.client_handler] [139754657663696] Error while handling: interview_node (node 34): Failed to interview node 34
2024-06-12 06:32:18.342 (Dummy-2) CHIP_ERROR [chip.native.EM] Failed to Send CHIP MessageCounter:134707284 on exchange 42915i with Node: <0000000000000000, 0> sendCount: 4 max retries: 4
2024-06-12 06:32:19.002 (Dummy-2) CHIP_ERROR [chip.native.EM] Failed to Send CHIP MessageCounter:134707283 on exchange 42914i with Node: <0000000000000000, 0> sendCount: 4 max retries: 4
2024-06-12 06:32:26.960 (Dummy-2) CHIP_ERROR [chip.native.SC] CASESession timed out while waiting for a response from the peer. Current state was 1
2024-06-12 06:32:26.960 (Dummy-2) CHIP_ERROR [chip.native.SC] CASESession timed out while waiting for a response from the peer. Current state was 1
2024-06-12 06:32:29.961 (MainThread) INFO [matter_server.server.sdk.node_40] Attempting to establish CASE session... (attempt 2 of 2)
2024-06-12 06:32:29.962 (MainThread) INFO [matter_server.server.sdk.node_37] Attempting to establish CASE session... (attempt 2 of 2)
2024-06-12 06:33:09.854 (Dummy-2) CHIP_ERROR [chip.native.EM] Failed to Send CHIP MessageCounter:134707286 on exchange 42917i with Node: <0000000000000000, 0> sendCount: 4 max retries: 4
2024-06-12 06:33:12.051 (Dummy-2) CHIP_ERROR [chip.native.EM] Failed to Send CHIP MessageCounter:134707285 on exchange 42916i with Node: <0000000000000000, 0> sendCount: 4 max retries: 4
2024-06-12 06:33:18.673 (Dummy-2) CHIP_ERROR [chip.native.SC] CASESession timed out while waiting for a response from the peer. Current state was 1
2024-06-12 06:33:18.675 (Dummy-2) CHIP_ERROR [chip.native.SC] CASESession timed out while waiting for a response from the peer. Current state was 1
2024-06-12 06:33:59.490 (Dummy-2) CHIP_ERROR [chip.native.EM] Failed to Send CHIP MessageCounter:134707288 on exchange 42919i with Node: <0000000000000000, 0> sendCount: 4 max retries: 4
2024-06-12 06:34:01.521 (Dummy-2) CHIP_ERROR [chip.native.EM] Failed to Send CHIP MessageCounter:134707287 on exchange 42918i with Node: <0000000000000000, 0> sendCount: 4 max retries: 4
2024-06-12 06:34:07.184 (Dummy-2) CHIP_ERROR [chip.native.SC] CASESession timed out while waiting for a response from the peer. Current state was 1
2024-06-12 06:34:07.185 (MainThread) WARNING [matter_server.server.device_controller.node_40] Setup for node failed: Unable to establish CASE session with Node 40
2024-06-12 06:34:07.186 (Dummy-2) CHIP_ERROR [chip.native.SC] CASESession timed out while waiting for a response from the peer. Current state was 1
2024-06-12 06:34:07.186 (MainThread) WARNING [matter_server.server.device_controller.node_37] Setup for node failed: Unable to establish CASE session with Node 37
2024-06-12 06:37:39.569 (MainThread) INFO [matter_server.server.device_controller.mdns] Node 37 discovered on MDNS
2024-06-12 06:37:39.569 (MainThread) INFO [matter_server.server.device_controller.mdns] Node 40 discovered on MDNS
2024-06-12 06:37:39.569 (MainThread) INFO [matter_server.server.device_controller.node_37] Setting-up node...
2024-06-12 06:37:39.571 (MainThread) INFO [matter_server.server.device_controller.node_40] Setting-up node...
2024-06-12 06:38:20.578 (Dummy-2) CHIP_ERROR [chip.native.EM] Failed to Send CHIP MessageCounter:134707289 on exchange 42920i with Node: <0000000000000000, 0> sendCount: 4 max retries: 4
2024-06-12 06:38:21.382 (Dummy-2) CHIP_ERROR [chip.native.EM] Failed to Send CHIP MessageCounter:134707290 on exchange 42921i with Node: <0000000000000000, 0> sendCount: 4 max retries: 4
2024-06-12 06:38:28.280 (Dummy-2) CHIP_ERROR [chip.native.SC] CASESession timed out while waiting for a response from the peer. Current state was 1
2024-06-12 06:38:28.282 (Dummy-2) CHIP_ERROR [chip.native.SC] CASESession timed out while waiting for a response from the peer. Current state was 1
2024-06-12 06:39:11.019 (Dummy-2) CHIP_ERROR [chip.native.EM] Failed to Send CHIP MessageCounter:134707292 on exchange 42923i with Node: <0000000000000000, 0> sendCount: 4 max retries: 4
2024-06-12 06:39:12.390 (Dummy-2) CHIP_ERROR [chip.native.EM] Failed to Send CHIP MessageCounter:134707291 on exchange 42922i with Node: <0000000000000000, 0> sendCount: 4 max retries: 4
2024-06-12 06:39:16.792 (Dummy-2) CHIP_ERROR [chip.native.SC] CASESession timed out while waiting for a response from the peer. Current state was 1
2024-06-12 06:39:16.793 (Dummy-2) CHIP_ERROR [chip.native.SC] CASESession timed out while waiting for a response from the peer. Current state was 1
2024-06-12 06:39:19.794 (MainThread) INFO [matter_server.server.sdk.node_37] Attempting to establish CASE session... (attempt 2 of 2)
2024-06-12 06:39:19.795 (MainThread) INFO [matter_server.server.sdk.node_40] Attempting to establish CASE session... (attempt 2 of 2)
2024-06-12 06:40:01.378 (Dummy-2) CHIP_ERROR [chip.native.EM] Failed to Send CHIP MessageCounter:134707293 on exchange 42924i with Node: <0000000000000000, 0> sendCount: 4 max retries: 4
2024-06-12 06:40:02.513 (Dummy-2) CHIP_ERROR [chip.native.EM] Failed to Send CHIP MessageCounter:134707294 on exchange 42925i with Node: <0000000000000000, 0> sendCount: 4 max retries: 4
2024-06-12 06:40:08.506 (Dummy-2) CHIP_ERROR [chip.native.SC] CASESession timed out while waiting for a response from the peer. Current state was 1
2024-06-12 06:40:08.508 (Dummy-2) CHIP_ERROR [chip.native.SC] CASESession timed out while waiting for a response from the peer. Current state was 1
2024-06-12 06:40:50.206 (Dummy-2) CHIP_ERROR [chip.native.EM] Failed to Send CHIP MessageCounter:134707296 on exchange 42927i with Node: <0000000000000000, 0> sendCount: 4 max retries: 4
2024-06-12 06:40:50.231 (Dummy-2) CHIP_ERROR [chip.native.EM] Failed to Send CHIP MessageCounter:134707295 on exchange 42926i with Node: <0000000000000000, 0> sendCount: 4 max retries: 4
2024-06-12 06:40:57.016 (Dummy-2) CHIP_ERROR [chip.native.SC] CASESession timed out while waiting for a response from the peer. Current state was 1
2024-06-12 06:40:57.017 (MainThread) WARNING [matter_server.server.device_controller.node_37] Setup for node failed: Unable to establish CASE session with Node 37
2024-06-12 06:40:57.019 (Dummy-2) CHIP_ERROR [chip.native.SC] CASESession timed out while waiting for a response from the peer. Current state was 1
2024-06-12 06:40:57.019 (MainThread) WARNING [matter_server.server.device_controller.node_40] Setup for node failed: Unable to establish CASE session with Node 40

Additional information

No response

Which version of Home Assistant Core are you using?

They work perfectly well in HomeKit and in Alexa.

Note that HomeKit is a different protocol, not related to Matter. You probably meant to say in Apple Home.

First it was not easy as by default adding them didn’t work and I had to do some unusually many trial and error to finally succeed. After adding them they worked for 10 mins or so and then went offline. With each full restart of HA server these devices appear for 10 mins and then go permanently offline.

10 minutes is exactly the liveness check of battery operated devices. So it seems the Eve did not report in after 10 minutes :thinking:

What is the node number of the Eve device?

Can you try to re-add again, but this time before adding make sure to do the follwing steps first:

Delete the device from Home Assistant, wait for 20-30 seconds (the server attempts to connect to the device to remove the credentials from the device. That might fail in your case).
Restart the Matter Server add-on
Verify that the device is still gone (with that, HA really doesn't know about the device)
Go to Apple Home, navigate to the device's "Accessory Settings", click on "Connected Services", delete any service named "4939" (this is Home Assistant, with that we make sure the device really forgets about Home Assistant)
Now try to pair the device again.

Hi, thank you for the quick reply.

Please see my comments below:

On 12 Jun 2024, at 08:55, Stefan Agner @.***> wrote:

Which version of Home Assistant Core are you using?

2024.6.2 They work perfectly well in HomeKit and in Alexa.

Note that HomeKit is a different protocol, not related to Matter. You probably meant to say in Apple Home.

First it was not easy as by default adding them didn’t work and I had to do some unusually many trial and error to finally succeed. After adding them they worked for 10 mins or so and then went offline. With each full restart of HA server these devices appear for 10 mins and then go permanently offline.

Yes, Apple Home app. Add these devices as Matter Devices (not HomeKit devices) and then share these devices with Alexa and HA. Sharing with Alexa works flawlessly. Sharing with HA doesn’t.

Connection with AppleTV is working well, as all my HomeKit and HomeBridge integrations are working without any problems.

10 minutes is exactly the liveness check of battery operated devices. So it seems the Eve did not report in after 10 minutes 🤔

Not that Eve Energy is a power socket devices, that is not battery operated. Usually when it works then battery operated door sensors work too. It is when it disappears that battery operated devices disappear with it too. What is the node number of the Eve device?

According to Matter Server webpage:

Node 34 Offline Eve Systems Eve Energy 20EBO8301

Node 37 Offline Eve Systems Eve Door 20EBN9901

Node 40: Offline Eve Systems Eve Door 20EBN9901

Can you try to re-add again, but this time before adding make sure to do the follwing steps first:

Delete the device from Home Assistant, wait for 20-30 seconds (the server attempts to connect to the device to remove the credentials from the device. That might fail in your case). Restart the Matter Server add-on Verify that the device is still gone (with that, HA really doesn't know about the device) Go to Apple Home, navigate to the device's "Accessory Settings", click on "Connected Services", delete any service named "4939" (this is Home Assistant, with that we make sure the device really forgets about Home Assistant) Now try to pair the device again.

Did exactly that, didn’t help unfortunately. Same issues.

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/addons/issues/3637#issuecomment-2162248781, or unsubscribe https://github.com/notifications/unsubscribe-auth/AD2QG7RTFXD4BBLY53SHI43ZG7WEVAVCNFSM6AAAAABJFR766SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRSGI2DQNZYGE. You are receiving this because you authored the thread.

Hi,

Any updates there. Matter with Eve products is still not working in HA, while working perfectly well between HomeKit and Alexa.

Any plans to have it resolved? Any additional details I can provide?

Thank you E

On 12 Jun 2024, at 11:17, E Hajar @.***> wrote:

Hi, thank you for the quick reply.

Please see my comments below:

On 12 Jun 2024, at 08:55, Stefan Agner @.***> wrote:

Which version of Home Assistant Core are you using?

2024.6.2 They work perfectly well in HomeKit and in Alexa.

Note that HomeKit is a different protocol, not related to Matter. You probably meant to say in Apple Home.

First it was not easy as by default adding them didn’t work and I had to do some unusually many trial and error to finally succeed. After adding them they worked for 10 mins or so and then went offline. With each full restart of HA server these devices appear for 10 mins and then go permanently offline.

Yes, Apple Home app. Add these devices as Matter Devices (not HomeKit devices) and then share these devices with Alexa and HA. Sharing with Alexa works flawlessly. Sharing with HA doesn’t.

Connection with AppleTV is working well, as all my HomeKit and HomeBridge integrations are working without any problems.

10 minutes is exactly the liveness check of battery operated devices. So it seems the Eve did not report in after 10 minutes 🤔

Not that Eve Energy is a power socket devices, that is not battery operated. Usually when it works then battery operated door sensors work too. It is when it disappears that battery operated devices disappear with it too. What is the node number of the Eve device?

According to Matter Server webpage:

Node 34 Offline Eve Systems Eve Energy 20EBO8301

Node 37 Offline Eve Systems Eve Door 20EBN9901

Node 40: Offline Eve Systems Eve Door 20EBN9901

Can you try to re-add again, but this time before adding make sure to do the follwing steps first:

Delete the device from Home Assistant, wait for 20-30 seconds (the server attempts to connect to the device to remove the credentials from the device. That might fail in your case). Restart the Matter Server add-on Verify that the device is still gone (with that, HA really doesn't know about the device) Go to Apple Home, navigate to the device's "Accessory Settings", click on "Connected Services", delete any service named "4939" (this is Home Assistant, with that we make sure the device really forgets about Home Assistant) Now try to pair the device again.

Did exactly that, didn’t help unfortunately. Same issues.

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/addons/issues/3637#issuecomment-2162248781, or unsubscribe https://github.com/notifications/unsubscribe-auth/AD2QG7RTFXD4BBLY53SHI43ZG7WEVAVCNFSM6AAAAABJFR766SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRSGI2DQNZYGE. You are receiving this because you authored the thread.

Do you have other devices connected to the AppleTV Thread network besides the Eve product?

To me it sounds like all devices connected via Thread go unavailable, which very much sounds like this report on the community forum: https://community.home-assistant.io/t/aqara-p2-sensors-status-changes-to-unavailable/739099/1

What networking gear are you using? Do you have HomePods connected to the AppleTV (for audio)?

In general, I have a couple of Nanoleaf thread bulbs and a single Eve Motion sensor connected to my AppleTV 4K 3. Gen. They stay all online all the time on my HA installation as well as in Apple Home.

So this isn't a general Home Assistant issue, but something related to your environment.

What Home Assistant OS version are you using and on which hardware?

No, I only have 1 router device Eve Energy and other leaf devices which connect to that Eve Energy. So I do not have any other device to test it with, partly because these do not work well in HA and so I am reluctant to invest into more Matter devices.

I use latest gen AppleTV and Alexas throughout the house. Apple TV and HA are connected using ethernet cable. Alexas are on wi fi.

I would also assume that this is something with my network that is blocking Matter connections somehow. But then why is it working perfectly with HomeKit and then I can share these devices with Alexa and they work perfectly with Alexa too. But whenever I try to share them with HA I struggle for HA to even find them and even if it does connection lasts for some 10 mins and then they again appear offline?

Also why did these devices work well with HA until April and starting April update they stopped?

If it wasn’t for those 2 clues I wouldn’t be thinking it is HA, but those two points indicate that it is very likely something not well implemented in Beta Matter Server and it may be a recent regression as it used to work well in the past.

My HAOS is the latest. Hardware is Trigkey PC.

On 25 Jun 2024, at 15:07, Stefan Agner @.***> wrote:

Do you have other devices connected to the AppleTV Thread network besides the Eve product?

To me it sounds like all devices connected via Thread go unavailable, which very much sounds like this report on the community forum: https://community.home-assistant.io/t/aqara-p2-sensors-status-changes-to-unavailable/739099/1

What networking gear are you using? Do you have HomePods connected to the AppleTV (for audio)?

In general, I have a couple of Nanoleaf thread bulbs and a single Eve Motion sensor connected to my AppleTV 4K 3. Gen. They stay all online all the time on my HA installation as well as in Apple Home.

So this isn't a general Home Assistant issue, but something related to your environment.

What Home Assistant OS version are you using and on which hardware?

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/addons/issues/3637#issuecomment-2188899813, or unsubscribe https://github.com/notifications/unsubscribe-auth/AD2QG7QFNC7UCG6SVSX2B4TZJFTRXAVCNFSM6AAAAABJFR766SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBYHA4TSOBRGM. You are receiving this because you authored the thread.

But then why is it working perfectly with HomeKit and then I can share these devices with Alexa and they work perfectly with Alexa too. But whenever I try to share them with HA I struggle for HA to even find them and even if it does connection lasts for some 10 mins and then they again appear offline?

Also why did these devices work well with HA until April and starting April update they stopped?

I also don't know, if I'd know, I would tell you :smile:

If it wasn’t for those 2 clues I wouldn’t be thinking it is HA, but those two points indicate that it is very likely something not well implemented in Beta Matter Server and it may be a recent regression as it used to work well in the past.

If you use the add-on you can revert back to a previous backup. However, you might need to downgrade the Core too.

But if this was a specific version, it would be interesting which version broke it. As mentioned, I do have running a setup with AppleTV just fine here, with latest HAOS and the latest add-on, so I am really not sure what change could have broken this.

My HAOS is the latest. Hardware is Trigkey PC.

Are you using virtualization or is HAOS running natively (generic-x86-64)?

home-assistant / addons