Rectifiers, battery strings, generators, shelter HVAC, door sensors and edge devices publish over MQTT; ConnectMQ delivers it to your NOC dashboards, OSS and field service tools. Know about a mains failure while the batteries are still carrying the load.
No card required
PUBLISH telco/north/site-ank-1187/power/rectifier
{"mains":"fail","dc_v":51.2,"load_a":38.5,"batt_soc":86,"runtime_min":142,"ts":"2026-10-22T03:17:55Z"}QoS 1 · TLS 8883 · PUBACK
Radio and transport equipment is managed by vendor element managers and the OSS, but the passive infrastructure — power, batteries, generator fuel, cooling, doors — often still runs on SNMP traps, legacy RTUs and site visits. Battery runtime surprises, failed air conditioners and break-ins are found when the site goes off air, and CPE and edge devices at customer premises add yet another fleet to watch.
A site controller or RTU reads rectifiers, battery strings, the generator and HVAC over Modbus or SNMP, plus door, smoke and fuel sensors.
It publishes to telco/{region}/{site}/{system} over TLS, with power and HVAC state retained and alarms sent as events with QoS 1.
Threshold rules flag mains failure, low battery voltage or a hot shelter; the live dashboard shows sites by region, and Last Will marks a site controller that went silent.
Your OSS or alarm manager correlates site alarms with radio alarms, field service sends a technician or a mobile generator, and the energy team tracks consumption per site.
A clear topic per region, site and system; wildcard subscriptions let the NOC see everything and a regional team only its own region.
MQTT’s small overhead and keepalive suit sites on microwave, LTE or satellite links, and QoS 1 resends an alarm until the broker acknowledges it.
Every site controller and CPE has its own credentials and per-topic ACL, so a device stolen from a site cannot read or publish for any other.
Commands such as a generator test or a new HVAC set point go out on command topics that only your OSS or NOC tools are allowed to publish to.
telco/north/site-ank-1187/power/rectifier (retained)
telco/north/site-ank-1187/battery/string-1
telco/north/site-ank-1187/hvac/unit-1 (retained)
telco/north/site-ank-1187/alarms
cpe/fwa-28812/status (retained)SNMP is established for network elements, but it relies on polling and traps, struggles through NAT and serves one manager at a time. MQTT devices push over one outbound TLS connection and any number of systems can subscribe. Many operators keep SNMP inside the site and let the site controller publish to MQTT.
Most rectifier and battery controllers expose Modbus or SNMP. A site controller, RTU or small edge gateway reads them and publishes over MQTT with TLS; newer site controllers and many CPE and edge devices support MQTT natively.
Yes. A small integration service subscribes to the alarm and status topics and forwards them to your OSS or alarm manager through its API, while dashboards and data platforms subscribe to the same messages in parallel.
Start on the Free plan — no card required — connect your first devices today and upgrade when you go live.
