This guide will help you configure your Z3 NetMeter OMNI device to send data to ioTORQ EMIS through HTTPS.
Prerequisites
Before you begin, you'll need:
A Z3 NetMeter OMNI device with internet connectivity
An ioTORQ EMIS account with API access
Access to your Z3 NetMeter's configuration interface
Your ioTORQ EMIS domain name whitelisted in your company firewall to allow outbound HTTPS connections from the NetMeter
Step 1: Request an API Token
Contact ioTORQ EMIS support to request an API token for your Z3 NetMeter integration:
Email: [email protected]
Include in your request:
Your ioTORQ EMIS account name
The purpose: Z3 NetMeter integration
Number of devices you plan to connect
A name for each device
Once you receive your API token, save it securely - you'll need it in Step 3.
Step 2: Create Automatic Variables
For each measurement channel on your Z3 NetMeter, you need to create a corresponding variable in ioTORQ EMIS:
In ioTORQ EMIS, navigate to Variables → New Automatic Variable
Create a new automatic variable for each channel you want to track
Use this naming format for the variable code:
Z3.{device_id}.ch{channel_number}Configure the units (kWh, kW, etc.) and other properties for each variable as needed
Example
If you want to identify your device as METER_A and have 3 channels:
Create variable with code:
Z3.METER_A.ch0(for channel 0)Create variable with code:
Z3.METER_A.ch1(for channel 1)Create variable with code:
Z3.METER_A.ch2(for channel 2)
Important: The device ID you choose here must match exactly what you configure in Step 3.
Step 3: Configure Your Z3 NetMeter
Access your Z3 NetMeter's configuration interface and set up the push API:
Host URL
Set the push URL to your ioTORQ EMIS instance:
your-instance.iotorq.com/ems/api/import/z3/
Replace your-instance.iotorq.com with your actual ioTORQ EMIS domain.
Protocol
Use "HTTPS"
Port number
Use 443
ApiKey
Configure the ApiKey header using this format:
{api_token}:{device_id} Where:
{api_token}: The API token you generated in Step 1{device_id}: A unique identifier that you choose for this device (must match the variables created in Step 2)
Example:
f809ccb1fca84a4af9e9c14a413b8069377e0e5f:METER_A
Important: The device ID is case-sensitive and must match exactly with your variable names
Method:
POST
Data Packet Format:
JSON
Data to Transmit
Configure which measurement channels the NetMeter should export to ioTORQ EMIS.
Step 4: Test the Connection
After configuring your NetMeter, test the connection:
Check the NetMeter's debug screen (Setup -> Data Push Configuration) for successful connection messages. If there is a problem communicating with the server, the “Comm. Errors” field will be incremented and the error type will be indicated in “Last Error Code” in addition to a timestamp of when the last error occurred.
In ioTORQ EMIS, navigate to your automatic variables
Verify that data is being received within a few minutes
If you don't see data:
Verify the push URL is correct
Check that the ApiKey format is exact (token:device_id)
Ensure the automatic variables were created with the correct naming pattern
Review the NetMeter Push API documentation for error messages: https://www.z3controls.com/doc/Z3-NetMeter-OMNI-Push-API-Spec(1.0.3).pdf
How It Works
Automatic Data Upload
Once configured, your Z3 NetMeter will automatically:
Send timestamped measurement data to ioTORQ EMIS at regular intervals
Buffer data during internet outages and upload when connectivity is restored
Recover from power losses and device reboots
Synchronization After Outages
When your NetMeter reboots or recovers from a power loss:
It contacts the ioTORQ EMIS server to check what data has already been received
It uploads only the data that the server hasn't received yet
This prevents duplicate data and ensures efficient bandwidth usage
The system can recover data from outages up to 30 days long.
Troubleshooting
No Data Appearing in ioTORQ EMIS
Check these common issues:
Variable naming mismatch: Verify your automatic variables use the exact format
Z3.{device_id}.ch{channel_number}where{device_id}matches your NetMeter configurationIncorrect ApiKey format: Must be
{api_token}:{device_id}with a colon separator, no spacesInvalid API token: Verify the API token provided by EMIS support match the one used in the configuration
Wrong push URL: Ensure you're using your correct ioTORQ EMIS instance domain
Variables not created: Create automatic variables before the NetMeter starts sending data
Support
If you encounter issues that you cannot resolve:
Contact: [email protected]
Include in your support request:
Your device ID
Z3 NetMeter firmware version
Error messages from the NetMeter debug logs
Screenshots of your NetMeter configuration (if applicable)