Firmware 2.2.1(5) API Reference [Aug 1, 2026]

Introduction

Overview

• Authentication (pw): All API calls require the device password via the pw parameter. The value must be provided as a lowercase MD5 hash. The OpenSprinkler app and web interfaces handle this hashing automatically. If you are making direct API calls, you must hash your plaintext password before sending the request. You can use any standard MD5 generation tool for this.
• Device IP: Throughout this document, os-ip denotes the controller's IP address or hostname.
• Command Parameters: Parameters can be sent in any order. You do NOT need to include every parameter in a request - any omitted parameter will retain its current value on the device.
• Return values are all formatted in JSON, for example: {"fwv":221}, {"result":1}. Below is the list of error codes:

Code	Meaning
1	Success
2	Unauthorized (missing device password or device password is incorrect)
3	Mismatch (new password and confirmation password do not match)
16	Data Missing (missing required parameters)
17	Out of Range (value exceeds the acceptable range)
18	Data Format Error (provided data does not match required format)
19	RF code Error (RF code does not match required format)
32	Page Not Found (page not found or requested file missing)
48	Not Permitted (e.g. cannot operate on the requested station)
64	Upload failed (e.g. OTA firmware update failed)

---

Changes in Firmware 2.2.1(5)

• Supported Hardware: Firmware 2.2.1(5) runs only on OpenSprinkler v3.x (ESP8266) and OSPi/Linux. Earlier controllers (OpenSprinkler v2.3 and older) are no longer supported.
• Expanded Sensors: New endpoints manage Expanded Sensors, their readings, metadata, and logs: /jsn, /csn, /dsn, /jsd, /jsl, and /dsl. Sensor readings can scale program water times through the sensor adjustment curves; see /jpa. For analog sensor hardware and setup, see the Sensor Expander documentation.
• Sensor Terminology:
  • Built-in Sensors refer to sensor ports on the main controller, identified by SN1–SN4. They support digital sensors such as rain, flow, and program switch.
  • Expanded Sensors are configurable sensors managed through the Expanded Sensor API. They support analog sensors connected to the external Sensor Expander and virtual sensors such as Aggregate and System Internal sensors.
• Extended Master Support: The firmware now supports up to four master stations. /jo exposes the additional master options, /jn returns the Master 3 and Master 4 binding attributes, and /cs can modify those bindings.
• Built-in Sensors SN3 and SN4: OpenSprinkler v3.4 supports up to four Built-in Sensors, extending the previous SN1/SN2 support to SN3/SN4. The additional sensors are exposed through /jo (options) and /jc (status), with per-station ignore attributes returned by /jn and modified through /cs.
• Extended Effective Runtimes: Weather- and sensor-adjusted station runtimes may now exceed the 18-hour (64800-second) limit. While programmed water times are still limited to 18 hours, after scaling by weather or sensor adjustment, the resulting water time is allowed to exceed this limit.

In the following, new changes since the last firmware are highlighted in green like here.

---

Controller Status & Configuration

Get Controller Variables /jc

Usage: http://os-ip/jc?pw=xxx

Variable	Explanation
devt	Device time in Unix epoch seconds (local time, adjusted to the device’s time zone).
nbrd	Number of 8-station groups/boards, including the main controller.
en	Operation enable bit (1: enabled; 0: disabled).
sn1	Built-in Sensor SN1 status (1: active; 0: inactive).
sn2	Built-in Sensor SN2 status (OS v3.x and OSPi only).
sn3/4	Built-in Sensor SN3/SN4 status (1: active; 0: inactive). Available on OpenSprinkler v3.4+.
rd	Rain delay flag (1: manual rain delay active; 0: not active).
rdst	Rain delay stop time (epoch seconds); 0: rain delay is not in effect.
sunrise	Today’s sunrise time, number of minutes since midnight.
sunset	Today’s sunset time, number of minutes since midnight.
eip	External IPv4, as a 32-bit integer: (ip[3]<<24)+(ip[2]<<16)+(ip[1]<<8)+ip[0].
lwc	Timestamp (epoch seconds) of the last weather request.
lswc	Timestamp (epoch seconds) of the last weather response. 0 means no successful response yet.
lupt	Timestamp of the most recent device reboot (epoch seconds).
lrbtc	Cause code for the last reboot (see Reboot Cause Codes).
lrun	Last completed station run: [station, pid, duration, end]. station is 0-based; pid is the 1-based program index, with special value 99 indicating a manual run and 254 a run-once program. duration is the actual elapsed runtime in seconds and may exceed 65535 after weather or sensor adjustment; end is the completion time in epoch seconds.
RSSI	Wi-Fi signal strength (dBm, OS 3.x only).
mac	Hardware MAC address.
loc	GPS coordinates of the device location.
jsp	JavaScript URL. Default: https://ui.opensprinkler.com/js
wsp	Weather script URL. Default: weather.opensprinkler.com
wto	JSON object containing weather adjustment options; fields depend on the selected adjustment method.
wtdata	JSON object containing raw data relayed from the weather server; used to compute watering percentage.
wterr	Error code from the last weather server response (see Weather Error Codes).
ifkey	IFTTT Webhooks key (enables IFTTT notifications).
mqtt	JSON object containing MQTT configuration parameters.
curr	Total current draw across all zones (mA). Available only on controllers with current sensing capability.
sbits	Station status bits. An array where each byte is an LSB bitfield for an 8-station group. Example: 2 (0b00000010) → 2nd station is open; 192 (0b11000000) → 7th and 8th stations are open.
ps	Program status array with one [pid, rem, start, gid] entry per station. pid is 0 when idle, normally the 1-based program index, 99 for a manual run, or 254 for a run-once program. rem: the remaining runtime; start: the scheduled start time; gid: the sequential group ID. If the corresponding sbit=0 while pid!=0, the station is queued but not running.
flwrt	Flow-sensor count window (seconds). This value is firmware-dependent and is NOT the flow sampling rate. Instead flcrt/flwrt gives the flow rate (clicks per second).
flcrt	Flow-sensor count (windowed): number of clicks during the last flwrt secs.
flcto	Flow count (total): cumulative flow-sensor clicks since power-on (reset on reboot).
pq	Pause state (0: inactive; 1: active).
pt	Countdown timer for an active pause (seconds).
nq	Number of elements in the program queue (zones running or waiting).
otc	JSON object containing OpenThings Cloud (OTC) configuration parameters.
otcs	OTC connection status (0: not enabled; 1: connecting; 2: disconnected; 3: connected).
dname	Device name (included in notification messages to identify the controller).
gpio	Array of spare/free GPIO pins (usable for GPIO stations).
email	JSON object containing email notification settings.
ocs	Overcurrent status. 0: none; 255: system-wide overcurrent; any other value is the one-based station number that triggered the overcurrent condition. Unlike regular API station indices, this value starts at 1.
wtrestr	Weather restriction status (0: inactive; 1: active).
wls	Array of current multi-day average watering levels. Length depends on provider (e.g., Apple up to 10 days; others may support fewer).
apdv	Active/Actual USB-PD voltage in decivolts; divide by 10 to obtain volts (for example, 90 means 9.0 V). Read-only, for DC-powered OS v3.4.

---

Change Controller Variables /cv

Usage: http://os-ip/cv?pw=xxx&rsn=x&rrsn=x&rbt=x&en=x&rd=x&re=x&update=x&ap=x&rocs=x

Parameter	Meaning
rsn	Reset all stations (both running and queued). 1 triggers the reset; 0: no effect.
rrsn	Reset all running stations (but not queued ones). 1 triggers the reset.
rbt	Reboot the controller. 1 triggers the reboot.
en	Enable/disable operation. 1: enable; 0: disable. The setting is saved and persists across reboot.
rd	Set rain delay (hours). Range: 0–32767. 0 clears any active rain delay.
re	Set Remote Extension mode. 1: enable; 0: disable. The setting is saved and persists across reboot. In Remote Extension mode, the controller does not run its own programs or perform weather queries; it passively receives station commands from the master controller.
ap	Reset to AP mode for Wi-Fi reconfiguration without erasing settings/programs. Effective on OS 3.x only.
update	Trigger firmware update (OSPi/Linux only).
rocs	Clear overcurrent status (ocs). 1: clears.

Examples:

• http://os-ip/cv?pw=xxx&rbt=1: reboot controller
• http://os-ip/cv?pw=xxx&en=0: disable operation
• http://os-ip/cv?pw=xxx&rd=24: set a 24-hour rain delay

---

Get Options /jo

Usage: http://os-ip/jo?pw=xxx

Note: options marked RO are read-only and not modifiable via the /co command

Variable	Explanation
fwv	Firmware version (e.g., 221 → v2.2.1). RO
fwm	Firmware build number. RO
tz	Time zone (offset_hours*4+48). Examples: GMT+0→48; GMT−4→32; GMT+9:30→86. The value must be between 0–108.
dhcp	Use DHCP (1: yes, 0: no).
ip{1,2,3,4}	Static IP (ignored if dhcp=1).
gw{1,2,3,4}	Gateway (router) IP (ignored if dhcp=1).
dns{1,2,3,4}	DNS server IP (ignored if dhcp=1).
subn{1,2,3,4}	Subnet mask (ignored if dhcp=1).
ntp	Use NTP sync (1: yes, 0: no).
ntp{1,2,3,4}	Custom NTP server IP (ignored if ntp=0).
hp{0,1}	The lower and upper bytes of HTTP port: http_port=(hp1<<8)+hp0.
hwv	Hardware version. RO
hwt	Hardware type (172 / 0xAC: AC-powered; 220 / 0xDC: DC-powered; 26 / 0x1A: Latch). RO
ext	Configured number of 8-zone expansion groups (excluding the main controller). A physical 16-zone Zone Expander counts as two groups.
sdt	Station delay time (seconds). Range [-600, 600] (i.e. [-10, 10] minutes), in increments / step of 5 seconds.
mas?	Master station 1–4, specified as a 1-based station number (0: none). ? is empty for Master 1 (legacy naming), or 2, 3, or 4 for the corresponding master.
mton?	Master ON time adjustment in seconds. Uses the same ? suffix as mas?. Range [-600, 600], step 5.
mtof?	Master OFF time adjustment in seconds. Uses the same ? suffix as mas?. Range [-600, 600], step 5.
sn?t	Built-in Sensor type, where ? is 1–4. Value: 0: none, 1: rain, 2: flow, 3: soil, 240: program switch. Flow (2) is valid only for sn1t; SN3/SN4 are available on OpenSprinkler v3.4+.
sn?o	Sensor option. 0: normally closed; 1: normally open (default). ? is 1-4, the same as sn?t.
sn?on/sn?of	Sensor activation / deactivation delay in minutes. These delays apply only to rain and soil sensors. ? is 1-4, the same as sn?t.
wl	Water level (% watering). Range 0–250.
den	Operation enable bit. To change, you must use the /cv command.
ipas	Ignore password. 1: ignore; 0: do not ignore.
devid	Device ID.
dim	LCD dimming level (0: display off when idle).
bst	Boost time (milliseconds) for DC-powered & Latch controllers. Range 0–1000, step size 4.
uwt	Weather adjustment method. 0: Manual; 1: Zimmerman; 2: Auto Rain Delay; 3: ETo; 4: Monthly. NOTE: Previously uwt.bit[7] flagged California water restriction; that bit is no longer used: instead, water restriction is indicated in the wto (weather options) variable.
lg	Enable logging (1: on, 0: off).
fpr{0,1}	Flow pulse rate (scaled by 100), calculated as ((fpr1<<8)+fpr0)/100.0.
re	Remote extension mode. To change, you must use the /cv command.
dexp/mexp	Detected / maximum supported numbers of 8-zone expansion groups, excluding the main controller. A physical 16-zone Zone Expander counts as two groups; dexp=-1 means expansion hardware cannot be auto-detected. RO
sar	Special-station auto-refresh. When 1, special (e.g. RF, Remote IP/OTC, HTTP) stations automatically refresh to remain synchronized with the main controller. Enable this for Remote IP/OTC program runtimes over 18 hours because each forwarded /cm timer remains capped at 18 hours for compatibility.
fwire	Force wired connection (OS 3.x only). 1: stay wired; 0: allow Wi-Fi.
ife	Notification event enable bits. A bit field: • b0: Program scheduled • b1: Built-in Sensor SN1 update • b2: Flow sensor status update • b3: Weather update (e.g. water level change, eip change) • b4: Reboot • b5: Station finish • b6: Built-in Sensor SN2 update • b7: Rain delay update
ife2	Extended notification bits: • b0: Station start • b1: Flow alert • b2: Current alert • b3: Built-in Sensor SN3 update • b4: Built-in Sensor SN4 update.
imin	Undercurrent threshold in mA, in increments of 10 mA.
imax	Overcurrent threshold in mA, in increments of 10 mA. 0: system default; 2550: disabled.
tpdv	Target USB-PD voltage (in decivolts) for DC-powered OS v3.4+. Example: tpdv=78→7.8 V.

---

Change Options /co

Usage: http://os-ip/co?pw=xxx&[opn]=[opv]&loc=x&wto=x&ifkey=x&ttt=x
&otc=x&dname=x&mqtt=x&email=x

Parameter	Meaning
[opn]	Option name to modify (see the options list above). RO fields cannot be changed. You can include multiple option changes in one call (e.g., &tz=32&dhcp=1).
[opv]	New value to be assigned to [opn].
loc	Location string (URL-encoded). Accepts "city,state", ZIP code, or "lat,lon". When you use the UI/app to set the location, it always converts it to GPS.
wto	Weather options as URL-encoded JSON without the outer {}. Fields depend on the selected method (e.g., Zimmerman has six parameters for the weights and baselines of temp t, humidity h, and rain r).
ifkey	IFTTT Webhooks key.
ttt	Set device time manually (epoch seconds). Ignored if ntp=1
otc	OpenThings Cloud (OTC) configuration as JSON without the outer {}. Example: otc="en":1,"token":"token","server":"ws.cloud.openthings.io","port":80
mqtt	MQTT configuration as JSON without the outer {}. Example: mqtt="en":1,"host":"x","port":1883,"pubt":"opensprinkler","subt":""
email	Email configuration as JSON without the outer {}. Example: email="en":1,"host":"x","port":465,"user":"a@b.io","pass":"","recipient":""
dname	Device name.

Examples:

• os-ip/co?pw=xxx&loc=42.01,-75.22: change location to GPS coord 42.01,-75.22
• os-ip/co?pw=xxx&hp0=144&hp1=31: change HTTP port to 8080 (31*256+144=8080)
• os-ip/co?pw=xxx&sdt=30: set station delay time to 30 seconds
• os-ip/co?pw=xxx&sn1t=1&sn1o=1: configure Built-in Sensor SN1 as a normally-open rain sensor

---

Set Device Password /sp

Usage: http://os-ip/sp?pw=xxx&npw=xxx&cpw=xxx

Parameter	Meaning
npw	MD5 hash of the new password.
cpw	Repeat the same MD5 hash for confirmation.

Examples:

• os-ip/sp?pw=xxx&npw=e0ff85143dfa717536cbb668cc8f8e8b&cpw=e0ff85143dfa717536cbb668cc8f8e8b: change password to the MD5 hash of the plaintext password sprinkler.
• If either npw or cpw is omitted, Data Missing error is returned. If npw and cpw do not match, a Mismatch error is returned. Refer to the list of error codes.

---

Change UI and Weather URLs /cu

Usage: http://os-ip/cu?pw=xxx&jsp=xxx&wsp=xxx

• jsp: UI source URL (URL-encoded)
• wsp: Weather server URL (URL-encoded)

Example:

• os-ip/cu?pw=xxx&jsp=https%3A%2F%2Fui.opensprinkler.com%2Fjs: set the UI source URL to https://ui.opensprinkler.com/js.

The two URLs are saved across reboots and can be changed independently; an omitted parameter remains unchanged. On success, /cu returns an HTML response that redirects the browser to the controller home page.

---

Stations & Manual Control

Get Station Names and Attributes /jn

Usage: http://os-ip/jn?pw=xxx

Variable	Explanation
snames	Array of station names (length equals number of zones).
maxlen	Maximum characters allowed per station name.
stn_grp	Sequential group ID for each zone. Value: 0–3 identifies a sequential groups (A, B, C, or D); 255 is the parallel group P.
masop?	Master 1–4 operation bitfields. ? is empty for Master 1, or 2, 3, or 4 for the corresponding master. Each array byte represents one 8-zone group, with its least-significant bit corresponding to the first zone in that group. A set bit means the zone activates that master. For example, 254 (0b11111110) assigns every zone except the first to the master.
ignore_rain	Rain-delay ignore bitfields, using the same 8-zone-group layout. A set bit means the zone ignores rain delay.
ignore_sn?	Sensor SN1–SN4 ignore bitfields, using the same 8-zone-group layout. ? is 1-4; a set bit means the zone ignores that sensor. ignore_sn3 and ignore_sn4 are available only on OpenSprinkler v3.4+.
stn_dis	Zone-disable bitfields. A set bit means the zone is disabled.
stn_spe	Special-station bitfields. A set bit means the zone is configured as a special station.

OpenSprinkler v3.4 example: {"masop":[255],"masop2":[0],"masop3":[0],"masop4":[0],"ignore_rain":[0],"ignore_sn1":[0],"ignore_sn2":[0],"ignore_sn3":[0],"ignore_sn4":[0],"stn_dis":[0],"stn_spe":[0],"stn_grp":[0,0,0,1,0,0,0,0],"snames":["S01","S02","S03","S04","S05","S06","S07","S08"],"maxlen":32}

---

Get Special Station Data /je

Usage: http://os-ip/je?pw=xxx

Response Format: {"0":{"st":xxx, "sd":"xxx"}, "1":{"st":xxx, "sd":"xxx"}, ...}
Only stations whose stn_spe bit is set appear.

Key	Meaning
station_id	Object key containing the 0-based station index as a string (for example, "0" or "1").
st	Special-station type code (see table below).
sd	Type-specific data payload associated with st.

Station Types:

st	Type	Format of sd
0	Standard	Should not appear here, as only special stations are listed.
1	RF (Radio Frequency)	Either a legacy 16-character RF hexadecimal code (protocol 1, 24 bits), or a 25-character extended code prefixed with H that supports other protocols and bit lengths.
2	Remote (IP)	14-character hexadecimal string: 8 characters for the IPv4 address, 4 for the port, and 2 for the 0-based station index.
3	GPIO	3-character string: 2 digits for the GPIO pin number, and 1 digit for the active state (1 or 0).
4	HTTP	Comma-separated string (up to 275 characters) formatted as: server,port,on_cmd,off_cmd. Assume server is HTTP.
5	HTTPS	Same format as st=4. Assume server is HTTPS.
6	Remote (OTC)	35-character fixed-width string: 32 characters for the OTC token, 1 reserved character, then 2 hexadecimal characters for the 0-based station index.

Example: {"0":{"st":2,"sd":"c0a80093005002"},"1":{"st":1,"sd":"05331305333C0021"},
"2":{"st":4,"sd":"demo.opensprinkler.com,80,on/?z=1,off"}}

---

Change Station Names and Attributes /cs

Usage: http://os-ip/cs?pw=xxx&s?=x&m?=x&n?=x&u?=x&v?=x&i?=x&j?=x&k?=x&o?=x&r?=x&d?=x&p?=x&g?=x&sid=xx&st=xx&sd=xx

Parameter	Meaning
s?	Station name: ? is the 0-based station index. Example: s2=Front%20Lawn sets the third station to Front Lawn. Max length is maxlen from /jn.
m?/n?/ u?/v?	Master 1/2/3/4 operation bitfields, respectively. ? is the 0-based 8-zone-group index: 0 covers zones 1–8, 1 covers zones 9–16, and so on. For example, m0=255 assigns all zones in the main group to Master 1, while u1=4 assigns zone 11 to Master 3. See masop? under /jn.
i?	ignore_rain bitfields.
j?/k?/ o?/r?	Built-in Sensor SN1/SN2/SN3/SN4 ignore bitfields, respectively. ? is the 0-based 8-zone-group index. SN3/SN4 settings (o?/r?) apply only to OpenSprinkler v3.4+.
d?	stn_dis (station disable) bitfields.
p?	stn_spe (station special) bitfields.
g?	Station group ID (not a bitfield). ? is the 0-based station index; the value is 0–3 for a sequential group or 255 for the parallel group.
sid	Special-station target index (station id).
st	Special-station type (see /je).
sd	Special-station data payload (see /je). URL-encoded.

Note:

• Multiple assignments can be combined in one call; omitted fields are unchanged.
• To make a station "special", set the corresponding p? bit and provide sid/st/sd.

Examples:

• os-ip/cs?pw=xxx&s0=Front%20Lawn&s1=Back%20Lawn: set the first two stations' names
• os-ip/cs?pw=xxx&m0=127&s7=Garage: set station 8's name and master operation bits for board m0 (127=all but station 8 activate Master1).
• os-ip/cs?pw=xxx&sid=2&st=1&sd=00553300553c001c: set special station data for station 3
• os-ip/cs?pw=xxx&g4=1: assign group id 1 to station 5.

---

Get Station Status /js

Usage: http://os-ip/js?pw=xxx

Variable	Explanation
sn	Array of 1/0 indicating each station's On/Off status.
nstations	Total number of stations.

Example: {"sn":[1,1,0,0,0,0,0,0],"nstations":8}
Stations 1 and 2 (at indices 0 and 1 in the array) are currently open

---

Manual Station Run /cm

Usage: http://os-ip/cm?pw=xxx&sid=xx&en=x&t=xxx&ssta=x&qo=x

Parameter	Meaning
sid	Station index (starting at 0).
en	Enable (1: open, 0: close).
t	Runtime in seconds, from 1 to 64800 (18 hours). Required when opening a zone.
qo	Queuing option (applies when opening a zone). 0: append after other zones (default); 1: insert ahead of other zones.
ssta	Shift remaining stations in the same sequential group when closing a zone (en=0). 0: don’t shift; 1: shift. Ignored when opening a zone.

Note:

• Opening a master station by itself is not allowed (error), as it cannot be operated independently. To run a master alone, you can make use of a dummy zone (i.e. a zone not physically connected) and open that zone, which in turn opens the associated master(s).
• Opening a station that already has a runtime queue entry, whether running or waiting, returns a “not permitted” error. This error is also returned if the runtime queue is full.
• Manually started stations are assigned a program ID of 99.

Examples:

• os-ip/cm?pw=xxx&sid=0&en=1&t=360: open station 1 for 6 minutes, append to the queue.
• os-ip/cm?pw=xxx&sid=3&en=1&t=300&qo=1: open station 4 for 5 minutes, insert ahead of other zones.
• os-ip/cm?pw=xxx&sid=3&en=0: close station 4. Remaining stations in the same sequential group retain their original assigned start times.
• os-ip/cm?pw=xxx&sid=3&en=0&ssta=1: close station 4 and shift remaining stations in the same sequential group, so the next station starts immediately.

---

Pause Queue /pq

Usage: http://os-ip/pq?pw=xxx&dur=x&repl=x

Parameter	Meaning
dur	Toggle-style pause. If no pause is active and dur>0, start a pause of dur seconds. If a pause is active, cancels the pause (resume stations) regardless of dur value.
repl	Replace/set pause. Sets the pause to repl seconds (starts new or updates existing). repl=0 cancels any active pause. If both repl and dur are present, repl takes precedence.

Examples:

• os-ip/pq?pw=xxx&dur=600: start a 10-minute pause if none active; otherwise cancel pause.
• os-ip/pq?pw=xxx&repl=250: start a 250-second pause if none active; otherwise replace it.

---

Expanded Sensors & Sensor Logs

Expanded Sensor support is a major addition in firmware 2.2.1(5). The endpoints in this section let clients retrieve configured sensors and their latest readings (/jsn), change (add/modify) sensors (/csn), delete sensors (/dsn), and obtain the metadata for sensor configuration interfaces (/jsd). Separate log endpoints retrieve and export historical readings (/jsl) or clear an individual sensor's history (/dsl).

Each sensor has a stable ID (uuid) and a positional index (sid). The uuid is assigned when the sensor is created, does not change when other sensors are added or deleted, and is not reused during normal operation; a factory reset restarts UUID allocation. After a sensor is deleted, its UUID may still identify retained log records. The sid is the sensor's current index in the sn array and may change when the array changes. Use uuid for durable references.

Get Expanded Sensors /jsn

Usage: http://os-ip/jsn?pw=xxx

Returns the configured sensors and their latest readings. Each sensor contains:

Key	Meaning
uuid	Stable sensor ID (1–65535), unaffected when other sensors are added, deleted, or reordered.
name	User-assigned sensor name.
type	Sensor type. 0: Aggregate; 1: ADS1115; 2: Weather (disabled in this release); 3: System Internal; 4: Onboard Digital (i.e. Built-in Sensor input).
unit	Unit index (see /jsd).
flag	Bitmask. Bit 0: sensor enabled; 1: logging enabled; 2: show the sensor value on the homepage.
status	Runtime status bitmask: Bit 0: a valid reading is available Bit 1: the last read failed Bit 2: the reading is stale Bit 3: the reading exceeded max and was clamped Bit 4: the reading was below min and was clamped Bits can be combined. Examples: status=0: no successful reading yet; 1: a valid, in-range reading; 9 (0b01001): a valid reading clamped to max.
interval	Sampling interval, in minutes.
min/max	Output clamping range.
value	Last stored reading. Consult status before using it: after a failed or overdue update, this may be an older reading.
extra	Type-specific JSON object, described below.

Example: {"sn":[{"uuid":1,"name":"Soil 1","unit":0,"flag":3,"status":1,"interval":15,"min":0,"max":5,"value":2.7,"type":1,"extra":{"pin":1,"scale":1,"offset":0,"subtype":0}}],"count":1}

extra Object by Sensor Type:

The action, subtype, metric, and input fields are returned as integer indices — the same values accepted by /csn (e.g. action:2 is Average, subtype:0 is Linear).

Sensor type	Fields returned in extra
Aggregate	action: aggregation index (0:Min, 1:Max, 2:Average, 3:Sum, 4:Median, 5:Range). children: array of up to 8 {uuid,scale,offset} objects. A child with uuid=0 is unused.
ADS1115	pin, scale, offset, and subtype. Piecewise Linear (subtype:1) also includes points: an array of up to eight {x,y} objects.
System Internal	metric: which system metric (see /csn metric).
Onboard Digital	input: built-in sensor input index (0–3 = SN1–SN4).

extra Examples by Sensor Type:

• ADS1115 (linear): {"pin":1,"scale":1,"offset":0,"subtype":0}
• ADS1115 (piecewise): {"pin":1,"scale":1,"offset":0,"subtype":1,"points":[{"x":0,"y":0},{"x":3,"y":100}]}
• Aggregate: {"action":2,"children":[{"uuid":1,"scale":1,"offset":0},{"uuid":2,"scale":1,"offset":0}]}
• System Internal: {"metric":3} — Onboard Digital: {"input":0}

---

Change (Add/Modify) Expanded Sensor /csn

Usage: http://os-ip/csn?pw=xxx&uuid=xxx&type=xxx&...

To add a new sensor, use uuid=-1 (or sid=-1); omitted common parameters use the defaults shown below. To modify an existing sensor, specify the target with either uuid (stable ID) or sid (positional index); if both are given, uuid takes precedence; omitted common parameters retain their current values. The type parameter is always required.

Parameter	Meaning
uuid	Sensor stable ID (1–65535); -1 to add a new sensor.
sid	Sensor positional index (0-based); -1 to add a new sensor.
type	Sensor type. 0: Aggregate; 1: ADS1115; 2: Weather (disabled in this release); 3: System Internal; 4: Onboard Digital. Required.
name	Expanded Sensor name. Default: New Sensor.
min/max	Output clamping range. Defaults: min=0, max=5.
interval	Sampling interval, in minutes (≥ 1). Default: 15.
unit	Unit index. Default: 4 (Volt).
flag	Bitmask. Bit 0: sensor enable; 1: log; 2: show on homepage. Default: 1 (enabled only).

Type-Specific Parameters:

Parameter	Applied to	Meaning
children	Aggregate	Up to eight source sensors, encoded as semicolon-separated triples uuid,scale,offset;uuid,scale,offset;…. uuid=0 marks an unused child. Child defaults: scale=1, offset=0.
action	Aggregate	Aggregate action: 0: Min, 1: Max, 2: Average, 3: Sum, 4: Median, 5: Range (Max-Min). Default: 2 (Average).
pin	ADS1115	Analog input pin (1–16). Default: 1.
subtype	ADS1115	ADS1115 subtype: 0: Linear 1: Piecewise Linear 10/11: SMT50 Temperature/Moisture 12/13/14: SMT100 Temperature/Moisture/Permittivity 15: VH400 Soil Moisture 16: THERM200 Temperature 17: AquaPlumb Water Level Default: 0. Values 2–9 are reserved and rejected.
scale/ offset	ADS1115	Final adjustment applied as value = scale × sensor_value + offset. Defaults: scale=1, offset=0.
points	Piecewise Linear	Comma-separated x0,y0,x1,y1,... pairs, defining 2–8 sample points, sorted by nondecreasing input x.
metric	System Internal	Metric selector. For ESP8266: 0: Free Heap, 1: Free Flash, 2: WiFi RSSI, 4: Heap Fragmentation. For OSPi/Linux: 3: CPU Temperature.
input	Onboard Digital	Built-in Sensor input: 0-3: SN1-SN4 respectively. SN3/SN4 only available on OpenSprinkler v3.4 or later.

Subtype-specific units and recommended min/max values are provided by /jsd (see below). API clients should use that metadata when constructing /csn requests.

Examples:

• Add an ADS1115 voltage sensor on pin 1 (enabled + logging): /csn?pw=xxx&uuid=-1&type=1&name=Soil+1&pin=1&subtype=0&unit=4&min=0&max=5&interval=15&flag=3
• Add an averaging Aggregate over sensors 1 and 2: /csn?pw=xxx&uuid=-1&type=0&name=Avg&action=2&children=1,1,0;2,1,0
• Convert sensor 5 to Piecewise Linear (0 V → 0, 3 V → 100): /csn?pw=xxx&uuid=5&type=1&subtype=1&points=0,0,3,100

---

Delete Expanded Sensor /dsn

Usage: http://os-ip/dsn?pw=xxx&uuid=xxx

To delete an existing sensor, specify the target with either uuid or sid (uuid takes precedence if both are given). To delete all sensors, use uuid=-1 (or sid=-1).

---

Get Expanded Sensor Descriptions /jsd

Usage: http://os-ip/jsd?pw=xxx

Returns descriptive metadata used by the UI to build the Expanded Sensor configuration menus: available types, units, and per-type arguments, along with their display names.

The response has five top-level keys:

{ "sensors":[...], "units":[...], "enums":{...}, "as":[...], "flags":[...] }

Top key	Meaning
sensors	Array of sensor-type descriptions. The array index is the sensor type. Each entry contains its display name and type-specific arguments; it may also indicate that the type is disabled or that required hardware was not detected.
units	Available sensor units, encoded as [id,name,symbol,group]. The group value indexes enums.SensorUnitGroup.
enums	Named arrays used by enum arguments, including SensorUnitGroup, AggregateAction, and WeatherAction. Each array index is the value submitted to /csn.
as	The top-level as is the list of arguments common to all sensor types (name, interval, unit, min/max, type). Separately, each entry in sensors has its own as array for that type's specific arguments.
flags	Persistent sensor-flag descriptions. The array index is the corresponding bit position in /jsn.flag and /csn.flag; d gives that bit's default state.

Argument objects (in as) and similar entries use compact keys:

Compact Key	Meaning
n	Display name
a	The /csn argument this maps to
t	Data or editor type
d	Default value
h	Optional UI hint
as	Type-specific argument array in a sensor-type description
dis	1 when the sensor type is disabled
hwd	1 when required hardware is detected; 0 when it is not
o	Inline options for an enum argument
id	Numeric option value submitted to /csn
l	Option display label
hd	Arguments hidden when an option is selected
dfl	Argument defaults applied when an option is selected
ug	Allowed sensor-unit group
lk	Arguments locked when an option is selected
e	Element schema for an array argument
indicator	Marks the field used to determine whether an array element is populated

For example, this object from the common as array describes the sampling interval:

{
  "n": "Interval",
  "a": "interval",
  "t": "int::[1,any]",
  "d": "15",
  "h": "Sensor's update interval (in minutes)"
}

Type-specific arguments use the same structure. For example, the Aggregate Sensor's action refers to the top-level AggregateAction enum and defaults to index 2 (Average):

{
  "n": "Action",
  "a": "action",
  "t": "enum::AggregateAction",
  "d": "2"
}

The corresponding enum is returned as "AggregateAction":["Min","Max","Average","Sum","Median","Range"]. These are excerpts; the complete response also contains all sensor type definitions, units, common arguments, and flag descriptions.

A unit entry such as [17,"Celsius","°C",4] identifies unit 17, its display name and symbol, and unit group 4 (Temperature in enums.SensorUnitGroup).

The flags array is returned in bit order:

[
  {"n": "Enabled", "d": 1},
  {"n": "Logging", "d": 0},
  {"n": "Show on Home", "d": 0}
]

These entries describe flag bits 0, 1, and 2, respectively.

---

Get Expanded Sensor Log /jsl

Usage: http://os-ip/jsl?pw=xxx&[uuid=xxx]&[count=xxx]&[before=xxx]&[after=xxx]&[cursor=xxx]&[fmt=xxx]&[page=1]

Parameter	Meaning
uuid	Filter records by sensor uuid; use -1 (default) for all sensors.
sid	Filter records by positional index (uuid takes precedence if both are given).
count	Max records to return (default 100). max/all returns up to the full capacity. With page=1, this instead bounds the number of slots scanned per request (see Pagination below).
before	Return only records at or before this epoch value.
after	Return only records at or after this epoch value.
cursor	Pagination offset. Without page=1, the number of records to skip from the oldest; with page=1, an absolute physical slot offset (see Pagination below).
fmt	Output format: json (default), csv, or binary.
page	Set to 1 for reliable physical-slot pagination, including across deleted, sensor-filtered, or time-filtered records.

Output formats:

• json — [[uuid,timestamp,value],...] array of arrays.
• csv — uuid,timestamp,value rows with a header; served as a sensor_log.csv download.
• binary — packed records (uint32 timestamp, float value, uint16 uuid); the most compact form for bulk export.

Records are returned oldest-first (chronological order).

Example (json format): [[1,1731000000,2.71],[1,1731000900,2.68]]

Rules during paginated reads:

• count bounds the number of slots scanned per request (the work done), not the number of records returned.
• Always set the next cursor to the returned X-OS-Next-Cursor (see below). Never add the row count yourself — the server may skip whole out-of-window files and advance the cursor past your value.
• Repeat the same uuid/sid/before/after on every request.
• Stop when X-OS-Page-Done is 1. Do not stop merely because a page was short, and note that a bounded time window can finish before the cursor reaches X-OS-Total-Slots.

Response headers:

Variable	Meaning
X-OS-Next-Cursor	Physical cursor for the next request.
X-OS-Total-Slots	Total number of record slots when the request began.
X-OS-Window-Start	First physical slot in the requested time window.
X-OS-Window-End	One past the last physical slot in the requested time window.
X-OS-Page-Done	1 when the retrieval is complete.

Client loop:

cursor = 0
do:
  resp = GET /jsl?pw=..&uuid=U&after=A&before=B&page=1&count=200&cursor=cursor
  append rows from resp.body
  cursor = resp.header["X-OS-Next-Cursor"]
  progress = (cursor - X-OS-Window-Start) / (X-OS-Window-End - X-OS-Window-Start)
while resp.header["X-OS-Page-Done"] != 1

The firmware continues to log sensors during a /jsl request; if a full ring rotates between page requests, its physical ordering can shift and produce a skipped or duplicated record. Paginated export is therefore best-effort rather than a transactional snapshot. Requests without page=1 retain the original API behavior (return the oldest count records after skipping cursor, within any before/after/uuid filters).

---

Delete Expanded Sensor Log /dsl

Usage: http://os-ip/dsl?pw=xxx&uuid=xxx
Paginated: http://os-ip/dsl?pw=xxx&uuid=xxx&page=1&[cursor=xxx]&[count=xxx]

Delete log records of a sensor specified by its uuid. Use uuid=-1 to clear the entire log.

{"result":1,"next":819,"total":40950,"deleted":37,"done":0}

Field	Meaning
next	Cursor for the next request.
total	Total slots present when this request began.
deleted	Records deleted in this request.
done	1 when next has reached total; otherwise 0.

Rules:

• cursor defaults to 0; count defaults to one log file's record capacity and is capped at that value.
• Continue with the returned next until it reaches the total frozen from the first response, even when deleted is 0 (matching records may appear in later slots).
• Retrying the same cursor is safe (the operation is idempotent).
• Freeze total from the first response and cap the final request's count to initialTotal - cursor, so records logged after deletion began are left untouched.

Client loop:

cursor = 0; initialTotal = null
do:
  cnt = (initialTotal == null) ? DEFAULT : min(DEFAULT, initialTotal - cursor)
  resp = POST /dsl?pw=..&uuid=U&page=1&cursor=cursor&count=cnt
  if initialTotal == null: initialTotal = resp.total   # freeze the target
  cursor = resp.next
while cursor < initialTotal

Paginated delete requires a specific, non-zero uuid. On the other hand, clearing all logs with uuid=-1 needs no pagination — it simply deletes every log file without scanning the content, a fast one-shot operation — so uuid=-1 cannot be combined with page=1.

---

Programs & Scheduling

Get Program Data /jp

Usage: http://os-ip/jp?pw=xxx

Variable	Explanation
nprogs	Number of programs.
nboards	Number of 8-zone groups (includes the main controller).
mnp	Max number of programs allowed (40 for this firmware).
mnst	Max number of fixed start times per program (4 in this firmware).
pnsize	Max characters allowed for a program name (32 in this firmware).
pd	Array of Program Entries; each follows the structure below.

Program Entry Structure:
[flag, days0, days1, [start0, start1, start2, start3], [dur0, dur1,...], name, [endr, from, to], sensorAdjustment]

Field	Explanation
flag	Bitfield of program flags (see flag table below).
days0,days1	Start-day data (see Start-day types below).
start0..start3	Start-time data (see Start-time encoding below).
dur?	Per-station programmed durations in seconds (max: 64800). The length must equal station count. Supports two special values: 65534 → sunrise-to-sunset duration; 65535 → sunset-to-sunrise duration. These programmed values are capped at 64800, but the effective runtime after weather/sensor scaling may exceed it, up to the maxrt reported by /jpa.
name	Program name (≤pnsize characters).
[endr,from,to]	Date-range tuple (see Date-range tuple below).
sensorAdjustment	Sensor-adjustment object (described below), or {} when no sensor adjustment is assigned.

flag bitfield

bit(s)	Meaning
0	Program enable flag (en). 1: enabled; 0:disabled.
1	Use weather flag (uwt). 1: yes; 0: no.
2–3	Odd/Even restriction. 0: none; 1: odd-day; 2: even-day; 3: undefined.
4–5	Start-day type. 0: weekly; 1: single-run; 2: monthly; 3: interval-day.
6	Start-time type. 0: repeating type; 1: fixed times.
7	Date-range enable. 0: off; 1: on.

Start-day Types. Depending on flag.bits[4-5]:

• 0 → Weekly: days0.bits[0-6] store the binary selections (LSB) from Monday to Sunday. days1 is unused. Example: days0=127 (0b1111111) runs daily; days0=21 (0b0010101) runs Mon/Wed/Fri.
• 1 → Single-run: days0 and days1 together form a 16-bit unsigned integer encoding the day (epoch_seconds / 86400).
• 2 → Monthly: days0 stores the day of the month (1-31). Use 0 for the last day of a month.
• 3 → Interval-day: days1 is the interval day (every N days); days0 is the remainder ("starting in" offset). Example: days1=3, days0=0 means every 3 days starting today.

Start-time Encoding. Depending on flag.bit[6]:

• 1 → Fixed start-time: each of start0, 1, 2, 3 is a 16-bit integer representing an independent start time. For each:
  • If bit[15]=1 (negative value), this start time is disabled.
  • If bits[13-14] are both 0, this is a standard time (0-1439) representing the minute count from 00:00 AM to 11:59 PM.
  • If bit[13]=1, this is a sunset-based time; if bit[14]=1, this is a sunrise-based time. In either case, the remaining bits define a signed offset from the sunset / sunrise time, with bit[12] being the sign (1=negative), and bits[0-10] (i.e. start_time & 0x7FF) the absolute value of offset in minutes.
• 0 → Repeating start-times: start0 stores the first start-time (same encoding as above); start1 is the repeat count; start2 the interval (every N) minutes; start3 unused. Example: [480,5,120,0] → start at 8:00 AM, repeat every 2 hours for 5 times.

Date-range tuple: [endr,from,to]

• endr: Date-range enable. Must equal flag.bit[7].
• from, to: Start and end dates, encoded as (month<<5)+day. Example: Feb 3 is encoded as (2<<5)+3=67. Defaults: from=33 (Jan 1), to=415 (Dec 31).
• from and to are both inclusive. If from=to, it defines a range of one day. If from>to, the range wraps into the next year.

Sensor-Adjustment Object:

A program can scale its station run times by an Expanded Sensor reading, on top of the weather-based watering level. This adjustment is set via /cp's snadj parameter, and the resolved per-program factor is reported by /jpa as sa (with ta = wa × sa).

{"flag":flag,"uuid":uuid,"splits":[{"x":x0,"y":y0},{"x":x1,"y":y1},...]}

Field	Explanation
flag	Bitmask. Bit 0 enables the adjustment; other bits are reserved.
uuid	Stable ID of the Expanded Sensor used by this program.
splits	Up to eight points mapping sensor values (x) to program adjustment factors (y). Points are sorted by nondecreasing x; duplicate x values are allowed and define a step. Values between points are linearly interpolated, while values outside the range use the nearest endpoint factor.

If the adjustment is disabled, has no points, references a missing or disabled sensor, or the reading is unavailable, invalid, or stale, its effective factor is 1.0 (100%).

Example: {"nprogs":2,"nboards":1,"mnp":40,"mnst":4,"pnsize":32,"pd":[[3,127,0,[480,2,240,0],[0,2700,0,2700,0,0,0,0],"Summer",[0,33,415],{"flag":1,"uuid":5,"splits":[{"x":0,"y":1},{"x":500,"y":0.5}]}],[2,9,0,[120,0,300,0],[0,3720,0,0,0,0,0,0],"Fall Prog",[0,33,415],{}]]}

---

Change Program Data /cp

Usage: http://os-ip/cp?pw=xxx&pid=xx&en=x&uwt=x&name=xxx
&v=[flag,days0,days1,[start0,start1,start2,start3],[dur0,dur1,dur2…]]&from=xxx&to=xxx&snadj=flag,uuid,x0,y0,...

Parameter	Meaning
pid	Program index, in the range [-1, N-1]. If pid=-1: add a new program; otherwise, modify an existing program.
en	Directly set the program's enable bit (flag.bit0). If present, all other parameters are ignored!
uwt	Directly set the uwt bit (flag.bit1). If present, all other params are ignored!
name	Program name (URL-encoded, without quotes).
v	Program body (see /jp endpoint), excluding name, from/to, and sensorAdjustment (set separately via snadj).
from/to	Date-range parameters (month<<5)+day (see /jp endpoint).
snadj	Optional sensor adjustment encoded as flag,uuid,x0,y0,x1,y1.... Bit 0 of flag enables the adjustment; uuid is the Expanded Sensor's stable ID; and the remaining values define up to eight points with nondecreasing x and nonnegative y. Omit this parameter when modifying a program to preserve its existing adjustment. Use snadj=0,0 (disabled, no sensor) to clear it.

NOTE: The v parameter is still required when changing snadj: sensor adjustment cannot be modified as a standalone partial update. The program name Run-Once with repeat is reserved for temporary programs created by /cr and will thus be rejected here.

Examples:

• os-ip/cp?pw=xxx&pid=0&en=0: disable program 1.
• os-ip/cp?pw=xxx&pid=1&uwt=1: enable "use weather" on program 2.
• os-ip/cp?pw=xxx&pid=-1&v=[3,127,0,[480,2,240,0],[1800,1200,0,0,0,0,0,0]]&name=Summer%20Prog: add a new program, enabled, use weather adjustment, no date range, no restriction, weekday schedule that runs on every day, repeating start time type, start at 8:00 AM, repeat every 4 hours for 2 times, and the watering times are: station 1 – 30 minute; station 2 – 20 minutes, program name is "Summer Prog".
• os-ip/cp?pw=xxx&pid=-1&v=[131,127,0,[480,2,240,0],[1800,1200,0,0,0,0,0,0]]&name=Winter%20Program&from=353&to=67: add a new program, enabled, using date range from Nov 1 to Feb 3, named "Winter Program", the other parameters are the same as the "Summer Prog" above
• os-ip/cp?pw=xxx&pid=-1&v=[3,127,0,[480,2,240,0],[1800,1200,0,0,0,0,0,0]]&name=Sensor%20Adjusted&snadj=1,5,0,1,500,0.5: add a program using Expanded Sensor UUID 5; its sensor factor decreases linearly from 1.0 at a reading of 0 to 0.5 at a reading of 500.

---

Get Program Adjustments /jpa

Usage: http://os-ip/jpa?pw=xxx

Returns the current weather (wa), sensor (sa), and the total (ta) adjustment factors for each program, in the same program order as jp.pd. Factors use 1.0 for 100%; ta is wa × sa. maxrt is a fixed, universal cap on any single station's effective runtime (in seconds). Preview clients should calculate min(base_duration × ta, maxrt).

Example: {"jpa":[{"wa":1.25,"sa":0.8,"ta":1.0}],"maxrt":604800}

---

Manually Start a Program /mp

Usage: http://os-ip/mp?pw=xxx&pid=xx&uwt=x&usa=x&qo=x

Parameter	Meaning
pid	Program index (starting from 0).
uwt	Use weather (1: apply the selected program's configured weather adjustment; 0: use a weather factor of 100%). Default: 0.
usa	Use sensor adjustment (1: apply the program's configured sensor adjustment; 0: use a sensor factor of 100%). Default: 0.
qo	Queuing option. 0: append the new program to the end of the queue; 1: insert at front (preemptive); 2: replace, i.e. reset all zones, clear queue, then start the new program. If qo is omitted, the default behavior is 2 (backward compatible).

Note: Program name annotations are honored when starting a program manually. If pid is out of bound, an error is returned.

Examples:

• os-ip/mp?pw=xxx&pid=0&uwt=0: reset all zones, then start program 1 at 100% watering level. As qo is omitted, this behavior is backward compatible with previous firmwares.
• os-ip/mp?pw=xxx&pid=1&uwt=1&qo=0: append program 2 at the end of the queue, using the current watering level.
• os-ip/mp?pw=xxx&pid=1&uwt=1&qo=1: insert program 2 at the front of the queue.
• os-ip/mp?pw=xxx&pid=1&uwt=1&qo=2: reset all zones, then start program 2 using the current watering level.
• os-ip/mp?pw=xxx&pid=1&uwt=1&usa=1&qo=2: reset all zones, then start program 2 using both its weather and sensor adjustments.

---

Delete Program(s) /dp

Usage: http://os-ip/dp?pw=xxx&pid=x

pid: Program index in [0, N-1]. pid=-1 deletes ALL existing programs.

Examples:

• os-ip/dp?pw=xxx&pid=1: delete program 2.
• os-ip/dp?pw=xxx&pid=-1: delete all programs.

---

Move Up (Re-order) a Program /up

Usage: http://os-ip/up?pw=xxx&pid=x

pid: Program index in [1, N-1]. pid=0 has no effect.

Examples:

• os-ip/up?pw=xxx&pid=2: move program 3 up, before program 2.
• os-ip/up?pw=xxx&pid=0: no effect as the program 1 cannot be moved up.

---

Run-Once Program /cr

Usage: http://os-ip/cr?pw=xxx&t=[x,x,...,x]&cnt=xxx&int=xxx&uwt=xxx&anno=xxx&qo=x

Parameter	Meaning
t	Array of per-station duration (in seconds). A value of 0 means that station does not run. Stations launched via this command are assigned program ID 254.
cnt	Repeat count. 0: run once (no repeats).
int	Repeat interval (in minutes). Must be >0 if and only if cnt>0.
uwt	Use weather. 1: apply current watering level to durations; 0: no.
anno	Program name annotation, in the form of >X where X is an annotation letter. See OpenSprinkler User Manual.
qo	Queuing option (same as /mp). 0: append to end; 1: insert at front; 2: replace (reset all zones, clear queue, then start). Default is 2 if qo is omitted.

NOTE: If the program is set to repeat (cnt>0 and int>0), the firmware auto-creates a single-run program named "Run-Once with repeat" (plus anno). This is necessary to support repeats.

Examples:

• os-ip/cr?pw=xxx&t=[60,0,60,0,60,0,60,0]: reset all zones, then start a run-once program that turns on stations 1, 3, 5,7 for 1 minute each. As qo is omitted, this behavior is compatible with previous firmwares.
• os-ip/cr?pw=xxx&t=[60,0,60,0,60,0,60,0]&uwt=1&qo=0: append the run-once program at the end of the queue, using the current watering level.
• os-ip/cr?pw=xxx&t=[60,0,60,0,60,0,60,0]&uwt=0&qo=1: insert the run-once program at the front of the queue, using 100% watering level.
• os-ip/cr?pw=xxx&t=[60,0,60,0,60,0,60,0]&cnt=3&int=15&anno=>N: similar to the first example above, but also set it to repeat every 15 minutes for 3 times. This auto-creates a single-run program, appending the annotation >N to the program name (>N tells the program to run zones in reverse order of zone names).

---

Sprinkler Logs

Get Sprinkler Log Data /jl

Usage:
http://os-ip/jl?pw=xxx&start=xxx&end=xxx&type=x
http://os-ip/jl?pw=xxx&hist=n&type=x

Parameter	Meaning
start	Start time (epoch seconds), inclusive.
end	End time (epoch seconds), inclusive. Max span: 365 days.
hist	History window in days back from today. 0: today only; 1:today+yesterday; and so on. Max span: 365 days.
type	Filter special events (indicated by pid=0). Choices: s1,s2,s3,s4,rd,fl,wl. s3 and s4 are available on OpenSprinkler v3.4 or later.

Log Record Format

• [pid,sid,dur,end]: standard run
• [pid,sid,dur,end,flow]: with the Built-in flow sensor enabled (5th element)

Field	Meaning
pid	Program index (1-based); special events use pid=0.
sid	Station index (0-based); or a special event code (string) when pid=0.
dur	Duration in seconds. Weather- and sensor-adjusted runs may exceed 65535, up to /jpa.maxrt.
end	End time (epoch seconds).
flow	Optional flow metric for the run (present only if the Built-in flow sensor is enabled).

Special Event Code
A log record is a special event if its pid=0, in which case sid is a string code:

sid	Meaning
s1-s4	Built-in Sensor SN1-SN4 event. SN3/4 events are available on OpenSprinkler v3.4 or later.
rd	Rain delay event
fl	Flow reading
wl	Watering level log

Example Request: http://os-ip/jl?pw=pw_md5&start=1413567367&end=1413657367
Response: [[3,17,616,1413511817], [0,"rd",86400,1413511845], [254,1,5,1413512107], [1,3,2700,1413552661], [5,3,1200,1413559201]]

---

Delete Sprinkler Log Data /dl

Usage: http://os-ip/dl?pw=xxx&day=n

day: Day index calculated as floor(epoch_seconds/86400). Use day=all to delete all Sprinkler Logs. NOTE: This does not delete Expanded Sensor logs; use /dsl for those.

Examples:

• os-ip/dl?pw=xxx&day=16361: delete the log file for day Oct 18, 2014.
• os-ip/dl?pw=xxx&day=all: delete all Sprinkler Log files.

---

Combined Data & Diagnostics

Get All /ja

Usage: http://os-ip/ja?pw=xxx
Returns a single JSON combining the return values of /jc, /jo, /jn, /js, /jp, and /jsn.

Variable	Source
settings	/jc (controller variables)
options	/jo (options)
stations	/jn (station names and attributes)
status	/js (station status)
programs	/jp (program data)
sensors	/jsn (Expanded Sensor data)

Example Return: {"settings":{...},"options":{...},"stations":{...},"status":{...},"programs":{...},"sensors":{...}}

---

Debug Information /db

Usage: http://os-ip/db
Returns diagnostic information such as the firmware build date, time, and available heap/RAM. Authentication is not required.

---

List Files /lf

Usage: http://os-ip/lf?pw=xxx
Lists files and their sizes on the ESP8266 internal file system. This endpoint is only available on OpenSprinkler v3 (i.e. ESP8266-based).

Response: {"files":[["/filename",size],["/logs/filename",size],...]}

---

Reference Tables

Reboot Cause Codes

Interpretation of the lrbtc variable in /jc result.
Source: https://github.com/OpenSprinkler/OpenSprinkler-Firmware/blob/master/defines.h

Code	Cause
0	None/unknown
1	Factory reset
2	Button triggered
3	Reset to AP mode
4	API/timer triggered
5	API triggered reboot
6	Switched from AP to client mode
7	Firmware update
8	Weather call failed >24h
9	Network failed too many times
10	NTP sync reboot
11	Program-triggered reboot
99	Power-on

---

Weather Error Codes

Interpretation of the wterr variable in /jc result.

Code	Meaning
0	Success
-1	Request not received
-2	Cannot connect to weather server
-3	Request timed out
-4	Received empty response

Positive codes are application errors from the weather service. Refer to https://github.com/OpenSprinkler/OpenSprinkler-Weather/blob/master/src/errors.ts

---