I have two eve motion sensors (matter) in my bathroom, but they keep loosing connection! Every time i have to reset them! Before i worked with homekit and i didn’t have a homey pro and then they worked perfect! Now they stop working one after the other!
Somebody the same problem?
Ok thanks! I will try that!
Hi guys,
Not to hijack this thread, but I have the same problem more or less. I have recently bought 5 Eve Motion (Thread/Matter versions) and they work in the Eve app and Apple Home.
I then shared the (Apple) Matter device with Homey Pro using the “connect via iOS” option (with a share matter device code from Apple Home) in the hopes everything then stays in the existing Apple created Thread network instead of having Homey Pro create a competing network. Not sure how that works though?
The problem is after some hours or maybe a day or two the Eve Motion device stops working in Homey Pro. They still work in Apple Home and the Eve app. The only fix I have so far is to reset the device and reconfigure everything again.
Any advice or insights are highly appreciated.
Do you use zigbee devices as well?
It"s not recommended to use both Thread and zigbee at the same time (the controllers share the hardware).
Yes - I use Zigbee also. Hmm - is this really an official recommendation? Not mixing zigbee and thread I mean? I did not know that - it seems like a huge limitation. Do you know of a source for this information? I would love to read up on that.
Thanks for your inputs 
It’s not official, but other companies that use the same Zigbee/Thread chip as Homey does very much advise against using Zigbee and Thread together on the same chip because it can cause issues.
However, I’m not sure if your devices are using Homey’s Thread network anyway, since you paired them through iOS and (therefore) should have an Apple-based Thread Border Router (like an ATV or a HomePod) that is managing the Thread connections.
From what I know, the “multi-admin” part, where you can share a Matter device between multiple ecosystems, is implemented on the Matter protocol layer and not the Thread protocol layer. So it could be that your device is connected over Thread with your Apple TBR and passed to Homey over Matter, which would use a network connection, not a Thread connection (if you feel like testing this: turn off your Apple TBR and see if the device is still accessible from Homey; if so, it is connected to Homey over Thread. If not, it’s connected to Homey over Matter via your network).
FWIW, I’ve been reading multiple posts from people that are having issues with Matter devices, where they disappear or disconnect from Homey after a while.
Thanks for the fast responses guys - really appreciate that.
What you are describing is exactly how I understand this to work - and why I chose to join the matter device via iOS. To leverage I already have 4-5 powered Apple devices both acting with border router redundancy as well as routing/repeaters for the thread signals.
I would imagine joining the devices via Homey Pro’s thread radio would stand up a competing thread network with only one TBR (Homey) and no signal repeaters in my case…
Also I can tell in the device properties in Homey that the Eve Motion devices are connected to the Apple Thread network. I would need to turn them all off to verify though…
If Homey tells you the device is connected to the Apple Thread network, your issue is with Matter and not with Thread, so it’s a networking issue.
Like I said before, I’ve been reading multiple report from people having issues with Matter on Homey, where their devices disappear after some time. AFAIK this hasn’t been picked up by Athom yet (or at least not publicly). You can try issuing a support request.
Thanks for the feedback - I already created a support ticket and will add the comments from this thread once I connect with the support team
FYI I have reconfigured all Eve Motion (and also 2 Eve Energy for Thread coverage) devices to run on Homey Pro’s Thread network instead of Apple’s.
It’s clear in the device properties they now belong to the Home Pro Thread network. Will be interesting to see if this makes a difference.
For now they seem responsive - but far more (motion) sensitive than when connected to the Apple Thread Network. Maybe Eve controls some aspects I miss out on in Homey… Anyways - will let it run for a few days…
Eve matter. I have exactly the same problem but I haven’t got an apple ecosystem all Android so it’s going in the bin soon
@Henrik_Otterstrom How is it working for you?
Well…
Much has happened since my last post. Long post warning… 
It turned out for some strange reason I had 2 Apple Thread networks running at the same time. Some devices on one, others on another resulting in uneven Thread coverage and strange behaviours. I had no idea this was possible but apparently it is and Apple seems to create a Thread network for every Home you create. Why I ended up with 2 even though I only had 1 Home defined is beyond me.
Anyways - long story short I ended up removing all devices and my Apple Home as well as disabling HomeKit on all Apple Thread Border Routers. Then rebuilding everything from scratch, deciding to use only Apple TBR’s and build the strongest possible Thread network with what I have.
I joined most devices first using Apple Home and then shared the Matter devices with Home Assistant and Homey. But I also joined devices to Homey or Home Assistant first and then shared them with the others. Everything just worked and it has been rock solid for the past 3 weeks or so…
…Until yesterday where 1 of the Eve Motions again stopped responding in Homey Pro. Exactly the same symptom. Still working fine in Apple Home and Home Assistant. And this time I only have 1 Thread network 
Honestly I don’t know what to make of it. Matter seems less stable in Homey. The same devices works flawlessly in Apple Home and Home Assistant at the same time.
I have learned a lot about how Thread and Matter works and how mDNS is really important. Tip: Look for the “Discovery” apps on iOS/macOS for insight into the Thread and Matter components in your network.
Is it allowed to hijack a hijacked thread?
i am having difficulty connecting eve door sensors, which are already connected to apple home, to homey. The first two went well, the third sensor does not want to connect at all to homey.
You mentioned a shared device code from Apple Home. Where did you get those?
If the Matter device is connected to an existing ecosystem you can set the device in pairing mode and get a code you can use in another ecosystem. This works across Apple Home, Homey Pro and Home Assistant here in my testing (and I assume Google or Amazon).
If the device is already in Apple Home, open its properties and go to the buttom. Here you find the link to get the code. Once you copy the code to your clipboard use the Homey App and add a Matter device. Chose to use the iOS Thread Network. Since you can’t scan a QR code at this time click the link above the camera view, chose your device type and and paste in the code.
In my testing you still need to be within bluetooth range of the device much like when you add it for the first time.
I think the device is in pairing mode for 15 minutes, so if things go wrong wait enough time before trying again.
I dont have the option to provide screenshots at this time, so I hope this makes sense?
Hi Hendrik,
Thanks for the explanation. I understand it, but unfortunately, I end up getting the error that the devixe cannot be found and the message ‘try again later’.
I have several eve door sensors. The first two, I got connected after several tries (no idea how). The third one does not want to connect to the homey.
Best wishes,
Niels
When pairing, make sure Homey, the device and your phone are in Bluetooth range, meaning not more than a few meters apart from eachother.
After trying again and again, it did work. Maybe it is at the edge of bluetooth range of the homey device? Hendrik and Peter, thanks for the help
I believe it is your phone that needs to be within bluetooth range of your device when pairing. I don’t believe it matters where your Homey Pro is located. Your phone has the Thread credentials and it pushes them to the device over Bluetooth initially. It might be the Homey Pro can do the same, but then only if you are using Homey’s Thread network. In that case proximity to Homey Pro is key. YMMV.
I had similar experiences until I realised this. And as I wrote about the 15 minutes pairing mode - if you have tried several identical devices they might all be actively in pairing mode and they all look the same on the phone right before you need to enter the code. Really bad design IMHO - they show up as device type / default name instead of the name you gave the device in the first eco system that adopted it.
Also make sure you decide from the beginning what Thread network you are going to use. Technically it will work even if you spread your devices over several Thread networks. Matter is a routed protocol after all so they will talk via the thread border routers. But until some later version of Thread you end up diluting your Thread radio coverage if you use more than 1 Thread network.
IMHO: What ever ecosystem you have the most - use that for Thread network. In my case it is Apple TV’s and HomePods so I join all my devices to Homey using the iOS network - not Homeys default own Thread network… See ChrisG’s screenshot in the beginning of this thread.
So the lesson I took from this: Open the device for pairing one at the time and stand physically close to it when entering the code. This made it work every time for me…
