The Tower Monitoring architecture follows a distributed design that enables autonomous operation at remote tower sites while maintaining centralized visibility and control through the Genesis platform.
The diagram below illustrates how the Victron Energy, EFOY Fuel Cell, and Teltonika IoT subsystems interact within the tower ecosystem and how telemetry and alarms are transmitted to the command center.

At the site level, Victron manages solar and battery performance, EFOY ensures backup power availability, and Teltonika provides communication, GPS tracking, and edge telemetry routing. These subsystems communicate securely with their respective cloud services, where Genesis collects real-time operational data through authenticated API channels.

Within Genesis, this incoming data is normalized, correlated, and continuously analyzed against configured alarm rules. Any deviation—such as low battery voltage, reduced solar input, fuel depletion, or network loss—triggers an alarm routed automatically to the operator console or central monitoring system.

This distributed yet unified architecture ensures every tower operates independently in the field while maintaining synchronized health and alarm visibility across all sites in the Genesis command center.

The Tower Monitoring architecture is organized in five layers that describe how field telemetry becomes alarms and operator actions in Genesis.

Field Layer — Devices and Sensors

This layer contains the hardware installed at each tower site and the telemetry each device provides.

• Victron Energy devices (MPPTs, Battery Monitors, Inverters) supply power metrics such as battery voltage, charging current, state of charge, solar input, and system alarms. These devices are typically published to the Victron VRM cloud for remote access.

• EFOY Fuel Cells report fuel cartridge level, runtime estimates, output voltage, and internal temperature. They usually push data to the EFOY Cloud.

• Teltonika-IOT routers handle network connectivity, GPS position, SIM data usage, input/output status, and jamming detection. They provide both status telemetry and remote I/O for site control.

Each device continuously collects sensor data and health indicators that are required for both routine monitoring and alarm detection.

Edge Communication Layer — Local and Mobile Links

This layer covers how devices reach the cloud when fixed infrastructure is not available.

• Victron devices forward telemetry to the Victron VRM service via internet connectivity provided by the site router or cellular uplink.

• EFOY devices forward to the EFOY Cloud using the configured cellular or gateway connection.

• Teltonika routers provide the primary WAN link for the tower, and may also expose local device endpoints (SNMP, HTTP, or vendor APIs) used by on-site systems.

The router also supplies remote access and optional VPN channels. Local I/O states and short term buffering occur here when connectivity is intermittent.

Cloud Aggregation Layer — Vendor Clouds and APIs

Vendor cloud platforms centralize device telemetry and present secure APIs that Genesis consumes.

• Victron VRM API provides real time device metrics required for energy monitoring rules.

• EFOY Cloud API exposes fuel cell telemetry and status reports.

• Teltonika Cloud / Local API supplies router diagnostics, SIM usage statistics, GPS, and I/O states.

Genesis connects to these cloud APIs using tenant level credentials, API keys, or account credentials to retrieve device lists, telemetry streams, and event logs.

Integration Layer — Genesis IoT Engine

Genesis normalizes vendor telemetry and applies alarm logic.

• Genesis discovers devices via cloud API calls and registers them under the tenant and site mapping.

• Incoming telemetry is parsed and mapped to Genesis device models (Energy Monitoring, Fuel Cell Monitoring, Connectivity Monitoring).

• Configurable alarm rules (JSON) evaluate the telemetry against thresholds, delays, and compound logic. Example rule groups include: Battery Voltage, Charger Status, Fuel Level, Network Loss, SIM Overuse, Input State Change, and Jammer Detection.

• When a rule is triggered, Genesis generates an event with assigned event codes, stores related telemetry, and attaches any available verification media.

Monitoring Layer — Command Center and CMS Integration

This layer covers how operators receive and act on alerts.

• Events are routed to operator consoles via integrated CMS channels such as IMMIX, AmWin, Evalink, or LISA.

• Each event lifecycle is tracked: creation, escalation, acknowledgement, and automatic clear/restoration when parameters return to normal.

• Genesis supports operator actions such as remote device commands (e.g., Teltonika remote restart, Victron remote setpoints if supported), notification workflows, and maintenance tickets.
  

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

Configuration Outcome

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.

The Custom Alarm Rules configuration JSON in Genesis is structured into three main sections: Energy Monitoring, Fuel Cell Monitoring, and Connectivity Monitoring.

• The Energy Monitoring section contains alert configurations specific to Victron devices, covering parameters such as battery voltage, and state of charge.

• The Fuel Cell Monitoring section defines alert rules for EFOY systems, including fuel level, voltage, temperature, and state of charge thresholds.

• The Connectivity Monitoring section manages alerts for Teltonika IoT devices, covering aspects such as network signal quality, SIM data usage, input/output status changes, and jammer detection.

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

• When voltage falls below 12V, an alert with event code battery.voltage.warning is raised.

• When voltage returns within range (12V–14V), Genesis automatically logs the recovery event and clears the alert.

• When voltage exceeds 14V, a high-voltage warning is generated.

Monitors the remaining charge percentage in the battery bank.

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

• SOC below 15% triggers low battery alert.

• Restores to normal when SOC rises above the threshold.

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

• Below 10°C or above 35°C → Thermal warning.

"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"
  }
}

Default JSON Configuration

Default JSON Configuration

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

An alert is triggered when the network signal drops very low. Genesis automatically clears the alert when the signal back to acceptable range.