[APP][Pro] Shelly Neo Smart Water Valve - Lightning-fast Local Control, Live Telemetry & Native Energy Integration

Apps
, , , ,
1

[APP][Pro] Shelly Neo Smart Water Valve

Lightning-Fast Local Control, Live Telemetry & Native Energy Integration

Hello Homey Community! :waving_hand:

I have just released the initial test version of the Shelly Neo Smart Water Valve app for Homey Pro.

This app adds local network support for the Shelly-powered Neo Smart Water Valve (NAS-WV02W) to your Homey ecosystem.

[!NOTE]
Credits & Inspiration:
While designing and writing this app, I was greatly inspired by the excellent structure and MQTT telemetry approach used in the WS90 Weather (MQTT) app by Roger Florén. A huge thanks to him for demonstrating how clean MQTT integrations can be in Homey!

:rocket: Get the App (Test Channel)

You can install and start testing the initial release right now via the test link:
:backhand_index_pointing_right: Install Shelly Neo Smart Water Valve (Test)

:high_voltage: The Core Advantage: 100% Local-First & Cloud-Free!

Traditional smart valves often rely on sluggish, internet-dependent cloud integrations. When it comes to home security and leak prevention, every millisecond counts!
This app bypasses the cloud entirely:

  • Instant Control via HTTP RPC: Toggle your water main valve directly in Homey or via Flows. Commands are sent locally over HTTP and execute in milliseconds—even if your internet connection is down.
  • Instant Telemetry via MQTT: The valve pushes sensor updates (pressure, flow, temperature) asynchronously to a local MQTT broker, updating Homey immediately without constant, heavy polling.

:droplet: :bar_chart: Native Homey Energy Integration!

One of the most premium features of this app is its seamless integration with Homey’s native Energy and Water monitoring tab!

[!IMPORTANT]
Track Your Water Footprint & Usage History!
The app reads the cumulative water consumption sensor from your valve and maps it directly to Homey’s native meter_water capability.

  • Automatic Energy Dashboard Integration: Your water usage is recorded and plotted automatically under Homey’s built-in Energy tab.
  • Historical Usage Charts: Visualize your water consumption over hours, days, weeks, or months with Homey’s clean, native interactive bar charts.
  • No Setup Needed: Add the device, and Homey instantly begins tracking your water footprint!

:hammer_and_wrench: Key Capabilities & Monitored Sensors

  • Valve Control: Fast, reliable open/close toggle.
  • Current Water Flow Rate: Live monitoring of flow velocity (L/min) to detect active usage.
  • Water Pressure: Live pressure monitoring, automatically converted from kPa to mbar for perfect standard compatibility.
  • Water Temperature: Monitor the temperature of your water main in Celsius (°C), perfect for freeze warnings!
  • Water Consumption: Track total liters consumed.

:locked: Advanced Flow Cards (Automation)

We have introduced dedicated Flow cards to let you build powerful home security automations:

  • Triggers (WHEN):
    • Valve was opened / closed
    • Water started / stopped flowing
    • Water pressure exceeded a threshold (e.g., Surge protection)
    • Water temperature exceeded a threshold (e.g., Freeze warning)
  • Conditions (AND):
    • Valve is open / closed
    • Water is / is not flowing
    • Water pressure is above / below a threshold
    • Water temperature is above / below a threshold
  • Actions (THEN):
    • Open / Close the valve

Automation Example: Protect your home by automatically shutting off the main water valve the millisecond a flood sensor (like Shelly Flood or Aqara) detects water, and get alerted if the water pressure surges dangerously.

:gear: Quick Installation Guide

  1. MQTT Broker: Ensure you have a local MQTT broker on your network (we highly recommend installing the MQTT Server and MQTT Client apps on your Homey Pro).
  2. Valve Setup: Access your Neo Smart Valve’s local web UI by typing its IP address into a web browser. Go to MQTT Settings, enable it, and point it to your Homey’s IP address.
  3. Add to Homey: Go to the Homey app, click Add Device, search for Shelly Neo Smart Water Valve, enter your device’s local IP address and MQTT status topic (default: shelly/valve/status), and you are good to go!

Feedback, feature requests, and bug reports are welcome in this thread! Let me know how the app is performing in your smart home.

Happy automating! :droplet::shield:

2

Local web interface not reachable on my unit — HTTP RPC control blocked (model S3XT-0S)

Hi, thanks for building this app. I’m trying to set it up but I’m stuck at step 4 of your setup guide, and I suspect it may be a hardware or firmware variant issue rather than something on my network.

My device:

  • Device Type: Neo Smart Water Valve
  • Device Model: S3XT-0S
  • Firmware: 20250602-061842/1.7.99-xt-prod0-gf2d5965 (the Shelly app reports this as the latest — “Your device is up to date”)
  • Device IP: 192.168.20.88, Homey Pro on 192.168.20.104 — same subnet, no routing or firewall between them

What I’m seeing:

The valve does not expose a reachable local web interface. Specifically:

  • ICMP is dropped (no ping response), but the ARP entry on the router is complete (DC flag), so the device is reachable at layer 2 and is clearly online and transmitting.
  • TCP port 80 returns connection timeout, not connection refused — tested from the router itself, on the same VLAN as the valve:
/tool fetch url="http://192.168.20.88/rpc/Shelly.GetDeviceInfo"
failure: connection timeout
  • So I cannot open the valve’s IP in a browser, which means I cannot reach the MQTT settings the way your guide describes in steps 4 and 5.

I can configure MQTT from the Shelly Smart Control app instead — under Networks it offers MQTT, RPC over UDP, Outbound websocket and Cloud — so the telemetry side should be solvable that way.

My questions:

  1. Which model string and firmware version does your valve run? I’m wondering whether there are hardware revisions with different local API behaviour.
  2. Did you have to enable anything specific to get the local web interface / HTTP RPC working, or was it available out of the box?
  3. Your app uses local HTTP RPC for valve open/close. If port 80 stays closed on my unit, the THEN Flow cards (Turn on / Turn off / Toggle) will fail even with MQTT telemetry working correctly. Would you consider adding RPC over MQTT as a fallback control channel? The device exposes the standard Shelly RPC topics (<id>/rpc for requests, <src>/rpc for responses), so RPC calls should be possible over the broker without needing port 80 at all.

I’ll follow up with the output of Shelly.ListMethods once I have MQTT running, in case it’s useful for adding an MQTT-based control fallback.

Happy to run any diagnostics on my unit if that helps. Thanks.

3

Hi Zoltan,

Thank you very much for the detailed feedback and for taking the time to document all your findings and tests.

I’m currently on vacation and away from my development setup, and I’ll be back in about two weeks. Once I’m back, I’ll take a closer look at the S3XT-0S variant, the HTTP RPC behavior you described, and the possibility of adding RPC over MQTT as a fallback control method.

Your detailed diagnostics will definitely be helpful when I start investigating this.

Thanks again for testing the app and for your patience. I’ll get back to this as soon as I return.