next trail
Hello i need some help i have all of my light switches in the house that are connected to homeassistent with matter and one day they all went ofline and how when i try to reconnect then in getting this error. iv tryed almost everything i could think of and still cant get it to work. iv even installed Homeassistent os on a seperate machine and still the same error Hopefully someone can help
elfin copper
For me this seems like the device was discovered correctly nbut could then not be communicated with. So the first things are usial network troubleshootings and ensureing to use the right QR code and such.
next trail
thats the weard part is that it all worked flawlesly untill one day i rebooted my udm-pro and now i cant connect any of then back but the weard part is that my front door lock works just fine
next trail
For me this seems like the device was discovered correctly nbut could then not b...
im not very perfitiant at network side of thing but ill mess with it and fee what i can do
elfin copper
Sometimes commodity and consumer grade networking he is the best. So in your case I would say we need log. But honestly I do not start looking strongholds server logs because not likely to bring any benefit. With the beta server I know what’s up and how to read logs.
next trail
i updated to the new matter and this is what in getting
next trail
Sometimes commodity and consumer grade networking he is the best. So in your cas...
this is the log
and this is what i get while trying to reconnect a new switch
next trail
i even completely reintalled matter and this is what in getting now
elfin copper
Ok, for me it seems you either use wrong QR codes or your network has UDP/MDNS issues (no network segmentation in any form?)
The first image above that tells "Operative reconnection failed" means that we were able to do the normal commissioning with the device and installed all certificates. After this the device announces itself via MDNS with it's operational announcement and we then finish the commisioning. But exactly this operative announcement is missed.
The second image means that we were searching your network for commissionable devices (without any specific code criteria, just plain "any commisisonable") but there was no device that was announcing itself. If the device is really unpaired and you did not enabled BLE for the server then yes this could be the reason because BLE was not used to scan.
Your first logfile shows the startup of your matter server with one node. this node has an IP and also announces itself correctly operationally and can be connected and controlled. all fine. no errors visible.
The second logfile shows a connection try with a PIN and a given IP, and is basically like I said above: Commissioning works, but device never shows up with it's operational announcement.
So the interesting question is why the operational announcements are misisng
next trail
mDNS enabled on the network and when I go to pair the device to home Assistant if finds it on the app connects to it connects to the network but then when it tries to connect it to home Assistant it fails