I transitioned an Eve Energy plug from HomeKit to Matter. It’s in Apple Home and I can turn on Pairing mode and get the code, but nothing shows up in HA.
I am running 2022.02.0, Matter Server 3.0.2, and have the Matter Integration installed.
I went in to the integration and set WiFi credentials (Why? I do not know since HA is wired on the same network, but it wasn’t working so I tried it). I tried restarting HA.
In the original video about Matter, there were some services used for adding (provisioning) devices, but those do not seem to be available anymore.
I have a SkyConnect as well, but I haven’t transitioned it to the ZigBee/Thread firmware yet - I don’t think that would help though either since the device is already provisioned in Apple Home, so the only way to add it I believe is using the pairing mode (vs adding it to HA’s thread network).
I also got to this screen, it took a while but then I was able to add a name and my contact sensor appeared in HA. But it always says “closed” and won’t change (although it changes in Apple Home)…
Edit: Ah, seems like I had to first set it into pairing mode via Apple Home app (will give you a specific code). And then use this code inside the HA app to pair it… now the value changes in HA as well. It just says “open” when it’s closed and the other way around…
Open the Home app, go to the device, tap on “Activate Pairing mode” almost at the bottom (or similar, I got it in German )
Got a popup with a pairing number, tapped “Copy number”, the popup closes
Go to the HA app, tap on “Configure” at the Matter integration
Tap on “Commission device”
The HomeKit popup with camera view opens
Above the camera view I tapped on “More options” to get a list of nearby devices
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.
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.
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
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
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?
Follow instructions when received from Eve to obtain new Matter Code
Upgrade firmware in Eve Development app (instructions tell how to obtain), including scanning new Matter QR code
Get Matter Server Add On in HA (enable advanced mode in my HA profile first)
Add Matter Integration in HA
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.
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).
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.
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.
)