This guide takes you from an Index AMI fresh out of the box to a meter sending readings to the AMI Platforms. The journey has two parts: a seven-step initial configuration and a set of additional features you enable according to your installation.
In this guide
Initial configuration
Before you start you need
- Index AMI HW3 gateway powered up (connected to the meter, an external 5–24 VDC source, or via a USB-A→USB-C cable from the PC for bench configuration).
- Configuration tool: Android app (Google Play; requires Bluetooth enabled — Android 12 or later) or desktop tool for Windows / Linux — you only need one.
- Compatible harness for your meter model (see the harness guide).
- Mobile operator credentials (APN) if using your own SIM instead of the Noatec SIM.
- Access to your MQTT broker or WireGuard server (if applicable in your deployment).
Estimated time
With a template available: create from existing format 2–5 min · load onto each device 2–3 min per unit.
Initial configuration
Follow these seven steps in order — each one prepares the next. By the end, the Index AMI will be reading the meter correctly.
01Choose and install your configuration tool
Pick one of the two options — you don't need both. The Android app is ideal for field installations; the desktop tool for mass deployments and advanced diagnostics.
- Android: download the Index AMI Gateway app from Google Play and install it on your Android 12 or later smartphone.
- Windows: download the .exe installer from soporte@noatec.co and run as Administrator.
- Linux: download the AppImage, make it executable with chmod +x and run it.
- Desktop tool only: app login admin / Admin1234! — change it in Tools → Settings → User account. The Android app has no app login of its own; its only access is the device login (admin/admin, Step 03).
02Connect the harness to the meter
Connect the compatible harness between the meter's serial port and the Index AMI phoenix connector. This step defines the protocol (RS485 or RS232) and communication speed.
- Identify your meter model in the compatibility table.
- Connect the harness to the correct meter port (RJ45-1, RJ45-2, DB9, RJ12 depending on model).
- Connect the other end to the Index AMI phoenix connector.
- Power up the Index AMI — the green LED should blink slowly.
03Connect via Bluetooth (BLE) and log in
From the desktop tool or Android app, establish the BLE connection with the Index AMI. BLE range: ~3 metres.
- A slow-blinking LED (~2 s) on the Index AMI means it is ready to pair. In the scan list, pick the unit with the best signal (ideally above -70 dBm).
- Desktop tool: go to Configure device (BLE) → Scan devices → select the Index AMI.
- Android app: Scan Devices button → select the Index AMI from the list → enter PIN 123456 if prompted.
- Device login: username admin, password admin (factory defaults). After login, the app downloads the device information (~60 s).
04Configure identification, NTP and ICMP
Assign a unique identifier to the Index AMI and synchronise its clock. This data appears in all logs and is essential for traceability.
- Custom label: unique code per unit (e.g. MET-NORTH-001).
- NTP host: pool.ntp.org (or your corporate network server).
- ICMP host: 8.8.8.8 — connectivity monitoring every 60 seconds.
- Scheduled restart: 24 h recommended for field deployments.
05Configure APN / LTE connectivity
Enter the operator APN so the Index AMI establishes the 4G data channel. Without this step the Index AMI has no internet access.
- Select the operator from the list (Noatec, Claro, Movistar, Tigo, Avantel) or enter a custom APN.
- Verify the connection: Overview → Device Status → assigned IP address.
06Configure meter protocol (UART / TCP)
Configure the serial communication mode with the meter. Use a predefined profile for compatible models — saves time and eliminates errors.
- Desktop tool: select the meter template and generate the conf.json.
- Mobile app: Connectivity Configuration → Profile / JSON button → select the meter from the list (predefined profile) or upload a conf.json file if no profile matches your specifications.
- Key parameters: UART mode (RS485/RS232), baud rate (9600 typical), TCP mode (port 8090).
- Apply changes — the Index AMI restarts (~30 s), BLE disconnects and the app does not reconnect on its own: scan and connect again to continue. This happens after every 'Apply changes'.
07Verify the first reading
Confirm that the Index AMI is reading the meter correctly before declaring the installation complete.
- Overview → Device Profile: verify label, firmware and synchronised UTC time.
- Overview → Device Status: confirm assigned IP and visible LTE operator.
- Overview → Connectivity Status: Bridge or MQTT status 'Connected'.
- Check AMI Platforms or broker logs — the first Index AMI messages should appear within 60 s.
- Hardening: change the device's factory credentials in Management → Security before dispatching to the field.
With the steps above the Index AMI is already reading the meter, but not yet delivering the data. To send the readings to your server or the AMI Platforms you must set up the communication channel — direct TCP, MQTT or WireGuard VPN — and, if needed, enable alerts. Configure whatever applies to your installation.
Additional features
08Activate WireGuard VPN· recommended
Establish the encrypted tunnel between the Index AMI and your server. Enables secure remote access for diagnostics and reconfiguration without a field visit.
- Requires a previously configured WireGuard server. See the server guide if not ready yet.
- Enable VPN in Connectivity Configuration → check the box → load the server public key and the client private key (.key). The Index AMI generates its own key pair internally.
- Verify the handshake: Overview → Connectivity Status.
09Configure MQTT· optional
Connect the Index AMI to your MQTT broker to publish readings and receive remote configuration commands. Skip this step if using only the direct TCP channel.
- Use MQTT over SSL (port 8883) in production — never unencrypted TCP on public networks.
- You need: broker hostname, unique client ID, CA and client certificates (.pem / .key).
- To set up your own broker: see the Mosquitto with TLS article.
10Configure alerts· optional
Enable critical event notifications: power cut, high temperature and digital switch.
- Last Gasp: always enable for field installations.
- Temperature: threshold 65 °C, hysteresis 5 °C, period 60 s for industrial panels.
- SWITCH1: configure the state (Low / High) according to the type of signal connected.
Tips for mass deployments
If you are installing several units, these tips save time in the field:
- Desktop tool flow: create one template per meter model and use the Generation Wizard (4 steps: select template → register devices → preview and validation → generate) to produce a conf.json per unit.
- BLE provisioning from the PC (Configure device): files are written in order — certificates first, conf.json last — so the device boots correctly with the new configuration.
- Every successful BLE provisioning creates an encrypted backup (AES-256) with a unique password per device under Tools → Recovery. Export your templates before switching PCs: they cannot be recovered from device backups.
- Physically label each Index AMI with its custom label before dispatch. A crossed dispatch causes problems that are hard to trace in the field.
- The WireGuard server and MQTT broker must be operational before deploying units in the field. Set them up with the IT team as a prior step.
- The Android app is ideal for field installations (BLE access without a laptop). The desktop tool is superior for mass deployments and advanced diagnostics.
Something not working?
- Meter not responding → RS485 diagnostics: bus not responding
- No LTE signal or disconnections → LTE signal on IoT devices: RSSI, RSRP, RSRQ
- VPN tunnel not coming up → WireGuard server: installation and configuration