Cycles

Five named cycles. Pick up to eight active zones for each one. Cycle 1 starts as Front garden: zones 1, 4 and 5. The left irrigation button lists them under Cycles, then the zone switches under Manual.

Run length

These minutes are the ends of the slider on each zone.

Wi-Fi

This is the same Wi-Fi the fence, siren, doorbell, and other ESP boards use. A new sketch download bakes it in.

Loading…

Controller

Signal —

Demo

Uses the active zones. With this on, the bottom-left irrigation button stays on the dashboard so you can drop a zone and add a pipe, even with no controller attached.

A board shows up here after it announces itself. Use it, or add the id you flashed.

Pump and 16 valve relays

Drive relays from the ESP32. Do not put mains or the pump coil straight on a GPIO.

Pin map

Share ground between the relay board and the ESP. Keep the 24 V valve supply off the ESP pins.

ESP32-S3 · 16-zone irrigation

Board: ESP32S3 Dev Module. Library: PubSubClient. The Pi decides duration and sends off until this board reports the valve closed. The sketch also has a local duration backstop.

home-security/irrigation/command  ← {"zone":1,"on":true,"durationSec":600}
home-security/irrigation/status   → {"deviceId":"esp-irrigation-1","zones":[0,1,0,...]}
home-security/devices/esp-irrigation-1/hello

When an ESP32 connects over WiFi/MQTT it announces itself. Assign it to fence left/right and a floor, then Place on floor to drop the zone markers on that plan.

JVA ↔ ESP32 gateway wiring

Never connect fence high-voltage (kV) wires to the ESP32. Only dry contacts, isolated LV scalers, and relay-isolated control.

What you need

• JVA energizer with dry-contact control input (IN1 / gate) and alarm outputs (or keypad bus).
• ESP32-S3 (3.3 V) — fence gateway only; doors/motion stay on the Pi.
• Relay module (3.3 V coil or transistor-driven) from GPIO 10 → JVA arm/disarm input. Do not drive the JVA input from a bare GPIO.
• Alarm contacts: JVA alarm OUT → ESP GPIO with INPUT_PULLUP, contact to GND (active LOW). Optocoupler preferred for surge isolation.
• Voltage read path: never tap the fence wire. Use one of:
  • JVA monitor / keypad-bus module that outputs LV proportional signal or Modbus/serial kV, or
  • Manufacturer-approved fence voltage sensor → isolated divider → 0–3.3 V into ADC (GPIO 1 / 2).
• Level / regulation: ESP ADC absolute max ≈ 3.3 V. Use a resistive divider + clamp (e.g. Schottky to 3.3 V) after isolation. Prefer ADC1 pins on S3. Calibrate KV_PER_ADC_VOLT in the sketch against a known kV meter.
• Power: separate 5 V supply for ESP (USB/regulator); share GND with relay/opto low side only — keep fence earth / HV return isolated from logic ground.
• Optional: JVA PAE / keypad protocol bridge for true bus kV instead of analog estimate.

Pin map (default sketch)

* Fence left/right GPIOs: Sensor inventory → Unassigned · ESP32 → assign dropdown.

Doorbell ↔ ESP32-C3 wiring

Dry contacts / buttons only. Active LOW to GND. Do not feed 12 V doorbell transformers into the C3 — use a relay or isolated dry contact.

What you need

• ESP32-C3 Super Mini — doorbell gateway only. Fence stays on the S3; doors/motion stay on the Pi.
• Two buttons or dry contacts — one side to GND, the other to the assigned GPIO (inventory: Bell 1 / Bell 2).
• Mechanical doorbell with 12–24 V transformer: put a relay or optocoupler on the chime loop; C3 only sees the dry contact. Never put AC on the GPIO.
• Power: USB 5 V to the C3. Share GND with the button/relay low side only.
• Inventory GPIOs are baked into the downloaded sketch. Default 2 and 3 if unassigned.

Pin map (default sketch)

* Pins come from Sensor inventory → Doorbell GPIOs · ESP32-C3.

Wi‑Fi settings

Loading…

Saved credentials are injected into the doorbell firmware zip — no sketch edits needed.

Safe pins only

Sensor wires go to the MCP23017 chips, not to ESP32 strapping pins. Forbidden on the module: GPIO 0, 3, 45, 46 (strap), 19–20 (USB), 26–37 (flash/PSRAM), 43–44 (UART). GPIO 0 is the BOOT button only.

MCP23017 terminals

Chip 0x20 is T0–T15. Chip 0x21 is T16–T31. Address 0x20: A2=A1=A0 to GND. Address 0x21: A0 to 3.3V, A2=A1 to GND. Each terminal is +5V, SIG, GND. After the Pi sees the board, assign terminals in Sensor inventory. Unassign the ones you are not using.

• Reed / door / window / fence: SIG and GND only. Leave +5V unconnected.
• PIR: +5V, GND, and OUT to SIG. OUT must be 3.3V, not 5V.
• USB-C 5V / 2A powers the module, the LEDs, and any PIRs you enable. A 500mA port can brown out on Wi‑Fi peaks.

Wi‑Fi settings

Loading…

Same SSID store as the other ESP firmware. Re-download the zip after saving. MQTT host is the Pi LAN address from Tailscale settings, not the Tailscale IP.

ESP32 ↔ relay ↔ siren / strobe

Never put 12 V or mains on an ESP GPIO. The ESP only drives relay IN pins (3.3 V). The siren and strobe run from their own supply through the relay contacts.

What you need

• ESP32 (Dev Module or S3) — siren gateway only. Fence stays on its S3; doors/motion stay on the Pi.
• 2-channel relay module (5 V coil, opto preferred). GPIO 4 / 5 drive IN1 / IN2. Do not drive the siren coil from a bare GPIO.
• Siren (typically 12 V) and strobe on their own PSU. Relay COM = PSU negative (or positive — pick one convention and stick to it); NO = device negative.
• Power: USB 5 V for the ESP. Relay VCC from 5 V. Share GND between ESP and relay logic only — keep the 12 V return on the contact side.
• Active LOW is the sketch default (IN pulled low = relay on). Flip RELAY_ACTIVE_LOW if your board is active HIGH.
• Level: ESP GPIO is 3.3 V. Most 5 V relay boards accept 3.3 V IN; if not, use a transistor / opto driver.

Pin map (default sketch)

Wi‑Fi settings

Loading…

Saved credentials are injected into the siren firmware zip.

Wi‑Fi settings

Loading…

Resolving connection…

After upload, add a device above with command topic home-security/switches/esp-mqtt-switch-1/set and state …/state.

Sensor wiring · ESP32

Ultrasonic module is 5 V — use a level shifter on ECHO if needed. DFRobot runs at 3.3–5 V; digital OUT to GPIO only.

Ultrasonic waterproof (9MUDISTSENW)

• VCC → 5 V · GND → GND
• TRIG → assigned GPIO (default 18) · ECHO → assigned GPIO (default 19)
• Mount at top of tank facing water surface. Tank height (mm) in Control tab calibrates % full.

DFRobot Gravity non-contact digital

• VCC → 3.3 V · GND → GND · DOUT → assigned GPIO (default 4)
• Mount at desired alert height — HIGH when liquid detected within ~20 mm of face.
• Reports 100% when wet, 0% when dry (threshold sensor).

ESP32 shared

• USB 5 V power · Wi‑Fi to MQTT broker on Pi
• Up to 2 sensors on one board — use distinct GPIOs per sensor

Wi‑Fi settings

Loading…

Resolving…

Save Control config first — sensor names, types and GPIOs are baked into the zip. Wi‑Fi + MQTT_HOST prefilled.

Install & read levels

1. Configure both sensors in Control (names, type, GPIO, tank height mm).
2. Save Wi‑Fi under WiFi settings.
3. Download firmware from Firmware, flash with Arduino IDE (ESP32 Dev Module).
4. Power ESP32 — it publishes to home-security/jojo/{sensorId}/level.
5. Click Place on floor for each sensor — drag the 3D level node in edit mode.
6. Live reading format: 23% with [23% Full] embossed label.

Ultrasonic calibration

Measure empty-tank distance sensor-to-floor, enter as tank height. Percent = (height − distance) / height.

DFRobot placement

Fix sensor at the minimum level you care about (e.g. 20% mark). When water reaches the face, dashboard shows 100% at that point.