Hanwu develops configurable smart smoke detectors, heat detectors, human presence sensors and water leak alarms as complete OEM/ODM product systems, with embedded firmware, branded apps, web monitoring, cloud integration and production testing coordinated around the selected device.

Plan an Alarm or Detection Product Review the Complete Product System

Starting point: Alarm and detection devices
Project fit: Alarm-device and detection-product brands
Program path: Configuration, sample, pilot and production release

Ceiling-mounted smart alarm or detection device installed in a commercial room.

When Alarm and detection devices are the right starting point

Each configured model starts from its sensing purpose, installation environment, users, event behavior, connectivity, power, software workflow and target market. Smoke, heat, presence and water-leak events remain separate throughout specification and validation.

Connected smoke detector with its device-status and alert interface.

Smart smoke detectors

Connected heat detector with its monitoring and notification interface.

Smart heat detectors

Human-presence sensor with occupancy status shown in the connected software.

Human presence sensors

Water-leak alarm with event status shown in the monitoring interface.

Smart water leak alarms

Branded alarm and detection apps for status, alerts and device operations

The OEM/ODM scope can connect the selected smoke, heat, presence or water-leak product to branded mobile workflows, a web monitoring platform and agreed notification or data interfaces.

Branded sensor user and installer app

Support onboarding, room or zone assignment, device status and product-specific notifications in a branded mobile workflow.

Installers, property users and authorized responders

Install and assign a device to a room or zone
Review live device, battery and connection status
Receive the approved alarm, warning, fault or presence notification

Sensor app installation and zone assignment screen — **Installation and zone assignment**
Device onboarding, room assignment and installation checks

Interface scopeDevice status

Device status

Device state, connection, battery and latest approved event

Sensor app alerts and notifications screen — **Alerts and notifications**
Product-specific alarm, warning, fault or presence events

Alarm and detection monitoring platform

Organize sites, zones, devices, events, faults and maintenance records through a role-based browser interface.

Facility, support and device-operations teams

Review sites, zones and device status
Investigate alarms, events, faults and maintenance needs
Route notifications and export approved data

Web monitoring platform site and sensor overview — **Site and sensor overview**
Sites, zones, device status and active events

Web monitoring platform event and maintenance history — **Event and maintenance history**
Alarm, presence, leak, fault and maintenance history with role filters

Notification, API and deployment integration

Define event fields, notification ownership, third-party interfaces, hosting and product-data boundaries before the configured sample.

App and approved notification channels
REST API or agreed data exchange
Building or property-system integration
Public, dedicated or private deployment

Alarm and detection architecture linking field devices, connectivity, alerts and the monitoring platform.

Software areas you can configure

App identity, languages and user roles
Device, room, site and zone model
Product-specific event and notification rules
Dashboard fields, filters and reports
API, hosting, accounts and data ownership

Software outputs for review

Mobile onboarding and event-flow definition
Monitoring-platform definition
Device, site and event data model
Notification and integration boundary
Configured software build for sample review

Core product functions

Sensor interface and embedded alarm or detection logic
Device onboarding and room or zone assignment
Power, reconnect and device-health behavior
Cloud alerts and event history
Role-based monitoring and API options
Trigger, programming and communication tests

Monitoring dashboard showing connected sensor status and event panels. — Hardware, connectivity and operating software are configured as one product system.

Decisions that turn the starting point into your product

A configurable smoke, heat, presence or water-leak device platform with firmware, branded software, monitoring workflows and production tests.

Keep device events, firmware, branded software and factory checks aligned, so the sample proves the same operating flow the production release must repeat.

Smoke, heat, presence or water-leak detection configuration
Enclosure, installation and power arrangement
Wi-Fi, Bluetooth, NB-IoT or Cat.1 where applicable
Alarm, warning, fault and routine-status behavior
Branded app, monitoring platform and notification workflow
API, hosting, packaging and production-test scope

Configure the product around your market—not around a generic demo.

Start from the closest product system, then agree what changes across the device, software, brand experience, deployment and production release.

Hardware and enclosure

Adapt the product form, interfaces, power, accessories, installation, labeling and packaging.

Industrial-design and enclosure changes
Interfaces, accessories and installation
Labeling, packaging and documentation

Firmware and connectivity

Configure radio choice, device behavior, reporting, power, recovery and production programming.

Wi-Fi, Bluetooth, NB-IoT or Cat.1 where applicable
Device states, reporting and update logic
Programming and functional-test release

App, web and brand experience

Define branded mobile and browser experiences, roles, languages, workflows, alerts and support.

App identity and interface language
User, operator and administrator workflows
Dashboard fields, alerts and reports

Cloud, API, deployment and data

Agree interfaces, hosting, accounts, tenancy, source-code scope and product-data ownership.

API and third-party integration
Public, dedicated or private deployment
Account, hosting, source-code and data ownership

See how the configuration becomes a release

Review the work behind the product,not just the finished enclosure.

Use samples, fixtures, validation units and product-specific records to verify what will be built and tested for Alarm and detection devices.

Alarm and detection device product samples

Programming and functional-test fixtures for alarm and detection devices.

Alarm and detection pilot validation units prepared for representative checks.

Alarm and detection production documentation linked to the released configuration.

What stays fixed, what can change, and what must be checked again

Use the current Alarm and detection devices reference as the starting point. Any change that affects the product, software, installation or market must be reviewed before release.

Configuration boundary

Device and event behavior

Current: Reference samples cover the selected device family, device states and defined event flow.
Can change: Device type, enclosure, installation, power arrangement and approved event rules.
Recheck: Sensing behavior, event timing, installation and final enclosure conditions.

Connectivity and firmware

Current: Selected wireless path, reporting logic, device health and recovery behavior.
Can change: Wi-Fi, Bluetooth, NB-IoT or Cat.1 where applicable, plus reporting and retry rules.
Recheck: RF, power, reconnect behavior and support on the target network.

App and monitoring

Current: Onboarding, room or zone assignment, device status and product-specific events.
Can change: Branding, roles, notification flow, dashboard fields, API and hosting boundary.
Recheck: Device-state mapping, permissions, notifications and operator response workflow.

Production release

Current: Programming, communication and basic functional checks for the approved sample.
Can change: Configuration data, fixture flow, packaging and release-record requirements.
Recheck: Final test coverage, traceability and released hardware and software versions.

Typical buyer deliverables

Configured alarm or detection device sample
Event and device-state definition
App and monitoring screen scope
Connectivity, power and validation plan
Pilot and production test release

Validation boundary

Included in the reference configuration

Device startup, state and fault behavior in current samples
Selected connectivity and reporting workflow
App onboarding and product-event workflow
Programming and basic functional checks

Requires project-specific validation

Final sensing performance, enclosure and installation
RF, power and target-network behavior
Notification, monitoring and response responsibilities
Safety, radio and market compliance for the selected product

Reference validation does not automatically transfer to a changed enclosure, radio, battery, software stack, installation, legal entity or target market.

Configuration sheets, sample test records and applicable certification files can be reviewed against the selected product configuration, subject to file applicability and disclosure approval.

Request supporting product documents

Alarm and Detection Devices questions buyers ask

Best for

Alarm-device and detection-product brands
Programs needing a branded app or monitoring platform
Products requiring defined event and production-test workflows

Check first

Projects that combine different alarm or detection claims without separate requirements
Buyers without a defined device family, installation or target market

Typical scope

Sensor interface and embedded alarm or detection logic
Device onboarding and room or zone assignment
Power, reconnect and device-health behavior
Cloud alerts and event history

What you receive

Configured alarm or detection device sample
Event and device-state definition
App and monitoring screen scope

Questions buyers ask

Which alarm and detection devices can Hanwu develop?

The primary line covers configurable smart smoke detectors, smart heat detectors, human presence sensors and smart water leak alarms. The selected device family determines its event behavior, installation, software workflow, validation and compliance boundary.

Can the app and monitoring platform use our brand?

Yes. The scope can define app identity, languages, roles, onboarding, rooms or zones, dashboard fields, notification workflows, APIs, hosting and account or data ownership.

Are smoke, heat, presence and water-leak events handled the same way?

No. Alarm, warning, fault, presence and leak events require separate definitions, users, response rules and validation. The product specification records the selected device family and approved behavior.

Which connectivity options are available?

Wi-Fi, Bluetooth, NB-IoT or Cat.1 can be evaluated where appropriate. The choice follows installation, response, power, coverage, data, ownership and target-market requirements.

What is needed before an alarm or detection sample?

Provide the device family, target market, installation, intended users, event and notification requirements, power and connectivity preferences, software boundary and representative pilot conditions.

Connected Alarm and Detection Deployment IoT Connectivity Modules Mobile App and Dashboard Manufacturing and Testing

Related decisions for Alarm and Detection Devices

Open the use case, engineering layer or requirements guide that resolves the next product decision.

Turn this product into a reviewable sample brief.

Send the market, users, required functions, software boundary and what the first sample must prove.

Plan an Alarm or Detection Product

Bring a connected alarm or detection product to market.