MMatterhome

Sensors / Shelly

Shelly Flood S Gen4

Shelly Flood S Gen4 is a direct Matter-over-Wi-Fi flood sensor for Shelly-heavy homes. The safer expectation is Matter for the shared endpoint and Shelly for firmware, diagnostics, and any detailed device settings.

Matter over Wi-FiCompatibility guide
By Matterhome Editorial Team/Edited and fact-checked by JC Martinez
Shelly Flood S Gen4 product image

Direct Matter without a Shelly hub

Shelly Flood S Gen4 is listed by CSA as a Matter over Wi-Fi device. That makes the Matter path direct: it joins a Matter controller over Wi-Fi and does not need a Thread border router or a Shelly bridge for the Matter endpoint.

Setup path

Place and test the sensor before trusting the alert path. A flood sensor is only useful if the alert reaches the app or automation you expect.

Use Shelly's app or web interface for Wi-Fi onboarding, firmware, device settings, calibration, and any device detail that your Matter ecosystem does not expose cleanly.

What to verify

Matter should cover the common endpoint, but the valuable details can vary. For Shelly meters, plugs, and PM relays, verify wattage, energy totals, and reporting frequency. For flood and motor-control devices, test the exact alert or movement behavior before building routines around it.

Should you buy it?

Buy Flood S Gen4 when the physical format fits the job and you want a direct Wi-Fi Matter path. Skip it if you need every Shelly app feature to appear identically in Apple Home, Google Home, Alexa, SmartThings, and Home Assistant.

Best for

  • Water-risk spots where Wi-Fi is reliable
  • Shelly homes that want Matter-visible alerts
  • Buyers who will test alert behavior before trusting it

Skip if

  • Wi-Fi is weak at the leak-risk location
  • You need a professionally monitored safety system
  • Your ecosystem cannot use the alert state you need

Alternatives To Consider

Sources

Content feedback

Spot a mistake or missing context?

Send a quick note so it can be checked against the source material.

Report content issue