---
title: "W5500 and matter protocol are not compatible?"
url: "https://maker.wiznet.io/forum/15871"
markdown_url: "https://maker.wiznet.io/forum/15871/md"
type: "Forum topic"
category: "IO Modules"
author: "giulioto"
created: "2025-09-11T03:54:31+09:00"
last_activity: "2025-09-15T17:12:00+09:00"
language: "en"
tags: ["W5500", "Arduino IDE"]
views: 3
replies: 1
source: "WIZnet Makers forum (https://maker.wiznet.io/forum/)"
---

# W5500 and matter protocol are not compatible?

## Question

Asked by giulioto on 2025-09-11 in IO Modules.

Hi,

I'm using W5500 with esp32 (IDE Arduino, ethernet library) and matter library on my iot device.

The commissioning with Home Assistant is ok, i can manage my device normally.

Also after poweroff-poweron for a few seconds the device is available on Home Assistant.

But if i poweroff the device for over 2 minutes and Home Assistant detect the device as unavailable, after poweron the device don't reconnect to Home Assistant. I must decommission and recommission the device if i want to see it on Home Assistant.

From Home Assistant, the device responds to ping even if it is not visible via matter.

If i use wifi instead W5500 ethernet shield, the device reconnect normally and the problem does not occur.

Does anyone know of any bugs on the w5500 and Matter?

Thanks

## Replies

### Reply 1 by Hannah, 2025-09-15

Hello,
I’m not a Matter expert, so my answer may be limited. However, based on the AI’s suggestions, I recommend checking the following areas that often cause issues:

1. Use Wireshark capture to verify whether the device is actually sending mDNS/DNS-SD advertisements after boot.

2. Check the DHCP/IPv6 state.

- Note the difference compared to Wi-Fi: Wi-Fi stacks usually handle IP renewals and service re-announcements automatically, but with the W5500 this must be handled explicitly in the MCU firmware.

Confirming these two points first should help narrow down the root cause.

---

Source: https://maker.wiznet.io/forum/15871