Inverters, turbines, battery systems and chargers publish to one MQTT broker; your portfolio SCADA, asset management and VPP platform subscribe and send setpoints back. ConnectMQ runs the broker.
No card required
Every inverter, turbine and BESS vendor has its own monitoring portal and data format. Asset managers stitch exports together just to report on one portfolio.
Rooftop arrays, wind farms, storage containers and charging hubs sit on cellular links far from any control room. A tripped inverter or a stopped turbine loses production every hour nobody notices.
Batteries, chargers and flexible loads only earn their value in a VPP or grid-services programme if setpoints reach them in time and their state of charge is known now — not after the next poll.
One vendor-neutral MQTT layer between your sites and your software. You build the platform; ConnectMQ runs the broker.
An isolated MQTT 3.1.1 and 5 broker over TCP, TLS and WebSocket. Site controllers, data loggers and EMS gateways connect with standard clients — no broker for you to operate.
Every logger, BMS gateway and charger has its own credentials, and per-topic ACLs keep sites, partners and O&M contractors on their own topics. TLS on every connection.
Readings fan out to SCADA, forecasting and settlement in parallel, while curtailment, charge/discharge and charging-power commands go back on dedicated topics with QoS 1.
Last Will flags a site that goes silent, retained values show the last state of every asset, and threshold rules alert on inverter faults, low state of charge or high cell temperatures.
Renewable operators start with plant monitoring, then use the same broker for chargers, maintenance and metering.
Inverter, turbine and battery data from every plant in one place, with curtailment setpoints back to the plant controller
Explore the use caseSite telemetry, load management and live charger status for apps, alongside OCPP
Explore the use caseStream vibration, temperature and motor current to your models and open work orders before a machine fails
Explore the use caseAMI interval data from electricity, water and gas meters, plus grid sensor readings, to MDM, billing and operations
Explore the use casesolar/park-08/inv-12/telemetry
solar/park-08/inv-12/setpoint
wind/farm-03/wtg-05/status (retained)
bess/site-02/bms/state (retained)
vpp/pool-a/dispatch/setMost inverters speak Modbus TCP or SunSpec Modbus, so a data logger or edge gateway on site reads them and publishes per-inverter topics to ConnectMQ; some loggers and newer inverters publish MQTT directly. Publish on change or at a fixed interval, and send setpoints such as curtailment back on a commands topic.
Yes. A VPP needs state from many small assets and a fast way to send dispatch signals back. Batteries, chargers and heat pumps publish availability and state of charge; your VPP platform subscribes, decides and publishes setpoints per asset or group. ConnectMQ is the transport — the optimisation and market logic stay in your platform.
They work at different levels. Modbus is a local poll-response protocol between a logger and the inverter or BMS on site. MQTT moves that data from many sites to the cloud and to every system that needs it, over one outbound TLS connection per site. The typical architecture uses both.
Yes, alongside OCPP. Chargers usually talk OCPP to your charge point management system; site meters, load managers and CPMS backends commonly use MQTT to share sessions, power and limits with dashboards, load balancing and energy management. ConnectMQ is an MQTT broker, not an OCPP server.
Start on the Free plan — no card required. Connect a solar park, a battery or a charging hub, then move to Basic or Scale when you go live. No overage charges, cancel anytime.
