Introduction

When we refer to Tower Monitoring in Genesis, we are describing an integrated ecosystem of multiple IoT subsystems working together to ensure the tower’s operational continuity, energy efficiency, and communication reliability.
Each subsystem plays a distinct but interconnected role, contributing to the tower’s overall intelligence and autonomy.

• Victron Energy oversees Power and Energy Monitoring, tracking parameters such as battery voltage, charging current, solar input, and load consumption. This ensures that the energy system operates within safe thresholds and provides early warning of battery or solar irregularities.

• EFOY Fuel Cells enable Fuel Cell Backup Monitoring, safeguarding critical uptime by reporting fuel levels, voltage output, state of charge, and internal temperature — essential for remote sites relying on autonomous energy sources.

• Teltonika IoT Devices manage Network Connectivity and Device Health Monitoring, including mobile network quality, SIM data usage, geofencing, input/output state changes, and advanced jamming detection for communication assurance.

Together, these intelligent systems form a unified monitoring architecture within Genesis. They continuously stream telemetry data from distributed towers into the Genesis IoT cloud, where it is analyzed, stored, and correlated with configurable alarm rules.

System Overview

Each device — whether it’s a Victron solar/battery controller, EFOY fuel cell, or Teltonika router — periodically reports status and sensor values to Genesis using secure communication channels.
These data points are evaluated in real time against pre-defined alarm thresholds and logic rules. When a condition breaches the configured limits, Genesis automatically:

1. Generates event alerts (using the assigned event codes and group codes).

2. Notifies the appropriate operator or system, through respective CMS channels (Evalink, AmWin, Lisa, IMMIX, etc...)

3. Tracks the event lifecycle, ensuring alerts are automatically cleared/restored when the parameters return to their normal range.

This end-to-end monitoring pipeline transforms raw device data into actionable intelligence, allowing operators to detect risks early, respond faster, and maintain consistent tower uptime across all remote locations.

Configuration Overview

In Genesis, each tower integrates multiple device types — each with its own configuration logic and threshold rules. The configuration defines how the system interprets sensor values, detects abnormal conditions, and triggers the appropriate alerts.
This section explains how configuration is structured for the three core subsystems: Victron Energy, EFOY Fuel Cell, and Teltonika IoT Connectivity.

Victron Energy Monitoring Configuration

Victron devices act as the primary power monitoring system of the tower, focusing on solar charging performance, battery health, and overall DC system voltage.

Victron Configuration in Genesis

To enable Victron Energy Monitoring within Genesis, the system requires certain key inputs that allow it to securely connect to the Victron VRM portal and retrieve live operational data from the associated devices.

1. Device Type: Victron

2. Device Name: A valid and unique name for identification in Genesis.

3. Serial Number: The serial number of the device, obtainable from the Victron VRM Portal.

4. Username and Password: Credentials with administrative privileges to access or read the configured device in the VRM Portal.
   

Configuration Screenshot

EFOY Fuel Cell Monitoring Configuration

EFOY devices provide backup power generation for sites where continuous power is critical. Their configuration ensures the fuel cell remains in optimal operating condition.

EFOY Configuration in Genesis

1. Device Type: EFOY Cloud

2. Device Name: A valid and unique name for identification in Genesis.

3. Serial Number: The unique serial number of the fuel cell, as listed in the EFOY Cloud Portal.

4. EFOY API Key: A valid API key with sufficient privileges to access all Solar and Power Controller parameters. It must be configured at Tenant level custom settings. Please find the screenshot below: 

1. Select the tenant
   

2. Click Edit
   

3. Goto Custom Property
   

4. Click Add
   

5. Name the property as "EFOYAPIKey" and provide the original API key as value.
   

6. Click Save.
   

Configuration Screenshot

In the IP Address field, you may optionally specify the EFOY Cloud API endpoint instead of a local device address. The Username and Password fields are optional. however, you can provide valid EFOY Cloud credentials as a backup to the API key.

Configuration Outcome

Once configured, Genesis connects securely to the EFOY Cloud API and begins fetching live operational data. This includes parameters such as fuel cell voltage, output power, cartridge level, energy generation rate, and system health—providing complete visibility into fuel cell performance and runtime efficiency.

Teltonika IoT Connectivity Configuration

Teltonika devices manage connectivity, communication, and environmental interaction for each tower. They report detailed I/O status, network health, SIM usage, GPS, and signal jamming conditions.

Teltonika IOT Configuration in Genesis

To enable Teltonika IOT Router within Genesis, the system requires certain key inputs that allow it to securely connect to the router and retrieve live operational data from the associated devices.

1. Device Type: Teltonika-IOT

2. Device Name: A valid and unique name for identification in Genesis.
   

3. IP Address: The public or VPN-accessible IP address of the Teltonika device.

4. Serial Number: The unique serial number of the router.
   

5. Control Port: The valid HTTP port used for device communication.
   

6. Username and Password: Administrative credentials that allow full access to all device parameters and subcomponents.

Configuration Screenshot

Configuration Outcome

Once connected, Genesis establishes a secure communication channel with the Teltonika Router, enabling continuous monitoring of key metrics such as signal strength, network uptime, connected I/O states, and environmental sensor data. Any deviations—such as loss of connectivity, abnormal input voltage, or I/O threshold breach—are automatically logged and can trigger real-time alerts to CMS.

Alarm Rules Overview

This section outlines the structure, purpose, and usage of the alarm rules configuration used for remote tower monitoring within Genesis.
Each part of the configuration defines a monitored category, its key parameters, and the conditions under which alerts are raised.

Configuring Alarm Rules

The Alarm Rules in Genesis are defined in JSON format, allowing precise and flexible configuration of alerting behavior.
Rules can be configured at either the Site level or Device level, depending on the monitoring scope.

To configure alarm rules:

1. Navigate to the desired Site or Device in Genesis.

2. Click Edit and go to the Additional Properties section.

3. Locate the property named Custom Alarm Rules.

4. Open the property’s hamburger menu and select Apply Default to load the preconfigured default rule set.

   • By default, all rules are inactive.

5. Modify the JSON configuration to enable specific rules by setting the "active" parameter to true for the relevant parameters.

6. Once saved, Genesis automatically applies the configured thresholds, continuously evaluates incoming telemetry, and triggers alerts when any parameter exceeds or falls below its defined range.

Victron Energy Monitoring

Battery Voltage Rule

"voltage": {
  "active": false,
  "low": 12,
  "high": 14,
  "eventCode": "battery.voltage.warning",
  "groupCode": "tower.solar.voltage.alert"
}

Battery State of Charge (SOC) Rule

"stateOfCharge": {
  "active": false,
  "low": 15,
  "eventCode": "battery.soc.warning",
  "groupCode": "tower.battery.soc.alert"
}

EFOY Fuel Cell Monitoring

Fuel Level Rule

"fuelLevel": {
  "active": false,
  "low": 15,
  "eventCode": "fuel.low.warning",
  "groupCode": "tower.fuel.level.alert"
} 

Voltage Rule

"voltage": {
  "active": false,
  "low": 12,
  "high": 15,
  "eventCode": "fuel.voltage.critical",
  "groupCode": "tower.fuel.voltage.alert"
}

State of Charge Rule

"stateOfCharge": {
  "active": false,
  "low": 15,
  "eventCode": "fuel.soc.warning",
  "groupCode": "tower.fuel.soc.alert"
}

Temperature Rule

"temperature": {
  "active": false,
  "low": 10,
  "high": 35,
  "eventCode": "fuel.temperature.warning",
  "groupCode": "tower.fuel.temperature.alert" 

Teltonika IoT Connectivity

Input/Output Status Change Rule

"IOStatusChange": {
  "input": {
    "AnalogCurrentLoop": {"active": false, "low": 4, "high": 20},
    "AnalogInput": {"active": false, "low": 11, "high": 14},
    "DigitalInput": {"active": false, "ranges": ["Low level", "High level"], "alertOn": "High Level"},
    "IsolatedInput": {"active": false, "ranges": ["Low level", "High level"], "alertOn": "High Level"},
    "PowerSocketInput": {"active": false, "ranges": ["Low level", "High level"], "alertOn": "High Level"},
    "eventCode": "input.statechange",
    "groupCode": "tower.input.statechange"
  },
  "output": {
    "IsolatedOutput": { "active": false, "ranges": ["Low level", "High level"], "alertOn": "High Level" },
    "Relay": { "active": false, "ranges": ["open", "closed"], "alertOn": "open" },
    "PowerSocketOutput": { "active": false, "ranges": ["Low level", "High level"], "alertOn": "High Level" },
    "eventCode": "output.statechange",
    "groupCode": "tower.output.statechange"
  }
}

Analog Current Loop

Analog Input

Digital / Isolated / Power Socket Inputs

Isolated / Power Socket Outputs

Relay Output

SIM Card Data Package Usage Rule

"simCardDataPackage": {
  "active": false,
  "simBillingStartDate": 1,
  "simDataPackageGB": 10,
  "usageWarningPercent": 80,
  "eventCode": "sim.data.usage.warning",
  "groupCode": "tower.connectivity.simdata.alert"
}

Configuration Parameters

• Triggers an alert when data usage exceeds 80% of 10GB.
  

Cellular Network Loss Rule

"cellNetworkLoss": {
  "active": false,
  "eventCode": "modem.signal.warning",
  "groupCode": "tower.connectivity.signal.alert"
}

Geo-Fencing Rule

Default JSON Configuration

"geoFencing": {
  "active": false,
  "radiusMetersWarning": 500,
  "eventCode": "geo.fence.breach",
  "groupCode": "tower.connectivity.geofence.alert"
}

This rule continuously monitors the GPS coordinates reported by the Teltonika router or GPS module.
If the device moves outside the configured radius, Genesis generates an alert indicating a potential tower displacement or unauthorized movement.
The location boundary is defined by the configured coordinates of the parent Site, ensuring that alerts are triggered only when the tower moves beyond its designated operational area.

Jammer Detection Rule

Default JSON

"jammerDetection": {
  "active": false,
  "criteria": {
    "signalDropThreshold": 25,
    "minSignalLevel": -113,
    "rsrqThreshold": -20
  },
  "eventCode": "modem.jammer.detected",
  "groupCode": "tower.connectivity.jamming.alert"
}

Configuration Notes

• Each rule has an active flag. When false, the system skips that rule.

• Thresholds can be adjusted per site depending on environmental conditions.

• Event Codes are unique identifiers used internally within Genesis for system integrations — particularly for notifying external Central Monitoring Systems (CMS) or third-party applications. They ensure consistent and standardized communication of alarm events across different platforms.

• Group Codes, while similar in structure to Event Codes, are specifically utilized within the Tower Monitoring Environment. They serve as logical identifiers for grouping related alarms, enabling efficient organization, filtering, and management of events within Genesis and its tower-level alerting workflows.