Short answer
Publication date: November 11, 2025
Technical teams in apartments, residential sites, hotels, and commercial facilities often cannot see equipment distributed across different panels from one location. A booster-pump fault may be noticed only after a water interruption, a flood only during a room inspection, and a lighting failure only after a resident complaint. This reactive approach consumes staff time and allows small failures to become larger problems.
NetRelay can make dry contacts, environmental sensors, and auxiliary loads visible over the local network. Four digital inputs can monitor door contacts, booster faults, water levels, or flood alarms. Four relay outputs can control lighting, fans, sirens, valves, or auxiliary contactors through a properly designed electrical panel. Ethernet, Wi-Fi, PoE, and 7–28 V DC support different technical-room and field-panel installations.
Booster pumps and water tanks
A general fault contact from the booster panel can be connected to a digital input. Low and high tank-level switches can provide water-level status. A low-level condition may generate an alarm or inhibit pump operation through a suitable control architecture. A high-level condition may command a filling valve.
NetRelay must not replace the booster's pressure and motor-protection controller. Thermal, phase, dry-run, and pressure protection should remain in the certified panel. NetRelay monitors permitted auxiliary contacts and may provide a command to an appropriate contactor circuit.
Flood and technical-room alarms
A water sensor can protect boiler rooms, pump rooms, server rooms, and storage areas. When the sensor provides a dry contact, NetRelay can trigger a siren, send an email workflow, or publish an MQTT event to facility software.
Short sensor activations can be filtered to reduce false alarms. The system should record when the alarm began and recovered. Automatic water-valve closure requires professional review of valve position, manual override, fire-water relationships, and safe operating conditions.
Common-area lighting
Sunrise/sunset triggers and timers can manage parks, gardens, and common-area lighting without frequent seasonal schedule changes. Lights may start 20 minutes after sunset and stop 30 minutes before sunrise. An optional RTC can preserve time during an NTP or internet outage.
The relay should normally command a suitable contactor rather than carry a large lighting group directly. Manual maintenance control should remain available. Energy savings can be calculated from the reduction in operating hours and installed load.
Ventilation and temperature
A supported external sensor and analog module can monitor technical-room temperature. If a threshold remains exceeded, a fan can start and stop with a recovery delay. Ping Watchdog can monitor network devices and create an alarm when a modem or local controller is unavailable.
Smoke extraction, fire ventilation, and gas systems that directly affect human safety must not be independently designed around NetRelay. NetRelay may monitor auxiliary status contacts from certified systems.
Commercial value for facility management
The value is larger than controlling a relay from a phone. It includes fewer routine inspections, earlier detection, and better information for maintenance providers. Useful metrics include:
- Monthly time spent on routine technical-room checks,
- Booster or flood events detected late,
- Unnecessary lighting hours,
- Alert-to-response time,
- Incidents verified remotely,
- Unnecessary service calls.
A pilot can begin with one pump room or an outdoor-lighting group. During 30–45 days, measure alarm accuracy, operating time, and staff interventions. Once value is verified, a standard design can be replicated across other buildings.
Safety limits
Fire detection, elevator safety, gas alarms, emergency systems, and other human-safety functions must continue through certified controllers. Electrical work must be performed by qualified personnel, with relay contact rating, load type, protection, and contactor selection calculated for the project.
Central management
Organizations with several buildings can connect devices to central software through MQTT. Naming each device by property, block, and technical room simplifies alarm management. HTTP API and WebSocket support integration with custom facility software, Home Assistant, or maintenance applications.
Before starting, list the contacts to monitor, loads to control, network availability, and notification recipients. The NetRelay technical team can use this information to evaluate device count, architecture, and pilot scope.
Prioritizing maintenance requests
Not every facility alarm has the same urgency. Flooding and booster faults need immediate action, while one failed outdoor-lighting group may enter planned maintenance. NetRelay events can be classified by severity.
A central dashboard can track active, acknowledged, in-progress, and closed states. Before traveling, technicians can review doors, temperature, network, and equipment contacts. Service providers receive fault contact, start time, and connectivity data rather than a vague “not working” report.
Supporting energy management
Beyond lighting schedules, fan, pump, and auxiliary runtime can be tracked. Relay state is not direct energy measurement; accurate consumption requires an appropriate meter. Runtime is still useful for maintenance and approximate analysis.
Sunrise/sunset schedules adapt seasonally. Savings claims should be validated using installed load, previous hours, and measured data.
Hotels and accommodation facilities
Hotel teams can monitor boiler rooms, tanks, network rooms, outdoor lighting, and auxiliary pumps. A low-risk pilot should begin in common technical areas rather than guest-room automation.
NetRelay does not replace certified fire or elevator systems. It can transfer permitted general fault contacts to a maintenance dashboard. Privacy and access requirements apply if any data is associated with guests or room activity.
Multi-building portfolios
Management companies can connect several properties to one MQTT broker. Standardize location, device names, input lists, severity, and responsible teams. Secure outbound connectivity is preferable to direct port forwarding.
Central data reveals recurring booster faults, floods, and lighting hours across buildings and can support maintenance-contract performance reviews.
User experience and manual control
Automation must not make essential services harder to operate. Keep local manual/automatic selectors, maintenance switches, and clear labels. Lighting and water systems need safe local behavior during communication outages.
Use authorization levels. Managers may view status while technical staff control pumps or valves. Critical actions may require additional approval or local verification.
Network security
Separate guest Wi-Fi, office, and building automation. Keep devices in an IoT VLAN and allow only required MQTT, API, and management traffic. Change default credentials and manage firmware and configurations.
Do not expose the web interface directly to the internet. Use VPN for support and log user actions and relay commands.
Professional discovery and quotation
Survey panels, contacts, load power, contactors, network coverage, PoE, DC power, cable routes, and notifications. Clearly separate monitoring-only functions from remote control.
Quote NetRelay, panel components, sensors, installation, software, training, and maintenance separately. Annual value can be calculated from staff inspection time, avoided damage, reduced operating hours, and service visits.
Frequently asked questions
Can it work with Home Assistant?
Yes. MQTT can represent inputs as binary sensors and relays as switches. Custom central software may be better for professional multi-property deployments.
Is one device needed per technical room?
It depends on I/O count, cable distance, and panel layout. Several networked devices may be better than carrying distant signals to one panel.
What happens after a power failure?
UPS runtime for NetRelay and network equipment must be designed. Safe relay startup states should be defined.
Where should the project begin?
Choose a technical area with high complaint or service cost, establish baseline data, and define pilot success in time and money.
A 45-day pilot and handover process
Review six months of faults, complaints, and service records. During week one, select a booster, flood, or lighting area and document current behavior. In week two, install wiring and software and test in observation mode with automatic commands disabled. Validate alarms and permissions during weeks three and four, then collect staff feedback and prepare the report.
The handover file should include panel diagrams, I/O lists, IP and device inventory, user permissions, manual operation, maintenance, and contacts. Knowledge must survive changes in management or service providers.
Communicating with residents and management
Do not describe the project as remote control of everything. Explain which common areas are monitored, what data is collected, and which faults can be detected earlier. If movement or access information is processed, privacy requirements apply.
Management reports should use prevented outages, response time, lighting hours, and service calls rather than technical jargon. This positions the investment as service continuity and damage prevention.
NetRelay does not replace the facility team; it helps the team reach the right event faster.
Long-term operating cost
Network changes, staff turnover, sensor failures, and firmware needs continue after installation. Annual maintenance should review connectivity, relays and contactors, sensor validation, user permissions, configuration backups, and alarm-recipient lists.
Management should not remember the system only after a fault. A short monthly report should show device availability, alarms, response time, and automatic equipment runtime. Unused or noisy rules should be corrected.
This operating discipline turns NetRelay from a temporary smart-building experiment into documented maintenance infrastructure. The buying decision should include continuing responsibilities and support, not only initial hardware cost.
Final engineering review
Before acceptance, test every input and permitted output, network loss, power return, manual override, and alarm escalation. Confirm that lighting, pumps, and valves return to defined safe states. Provide panel drawings, labels, user roles, contact lists, and configuration backups.
The project should also identify functions that NetRelay is not authorized to control. Clear boundaries around fire, elevator, gas, and emergency systems protect residents and service providers. A documented scope reduces accidental changes and helps a new maintenance contractor understand the installation without reverse engineering it.
Periodic review with management and technical staff keeps alarm priorities aligned with actual building operations, occupancy changes, and maintenance responsibilities.