Overview
Plugins are what bring MicroPowerManager to life. The Open Source core manages customers, devices and payments. Plugins connect that core to the external services and APIs a utility actually runs on. This makes it possible to integrate third-party systems without modifying the core application.
Anyone can build a plugin and contribute it to the Open Source project. See the Plugin Development Guide to get started.
Typical examples include:
- Manufacturer integrations (for token generation or remote management)
- Transaction providers (e.g. mobile money) or Payment aggregators
- Data import and export services
- External communication interfaces
Most plugins require an initial setup. This usually includes:
- Providing credentials for the external service
- Configuring synchronization intervals
- Defining connection parameters
After the initial configuration, plugins generally run without requiring changes in day-to-day operations.
INFO
The words plugin and integration are mostly used interchangeably. The integration of an external party or service with MicroPowerManager is implemented through development of a plugin.
Plugin overview
The following plugins are available, grouped by category. Each plugin links to its guide. A plugin whose documentation is marked as missing only has a placeholder page.
Payments and Mobile Money
| Plugin | Status | Documentation | Comment |
|---|---|---|---|
| Flutterwave Payment Provider | ✅ Ready | ✅ Ready | Hosted checkout via public payment URL; sandbox + production |
| Paystack Payment Provider | ✅ Ready | ✅ Ready | Hosted checkout via public payment URL; test + production |
| Pesapal Payment Provider | ✅ Ready | ✅ Ready | Hosted checkout via public payment URL; sandbox + production |
| Safaricom M-PESA (Daraja) Payment Provider | ✅ Ready | ✅ Ready | STK Push via operator-facing Initiate Payment page; sandbox + production |
| Vodacom MZ / M-Pesa | ✅ Ready | ✅ Ready | Production use requires Vodacom to validate test-environment transactions |
| Wavecom Payment | ✅ Ready | ❌ Missing | Manual: MicroPowerManager users must export transaction data, paste into template, and upload |
| Mesomb Payment | ⚠️ Requires refactoring | ❌ Missing | |
| Swifta Payment | ⚠️ Requires refactoring | ❌ Missing | |
| Wave Money Payment | ⚠️ Requires refactoring | ❌ Missing |
Reporting and Data Interfaces
| Plugin | Status | Documentation | Comment |
|---|---|---|---|
| Prospect Integration | ✅ Ready | ✅ Ready | |
| Odyssey Energy Integration | ✅ Ready | ✅ Ready | Odyssey pulls transaction and customer data from MicroPowerManager |
| ECREEE e-Tender Integration | ✅ Ready | ✅ Ready | e-Tender retrieves transaction and operational data for milestone verification |
| Bulk registration | ✅ Ready | ✅ Ready |
Devices and Manufacturer (OEM)
| Plugin | Status | Documentation | Comment |
|---|---|---|---|
| Steama Meter Integration | ✅ Ready | ✅ Ready | Periodic sync of sites, customers, meters, agents, and transactions |
| Spark SHS integration | ✅ Ready | ✅ Ready | |
| Angaza Solar Home System | ✅ Ready | ❌ Missing | |
| DalyBms (e-bike) | ✅ Ready | ❌ Missing | Battery Management System API, works only with e-bikes with Daly BMS installed |
| Gomelong Meter | ✅ Ready | ❌ Missing | |
| Microstar Meter | ✅ Ready | ❌ Missing | Companies have to make an agreement with MicroStarElectric to get their .p12 certificate |
| Stron Meter | ✅ Ready | ❌ Missing | |
| Calin Meter | ⚠️ Requires refactoring | ❌ Missing | |
| Calin Smart Meter | ⚠️ Requires refactoring | ❌ Missing | |
| Chint Meter | ⚠️ Requires refactoring | ❌ Missing | |
| Spark Meter | ⚠️ Requires refactoring | ❌ Missing | |
| Kelin Meter | ❌ Broken | ❌ Missing | They do not provide API anymore |
Communication and SMS
| Plugin | Status | Documentation | Comment |
|---|---|---|---|
| AfricasTalking SMS Gateway | ✅ Ready | ✅ Ready | |
| TextBee SMS Gateway | ✅ Ready | ✅ Ready | Uses an Android device you own as the SMS gateway |
| Viber Messaging | 🌑 No longer supported | ❌ Missing | No longer usable due to new strict chatbot criteria |
