Skip to main content

Local Web Server

Mains-powered Aqua-Scope WiFi devices feature an integrated HTTP web server that is directly accessible on the local network. It allows you to query sensor data, change configurations, control valves, and perform diagnostics — without cloud, without app, directly via browser or HTTP client.

Prerequisites​

  • WiFi device with mains power (not available on battery power)
  • Device and client on the same local network

Enabling the Web Server​

Factory Default State​

The web server is always active in factory default mode. During initial setup, it can be configured to remain permanently enabled.

Later via the App​

  1. Open the Aqua-Scope App
  2. Select the device
  3. Navigate to Configuration → Communication Options
  4. Enable Local Web Server

Access​

The web server is accessible via the device's local IP address or via mDNS:

  • http://<IP-address> (e.g., http://192.168.1.42)
  • http://scope.local (via mDNS, if only one device is on the network)

Pages and Endpoints​

Web Interface (Browser)​

URLDescription
/Home page — shows the home page (when WiFi is configured) or the setup page (in factory default state)
/homeHome page with device overview and sensor data
/setupWiFi configuration page (SSID, password, email, communication options)
/commandShell console for device diagnostics

Data API (JSON)​

URLMethodDescription
/dataGETAll current sensor values as JSON including device ID (eid)
/jsonGETSensor data in JSON format
/cdata.jsGETSensor data as JavaScript object (for web interface)
/connGETConnection status as JSON

Example: Retrieving Sensor Data​

curl http://192.168.1.42/data
{
  "temperature": "22.5",
  "pressure": "3200",
  "uptime": "86400",
  "battery": "3.3",
  "eid": "12345678"
}

The available fields vary depending on the device type.

Valve Control​

URLMethodDescription
/control?valve=<value>&token=<token>GETControl valve

Parameters:

ParameterDescription
valve0 or off = close, 100 or on = open
tokenSecurity token (must match the token stored in the configuration)

Examples:

# Close valve
curl "http://192.168.1.42/control?valve=off&token=my-token"

# Open valve
curl "http://192.168.1.42/control?valve=on&token=my-token"

# Open valve with numeric value
curl "http://192.168.1.42/control?valve=100&token=my-token"
Security

Valve control requires a valid token. Without the correct token, the command is rejected. The token is set during the webhook configuration (see JSON Webhook).

Configuration​

URLMethodDescription
/configGET/POSTRead and modify device configuration

The following settings can be changed via this endpoint:

ParameterFieldDescription
ssiWiFi SSIDWiFi network name
wpaWiFi PasswordWPA2 key
emaEmailRegistration email
mqtMQTTEnable MQTT service
mseMQTT ServerBroker hostname
mpoMQTT PortBroker port
musMQTT LoginUsername
mpaMQTT PasswordPassword
mdiMQTT DiscoveryEnable Home Assistant auto-discovery
mtlMQTT TLSEnable TLS encryption
jenJSON WebhookEnable webhook service
jurJSON URLWebhook target URL
jtoJSON TokenSecurity token
jexJSON XXTEAEnable XXTEA encryption
jraJSON RawEnable raw data transmission
lwsLocal Web ServerKeep web server enabled
bleBluetoothEnable Bluetooth
mbiModbus IPEnable Modbus TCP/IP
facFactory ResetSet to 1 for factory reset

Shell / Diagnostics​

URLMethodDescription
/shellPOSTExecute shell command (field: shell)
/consoleGETRetrieve console log

The shell accepts AT commands and diagnostic commands via HTTP POST.

# Query firmware version
curl -X POST -d "shell=AT+VER=?" http://192.168.1.42/shell

# Retrieve console log
curl http://192.168.1.42/console

Integration into Automation​

The local web server is suitable for direct integration into smart home systems without cloud dependency:

  • Home Assistant: Via the REST integration, /data and /control can be connected
  • Node-RED: HTTP request nodes for sensor queries and valve control
  • Shell scripts: Simple querying and control via curl

Supported Devices​

The local web server is available on all WiFi devices with mains power: