I have no problems to connect them.
Remember SkyConnect is ZigBee. Eve Energy is Bluetooth. So you have to have Bluetooth on the Hardware which runs Home Assistant.
And only the Eve Energy v3 which are Thread compatible will pair with a Home Assistant Hardware.
I am using a Raspberry Pi 3b which has bluetooth. I installed the beta firmware to my Eve Energy Outlet. I can’t figure out why it is refusing to connect to Home Assistant.
Here is the log output when trying to add the device. I am adding it using the pairing mode option in Apple Homekit.
2023-03-15 12:26:05 core-matter-server matter_server.server.server[126] INFO Starting the Matter Server...
2023-03-15 16:34:32 core-matter-server chip.CTL[126] INFO Setting attestation nonce to random value
2023-03-15 16:34:32 core-matter-server chip.CTL[126] INFO Setting CSR nonce to random value
2023-03-15 16:34:32 core-matter-server chip.CTL[126] INFO Starting commissioning discovery over BLE
2023-03-15 16:34:32 core-matter-server chip.CTL[126] INFO Starting commissioning discovery over DNS-SD
2023-03-15 16:34:32 core-matter-server chip.DL[126] ERROR Long dispatch time: 206 ms, for event type 2
2023-03-15 16:34:33 core-matter-server chip.BLE[126] INFO BLE removing known devices.
2023-03-15 16:34:33 core-matter-server chip.BLE[126] INFO BLE initiating scan.
2023-03-15 16:34:33 core-matter-server chip.DL[126] ERROR Long dispatch time: 660 ms, for event type 2
2023-03-15 16:34:33 core-matter-server chip.CTL[126] INFO Discovered device to be commissioned over DNS-SD
2023-03-15 16:34:33 core-matter-server chip.CTL[126] INFO Attempting PASE connection to UDP:[fd58:2bf0:26cf:0:60f3:e37e:e588:55ab]:5540
2023-03-15 16:34:33 core-matter-server chip.EM[126] INFO <<< [E:20448i M:93292473] (U) Msg TX to 0:0000000000000000 [0000] --- Type 0000:20 (SecureChannel:PBKDFParamRequest)
2023-03-15 16:34:33 core-matter-server chip.IN[126] INFO (U) Sending msg 93292473 to IP address 'UDP:[fd58:2bf0:26cf:0:60f3:e37e:e588:55ab]:5540'
2023-03-15 16:34:33 core-matter-server chip.-[126] ERROR ../src/inet/UDPEndPointImplSockets.cpp:411: OS Error 0x02000065: Network is unreachable at ../src/controller/SetUpCodePairer.cpp:255
2023-03-15 16:34:34 core-matter-server chip.CTL[126] INFO Discovered device to be commissioned over DNS-SD
2023-03-15 16:34:34 core-matter-server chip.CTL[126] INFO Attempting PASE connection to UDP:[fd58:2bf0:26cf:0:60f3:e37e:e588:55ab]:5540
2023-03-15 16:34:34 core-matter-server chip.EM[126] INFO <<< [E:20449i M:93292474] (U) Msg TX to 0:0000000000000000 [0000] --- Type 0000:20 (SecureChannel:PBKDFParamRequest)
2023-03-15 16:34:34 core-matter-server chip.IN[126] INFO (U) Sending msg 93292474 to IP address 'UDP:[fd58:2bf0:26cf:0:60f3:e37e:e588:55ab]:5540'
2023-03-15 16:34:34 core-matter-server chip.-[126] ERROR ../src/inet/UDPEndPointImplSockets.cpp:411: OS Error 0x02000065: Network is unreachable at ../src/controller/SetUpCodePairer.cpp:255
2023-03-15 16:34:36 core-matter-server chip.CTL[126] INFO Discovered device to be commissioned over DNS-SD
2023-03-15 16:34:36 core-matter-server chip.CTL[126] INFO Attempting PASE connection to UDP:[fd58:2bf0:26cf:0:60f3:e37e:e588:55ab]:5540
2023-03-15 16:34:36 core-matter-server chip.EM[126] INFO <<< [E:20450i M:93292475] (U) Msg TX to 0:0000000000000000 [0000] --- Type 0000:20 (SecureChannel:PBKDFParamRequest)
2023-03-15 16:34:36 core-matter-server chip.IN[126] INFO (U) Sending msg 93292475 to IP address 'UDP:[fd58:2bf0:26cf:0:60f3:e37e:e588:55ab]:5540'
2023-03-15 16:34:36 core-matter-server chip.-[126] ERROR ../src/inet/UDPEndPointImplSockets.cpp:411: OS Error 0x02000065: Network is unreachable at ../src/controller/SetUpCodePairer.cpp:255
2023-03-15 16:34:40 core-matter-server chip.CTL[126] INFO Discovered device to be commissioned over DNS-SD
2023-03-15 16:34:40 core-matter-server chip.CTL[126] INFO Attempting PASE connection to UDP:[fd58:2bf0:26cf:0:60f3:e37e:e588:55ab]:5540
2023-03-15 16:34:40 core-matter-server chip.EM[126] INFO <<< [E:20451i M:93292476] (U) Msg TX to 0:0000000000000000 [0000] --- Type 0000:20 (SecureChannel:PBKDFParamRequest)
2023-03-15 16:34:40 core-matter-server chip.IN[126] INFO (U) Sending msg 93292476 to IP address 'UDP:[fd58:2bf0:26cf:0:60f3:e37e:e588:55ab]:5540'
2023-03-15 16:34:40 core-matter-server chip.-[126] ERROR ../src/inet/UDPEndPointImplSockets.cpp:411: OS Error 0x02000065: Network is unreachable at ../src/controller/SetUpCodePairer.cpp:255
2023-03-15 16:34:43 core-matter-server chip.CTL[126] ERROR Commissioning discovery over BLE failed: ../src/platform/Linux/BLEManagerImpl.cpp:814: CHIP Error 0x00000032: Timeout
2023-03-15 16:34:43 core-matter-server chip.-[126] ERROR ../src/platform/Linux/BLEManagerImpl.cpp:814: CHIP Error 0x00000032: Timeout at ../src/controller/SetUpCodePairer.cpp:299
2023-03-15 16:35:02 core-matter-server chip.CTL[126] ERROR Discovery timed out
I GOT IT WORKING.
Resolution: Make sure ipv6 is enabled under network in Home Assistant.
------How I figured it out.------
I started watching this video “Matter in Home Assistant workshop - YouTube” and saw the below slide (I knew I had ipv6 disabled starting this adventure but didnt think it would be a problem.)
Meh, can anyone help me figure out how to delete the Eve (Matter) motion sensor (first screenshot)? I’ve tried selecting the hamburger menu beside Download Diagnostics and deleting device, which does nothing. I’ve tried deleting the Matter Beta integration, taking out the batteries from the sensor, and adding back the integration. It still automatically “finds” the same dead device, and I have no option to refuse to include it. I’ve tried deleting the entities, and HA won’t let me because it says they are still being provided by the integration.
The device is working in HomeKit.
The second screenshot shows yet other entities of the same device, which I had renamed in the UI. It says it is integrated via a sensor or binary sensor template, but I have no such entries in my configuration,yaml file, and I can’t select the boxes in the UI to try and delete. I have no idea where it’s pulling information from to populate this set of entities.
Thread integration is fine. I had already enabled ipv6.
So far, despite my earlier posts, it has been an utter fail in HA. I can’t get it to stay available; I have multiple dead entities; I can’t delete any of them. Any advice welcome!
I am trying to add an eve plug that I upgraded to matter. I have it in HomeKit and then click pairing mode in Homekit and use that code in the HA iOS app. After a few minutes I get a message saying thread boarder router required. I have a HomePod mini. Do i need something for my raspberry pi too?
Thanks
Disregard. I figured it out, you have to be on the owner account for it to add. It wont add with an authorized user
I am seeing the same error, and it makes zero sense whatsoever. I am trying to add the power point directly to Home Assistant. You have to be the owner of the home in HomeKit to add a device to Home Assistant without first adding it to the home? That makes zero sense whatsoever.
I’m happy to report that one of the updates in the Matter server seems to have resolved my problems, fingers crossed. I’ve added two Eve Motion/Occupancy sensors now and they seem to be responding properly over the last few days in both HA and HomeKit. The old dead entities are gone, which presumably was the 10-day auto purge. Manual purging (via Developer Tools → recorder.purge_entities) did not work, even after logging out and in again, as suggested in some other threads.
I added the sensors to HomeKit first, followed the Matter upgrade instructions on the Eve website, obtained the pairing code from the Apple Home settings for the device, and used the pair with code option with the “Add Matter Device” integration in HA. Trying to add the device in HA with the Matter QR code did not work.
So I added it to HomeKit first and then in HomeKit goto the device and get pairing code and then added it to HA with the the iphone that is has the iCloud master login for HK and it added right away.
Trying to add the device in HA with the Matter QR code did not work.
@Journeymnn I did the exactt thing, getting the matter code via iOS first. I origially paired it with an Android phone before. Now with my brand new Home Assistant Yellow, I disconnected it from Google and tried to connect it with HA, but it does not work (does not find the device).
I am new to HA so I dont know how and where to trouble shoot. The only thing I played around with up to now is Philips Hue integration which works just fine.
Andreas
There seems to be multiple ways to get the Eve Energy into Home Assistant. I won’t be using Matter for now, even though it works reasonably well now in 2023.6.x
Matter 1.0 still does not support Energy Monitoring devices and I want that in my HA Install.
did you ever resolve this?
i have the same problem with Aqara P2…
Halllo,
ich bin ziemlich neu bei HA.
HA läuft im Docker auf QNAP, matter-server ebenfalls.
Die Integration meiner Geräte hat relativ gut geklappt, nur bei Matter Geräten komme ich nicht weiter.
Ich habe es wie oben beschrieben über beide Wege versucht.
Der Fehler ist immer der Gleiche.
Ich finde nirgends eine Anleitung, ob ich den matter-server irgendwo integrieren muss oder wie und ob ich an den IPv6 Einstellungen in der Fritzbox oder HA etwas ändern muss.
Für eine Hilfe wäre ich dankbar.
Gruß
hardl
Is it a matter thread or matter wifi device? For matter thread device see here: https://community.home-assistant.io/t/thread-border-router-required-with-eve-and-matter Maybe this can help you.
Same problem here:
Cant add device (Eve Door and Windows Firmware 3.2.1 / Matter updated) via Home Assistant on iPhone.
Running Home Assistant OS 11.2 (Core 2023.12.3) in Proxmox as VM.
IP V6 → automatic.
Added Sensor via Eve app, sensor is available in ios Home App.
In Home Assistant app Eve Door an Window is selectable.
After I entered the pairing code, after a while the error message appeared that the device cannot be added.
23-12-21 21:23:20 core-matter-server PersistentStorage[126] INFO SetSdkKey: f/1/k/0 = b'\x15$\x01\x00$\x02\x016\x03\x15$\x04\x00%\x05\xb9 0\x06\x10\x90w\xc6\xd8%7\x83\x92\x9d\x0fSoH)s\x94\x18\x15$\x04\x00$\x05\x000\x06\x10\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x18\x15$\x04\x00$\x05\x000\x06\x10\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x18\x18%\x07\xff\xff\x18'
2023-12-21 21:23:20 core-matter-server PersistentStorage[126] INFO Committing...
2023-12-21 21:23:20 core-matter-server matter_server.server.device_controller[126] DEBUG CHIP Device Controller Initialized
2023-12-21 21:23:20 core-matter-server matter_server.server.storage[126] DEBUG Loading persistent settings from /data/13521755765619406805.json
2023-12-21 21:23:20 core-matter-server matter_server.server.storage[126] DEBUG Started.
2023-12-21 21:23:20 core-matter-server matter_server.server.device_controller[126] DEBUG Loaded 0 nodes
2023-12-21 21:23:20 core-matter-server matter_server.server.vendor_info[126] INFO Loading vendor info from storage.
2023-12-21 21:23:20 core-matter-server matter_server.server.vendor_info[126] INFO Loaded 100 vendors from storage.
2023-12-21 21:23:20 core-matter-server matter_server.server.vendor_info[126] INFO Fetching the latest vendor info from DCL.
2023-12-21 21:23:20 core-matter-server matter_server.server.vendor_info[126] INFO Fetched 100 vendors from DCL.
2023-12-21 21:23:20 core-matter-server matter_server.server.vendor_info[126] INFO Saving vendor info to storage.
2023-12-21 21:23:20 core-matter-server matter_server.server.server[126] DEBUG Webserver initialized.
2023-12-21 21:23:36 core-matter-server matter_server.server.client_handler[126] DEBUG [140292020789328] Connected from 192.168.178.142
2023-12-21 21:23:36 core-matter-server matter_server.server.client_handler[126] DEBUG [140292020789328] Received: {
"message_id": "6010b178685a45e1b771234027eb1471",
"command": "start_listening",
"args": null
}
2023-12-21 21:23:36 core-matter-server matter_server.server.client_handler[126] DEBUG [140292020789328] Received CommandMessage(message_id='6010b178685a45e1b771234027eb1471', command='start_listening', args=None)
2023-12-21 21:23:36 core-matter-server matter_server.server.client_handler[126] DEBUG [140292020789328] Handling command start_listening
2023-12-21 21:23:39 core-matter-server chip.DL[126] DEBUG No wifi interface name. Ignoring IP update event.
2023-12-21 21:25:04 core-matter-server chip.DIS[126] DEBUG SRV record already actively processed.
2023-12-21 21:25:04 core-matter-server chip.DIS[126] DEBUG SRV record already actively processed.
2023-12-21 21:25:04 core-matter-server chip.DIS[126] DEBUG SRV record already actively processed.
2023-12-21 21:25:04 core-matter-server chip.DIS[126] DEBUG SRV record already actively processed.
2023-12-21 21:25:04 core-matter-server chip.DIS[126] DEBUG SRV record already actively processed.
2023-12-21 21:25:04 core-matter-server chip.DIS[126] DEBUG SRV record already actively processed.
2023-12-21 21:25:04 core-matter-server chip.DIS[126] DEBUG SRV record already actively processed.
2023-12-21 21:25:04 core-matter-server chip.DIS[126] DEBUG SRV record already actively processed.
2023-12-21 21:25:04 core-matter-server chip.DIS[126] DEBUG SRV record already actively processed.
2023-12-21 21:25:04 core-matter-server chip.DIS[126] DEBUG SRV record already actively processed.
2023-12-21 21:25:04 core-matter-server chip.DIS[126] DEBUG SRV record already actively processed.
2023-12-21 21:25:04 core-matter-server chip.DIS[126] DEBUG SRV record already actively processed.
2023-12-21 21:25:04 core-matter-server chip.DIS[126] DEBUG SRV record already actively processed.
2023-12-21 21:25:04 core-matter-server chip.DIS[126] DEBUG SRV record already actively processed.
2023-12-21 21:25:04 core-matter-server chip.DIS[126] DEBUG SRV record already actively processed.
2023-12-21 21:25:04 core-matter-server chip.DIS[126] DEBUG SRV record already actively processed.
2023-12-21 21:25:11 core-matter-server chip.DIS[126] DEBUG SRV record already actively processed.
2023-12-21 21:25:11 core-matter-server chip.DIS[126] DEBUG SRV record already actively processed.
2023-12-21 21:25:11 core-matter-server chip.DIS[126] DEBUG SRV record already actively processed.
2023-12-21 21:25:11 core-matter-server chip.DIS[126] DEBUG SRV record already actively processed.
2023-12-21 21:25:11 core-matter-server chip.DIS[126] DEBUG SRV record already actively processed.
2023-12-21 21:25:11 core-matter-server chip.DIS[126] DEBUG SRV record already actively processed.
2023-12-21 21:25:11 core-matter-server chip.DIS[126] DEBUG SRV record already actively processed.
2023-12-21 21:25:11 core-matter-server chip.DIS[126] DEBUG SRV record already actively processed.
2023-12-21 21:25:11 core-matter-server chip.DIS[126] DEBUG SRV record already actively processed.
2023-12-21 21:25:11 core-matter-server chip.DIS[126] DEBUG SRV record already actively processed.
2023-12-21 21:25:11 core-matter-server chip.DIS[126] DEBUG SRV record already actively processed.
2023-12-21 21:25:11 core-matter-server chip.DIS[126] DEBUG SRV record already actively processed.
2023-12-21 21:25:11 core-matter-server chip.DIS[126] DEBUG SRV record already actively processed.
2023-12-21 21:25:11 core-matter-server chip.DIS[126] DEBUG SRV record already actively processed.
2023-12-21 21:25:11 core-matter-server chip.DIS[126] DEBUG SRV record already actively processed.
2023-12-21 21:25:11 core-matter-server chip.DIS[126] DEBUG SRV record already actively processed.
2023-12-21 21:25:20 core-matter-server matter_server.server.storage[126] DEBUG Saved data to persistent storage
2023-12-21 21:25:21 core-matter-server chip.DIS[126] DEBUG SRV record already actively processed.
2023-12-21 21:25:21 core-matter-server chip.DIS[126] DEBUG SRV record already actively processed.
2023-12-21 21:25:21 core-matter-server chip.DIS[126] DEBUG SRV record already actively processed.
2023-12-21 21:25:21 core-matter-server chip.DIS[126] DEBUG SRV record already actively processed.
2023-12-21 21:25:21 core-matter-server chip.DIS[126] DEBUG SRV record already actively processed.
2023-12-21 21:25:21 core-matter-server chip.DIS[126] DEBUG SRV record already actively processed.
2023-12-21 21:25:21 core-matter-server chip.DIS[126] DEBUG SRV record already actively processed.
2023-12-21 21:25:21 core-matter-server chip.DIS[126] DEBUG SRV record already actively processed.
2023-12-21 21:25:21 core-matter-server chip.DIS[126] DEBUG SRV record already actively processed.
2023-12-21 21:25:21 core-matter-server chip.DIS[126] DEBUG SRV record already actively processed.
2023-12-21 21:25:21 core-matter-server chip.DIS[126] DEBUG SRV record already actively processed.
2023-12-21 21:25:21 core-matter-server chip.DIS[126] DEBUG SRV record already actively processed.
2023-12-21 21:25:21 core-matter-server chip.DIS[126] DEBUG SRV record already actively processed.
2023-12-21 21:25:21 core-matter-server chip.DIS[126] DEBUG SRV record already actively processed.
2023-12-21 21:25:21 core-matter-server chip.DIS[126] DEBUG SRV record already actively processed.
2023-12-21 21:25:21 core-matter-server chip.DIS[126] DEBUG SRV record already actively processed.
2023-12-21 21:50:32 core-matter-server matter_server.server.client_handler[126] DEBUG [140292020789328] Received: {
"message_id": "a945cec8b09048aa8a5102ed355da356",
"command": "commission_with_code",
"args": {
"code": "MT:U1ZA30P9137K.56Y810"
}
}
2023-12-21 21:50:32 core-matter-server matter_server.server.client_handler[126] DEBUG [140292020789328] Received CommandMessage(message_id='a945cec8b09048aa8a5102ed355da356', command='commission_with_code', args={'code': 'MT:U1ZA30P9137K.56Y810'})
2023-12-21 21:50:32 core-matter-server matter_server.server.client_handler[126] DEBUG [140292020789328] Handling command commission_with_code
2023-12-21 21:50:32 core-matter-server matter_server.server.helpers.paa_certificates[126] INFO Fetching the latest PAA root certificates from DCL.
2023-12-21 21:50:32 core-matter-server matter_server.server.helpers.paa_certificates[126] INFO Fetched 0 PAA root certificates from DCL.
2023-12-21 21:50:32 core-matter-server matter_server.server.helpers.paa_certificates[126] INFO Fetching the latest PAA root certificates from Git.
2023-12-21 21:50:32 core-matter-server matter_server.server.helpers.paa_certificates[126] INFO Fetched 0 PAA root certificates from Git.
2023-12-21 21:50:32 core-matter-server chip.CTL[126] INFO Setting attestation nonce to random value
2023-12-21 21:50:32 core-matter-server matter_server.server.storage[126] DEBUG Saved data to persistent storage
2023-12-21 21:50:32 core-matter-server chip.CTL[126] INFO Setting CSR nonce to random value
2023-12-21 21:50:32 core-matter-server chip.CTL[126] DEBUG Stopping commissioning discovery over DNS-SD
2023-12-21 21:50:32 core-matter-server chip.CTL[126] INFO Starting commissioning discovery over DNS-SD
2023-12-21 21:51:02 core-matter-server chip.CTL[126] ERROR Discovery timed out
2023-12-21 21:51:02 core-matter-server chip.CTL[126] DEBUG Stopping commissioning discovery over DNS-SD
2023-12-21 21:51:02 core-matter-server chip.ZCL[126] ERROR Secure Pairing Failed
2023-12-21 21:51:02 core-matter-server matter_server.server.client_handler[126] ERROR [140292020789328] Error handling message: CommandMessage(message_id='a945cec8b09048aa8a5102ed355da356', command='commission_with_code', args={'code': 'MT:U1ZA30P9137K.56Y810'})
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/matter_server/server/client_handler.py", line 188, in _run_handler
result = await result
^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/matter_server/server/device_controller.py", line 167, in commission_with_code
raise NodeCommissionFailed(
matter_server.common.errors.NodeCommissionFailed: Commission with code failed for node 4
2023-12-21 21:51:03 core-matter-server chip.DIS[126] ERROR Timeout waiting for mDNS resolution.
Problem solved. 
I’ll describe here what my solution looks like for others with the same problem:
The only thing I had to do was enable IPv6 and convince Home Assistant to get an IPv6 address within Proxmox. (Matter → IPv6)
Interestingly, I only had to add the entry: net.ipv6.conf.all.forwarding=1 within
/etc/sysctl.conf.
From then on, my Home Assistant VM received an IPv6 address and I was able to add my Eve Door and Window Sensor as described at Matter (BETA) - Home Assistant.
Unfortunately I don’t know much about IPv6 yet, but here is my stored interface configuration from Proxmox. (Only IPv4)
#/etc/network/interfaces
auto lo
iface lo inet loopback
iface enp2s0 inet manual
iface enp1s0 inet manual
iface vmbr0 inet static
address xxx.xxx.xxx.xxx/24
gateway xxx.xxx.xxx.xxx
bridge-ports enp2s0
bridge-stp off
bridge-fd 0
bridge-vlan-aware yes
bridge-vids 2-4094
auto vmbr1
iface vmbr1 inet manual
bridge-ports none
bridge-stp off
bridge-fd 0
“Hi, I’m facing the same issue. Could you provide instructions on where to input what? I’m a complete beginner and would appreciate any accompanying images. Thanks!”
sorry it seems that this a a very long thread …
I’m strugling to add Eve Motion sensor to HA, but MAtter is working perfectly sinc eI was able to add a GW from Tuya and was able to add 3 bulbs from NanoLeaf taht were register in Apple Home.
When I try to say taht the Eve motion sensor was register in Apple Home and turn on pairing in Apple Home and copy the code, to add it in HA… it fail (unlike the bulbs from Nanoleaf)
can someone provide some guidance on how to make Eve working usign Matter
Thank you,
Paulo