Security & Premises Monitoring use case

The problem

NVR alerts are noisy. Nodlyn adds conditions, approvals, and multi-channel notify on top of your sensors.

Who it’s for: Home and small-business premises that already have Zigbee/Z-Wave contacts, cameras, or MQTT security topics.

How Nodlyn approaches Security & Premises Monitoring

Premises security here means contacts, locks, and camera/HTTP captures with optional AI classify — not a full VMS. Nodlyn adds scheduling, suppression, and approved unlock/disarm so noisy sensors become actionable alerts with evidence.

Reuse smart-home Discovery and MQTT topics from your existing alarm bridge; gate dangerous commands.

Example workflows

• Door open at night → snapshot → AI threat check → phone alert with photo
• Glass/contact sensor → lights + lock command (approved)
• Armed schedule → suppress daytime false positives

Quick start

1. Discover contacts/locks via smart-home protocols; subscribe MQTT topics from your alarm bridge.
2. Chain camera/HTTP capture with Vision/AI classify blocks.
3. Gate disarm or unlock commands behind approvals.
4. Audit sensitive runs in Cloud activity.

Starter templates in Studio

Open Templates in desktop Studio and search these names — they are real built-in graphs, not placeholder titles.

• Sensor Threshold Alert
• Approved Z-Wave Command
• MQTT Device Event → Slack

Related protocols

Guides (blog & wiki)

• ZigBee in Nodlyn: Sensors, Commands, and Zigbee2MQTT Automation Blog
• Z-Wave in Nodlyn: Node Control, Smart Sensors, and Z-Wave JS UI Integration Blog
• Building IoT Workflows with MQTT in Nodlyn Blog
• Device Discovery in Nodlyn: Matter, Zigbee, Z-Wave, CAN Bus & More Blog
• Build Approved Device Command Workflow Wiki
• Build Sensor Threshold Alert Workflow Wiki

Is this a full VMS?

No. It adds conditions, schedules, and approved unlock/disarm on top of contacts, MQTT topics, and camera/HTTP captures with optional AI classify.

Related use cases