About this edition
Preview edition 01 · September 2026
These guides are being prepared for the current RoboAlarms software. They cover everyday use and software configuration. Physical installation, mounting and wiring are intentionally excluded.
Documentation is a snapshot
Section titled “Documentation is a snapshot”The manuals are refreshed when the project owner chooses to publish a new documentation edition. They do not automatically change with every software commit.
Control labels and available options may differ if your firmware is newer or older than this edition. Check Settings > About for your installed version.
What the images show
Section titled “What the images show”Panel screenshots come from the actual RoboAlarms UI running in the host preview with fictional sample data. They are not photographs of installed hardware and do not prove physical sensor operation.
The documentation fixture omits the factory-code reminder and uses healthy background conditions for normal tasks. Warning images are used when the warning itself is relevant to the instructions. Detail images are cropped to make important controls readable.
Example addresses, names, pairing numbers and credentials are not values to copy into an installation.
Current coverage
Section titled “Current coverage”| Included | Outside this edition |
|---|---|
| Touchscreen daily operation | Mounting, wiring and hardware selection |
| Codes, users and permissions | Certification or installation acceptance |
| Setup, zone programming and network settings | Finished native Zigbee hardware setup |
| Home Assistant installation/pairing and sensor sharing | The unfinished Devices touchscreen |
| MQTT, ntfy and Pushover configuration | Remote keypad hardware and schedules |
| Browser Panel Manager instructions | General configuration backup/restore |
| Updates, storage and troubleshooting | PDF production |
Home Assistant images show its real 2026.9.3 interface with RoboAlarms integration 0.1.0 in an isolated documentation lab. A fictional panel supplies the example connection and zone data. These captures illustrate the setup flow; they are not a hardware or security acceptance test. HACS installation is described from its official instructions; no personal GitHub account was used for captures.
Before relying on a new setup
Section titled “Before relying on a new setup”Follow the commissioning checklist. Record hardware-dependent checks as untested until they have actually been performed.
Phone notifications and connected services do not establish a professional monitoring contract or guaranteed emergency dispatch.