02-20-2024 02:57 AM
I have 3 eve home sensors using matter over thread (2x eve motion and 1x eve door sensor) and they all seem to not be reporting their status to the Google home app, making automations fail to run. This happens quite often, every few days.
I initially thought it was the batteries but after replacing all of them the sensors flash when they change state signifying that they detected the change it is just not reflecting in the Google home app. (not being transmitted over the matter network??)
I have removed all sensors and re-added them but that did not solve it.
The only thing that seems to solve it briefly is restarting both my nest hubs (1x nest hub max and 1x nest hub gen 2)
Could this be the matter network going offline? (Hence the restart solves it) But then I'm not sure what causes the matter network to go offline.
02-22-2024 11:58 PM
This now has started to be on a nightly basis, the only thing that brings my matter devices back online is restarting my nest hub max and nest hub 2nd gen
04-23-2024 05:51 PM
Same. I have 4 of the motion sensors and they frequently go offline. Sometimes it's all of them, and sometime just a few. It seems to have become a more frequent problem.
06-18-2024 04:56 AM
This is still a problem in 06/18/2024. I have Nest wifi so what works for me is just doing a soft restart on the network, but this is rough.
Google, please fix this!
09-16-2024 09:53 AM
This problem is still happening to me September 2024. Google Home matter network is not reliable.
10-06-2024 02:05 AM
This also happens to me (Oct 6, 2024). My eve motion sensors are all working, but they appear as offline in the Google Home app.
11-29-2024 01:54 AM
Happens to me on a fairly regular basis with 3x Eve Energy plugs and a mixture of Nest Hub Mini 2's and Nest Minis - pairing to Google Home worked fine but the Eve's drop offline occasionally at random.
01-12-2025 08:17 AM
Same here, both on WiFi devices AND Matter devices. Using a Nest Hub 2nd gen as router.
01-29-2025 10:00 PM
This is driving me insane. I don't know if this an issue with the nest devices or the Eve motion sensors. And Google won't provide a way to schedule a reboot of these devices daily, because in their view, they're perfect. Matter was supposed to fix everything. Now it's just another pipedream.
01-30-2025 06:55 AM
I guess it's Google Nest fault, since it happens with various vendors, both on thread or on wi-fi.
03-07-2025 03:33 AM
I have and have had this same issue for months. I keep thinking it's placement of the router but other things work fine.
Just randomly things go offline and I have to unplug/plug in again. Automations become useless and I have to revert to the device app for operation until I do the power cycle or network reset
Seems as if Google needs a keep alive function. If a device isn't reporting, check back periodically or something. Beyond frustrated
So much for a "smart" home.
03-08-2025 11:01 AM
I echo this, and raised a ticket with the matter developers at google a couple of months ago. It seems to have become worse in that whenever there is a network change of any sort the connection gets lost. These network changes happen particularly frequently with Eero and other routers that seem to self-update more or less every other day, even if the assigned address (ipv6 and 4) from the ISP remains the same
I think what may be happening is that the there is a change of slaac address somewhere in the network after a reboot, either in the matter device, the hub controlling it or elsewhere. I suspect particularly that the nest hubs are not refreshing their cache of neighbour devices at a sensible frequency after acquiring a new address. I have found that disabling ipv6 on the router helps significantly; but downgrading network performance is hardly a good solution.
given that the devices remain online for all other ecosystems (tested with HA, Alexa, Apple, Chip-tool) I lay the blame firmly at Google dev's feet.
03-08-2025 12:16 PM
Won't disabling IPv6 disable Matter?
03-08-2025 12:36 PM
No. This is just disabling ipv6 on the router. Internal clients can still create their own link local addresses