Mobile App for Energy Consumption Monitoring

Imagine: at a 500 kW industrial facility, you have no hourly consumption data, exceeding the contracted power is a surprise at month-end. Penalties can reach 150,000 rubles per year. We develop mobile apps for energy consumption monitoring that solve this problem. In five years, we have delivered over 50 projects. A typical scenario: a meter with a Modbus RTU or P1 port outputs raw registers—voltage, current, power, accumulated energy in kWh. Without an app, these data are locked inside the cabinet. We turn them into a dashboard with charts and alerts, enabling savings of up to 30% on electricity. For example, on a 500 kW site, savings amount to about 200,000 rubles per year. Contact us for a free project assessment.

How to Set Up Energy Consumption Monitoring via a Mobile App?

Industrial electricity meters (Mercury 230, AGAT, Eastron SDM630) use Modbus RTU over RS-485. For residential smart meters (Sagemcom, Itron), DLMS/COSEM, M-Bus, or the P1 port (Dutch Smart Meter) are typical. Commercial models with GPRS/NB-IoT modules provide a cloud API from the manufacturer.

For Modbus meters, an RS-485 to Ethernet gateway (Moxa NPort, Anybus X-gateway) or an IoT gateway with a Modbus agent is required. The mobile app always works through a backend or MQTT broker—there is no direct connection to the meter. For the P1 port (Netherlands, Belgium), there are P1-to-MQTT adapters based on ESP32/Raspberry Pi that parse DSMR telegrams and publish to MQTT.

How to Aggregate and Store Data?

The meter outputs instantaneous values. The app needs trends per hour, day, month—this requires aggregation with storage. On the backend, use InfluxDB or TimescaleDB (PostgreSQL extension). TimescaleDB suits small installations: SQL queries, time_bucket function:

SELECT
  time_bucket('1 hour', time) AS hour,
  device_id,
  MAX(active_energy_kwh) - MIN(active_energy_kwh) AS consumption_kwh,
  AVG(active_power_w) AS avg_power_w
FROM energy_readings
WHERE device_id = $1
  AND time BETWEEN $2 AND $3
GROUP BY 1, 2
ORDER BY 1;

The difference between MAX and MIN of accumulated energy over a period gives consumption over that period. A simple and reliable formula, no deltas needed. TimescaleDB speeds up time-series queries by 2x compared to standard grouping.

Why Flutter and BLoC Are Better for Monitoring?

Flutter with BLoC enables cross-platform app development in a single codebase, reducing time-to-market by 1.7x compared to separate native developments. Tech stack: Dart, BLoC (Business Logic Component) for state management, fl_chart for histograms. Example dashboard:

class EnergyDashboardBloc extends Bloc<EnergyEvent, EnergyDashboardState> {
  final EnergyRepository _repo;
  StreamSubscription? _realtimeSub;

  EnergyDashboardBloc(this._repo) : super(EnergyDashboardInitial()) {
    on<LoadDashboard>((event, emit) async {
      emit(EnergyDashboardLoading());
      try {
        final current = await _repo.getCurrentReadings(event.meterId);
        final todayChart = await _repo.getHourlyConsumption(
          event.meterId,
          DateTime.now().subtract(const Duration(hours: 24)),
          DateTime.now(),
        );
        emit(EnergyDashboardLoaded(current: current, hourlyChart: todayChart));
        _startRealtimeUpdates(event.meterId);
      } catch (e) {
        emit(EnergyDashboardError(message: e.toString()));
      }
    });

    on<RealtimeUpdated>((event, emit) {
      if (state is EnergyDashboardLoaded) {
        emit((state as EnergyDashboardLoaded).copyWith(current: event.reading));
      }
    });
  }

  void _startRealtimeUpdates(String meterId) {
    _realtimeSub = _repo.realtimeStream(meterId)
        .listen((reading) => add(RealtimeUpdated(reading)));
  }
}

Dashboard cards: active power (kW), phase voltages (for three-phase meters: three values), cosφ (power factor), current day consumption, current month vs previous month consumption.

Consumption Chart — Mobile App Development

fl_chart with BarChart for hourly consumption is the standard in energy apps. Color coding by tariff zones (night tariff—blue, day—orange):

BarChartGroupData buildHourBarGroup(int hour, double consumption) {
  final isNightTariff = hour < 7 || hour >= 23;
  return BarChartGroupData(
    x: hour,
    barRods: [
      BarChartRodData(
        toY: consumption,
        color: isNightTariff ? Colors.blue.shade300 : Colors.orange.shade400,
        width: 12,
        borderRadius: const BorderRadius.vertical(top: Radius.circular(4)),
      ),
    ],
  );
}

What Is Included in Development?

We offer a turnkey service. Mobile app development for energy consumption monitoring includes:

• Analysis of your equipment and integration requirements
• Architecture design: backend (TimescaleDB/InfluxDB), API, mobile app
• Prototype development with a basic dashboard for approval
• Integration with existing meters and gateways (Modbus, DLMS, P1, cloud APIs)
• Server-side development: aggregation, alerts, user management
• Testing on real equipment
• Publishing on App Store and Google Play in compliance with guidelines
• Documentation and training for your operators

We guarantee integration quality and documentation. Typical development timeline: from 3 weeks for a single site to 3 months for a multi-site system with load management.

How to Set Up Power Overload Alerts?

Monitoring contractual power exceedance is key for commercial facilities. Exceeding maximum power leads to penalties from the energy supplier, which can reach 150,000 rubles per year. The backend logic checks a rolling 15-minute maximum; the mobile app receives an alert via FCM/APNs.

For Android, a push notification with PRIORITY_HIGH via FCM Data Message (not Notification Message) is delivered even in Doze mode. FCM Data Message is handled in FirebaseMessagingService.onMessageReceived() and displayed as a local notification with a custom sound.

Development Stages

How to Order Development?

1. Contact us for a free consultation.
2. We analyze your equipment and requirements.
3. Prepare a commercial proposal with an accurate timeline estimate.
4. After agreement, we start development with a prototype.
5. Iteratively refine, test, and publish the app.

Multi-Site Monitoring

For management companies overseeing 50-100 sites—a list of objects with color status indicators (normal/exceedance/no data), sorted by consumption. Lazy loading via ListView.builder with pagination of 20 objects.

Development of an app for monitoring a single meter with a dashboard and historical data: 3-4 weeks. Multi-site monitoring with load management and alerts: 2-3 months. Cost is calculated after analyzing equipment and requirements. Get a consultation—we will assess your project free of charge.

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.