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!
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.
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.
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.
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…