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.