Adding Matter device (Eve Energy)

[Shobba]

So, what I did with my window sensor:

1. Add it to Apple Home
2. Open the Home app, go to the device, tap on “Activate Pairing mode” almost at the bottom (or similar, I got it in German )
3. Got a popup with a pairing number, tapped “Copy number”, the popup closes
4. Go to the HA app, tap on “Configure” at the Matter integration
5. Tap on “Commission device”
6. The HomeKit popup with camera view opens
7. Above the camera view I tapped on “More options” to get a list of nearby devices
8. I tapped on the device I just copied the code of, pasted the code, and waited some time until the spinner disappeared and it asked me to add a device name.

[Jon123 (Jon)]

That’s the same procedure I followed, but I’m glad you shared it because it may help someone else in the future, it took me a bit to figure out how to do it the first time.

But it still gets stuck on the screen above. Having said that it seems to to show up differently sometimes.

Just now I tried it again and on the popup in the HA iOS app (that shows Matter devices that are in Apple Home) there were two options for the same device: Nearby and Other. I tried Nearby and received an error this time (I believe this is the option I used in my screenshot in the previous post).
So I tried the (same device) in the Other section and it asked for the pairing code. I pasted that in, and now it’s at the screen I shared earlier, but it’s titled “Eve Energy U.S. & Canada”, which is just the name of the device. It also sat here for about 10 minutes without anything change.

Screen recording: RPReplay_Final1675358344

[LGH]

I managed to commission an Eve energy outlet to Matter integration
Pretty much the steps outlined above, getting the pairing code from HomeKit and then using that in the HA app
Added it quite quickly and I can control the outlet using HA app, HomeKit, or Eve app

The downside is it is only an on/off switch. There is no power usage entities that I have with another (non-matter) Eve energy that was added to HA using the HomeKit controller method

[Jon123 (Jon)]

I’m wondering if it could be a network issue on my end.
I have HA running in a VM. The VM has its own IP which would be on the same subnet (vlan) as the Eve Energy. Other devices are able to be discovered but maybe there is something I need to fix.

Matter Server logs:

2023-02-02 12:11:31 core-matter-server chip.CTL[125] INFO Discovered device to be commissioned over DNS-SD
2023-02-02 12:11:31 core-matter-server chip.CTL[125] INFO Attempting PASE connection to UDP:[xxxx:xxxx:xxxx:x:xxxx:xxxx:xxxx:xxxx]:5540
2023-02-02 12:11:31 core-matter-server chip.EM[125] INFO <<< [E:34894i M:17577145] (U) Msg TX to 0:0000000000000000 [0000] --- Type 0000:20 (SecureChannel:PBKDFParamRequest)
2023-02-02 12:11:31 core-matter-server chip.IN[125] INFO (U) Sending msg 17577145 to IP address 'UDP:[xxxx:xxxx:xxxx:x:xxxx:xxxx:xxxx:xxxx]:5540'
2023-02-02 12:11:31 core-matter-server chip.-[125] ERROR ../src/inet/UDPEndPointImplSockets.cpp:411: OS Error 0x02000065: Network is unreachable at ../src/controller/SetUpCodePairer.cpp:255
2023-02-02 12:11:45 core-matter-server chip.CTL[125] ERROR Discovery timed out

[Jon123 (Jon)]

I’m at the point now where my router is giving the HA VM an ipv6 address.
I can ping that address from my machine.
But still not getting a connection to the device. I’m wondering if it’s because it may be connected via Thread?

[shanelord]

I’ve got my Eve Energy Outlet connected too, however, the status doesn’t seem to update correctly.

In HA:

1. Turn switch on (the physical switch turns on)
2. HA shows the toggle go ON, then it goes back to OFF (physical switch stays on).
3. No matter how many time I toggle it ON, it toggles back to OFF within a second.
4. Toggle it ON then OFF quickly turns the physical switch OFF.
5. Device logbook isn’t showing these interactions at all.

Really weird. I’m going to de-provision and try again.

I have the latest build HASSOS, Skyconnect etc all installed.

[Journeymnn (Michael)]

I was able to add an Eve Motion sensor to HA with the following steps:

1. Add it to Apple Home using HomeKit code
2. Participate in the Eve Matter upgrade program: Getting started with Matter | evehome.com.
3. Follow instructions when received from Eve to obtain new Matter Code
4. Upgrade firmware in Eve Development app (instructions tell how to obtain), including scanning new Matter QR code
5. Get Matter Server Add On in HA (enable advanced mode in my HA profile first)
6. Add Matter Integration in HA
7. Add Matter Device and enter the Matter code (don’t try to scan QR)

Now both Apple Home and HA see the device. Unfortunately, thus far it does not update in HA. It comes across as an occupancy sensor and is frozen in one state or the other. Illuminance does not register, but that is documented as the current state of the HA Matter integration, which currently only handles lights (some functions) and binary sensors. It’s not handling this binary sensor yet, though, at least for me.

[klassm (Matthias Klass)]

Hey ho.

Pairing via Apple Home worked great - but did someone manage to pair it via SkyConnect directly from HomeAssistant?

Matthias

[zenstrukt]

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).

[carstenb (Carsten)]

Nope, HA didn’t find the device for me. It only worked via Apple Home and then sharing.

[Journeymnn (Michael)]

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.

[superpower10]

Does Eve Energy paired over Matter show energy consumption?

[wmaker (Tommy Long)]

Here is a related thread you may want to track… looks like some have had success showing energy and some have not…

Eve Energy (v3 with Thread) power usage readout possible?

It works for me right now with a slight delay. if i switch it on via HA it takes about 5 secs to do so power reading comes up after 30 seconds and displays the correct wattage switching off takes around 3 secs, power reading follows 30 secs later to zero. in the history I can afterwards see time and Watt with the correct values.

[superpower10]

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.

[LGH]

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.

[Liqueseous (Ryan)]

Same issues here, I can add an Eve Energy Outlet to Homekit but it wont add to Home Assistant with SkyConnect.

[superpower10]

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.

[Liqueseous (Ryan)]

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

[Liqueseous (Ryan)]

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.)

[Journeymnn (Michael)]

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!