ALM-173-R1 Module for Alarm Systems

ALM-173-R1 Module for Alarm Systems

1. Overview & Description

The ALM-173-R1 is a configurable alarm I/O module for intrusion detection, fault annunciation, and local supervision. It integrates with a MicroPLC/MiniPLC or any Modbus master over RS-485 (Modbus RTU) and is configured via a USB-C WebConfig UI (Web Serial).

Highlights

• I/O: 17 opto-isolated digital inputs, 3 SPDT relays
• Local HMI: 4 buttons (ack/override) and 4 LEDs (status/alert)
• Interface: RS-485 (Modbus RTU), address 1–255, 9600–115200 baud
• Setup: Web browser (Chromium) via USB-C WebConfig; live status + safe device reset
• Design: Galvanically isolated field side; RP2350 MCU with MAX485 and PCF8574 expanders; powered from 24 VDC
• Integration: Modbus map exposes inputs, alarm/group bits, and relay states (works smoothly with Home Assistant / PLC / SCADA)

Quick use case: wire inputs → assign to alarm groups → choose Active-while or Latched-until-ack → map groups to relays/LEDs → connect RS-485 → acknowledge locally or via Modbus.

Core Capabilities

System Role & Communication

2. ALM-173-R1 — Technical Specification

2.1 Diagrams & Pinouts

ALM System Diagram	RP2350 MCU Pinout

Field Board Layout	MCU Board Layout

2.2 Quick Overview

• Function: Alarm/annunciator I/O with 17 opto DI + 3 SPDT relays
• Interface: RS-485 (Modbus RTU); address 1–255; 9.6–115.2 kbps
• Form factor: DIN-rail; USB-C service (Web Serial config)
• Local HMI: 4 buttons (ack/override), 4 LEDs (status/alert)

2.3 I/O Summary

2.4 Terminals & Pinout (Field Side)

Blocks:

• POWER: V+, 0V (24 VDC SELV)
• DI1…DI17: each with paired GND_ISO returns
• RELAY1 / RELAY3 (top): NC-C-NO; RELAY2 (bottom): NO-C-NC
• PS/1 (+12 V ISO) / PS/2 (+5 V ISO): sensors only (fused)
• RS-485: COM, B, A
• USB-C: service (not a load supply)

5.5 Electrical & MCU (Condensed)

• Power path: 24 VDC in → buck 5 V → LDO 3.3 V; isolated +12 V / +5 V rails for sensors
• Inputs: opto-isolated, protected; per-channel Enable / Invert / Group (1–3/None)
• Relays: HF115F drivers with isolation; onboard suppression; use external RC/TVS for inductive loads
• RS-485: MAX485-class with TVS/PTC; TX/RX indicators; half-duplex RTU
• USB-C: ESD/EMI protection; Web-Serial config only
• MCU/Storage: RP2350A dual-core + W25Q32 QSPI; I/O expanders PCF8574

2.6 Key Ratings

2.7 Mechanical & Compliance

• DIN-rail: EN 50022, 35 mm; PC/ABS V-0 enclosure
• Size / mass: 157.4 × 91 × 58.4 mm, ~420 g
• Dimensions drawing:
  
• Environmental: IP20, Type 1; impulse 2.5 kV; altitude ≤ 2000 m; pollution degree 2

2.8 Protections & Firmware (Brief)

• Protections: reverse/TVS on 24 V, isolated sensor rails with PTCs, TVS on RS-485/USB, opto isolation on I/O, contact snubbers onboard
• Alarm engine: Inputs → G1–G3 (Active-while / Latched-until-ack) + Any Alarm; relays can follow groups/master/override; LEDs/buttons configurable; Modbus map exposes states & controls

3. Use Cases 🛠️

These are practical examples of deploying the ALM-173-R1 with the HomeMaster Mini/Micro PLC or any Modbus RTU master.

Each case uses built-in firmware features via the Web Serial UI:

• Input settings: Enable, Invert, Group
• Relay logic: Enable, Invert, Group or Manual
• Alarm behavior: Latched or Momentary
• Buttons & LEDs: Ack / Override / Status
• Modbus: PLC reads status and controls relays

1) [Intrusion] Zone Alarm with Siren (Latched)

Trigger a siren when a sensor activates. Alarm stays ON until acknowledged.

Steps:

1. Map IN1 → Group 1; enable + invert if NC.
2. Set Group 1 → Latched until acknowledged.
3. Map Relay 1 → Group 1 (enable; invert if required).
4. Set Button 1 → Acknowledge Group 1.
5. Set LED 1 → Group 1, Blink mode.
6. PLC reads Group 1 + “Any Alarm” status.

2) [Access Control] Dual-Door Alarm with Shared Strobe

Two zones, each with own buzzer. Common strobe flashes on any alarm.

Steps:

1. Map IN1 → Group 1, IN2 → Group 2.
2. Set Groups 1 & 2 → Latched.
3. Map Relay 1 → Group 1, Relay 2 → Group 2.
4. PLC toggles Relay 3 when “Any Alarm” is active.
5. Set Button 1 → Ack G1, Button 2 → Ack G2.
6. Set LEDs 1–3 → G1, G2, Any Alarm.

3) [Supervision] Equipment Room Summary Alarm

Aggregate faults (smoke, thermal, flood, etc.) into one visual + Modbus alarm.

Steps:

1. Map IN1–IN8 → Group 1, invert per sensor.
2. Set Group 1 → Active while condition is active.
3. Map Relay 1 → Group 1 (to stack light).
4. Set LED 1 → Any Alarm, Blink.
5. PLC reads Any and Group 1 status.

4) [Access Control] Door Strike with Timeout Alarm

PLC unlocks door, monitors contact, alarms if left open too long.

Steps:

1. Map IN1 → Group 3 (Invert if NC).
2. Leave Relay 1 = Group None; PLC controls strike directly.
3. In PLC logic: if IN1 open too long → set Group 3 or energize Relay 2.
4. Set Button 4 → Ack Group 3, LED 3 → Group 3.

5) [Annunciator Panel] Any Alarm Indication

Use the front panel to show system-wide or per-group alarm state.

Steps:

1. Map inputs IN1…INn → Group 1–3.
2. Set groups to either Latched or Active while depending on use.
3. Set LED 1 → Any Alarm, Blink
4. Set LED 2 → Group 1, LED 3 → Group 2, LED 4 → Group 3
5. PLC mirrors lamp states to HMI/HA dashboard.

💡 Tip: “Any Alarm” is always available via Modbus and can be mapped to a summary relay or LED.

4. Safety Information

These safety guidelines apply to the ALM-173-R1 alarm I/O module. Ignoring them may result in equipment damage, system failure, or personal injury.

⚠️ Low-Voltage (SELV) only — This module is intended only for Safety Extra-Low Voltage (SELV) systems. Never connect mains or high-voltage circuits.

4.1 General Requirements

4.2 Installation Practices

4.3 I/O & Interface Warnings

🔌 Power

⚠️ Inputs & Relays

🧠 Communication & USB

👆 Front Panel

📶 Shielding & EMC

✅ Pre-Power Checklist

Ensure the following before applying power:

• All terminals are torqued and strain-relieved
• No accidental bridges between logic ground and GND_ISO
• Relays are correctly wired (COM/NO/NC) with snubbers installed
• RS-485 A/B polarity and termination are correct
• Sensor current on PS/1 (12 V) and PS/2 (5 V) is within limits

5. Installation & Quick Start

The ALM-173-R1 joins your system over RS-485 (Modbus RTU). Setup has two parts:

1. Physical wiring, 2) Digital configuration (WebConfig → optional ESPHome/PLC).

5.1 What You Need

LEDs: PWR steady ON in normal operation. TX/RX blink with RS‑485 activity.

Quick path: mount → wire 24 VDC & RS-485 (A/B/COM) → connect USB‑C → WebConfig: set Address/Baud & map inputs → groups → relays/LEDs → disconnect USB → hand over to controller.

5.2 Power

The module uses 24 VDC primary. Onboard regulation supplies logic and isolated 12 V / 5 V rails for sensors only.

• No power over RS‑485: the bus carries data only.
• Relays are dry contacts: do not power loads from internal rails.

4.2.1 Supply Types

• 24 VDC DIN-rail PSU → V+ / 0V.
• Sensor power → +12 V ISO / +5 V ISO (low-power, fuse/ptc limited).

5.2.2 Sizing

Account for:

• Base electronics
• Relay coil current (per energized relay)
• Sensor rails draw (+12/+5 ISO)

Rule of thumb: base load + worst-case relays + sensors, then add ≥30% headroom.

5.2.3 Power Safety

• Correct polarity; keep logic and GND_ISO separate unless intentionally bonded.
• Keep upstream fusing/breaker in place.
• Respect relay contact ratings; snub inductive loads.
• Use isolated rails only for sensors.
• De-energize before wiring; check for shorts.

5.3 Networking & Communication

Runtime control is via RS‑485 (Modbus RTU); USB‑C is for local setup/diagnostics (Web Serial).

5.3.1 RS‑485 (Modbus RTU)

Physical

• Terminals: A, B, COM (GND).
• Cable: twisted pair (preferably shielded) for A/B + common reference.
• Termination: 120 Ω at both physical ends; keep stubs short.

Protocol

• Role: RTU slave; controller is master.
• Address: 1–255; Baud: 9600–115200 (typ. 19200, 8N1).
• Provide local 24 VDC power (bus is data-only).

ESPHome (controller)

• Configure uart: pins and modbus_controller: for ALM.
• alm_address in YAML must match WebConfig.
• Polls discrete/holding; exposes relays, inputs, alarms to HA.

RS‑485 wiring checklist

• A→A, B→B, COM→COM
• Two end terminations; avoid star topologies
• Consistent A/B polarity end-to-end

5.3.2 USB‑C (WebConfig)

Purpose: Chromium (Chrome/Edge) Web Serial setup/diagnostics.

Steps

1. Connect USB‑C to the module.
2. Open https://www.home-master.eu/configtool-alm-173-r1 and click Connect.
3. Set Modbus Address & Baud (header shows Active Modbus Configuration).
4. Configure Inputs / Relays / LEDs / Buttons; changes apply live.
5. Use Serial Log; Reset Device if needed (auto-reconnect).

If Connect is disabled: ensure Chromium + serial permission; on macOS/Linux verify user serial permissions and that no other app is holding the port.

5.4 Installation & Wiring

⚠️ Qualified personnel only. De-energize the panel; verify with a meter. The ALM-173-R1 is SELV—never connect mains to logic/input terminals.

5.4.1 RS‑485 Field Bus

How

1. Shielded twisted pair (24–22 AWG recommended).
2. A→A, B→B, COM/GND→COM; keep polarity consistent.
3. 120 Ω at both physical ends of the trunk.
4. Single-point shield bond (usually at the controller).
5. Daisy-chain topology preferred (avoid stars).

5.4.2 Primary Power (24 VDC)

How

• Clean SELV 24 VDC to V+ / 0V.
• Observe polarity.
• Upstream fuse/breaker; proper panel bonding.

5.4.3 Digital Inputs (IN1…IN17)

How

• Wire each INx to its matching GND I.x return (dry contact / isolated low-voltage).
• Do not inject external voltage.
• Use shielded cable for long runs; avoid high‑dv/dt routes.
• Set Enable / Invert / Group in WebConfig; confirm via live dot.

4.4.4 Relays (RLY1…RLY3, COM/NO/NC)

How

1. External supply L → COM.
2. NO (or NC if fail-active required) → load; return to N/0 V.
3. Relays switch only (no internal power).
4. Respect contact ratings/codes.
5. Fit RC/TVS across inductive loads.

5.4.5 Final Checks

• Terminals torqued; strain relief applied.
• Isolation boundaries respected (GND_ISO vs logic).
• RS‑485 polarity/termination/biasing correct.
• Relays wired to proper COM/NO/NC; snubbers fitted.
• Power on: PWR steady; TX/RX blink under comms.

5.5 Software & UI Configuration

5.5.1 Connect

1. Plug USB‑C → 2) open the config page → 3) Connect → 4) verify Active Modbus Configuration in header → 5) use Serial Log / optional Reset Device.

5.5.2 Modbus Settings

• Address (1…255) → pick a unique RTU address.
• Baud → 9600, 19200 (default), 38400, 57600, 115200.
• Ensure the controller YAML (uart, modbus_controller, alm_address) matches.

Changes persist in flash; you can revisit anytime.

4.5.3 Alarm Modes

• None (disabled)
• Active while condition is active (momentary)
• Latched until acknowledged

Top-row indicators show live Any / G1 / G2 / G3 status.

4.5.4 Digital Inputs

For each IN1…IN17:

• Enabled, Inverted (for NC), Alarm Group (None/1/2/3).
• Live state dot = quick wiring check.

5.5.5 Relays

For RLY1…RLY3:

• Enabled, Inverted, Alarm Group:
  • None (0) → relay ignores groups (PLC/manual only)
  • Group 1/2/3 (1–3) → follows group state (incl. latching)
  • Modbus/Master (4) → controller-controlled

Tip: assign a Button to “Relay x override (manual)” for quick field tests.

4.5.6 LEDs & Buttons

LEDs (1–4)

• Mode: Steady / Blink
• Source: Any / Group 1/2/3 / Relay 1–3 overridden / None
• Live state dot shows activity.

Buttons (1–4)

• Action: Ack All / Ack G1–G3 / Relay 1–3 override / None
• Live press dot indicates input.

5.6 Getting Started (3 Phases)

Phase 1 — Wire

• 24 VDC to V+ / 0V
• RS‑485 A/B/COM (terminated ends, consistent polarity)
• Inputs to IN1…IN17 with GND I.x returns
• Relays to COM/NO/NC (snub inductive loads)
• (Optional) PS/1 +12 V ISO / PS/2 +5 V ISO for sensors

See: Installation & Wiring

Phase 2 — Configure (WebConfig)

• Set Address/Baud
• Pick Alarm modes (G1–G3)
• Map Inputs / Relays / LEDs / Buttons
• (Optional) Reset Device

See: WebConfig

Phase 3 — Integrate (Controller)

• Controller polls ALM via RS‑485
• Match Address and Baud
• Commission: read inputs & alarms; toggle relays; expose Ack/Override actions

See: Modbus RTU Communication and ESPHome Integration Guide

Verify

• LEDs: PWR ON; TX/RX blink on comms
• Inputs: toggle a few contacts; confirm live dots and Any/Gx indicators
• Relays: actuate from UI/controller; confirm field wiring (meter/indicator)
• Buttons/LEDs: test Ack/Override; confirm LED sources/modes

6. Modbus RTU Communication

Slave role: Modbus RTU over RS-485 (8N1, selectable 9600…115200 baud; typical 19200).
Address: 1…255 (set via WebConfig).
Data model: Discrete Inputs, Coils, Holding/Input Registers (live telemetry + configuration snapshots).

The tables below describe the factory default map used by the ALM-173-R1 firmware.

6.1 Input Registers (Read-Only)

Live, read-only snapshots convenient for dashboards and fast polling.

All 32-bit values (if any added in future) occupy two consecutive registers (lo, hi).

6.2 Holding Registers (Read/Write)

Configuration + low-rate control values (persisted by firmware where applicable).

Most daily setup is done in WebConfig; exposing these fields enables headless provisioning/backups from PLC/HA.

6.3 Discrete Inputs & Coils

Discrete Inputs (read-only flags)

Coils (write – single/multiple)

Coils obey priority: an Override holds a relay irrespective of group/master writes until you release it.

6.4 Scaling Summary

No engineering scaling is required for ALM core points. All values are boolean/bitfield or enum codes as defined above.

6.5 Basics & Function Codes

• Physical: RS-485 half-duplex; 120 Ω termination at both ends; consistent A/B polarity; shared COM/GND recommended if separate PSUs.
• Function codes: 0x01 Read Coils, 0x02 Read Discrete Inputs, 0x03 Read Holding, 0x04 Read Input (if utilized), 0x05/0x0F Write Coils, 0x06/0x10 Write Holding.
• Polling: Discrete/group bits at 5–10 Hz; mirrors at 2–5 Hz; holding snapshots on change or 1–5 s.

6.6 Register Map (Summary)

Discrete Inputs
00001..00017 DI1..DI17 state
00050..00053 Any, G1, G2, G3
00060..00062 Relay1..Relay3 mirrors
00090..00093 LED1..LED4 mirrors
00100..00103 BTN1..BTN4 pressed

Coils
00200..00202 Relay ON (RLY1..RLY3)
00210..00212 Relay OFF (RLY1..RLY3)
00220..00222 Override ON (RLY1..RLY3)
00230..00232 Override OFF (RLY1..RLY3)
00240 Ack All (pulse)
00241..00243 Ack G1..G3 (pulse)
00300..00316 Enable DIi (pulse)
00320..00336 Disable DIi (pulse)

Input Registers (Read-Only)
01100 FW version (U16)
01101 FW build/variant (U16)
01110 Active address (U16)
01111 Active baud code (U16)
01120..01121 DI bitmap (U16 lo/hi)
01130 Alarm summary bitmap (Any,G1,G2,G3)
01140 Relay bitmap
01150 LED bitmap
01160 Button bitmap

Holding Registers (R/W)
01200..01202 Group modes G1..G3 (0=None,1=Active-while,2=Latched)
01300..01350 IN1..IN17 [enable,invert,group] triplets
01400..01402 RLY1 [enable,invert,group]
01410..01412 RLY2 [enable,invert,group]
01420..01422 RLY3 [enable,invert,group]
01500..01503 BTN1..BTN4 action
01600..01607 LED1..LED4 [mode,source] pairs

6.7 Override Priority

7. ESPHome Integration Guide (MicroPLC/MiniPLC + ALM-173-R1)

The HomeMaster controller (MiniPLC/MicroPLC) running ESPHome acts as the Modbus RTU master on RS‑485. It polls the ALM-173-R1 and publishes entities to Home Assistant (HA). No HA add‑ons are required—everything runs on the controller.

7.1 Architecture & Data Flow

• Topology: Home Assistant ↔ ESPHome (controller) ↔ RS‑485 ↔ ALM-173-R1
• Roles:
  • ALM-173-R1: local alarm logic (inputs → groups → relays/LEDs; buttons for ack/override)
  • ESPHome: Modbus I/O; exposes entities/actions to HA
  • Home Assistant: dashboards, notifications, automations

Configure LED sources/modes and I/O mapping on the ALM via WebConfig; HA mainly consumes the resulting states.

7.2 Prerequisites (Power, Bus, I/O)

1. Power

• ALM: 24 VDC → V+ / 0 V
• Controller: per spec
• If supplies differ, share COM/GND between devices

1. RS‑485

• A↔A, B↔B (twisted pair), COM shared
• Terminate two physical ends (~120 Ω), bias at master
• Default serial: 19200 8N1; set address in WebConfig (examples use 5)

1. Field I/O (typical)

• IN1…IN17: dry contacts → map to Group 1/2/3
• RLY1…RLY3: siren/lock/indicator (dry contacts)
• Buttons/LEDs: local ack/override & status

7.3 ESPHome Minimal Config (Enable Modbus + Import ALM Package)

Use these exact variable names: alm_prefix, alm_id, alm_address.

uart:
  id: uart_modbus
  tx_pin: 17
  rx_pin: 16
  baud_rate: 19200
  parity: NONE
  stop_bits: 1

modbus:
  id: modbus_bus
  uart_id: uart_modbus

packages:
  alm1:
    url: https://github.com/isystemsautomation/HOMEMASTER
    ref: main
    files:
      - path: ALM-173-R1/Firmware/default_alm_173_r1_plc/default_alm_173_r1_plc.yaml
        vars:
          alm_prefix: "ALM#1"   # shown in HA entity names
          alm_id: alm_1         # unique internal ID
          alm_address: 5        # ALM Modbus ID from WebConfig
    refresh: 1d

For multiple ALMs, duplicate the alm1: block (alm2:, alm3:…) with unique alm_id / alm_prefix / alm_address.

7.4 Entities Exposed by the Package

• Binary sensors

  • IN1…IN17 (debounced)
  • Any Alarm, Group 1, Group 2, Group 3
  • Buttons pressed (BTN1…BTN4, optional diagnostics)
  • Relay/LED mirrors (dashboard readback)

• Switches

  • RLY1…RLY3 (manual/HA actuation)
  • Acknowledge (All / G1 / G2 / G3)
  • Override (force R1/R2/R3 ON/OFF, then release)

• Numbers/Selects (optional)

  • Readbacks for address/baud, group modes, and per‑channel enable/invert/group (for diagnostics/provisioning)

7.5 Command Helpers (Writes)

Package includes pulse‑safe helpers (auto‑release):

• Relays: R1/R2/R3 ON / OFF
• Overrides: Override ON/OFF for R1/R2/R3 (forces relay regardless of group until released)
• Acknowledges: Ack All, Ack G1, Ack G2, Ack G3
• (Optional) Inputs: Enable/Disable INx commissioning pulses

These appear as ESPHome switches/scripts usable in HA automations.

7.6 Using Your MiniPLC YAML with ALM

1. Keep your existing uart: and modbus: blocks.
2. Add the packages: block (above) and set alm_address to the device address in WebConfig.
3. Flash the controller. ESPHome discovers entities under alm_prefix (e.g., ALM#1 IN1, ALM#1 Relay 1).
4. Build dashboards and add buttons for Ack / Override actions as needed.

7.7 Home Assistant Setup & Automations

1. Add device: Settings → Devices & Services → ESPHome → add by hostname/IP.

2. Dashboards

• Annunciator: tiles for Any/G1/G2/G3, plus Ack All button
• Zones: IN1…IN17 grouped by area; toggles for RLY1/2/3
• Service/Night Mode: helper booleans that gate siren/override logic

1. Automations (examples)

• Any Alarm → ON: push notification + optional light flash; if service_mode = off then energize Relay 1 (siren)
• Group X (latched) → ON: prompt Ack Group X
• Modbus unavailable: critical alert + persistent HA notification

7.8 Troubleshooting

• No data/timeouts: check A/B polarity, COM/GND reference (if separate PSUs), termination/bias.
• Wrong package vars: must use alm_prefix, alm_id, alm_address (exact names).
• Relays not responding: ensure Enabled in WebConfig and not overridden.
• Latched alarms won’t clear: input must be normal and an appropriate Ack must be sent.
• Multiple ALMs: each needs a unique Modbus address and alm_prefix.

7.9 Version & Compatibility

• Tested with ESPHome 2025.8.0
• Controller YAML typically uses ESP‑IDF; Arduino works if preferred (adjust platform)

8. Programming & Customization

8.1 Supported Languages

• MicroPython
• C/C++
• Arduino IDE

8.2 Flashing via USB-C

1. Connect USB‑C.
2. Enter boot/flash mode if required.
3. Upload the provided firmware/source.

Boot/Reset combinations:

• Buttons 1 + 2 → forces the module into BOOT mode.
• Buttons 3 + 4 → triggers a hardware RESET.
  These behaviors are handled in hardware.
  Use these combinations during firmware flashing or to restart the device manually.

📷 Button numbering reference:

8.4 Firmware Updates

To update the firmware, use the Arduino IDE or PlatformIO via USB-C:

1. Connect the USB‑C cable to the module.
2. Press Buttons 1 + 2 together to enter BOOT mode.
3. Upload the updated binary located in Firmware/default_alm_173_r1/.

⚠️ Configuration stored in EEPROM is preserved during firmware updates unless manually cleared.

8.3 Arduino

• Select the appropriate board profile (Generic RP2350).

• In the Tools select Flash size 2MB (Sketch: 1MB, FS: 1MB )

• Add

  • #include
  • #include
  • #include
  • #include
  • #include
  • #include
  • #include
  • #include
  • #include “hardware/watchdog.h”

9. Maintenance & Troubleshooting

(Section placeholder for future additions.)

10. Open Source & Licensing

• Hardware: CERN‑OHL‑W 2.0
• Firmware & code samples: GPLv3 (unless otherwise noted)

11. Downloads

The following key project resources are included in this repository:

• 🧠 Firmware (Arduino/PlatformIO): Firmware/default_alm_173_r1/
  Main sketch implementing relays, button overrides, alarms, Modbus RTU, and WebSerial support.

• 🛠 Web Config Tool: Firmware/ConfigToolPage.html
  HTML‑based USB Web Serial configuration UI, used for meter options, calibration, relays, alarms, etc.

• 📷 Images & Visual Documentation: Images/
  Contains UI screenshots, module photos, diagrams, and layout references used in this documentation.

• 📐 Hardware Schematics: Schematics/
  Includes Field Board and MCU Board schematics in PDF format for hardware developers and integrators.

• 📖 Datasheet & Documentation (if available): Manuals/
  Contains PDF datasheets or technical overviews, if applicable.

12. Support

If you need help using or configuring the ALM-173-R1 module, the following resources are available:

• 🛠 Web Config Tool – Configure and calibrate via USB‑C in your browser.
• 🌐 Official Support Page – Knowledge base and contact options.

📡 Community & Updates

• Hackster Projects – Integration guides, wiring, and code examples.
• YouTube Channel – Video tutorials and module demos.
• Reddit Community – Questions, help, and user contributions.
• Instagram – Visual updates and product insights.