Hey ho.
Pairing via Apple Home worked great - but did someone manage to pair it via SkyConnect directly from HomeAssistant?
Matthias
I’ve been trying for a while… No such luck 
The app refuses to allow me to update my firmware and keeps pushing me the Apple Homepod/TV.
Meanwhile the thread networks in my environment advertise correctly (under meshcop), one is Home Assistant (Open Thread Router) and the other is my Google Nest.
Though, once you’re on Matter firmware - it should be easy enough to add (all you’d need is the Matter pairing code).
Nope, HA didn’t find the device for me. It only worked via Apple Home and then sharing.
Update to my earlier post. So far, the Eve Motion Sensor upgraded to Matter has been unstable in HA. It becomes unavailable every 10 minutes or so, flipping in and out of that state. I also have several dead entities associated with the device that I can’t delete, resulting in entities like ###.###_occupancy_3. I’ve also noticed that I can rename the entities when they are active, but if I rename the entire device, the integration dies.
I’ve tried deleting and adding it to HA in two ways, multiple times, each time deleting either the device or the entire Matter integration from HA and also deleting from Home. Finally, I reset it using a paper clip inserted into the small hole below the battery compartment until the red light blinks 5 times (per instructions from Eve support).
To delete from Home, go to your iPhone/iPad Settings → General → Matter Devices, and delete it there. Then delete from the Home app.
First way of trying to get it into HA was adding into either Eve app or Home app (result is the same) and then using device settings to get the pairing code. If I re-add the Matter integration into HA, it usually finds the device, but accepting that device has led to dead entities. So I then use the Add Matter Device integration, enter the pairing code, and that has worked…until it dies. This is also the reason for the dead entities.
I’ve also tried resetting and adding the device to HA first, but then Home app can’t find it.
For now I’m just keeping it sort of in HA with method one (adding to Home first), tolerating the very frequent “became unavailable” warnings, and using Home to automate the motion sensitive lights. It has been stable in Home. I’ve been doing this over Thread, as I have HomePod mini’s generating a Thread network. HA sees the Thread network via the Thread integration.
I’m sure it will get better, and it’s clear that Matter integration in HA is still beta. I’m just reporting my experience here in case it points towards ways to improve the integration.
Does Eve Energy paired over Matter show energy consumption?
Here is a related thread you may want to track… looks like some have had success showing energy and some have not…
Thank you.
But it seems they are talking about exclusively and directly connecting it over Bluetooth and Thread.
That works. I know that. Because I have done it.
Question is, if the Energy consumption will show in Home Assistant with Matter.
So first connecting it to HomeKit with Matter and then connecting it with Matter to Home Assistant.
As far as I understand things (and I could be wrong), Matter 1.0 does not yet support energy consumption data. So for now, all we have is simple switching.
Same issues here, I can add an Eve Energy Outlet to Homekit but it wont add to Home Assistant with SkyConnect.
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.)
2 Likes
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