#Here is the log of the whole day i.e.

1 messages · Page 1 of 1 (latest)

orchid briar
#

Can you tell me what nodes 3 and 6 are in your setup ? The matter server is continuously trying to reach these devices and they do not seme to be responding

paper valve
#

I have no idea to be frank but I can check if you can tell me how to?

orchid briar
#

Within Home Assistant, go to settings --> Devices & integrations --> Matter --> devices

#

click a matter device and within "device info" you should see the node id

paper valve
orchid briar
#

I assume these are your only 2 nodes and they are in non-working state since the beginning ?

#

What I'd like to propose is to start fresh. Remove the Matter integration. Make sure the add-on is removed.
Then re-install the Matter integration. Reset the device(s) to factory defaults and then try to pair it to HA.
That should either succeed or get an error on which we can zoom in.

paper valve
#

Actually, same devices are working well from my Home app on iOS (That is where I had paired it). I will try and remove those devices and re-install Matter server again once I reach home in next 6-7 hours.

I won't be able to reset those devices as working without issue on Home app.

I will update this thread after the reinstallation of the server.

orchid briar
#

OK, in the case you dont want to reset the devices, please delete our fabric from the home app.
Go the Apple Home app, open the device details there.
Click "Connected services" - remove all occurances of "4939"

paper valve
paper valve
#

Ok I tried adding devices. First 2 attempts failed and then it worked. So I think the issue I realised is, when you try to pair, you have to select the nearby device first and then put the pair code. You can't simply put the pair code directly. This may be a bug as it works with just code on Home app.

Here is the log: https://pastebin.com/nLSqpGYB

paper valve
#

I added one more device but this time it failed but I noticed one strange thing, it tried to unsubscribe from Node 3 first.. not sure why (Can this be because, I may have selected wrong plug from the list of nearby plugs?) - Here is the whole log along with the last failure: https://pastebin.com/jd6dhPLF

paper valve
#

Sorry for bombarding you with messages. To clear my doubt, I waited for some time for all the nearby devices to disappear and turned on the pairing mode again. This time, it showed me one device but still got the same error. Updated log: https://pastebin.com/Zr8bzhmX

orchid briar
#

Ok, I kind of hoped you would do one device first to limit the info in the logs but okay this will work.

orchid briar
#

Am I correct in observing that you didnt test this with the latest BETA version ? Because we did fix 2 things that relate to issues you reported

paper valve
#

I just changed the settings to allow beta and tried again. No luck. I have set the log to display just the errors. Here is the log file: https://pastebin.com/4QFUCFnX

orchid briar
#

what device are you trying to commission ?

#

and did you first remove our fabric again (or reset the device) ?

#

some devices are afwul bad at handling multiple fabrics

paper valve
#

This was a fresh device so no fabric was added for it. So far, all the devices I have tried are same Sonoff MINIR4M switches connected to multiple rocket switches at home.

orchid briar
#

Is your phone connected to a 2,4 ghz wifi ?
I assume your HA server is connected over ethernet ? and your apple devices like homepods etc ?

paper valve
#

My phone is connected to 5GHz WiFi, it worked earlier with the same set. HA is via Ethernet port and HomePods via WiFi but Apple TV via Ethernet Port.

orchid briar
#

please connect your phone to a wifi that is capable of doing 2,4 ghz

#

because those credentials will be sent to the sonoff device

#

and that is 2,4 ghz only

#

and once that is done we do the next step

paper valve
#

Ok trying, I didn't have to do this while adding on Apple's Homekit so I didn't think of it. Give me few minutes, trying it out.

orchid briar
paper valve
orchid briar
#

discovery times out, so our matter server can not discover the device using mdns

#

so that means network related issue somehow

#

I have seen some wifi mesh systems blocking multicast traffic between wifi and ethernet

#

but let's start with the basics. You are running Home Assistant OS latest version, on what hardware ?

paper valve
#

I am on HA Green

orchid briar
#

is IPv6 enabled on your router ? And in the Home assistant network settings ?

orchid briar
paper valve
#

Yes IPV 6 enabled everywhere

orchid briar
#

Bit of a long short here, but did you try restarting the green fully ? like restart the whole entire system

#

Its super strange that the matter server cant find the device at all

paper valve
#

Let me restart, I haven't tried it.

orchid briar
#

In the meanwhile can you tell me a bit about your network ? what wifi, switches etc

paper valve
#

Sure one min

#

I have TP Link Deco XE75 setup, it's connected to ISP's router via LAN Cable and no one devices connect to ISP router. I have TP Link unmanaged switch to which HA Green's port is connected to. The same switch has connection to one of the deco AP too.

orchid briar
#

OK, you'd say that should work fine. I believe others have similar setups that reported it working. Can't harm to simply restart every network component just to rule out old routing tables or whatever. As Matter is completely IP based, most issues with it are network related.

paper valve
orchid briar
#

One thing to keep an eye on is maybe that special iot network from deco

#

not sure if you use that but it may not be fully matter compliant

paper valve
#

Yes I use spcial IOT for all the IOT devices as it gives me dedicated 2.4 GHz. I will try restarting whole deco system too - just to rule out router related issues.

orchid briar
orchid briar
paper valve
#

I will check the TP Link's config for iOT and see if it's blocking any IPV6 traffic. I think there is some bug in HA which is causing this otherwise,, I would face similar issue with HomeKit as well.

orchid briar
paper valve
#

Oh

#

I think it has something to do with Sonoff MINI4RMs. After rebooting the mesh system, some of the already paired devices on HomeKit are not responding. Strangely, this time, I was able to add another device in HA.

#

I will keep looking around or may be even try connecting these switches via SonoffLAN add on instead of Matter

orchid briar
#

I have one of those sonoff devices here somewhere, didnt have a chance to properly test them, can do that tomorrow.

#

It sounds like an issue with your network, maybe that IoT network is causing trouble.
Anyways, if adding the devices now works on HA, the devices may also come back again on apple home.

paper valve
#

Oh, I will check on TP link forums too. I will keep you updated on my findings. Thanks for helping out.

orchid briar
#

Please let us know if you may find something, that is helpful for others

paper valve
#

So I tried pairing Sonoff switch directly with the HA but that does not work either. It works flawlessly with Apple Home but switch controls work via cloud. The switches which get connected to HA, work locally and really really well. So if we find a way to solve this Chip error / connectivity issue, I guess, it can perform way better than Apple Homekit.

orchid briar
#

Yeah, we need to find out why your home network is blocking the matter traffic to your HA server. Th ebest thing I can think up is that special IoT network from TP Link. Maybe they're doing some fancy filtering on that. Is your main network both 2,4 Ghz and 5Ghz ? If so, you could try to commisison the device using that SSID, see if that helps

paper valve
#

My main network is on 2.4 and 5 both. To set those devices on main network, I will have to turn off 5 GHz on it. Let me try for couple of days and see what can be causing the problem.

orchid briar
#

oh well, that should not be needed. If your main network is both - you can just join it to that network

#

I do that all the time on my network, which is also 2,4 + 5

paper valve
#

I will try - it had not worked in the past.

paper valve
#

So I changed the WiFi of 2 switches to main one. HA was able to add it but again it stopped responding mid way but it does respond properly on Apple HomeKit. So I am assuming it may be issue with the way Sonoff is set to work. I am planning to get rid of this matter thing as it's not working as expected (may be device is the issue). So will try SonoffLAN and see if it can help in any way.

paper valve
#

I am trying one more thing now, I have deleted those devices from eWeLink app completely and setup fresh directly in the Home App. I will monitor this process, let's see.

paper valve
#

So after I configured switches directly to Apple's Homekit - they work flawlessly but in HA, it lost the connection multiple times. Also, I keep seeing way too many errors like these:

2024-03-09 14:21:32 (Dummy-2) CHIP_ERROR [chip.native.SC] CASESession timed out while waiting for a response from the peer. Current state was 4
2024-03-09 14:21:38 (Dummy-2) CHIP_ERROR [chip.native.SC] CASESession timed out while waiting for a response from the peer. Current state was 1

orchid briar
#

So that means that the connection is somehow disturbed between device and HA.
Unfortunately we have seen this before with some wifi (mesh) systems.

#

A small trick could be to connect HA wireless and see if that helps, at least to pinpoint the situation