Eve Energy Matter - Can’t add it Home Assistant

smarthomeuser · May 17, 2024, 8:12pm

I updated my Eve Energy to Matter. It was successfully added to Apple Home.

But I can’t add it to Home Assistant.

I have tried it on Home Assistant on a Pi5 and a Home Assistant on a NUC (x86) which is a brand new installation. Both are less than 1m away from the Eve Energy.

What I did:

Open Apple Home
Click on the Eve Energy
Click on „Activate Pairing Mode“
Click on „Copy Code“
Went to Home Assistant → Integration → Add → Matter → „Already Paired“ → „Apple Home“
Paste Code
„Add Device“

→ Failed to add Device

Nyak · May 18, 2024, 10:19am

Have you tried adding via the Matter integration?

Worked perfectly for me.

smarthomeuser · May 18, 2024, 1:20pm

Is there another way than how I did it? If so, how?

Nyak · May 19, 2024, 12:27am

This link should help you out.

Scroll down to the ‘Adding a Matter device to Home Assistant’ section.

smarthomeuser · June 4, 2024, 12:41pm

But that’s exactly the way I described it and did it.

agners · June 6, 2024, 7:46am

Your steps do seem correct. Do you have other devices connected to your Matter server already?

Can you try again with the latest version of the Matter Server add-on? If you still experience problems, please post the logs of the Matter Server add-on after an attempt.

smarthomeuser · June 6, 2024, 5:37pm

Tried different Matter devices and couldn‘t connect any of them.

Will try again this weekend with the newest add-on and will post the information

smarthomeuser · June 7, 2024, 3:22pm

Here is the error from the Matter Add-on Log:

> 2024-06-07 17:18:57.791 (Dummy-2) CHIP_ERROR [chip.native.DIS] DNSSD packet parsing failed (for SRV records)
> 2024-06-07 17:18:57.791 (Dummy-2) CHIP_ERROR [chip.native.DIS] DNSSD packet parsing failed (for non-srv records)
> 2024-06-07 17:18:58.843 (MainThread) DEBUG [matter_server.server.device_controller.mdns] Commissionable Matter node disappeared: AsyncServiceInfo(type='_matterc._udp.local.', name='991955F7BA726443._matterc._udp.local.', addresses=[], port=None, weight=0, priority=0, server=None, properties={}, interface_index=None)

agners · June 7, 2024, 4:41pm

Hm, that is not a lot of log

Is this really everything from a commissioning attempt? There should be at least a info level message when commissioning starts (“Starting Matter commissioning…”).

smarthomeuser · June 7, 2024, 6:02pm

Changed Log-Level to verbose. Here is the result:

I copied only lines which are not double/trible etc.

2024-06-07 19:54:27.675 (MainThread) WARNING [zeroconf] Error with socket 67 (('::1', 5353, 0, 0))): [Errno 101] Network is unreachable

Traceback (most recent call last):

File "/usr/local/lib/python3.11/asyncio/selector_events.py", line 1200, in sendto

self._sock.sendto(data, addr)

OSError: [Errno 101] Network is unreachable

2024-06-07 19:55:51.732 (MainThread) DEBUG [matter_server.server.device_controller.mdns] Discovered commissionable Matter node: AsyncServiceInfo(type='_matterc._udp.local.', name='500A9645375CE188._matterc._udp.local.', addresses=[], port=5540, weight=0, priority=0, server='D6DE2FF4136A906E.local.', properties={b'VP': b'4874+80', b'DT': b'266', b'DN': b'Eve Energy', b'SII': b'800', b'SAI': b'800', b'T': b'0', b'D': b'2092', b'CM': b'2', b'RI': b'1700BE868F473977D8930EB351AE21DD1E7D', b'PH': b'36', b'PI': None}, interface_index=None)

2024-06-07 19:55:51.868 (Dummy-2) CHIP_DETAIL [chip.native.DIS] Warning: Attempt to mDNS broadcast failed on wlan0: src/inet/UDPEndPointImplSockets.cpp:416: OS Error 0x02000065: Network is unreachable

2024-06-07 19:55:51.869 (Dummy-2) CHIP_DETAIL [chip.native.DIS] mDNS broadcast had only partial success: 18 successes and 1 failures.

2024-06-07 19:55:51.880 (Dummy-2) CHIP_DETAIL [chip.native.DIS] Warning: Attempt to mDNS broadcast failed on wlan0: src/inet/UDPEndPointImplSockets.cpp:416: OS Error 0x02000065: Network is unreachable

2024-06-07 19:57:56.499 (MainThread) VERBOSE [matter_server.server.client_handler] [548168061712] Received: {

"message_id": "c9ab2316afa74c69b5b8eed54af7cc78",

"command": "commission_with_code",

"args": {

"code": "20116952115",

"network_only": true

}

}

2024-06-07 19:57:56.499 (MainThread) VERBOSE [matter_server.server.client_handler] [548168061712] Received CommandMessage(message_id='c9ab2316afa74c69b5b8eed54af7cc78', command='commission_with_code', args={'code': '20116952115', 'network_only': True})

2024-06-07 19:57:56.499 (MainThread) VERBOSE [matter_server.server.client_handler] [548168061712] Handling command commission_with_code

2024-06-07 19:57:56.499 (MainThread) INFO [matter_server.server.device_controller] Starting Matter commissioning with code using Node ID 10 (attempt 1/3).

2024-06-07 19:57:56.500 (Dummy-2) CHIP_PROGRESS [chip.native.CTL] Setting attestation nonce to random value

2024-06-07 19:57:56.500 (Dummy-2) CHIP_PROGRESS [chip.native.CTL] Setting CSR nonce to random value

2024-06-07 19:57:56.501 (Dummy-2) CHIP_DETAIL [chip.native.CTL] Stopping commissioning discovery over DNS-SD

2024-06-07 19:57:56.501 (Dummy-2) CHIP_PROGRESS [chip.native.CTL] Starting commissioning discovery over DNS-SD

2024-06-07 19:57:56.502 (Dummy-2) CHIP_DETAIL [chip.native.DIS] Warning: Attempt to mDNS broadcast failed on wlan0: src/inet/UDPEndPointImplSockets.cpp:416: OS Error 0x02000065: Network is unreachable

2024-06-07 19:57:56.504 (Dummy-2) CHIP_DETAIL [chip.native.DIS] mDNS broadcast had only partial success: 18 successes and 1 failures.

2024-06-07 19:57:56.505 (ThreadPoolExecutor-1_0) DEBUG [matter_server.server.storage] Saved data to persistent storage

2024-06-07 19:57:56.512 (Dummy-2) CHIP_PROGRESS [chip.native.CTL] Discovered device to be commissioned over DNS-SD

2024-06-07 19:57:56.512 (Dummy-2) CHIP_PROGRESS [chip.native.CTL] Attempting PASE connection to UDP:[fd0e:894b:f7b6:0:c7f0:b16a:f554:c29b]:5540

2024-06-07 19:57:56.512 (Dummy-2) CHIP_DETAIL [chip.native.IN] SecureSession[0x7f94001f00]: Allocated Type:1 LSID:37591

2024-06-07 19:57:56.512 (Dummy-2) CHIP_DETAIL [chip.native.SC] Assigned local session key ID 37591

2024-06-07 19:57:56.513 (Dummy-2) CHIP_PROGRESS [chip.native.EM] <<< [E:48815i S:0 M:109511587] (U) Msg TX to 0:0000000000000000 [0000] [UDP:[fd0e:894b:f7b6:0:c7f0:b16a:f554:c29b]:5540] --- Type 0000:20 (SecureChannel:PBKDFParamRequest)

2024-06-07 19:57:56.513 (Dummy-2) CHIP_DETAIL [chip.native.IN] SecureSession[0x7f94001f00]: Released - Type:1 LSID:37591

2024-06-07 19:57:56.513 (Dummy-2) CHIP_ERROR [chip.native.-] src/inet/UDPEndPointImplSockets.cpp:416: OS Error 0x02000065: Network is unreachable at src/controller/SetUpCodePairer.cpp:280

2024-06-07 19:57:56.590 (Dummy-2) CHIP_ERROR [chip.native.DIS] DNSSD packet parsing failed (for SRV records)

2024-06-07 19:57:56.590 (Dummy-2) CHIP_ERROR [chip.native.DIS] DNSSD packet parsing failed (for non-srv records)

2024-06-07 19:59:39.317 (Dummy-2) CHIP_DETAIL [chip.native.DIS] Warning: Attempt to mDNS broadcast failed on wlan0: src/inet/UDPEndPointImplSockets.cpp:416: OS Error 0x02000065: Network is unreachable

2024-06-07 19:59:39.318 (Dummy-2) CHIP_DETAIL [chip.native.DIS] mDNS broadcast had only partial success: 18 successes and 1 failures.

2024-06-07 19:59:39.319 (Dummy-2) CHIP_DETAIL [chip.native.DIS] SRV record already actively processed.

2024-06-07 19:59:39.319 (Dummy-2) CHIP_DETAIL [chip.native.DIS] SRV record already actively processed.

2024-06-07 19:59:39.319 (Dummy-2) CHIP_DETAIL [chip.native.DIS] SRV record already actively processed.

2024-06-07 19:59:39.320 (Dummy-2) CHIP_DETAIL [chip.native.DIS] Warning: Attempt to mDNS broadcast failed on wlan0: src/inet/UDPEndPointImplSockets.cpp:416: OS Error 0x02000065: Network is unreachable

2024-06-07 19:59:39.322 (Dummy-2) CHIP_DETAIL [chip.native.DIS] mDNS broadcast had only partial success: 18 successes and 1 failures.

smarthomeuser · June 12, 2024, 3:07pm

@agners
Any news?

MMAN · June 13, 2024, 7:51pm

I had the exact same situation and the thing that fixed it was making sure I had a local ipv6 address set up for all the devices. For whatever reason not having ipv6 set up on your router/the local inference will block it adding it to your HA even if it is set up in HomeKit

agners · June 14, 2024, 9:50am

...
2024-06-07 19:57:56.512 (Dummy-2) CHIP_PROGRESS [chip.native.CTL] Attempting PASE connection to UDP:[fd0e:894b:f7b6:0:c7f0:b16a:f554:c29b]:5540
...
2024-06-07 19:57:56.513 (Dummy-2) CHIP_ERROR [chip.native.-] src/inet/UDPEndPointImplSockets.cpp:416: OS Error 0x02000065: Network is unreachable at src/controller/SetUpCodePairer.cpp:280

It seems that there is no (current) route available to your Thread network

Do you use a Supervised or Container installation? There are some requirement to your Linux host to make sure router advertisments get properly processed: GitHub - home-assistant-libs/python-matter-server: Python server to interact with Matter

With Home Assistant OS, everything should be setup to work well out-of-the-box, including router reach-ability probing for fast failover etc.

smarthomeuser · June 15, 2024, 7:25pm

@agners
I use Home Assistant OS with Supervisor on a Pi5 and NUC. Both don’t work with the same Log output.

@MMAN
Thanks. I don‘t have a IPv6 Internal Network setup on. Why should I? It’s way to cumbersome for a private network.

And the Eve is Thread/Bluetooth so there is so LAN/WLAN in the game.

And if Matter requires IPv6 in the Internal Network, I and many othe private users will not use it.

smarthomeuser · June 23, 2024, 8:31am

Bought a new Meross Matter Smart Plug. Tried to add it.

Same thing. Same error. Can not add it the neither of the Home Assistant OS Superviser Systems.

agners · June 23, 2024, 9:53am

Hm, so you also get the Attempting PASE connection to UDP:? What IP address is it displaying there? The Meross Matter smart plug is a WiFi device, so this should be a link local address.

What IPv6 settings do you have in the network configuration?

While you don’t need to setup IPv6 addresses manually, the Thread network requires IPv6 to be enabled to receive IPv6 neighbor discovery messages (Settings → System → Network, make sure IPv6 is set to Automatic).

Since you’ve added the Eve device to Apple Home, I assume you are using Apple devices as Thread border router? What is your Thread border router? Is it in the same network (no firewalling etc.)?

smarthomeuser · July 16, 2024, 1:34pm

Problem solved.

First I had to activate IPv6 in my Home Network.

Second and more important:
Home Assistant is not able to add devices that are in a different VLAN.

HomeKit can do it easily.

That means that the Matter developers from Home Assistant have to do something to make it work over different VLANs.