Mobile App Development for BMS Building Management

BMS projects start the same way: the client shows a building diagram with controllers from Siemens Desigo CC, Schneider Electric EcoStruxure, or Johnson Controls Metasys and says, "We want all this on a phone." Behind that "all this" are dozens of protocols, polling cycles from 1 second to 15 minutes, a historical database going back years, and the requirement to work even when the main BMS server reboots. We take such projects turnkey: from protocol analysis to publishing in stores. Our experience: 10+ years in BMS integration and over 50 implemented sites. We evaluate the project in 2 days and guarantee stable operation under any load.

Protocols and Gateways

Industrial BMS systems speak BACnet/IP, Modbus TCP/RTU, KNX/IP, and LonWorks. They are not directly accessible from a mobile app—between the controllers and the REST/WebSocket API sits a gateway or middleware.

Typical integration stack:

Niagara Framework 4 (Tridium) is the de facto standard for large sites. It normalizes BACnet objects into a unified REST API (/haystack/api/read?filter=bacnet) and provides WebSocket streams of changes. Working with Haystack API via Dart:

class HaystackClient {
  final Dio _dio;
  final String _baseUrl;

  HaystackClient(this._baseUrl, String username, String password) :
    _dio = Dio(BaseOptions(
      baseUrl: _baseUrl,
      headers: {
        'Authorization': 'Basic ${base64Encode(utf8.encode('$username:$password'))}',
        'Accept': 'application/json',
      },
    ));

  Future<List<HaystackRow>> read(String filter) async {
    final response = await _dio.get('/haystack/api/read',
        queryParameters: {'filter': filter});
    final grid = HaystackGrid.fromJson(response.data);
    return grid.rows;
  }

  Future<Map<String, dynamic>> readPoint(String pointId) async {
    final response = await _dio.get('/haystack/api/hisRead',
        queryParameters: {
          'id': '@$pointId',
          'range': 'today',
        });
    return response.data;
  }
}

For sites with an MQTT gateway (Node-RED converts BACnet → MQTT JSON), we use the mqtt_client in Flutter. Topics are organized by building hierarchy: building/{buildingId}/floor/{floor}/zone/{zone}/{parameter}.

How We Integrate with Existing BMS?

The process always starts with an audit of the controllers: we find out which protocols are used, which version of Niagara or other middleware is installed, whether a REST/WebSocket API already exists or a gateway needs to be deployed. Then we design the data flow scheme: which points are read, which are written, and at what interval. Certified engineers configure the gateway and perform integration testing. The result is a unified interface on the phone instead of multiple control panels.

Real-Time Data Architecture: Why a DataHub is Critical?

The most challenging part of a BMS app is not the connection but managing the data stream. Temperature in 200 zones updates every 30 seconds, lighting changes by event, energy consumption every minute. All this cannot be resubscribed on every UI redraw.

The solution is a centralized DataHub at the application level:

class BmsDataHub {
  final MqttClient _mqtt;
  final _streams = <String, BehaviorSubject<BmsPoint>>{};

  Stream<BmsPoint> watchPoint(String pointId) {
    if (!_streams.containsKey(pointId)) {
      _streams[pointId] = BehaviorSubject();
      _mqtt.subscribe('building/+/+/+/$pointId', MqttQos.atLeastOnce);
    }
    return _streams[pointId]!.stream;
  }

  void _onMessage(List<MqttReceivedMessage<MqttMessage>> events) {
    for (final event in events) {
      final topic = event.topic;
      final payload = MqttPublishPayload.bytesToStringAsString(
          (event.payload as MqttPublishMessage).payload.message);
      final point = BmsPoint.fromJson(jsonDecode(payload));
      _streams[point.id]?.add(point);
    }
  }
}

BehaviorSubject from the rxdart package retains the last value—so a widget that subscribes after data arrives immediately gets the current state without waiting for the next polling cycle.

Interactive Floor Plan

Customers always want a building floor plan with live data. We convert DXF or SVG plans to SVG (via ODA File Converter for DXF), render them with flutter_svg and InteractiveViewer. Sensor points are overlaid onto the SVG using normalized coordinates:

class FloorPlanWidget extends StatelessWidget {
  final FloorPlan plan;
  final Map<String, BmsPoint> liveData;

  @override
  Widget build(BuildContext context) {
    return LayoutBuilder(builder: (context, constraints) {
      return Stack(children: [
        SvgPicture.asset('assets/floors/${plan.id}.svg',
            width: constraints.maxWidth),
        ...plan.sensors.map((sensor) => Positioned(
          left: sensor.x * constraints.maxWidth,
          top: sensor.y * constraints.maxHeight,
          child: SensorMarker(
            point: liveData[sensor.pointId],
            type: sensor.type,
          ),
        )),
      ]);
    });
  }
}

Markers change color based on thresholds: green (normal), yellow (warning), red (alarm). Thresholds are fetched from the BMS configuration—no hardcoding.

Control: Writing Values to BACnet Points

Reading is easier than writing. To command BACnet points (temperature setpoint, light on/off) via the REST gateway:

Future<void> writePoint(String pointId, dynamic value) async {
  // Optimistic UI update
  _hub.updateLocally(pointId, value);

  try {
    await _api.put('/haystack/api/pointWrite', data: {
      'id': '@$pointId',
      'level': 8,  // BACnet write priority (1-16, lower = higher priority)
      'val': value,
      'who': _authService.currentUser,
      'duration': 'PT0S',  // permanent
    });
  } on DioException catch (e) {
    // Roll back on error
    _hub.revertLocally(pointId);
    rethrow;
  }
}

BACnet Priority Array is a detail often overlooked—leading to confusion why a setpoint won't change: the controller accepts commands but they are overridden by a higher priority from BMS scheduling (level 2-4). Level 8 is standard for manual operator commands.

Alerts and Event Log

Alarm events from the BMS come via MQTT or WebSocket. Local push notifications are generated with flutter_local_notifications, server push (when the app is closed) via FCM with high priority (priority: high, content_available: true).

Event log: SQLite via drift for offline storage of 30 days of history, paginated loading from the API for older entries.

Access Control

On real sites, different users see different floors and zones. Rights are stored on the backend; the mobile client requests the list of accessible objects on login and does not build routes to inaccessible resources. Attempting to write to a forbidden point returns HTTP 403, triggering a local rollback and user notification.

What Is Included in Development?

• Analysis of controller protocols and BMS architecture.
• Design of integration scheme and data flows.
• Implementation of mobile client (iOS/Android on Flutter or native stack).
• Gateway configuration and integration testing.
• Publication in App Store and Google Play.
• 30 days of technical support after release.
• API documentation and staff training (optional).

Timeline and Cost

Cost is calculated individually after analysis of your controllers and requirements. Contact us for an evaluation—we will prepare a commercial proposal within 2 business days.

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.