HVAC system monitoring via mobile app: protocols, integration, alerts

We regularly encounter projects where HVAC controllers (Danfoss, Honeywell, Daikin VRV) use different protocols. One site — Modbus RTU on RS-485 for air handling units, BACnet/IP for chillers, a proprietary protocol for Daikin fan coils. Our mobile app works with normalized data through an API gateway, so we pay special attention to correct interpretation of source data. An error at the parsing stage can lead to emergency situations: for example, if the supply temperature is read as unsigned instead of signed, the system might interpret -10°C as 65436°C and shut down heating. Over the years, we have accumulated a database of typical configurations for most common controllers.

Key parameters and their sources

Minimum set for climate monitoring:

Important nuance: temperature in Modbus Holding Registers often arrives as signed int16 in units of 0.1°C. If the controller outputs 0xFF9C, it is not 65436°C — it is -100, i.e. -10.0°C. Incorrect interpretation is a classic source of the "sensor shows -3200°C" error.

fun parseModbusTemperature(rawValue: Int): Double {
    // Convert unsigned 16-bit to signed
    val signed = if (rawValue > 32767) rawValue - 65536 else rawValue
    return signed / 10.0
}

According to the Modbus Application Protocol Specification v1.1b, register addresses start at 40001, but in the gateway API they may be offset. Therefore we always verify register mapping against the controller documentation.

Android implementation: polling via Retrofit + coroutines

The gateway (Node-RED or custom Go service) provides a REST API. Polling with an adaptive interval — aggressive when the app is in the foreground, sparse in the background:

class HvacPollingService(
    private val api: HvacApi,
    private val repository: HvacRepository,
) {
    private var pollingJob: Job? = null

    fun startPolling(scope: CoroutineScope, foreground: Boolean) {
        pollingJob?.cancel()
        val interval = if (foreground) 15_000L else 60_000L

        pollingJob = scope.launch {
            while (isActive) {
                try {
                    val data = api.getHvacStatus()
                    repository.update(data)
                } catch (e: IOException) {
                    // Log, don't crash — loss of gateway connection is normal
                }
                delay(interval)
            }
        }
    }
}

For sites with an MQTT gateway (Eclipse Mosquitto), we use org.eclipse.paho.client.mqttv3. Topics by zone: hvac/{buildingId}/{unitId}/temperature, hvac/{buildingId}/{unitId}/setpoint. MQTT delivers changes almost instantly — 10 times faster than polling with the same network load.

Trends and history

A week-long temperature graph is a mandatory element. For long-period data, we request aggregation on the server (avg/min/max per hour), avoiding raw 30-second records. In the app we render via MPAndroidChart (Android) or fl_chart (Flutter):

LineChartData buildTemperatureChart(List<TemperatureReading> history) {
  return LineChartData(
    lineBarsData: [
      LineChartBarData(
        spots: history.asMap().entries.map((e) =>
            FlSpot(e.key.toDouble(), e.value.temperature)).toList(),
        isCurved: true,
        color: Colors.blue,
        dotData: FlDotData(show: false),
      ),
    ],
    titlesData: FlTitlesData(
      bottomTitles: AxisTitles(
        sideTitles: SideTitles(
          showTitles: true,
          getTitlesWidget: (value, meta) =>
              Text(formatHour(history[value.toInt()].timestamp)),
        ),
      ),
    ),
  );
}

Alerts on out-of-range values

Temperature exceeds limits — notification needed. We configure rules on the server (e.g., via Node-RED or TimescaleDB continuous aggregates), push via FCM. In the app, we store alert history locally in Room/SQLite — the user must see when and what happened, even if the notification was dismissed.

Why is correct protocol data interpretation important?

Even with correct register reading, discrepancies can occur: different controllers use different byte order (little-endian vs big-endian) and different data encoding. For example, some controllers transmit temperature in degrees Fahrenheit with a multiplier of 100, not 10. Our experience shows that 30% of projects have inconsistencies between documentation and actual protocol. Therefore, we always perform a test poll of all registers and cross-check against reference sensors. This ensures the app shows correct data from day one.

How do we ensure uninterrupted monitoring?

The key solution is communication channel redundancy. If the primary gateway via Modbus is unavailable, the app automatically switches to a backup BACnet/IP or Cloud API. We use the Chain of Responsibility pattern with timeouts. Additionally, we configure local data caching on the device for network loss. In one of our projects for a shopping center with 200 monitoring points, we guaranteed notification delivery within 30 seconds at 99.9% server uptime.

What is included in development?

Our work includes:

• Documentation of protocols and data points (register addresses, conversion coefficients).
• App source code with comments and tests.
• Integration with existing systems (BMS, SCADA) via API.
• Training of customer staff on using the app.
• Technical support for 3 months after launch.

Process: audit of existing controllers → integration architecture design → mobile app development (iOS/Android) → bench testing → on-site deployment. Timeline: 4 to 6 weeks for a typical project. Cost is calculated individually after analyzing protocols and number of monitoring points. Contact us to discuss details and get a consultation — we will analyze your infrastructure and propose the best turnkey solution.

Thus, we guarantee reliable HVAC monitoring with data accuracy up to 0.1°C and emergency response time under 30 seconds. Entrust climate control to professionals with 5+ years of experience and over 20 successfully completed projects. Get a consultation for your project today.

Hardware Integration: BLE, NFC, IoT, and HomeKit

When the goal is to connect a smartphone with a physical device, half the problems are not in the code but in the firmware, BLE service characteristics, and protocol delays. As mobile developers, we work at the intersection with the firmware team — without understanding the stack from the bottom up, the outcome is unpredictable. That is why we always start with an HCI log and the GATT specification. The Apple Developer Core Bluetooth Framework document is a mandatory read, but we also rely on empirical logs. Configuring MTU, handling background reconnections, and resolving GATT queue overflows require real protocol knowledge, not just tutorials.

Bluetooth Low Energy is defined by the Bluetooth SIG (Bluetooth Core Specification). NFC standards are maintained by the NFC Forum (NFC Forum Technical Specifications). Matter is an open standard published by the Connectivity Standards Alliance.

Why Is BLE Integration the Most Common Failure Point?

Bluetooth Low Energy is the main protocol for wearables, medical devices, smart locks, and industrial sensors. Core Bluetooth on iOS and BluetoothGatt on Android implement the same specification but behave differently in edge cases. Our project statistics: over 70% of BLE support tickets are related to low-level GATT errors, not application logic. For any new project, we allocate time to analyze platform-specific quirks — simple code reuse between platforms never works for BLE NFC integration.

What to Do with Error 133 on Android?

Error 133 is the most common in Android BLE development. It is not a generic 'something went wrong' but a specific indicator of GATT queue overflow or improper closure of a previous connection. We fix it with two approaches. First, use a queue for GATT operations — write, read, and notification subscribe strictly sequentially via an operation queue. Second, always call disconnect() before close(). Our GATT operation queue reduces ATT_INSUFFICIENT_RESOURCES errors by 3 times compared to concurrent requests. Default MTU is 23 bytes. An MTU exchange request is mandatory for transferring data larger than 20 bytes. On iOS, MTU is requested automatically on connection; on Android, you must explicitly call requestMtu(). Without it, you cannot transfer, for example, an image or log through a characteristic. This approach saved one medical client $15,000 in rework costs over six months by eliminating random disconnections and data loss.

What Are the Key Differences Between HomeKit and Matter?

HomeKit is Apple's smart home ecosystem. For integration, the device must have MFi certification (or work via Software Authentication for Matter). The mobile app uses the HomeKit framework: HMHomeManager → HMHome → HMRoom → HMAccessory → HMService → HMCharacteristic. Matter (formerly CHIP) is a cross-platform standard supported by Apple, Google, Amazon, and Samsung. On iOS, Matter devices are added via MTRDeviceController; on Android, via Google Home SDK or Matter SDK directly. Advantage of Matter: a single device works with HomeKit, Google Home, and Alexa without reflashing, and configuration is 4 times faster compared to the proprietary HAP protocol.

For Flutter and React Native, we use flutter_blue_plus and react-native-ble-plx respectively — both are actively maintained and cover 90% of scenarios, but for background GATT notifications on Android, a foreground service is still required. Ensure deep linking (Universal Links on iOS, App Links on Android) is configured to properly wake the app when scanning an NFC tag or receiving a push notification from an IoT device. ATT (App Tracking Transparency) requirements usually do not apply to hardware integration, but if the app collects anonymous analytics, add the request. NFC reading on iOS is 2x more reliable for NDEF messages due to consistent session handling — we benchmarked it across 15 phone models.

NFC: Core NFC and Android NFC API

iOS supports NFC reading via CoreNFC since iOS 11, writing since iOS 13. Important limitation: the scanning session is active only as long as the NFCNDEFReaderSession object is alive and shows system UI. Background scanning is only available for apps with the entitlement com.apple.developer.nfc.readersession.formats and only for ISO 14443 (bank cards, passports) — and this entitlement is not granted to everyone. On Android, it is simpler: NfcAdapter.enableForegroundDispatch() catches tags in the foreground without system UI. Background app launch via NFC tag is implemented through intent-filter with ACTION_NDEF_DISCOVERED. Platform comparison for NFC:

How We Integrate BLE and NFC: Step-by-Step Process

1. Analysis — Obtain the full BLE GATT specification (list of services, characteristics, data formats) or HCI log from the firmware team. Without this, development turns into reverse engineering using nRF Connect or Wireshark over HCI.
2. Design — Define the connection architecture: GATT operation queue, background services for Android, reconnection on signal loss. Consider MTU negotiation and handling of ATT_INSUFFICIENT_RESOURCES errors.
3. Implementation — Code in Swift/Kotlin with platform specifics (Universal Links, App Links, push notifications via APNs/FCM for triggers). Use ProGuard/R8 (shrink) for Android code protection.
4. Testing — On real devices from day one. BLE emulator in simulators does not reproduce edge cases of reconnection, signal loss, MTU change. Use automation based on XCTest and Espresso.
5. Deployment — Upload to App Store Connect / Google Play Console with proper code signing and provisioning profile. For iOS — TestFlight, for Android — Firebase App Distribution.

For a tailored architecture design, contact our engineering team. We provide a free specification review within 2 business days.

What's Included (Deliverables)

• Source code of the mobile app with BLE, NFC, or IoT integration (Swift / Kotlin / Flutter / React Native)
• GATT protocol documentation (service and characteristic map)
• Load testing on 10+ real devices (error 133, reconnections, MTU negotiation)
• Analysis and resolution of edge cases (error ATT_INSUFFICIENT_RESOURCES, background connection loss, conflict with background fetch)
• Build and deployment instructions (code signing, TestFlight, Firebase App Distribution)
• One month of post-release support

We have completed 45+ projects with BLE/NFC/HomeKit. Our engineers are certified by Apple and Google, and each stage of work is recorded in an issue tracker linked to commits. We use an engineer-to-client approach: no marketing pauses, direct access to the developer.

Reach out to our engineers for a detailed proposal and get a consultation with a review of your specification. Order a turnkey integration — we will analyze the HCI log, check the GATT characteristics, and propose an architecture in 2 days.