Since alpha.28 google home often cannot control devices and is often offline

datvista commented 1 day ago

Since alpha.28 google home often cannot control devices and is often offline Screenshot_20241113-072437

datvista commented 1 day ago

logs-3.txt

datvista commented 1 day ago

Use CPU a lot logs-4.txt

Apollon77 commented 20 hours ago

Ok some notes: 1.) Try to limit MDNS to one network interface because as you can see in the logs you announce and also listen on 17 network interfaces. This costs time, performance and can also be error prone as soon as one of the interfaces act weird. What can happen from time to tome 2.) I see 13 different bridges in that log? Do you really offer 13 bridges? Interesting mass scenario. SO would be interesting what "CPU a lot" exactly means ... especially also when the nodejs process reaches 80-90% or even more then it could really be that it is too much

All logs with "Resubmit message" means that we submitted a message but did not got any response ...
"Error while sending initial data reports NoResponseTimeoutError" means that there was an error on initially setting up a subscription ... so likely the hub or network was not available?
But also resubscription works as log shows, but sure if really 13 resubscriptions come in kind of in parallel this uses a lot CPU punctually because in fact it needs to collect all the data - and I assume you have some Alexa devices right or multiple ecosystems paired? Because I also see parallel subscriptions on the "same device" ...

In the end the logs are still "too short and punctual" to really really analyze issues here, so my summary:

13 devices in one process that gets announced
many parallel resubscriptions
some messages seems to not reach the target or hubs are not responding or such ... thats why they send messages multiple times but also still do not seems to get the response The main device that is "strange" is fd83:e39e:a75b:12e2:d415:250d:fc73:da7d ... this one opens new connects, does a subscription but then when the first data package is sent out it does not seems to get the response at all and this then ends in a loop ... so basically maybe really try to decide for one network interface

datvista commented 20 hours ago

But why is my google home still relatively stable with alpha 27?

Apollon77 commented 20 hours ago

@t0bst4r What were the changes between 27 and 28?

Apollon77 commented 20 hours ago

Maybe share a comparism log from start on for some minutes with 27 and 28

011V32 commented 13 hours ago

What were the changes between 27 and 28?

https://github.com/t0bst4r/home-assistant-matter-hub/compare/v3.0.0-alpha.27...v3.0.0-alpha.28

t0bst4r / home-assistant-matter-hub

Since alpha.28 google home often cannot control devices and is often offline #128