Appearance
Compatible hardware
Devices and gateways that Autoconnecto connects over MQTT and Modbus. Controllers first, then the proven Modbus energy and climate stacks, then common Modbus meters on the same path.
Controllers (native MQTT)
| Hardware | Role | Status |
|---|---|---|
| ESP32 (Arduino SDK) | Native MQTT — telemetry, shared attributes, RPC, OTA | Bench / board tested |
| STM32 (Arduino core) | Same MQTT topics via Arduino-core sketches | Supported path · see STM32 guide |
| Raspberry Pi / Linux SBC (Python SDK) | Installable autoconnecto — MQTT + HTTPS + GPIO | Examples + package in SDK repo |
ESP32
Flash the Autoconnecto Arduino SDK, put the device token in secrets.h. ESP32-S2 / S3 / C3 and other Espressif boards on the same Arduino core use this path. Confirm Wi‑Fi/TLS on your exact module.
Guides: ESP32 quick start · OTA updates · ESP32 as Modbus edge · Marketing: ESP32 MQTT
STM32
Same device contract as ESP32 when you use an STM32 Arduino core with enough RAM/flash for TLS. Not a separate binary SDK.
Guide: STM32 Arduino quick start (in the SDK repo)
Raspberry Pi / Linux SBC
Full install: pip install -e "./python[gpio,dotenv]" from autoconnecto-sdk (package autoconnecto). MQTT, HTTPS, shared attributes, RPC, and GPIO (digital out/in + Switch relay channels via gpiozero). Device client only — not a local platform edge.
| Named board | Notes |
|---|---|
| Raspberry Pi 5 | Primary test class · Raspberry Pi OS · BCM GPIO |
| Raspberry Pi 4 / 3 | Same path |
| Raspberry Pi Zero 2 W | Same path · Wi‑Fi |
| Orange Pi 5 (and similar Orange Pi) | Debian-class image · GPIO when the image exposes pins to gpiozero |
| Radxa ROCK 5 / ROCK Pi | Same class |
| BeagleBone Black / AI | Debian · check pin map for your cape |
| Industrial Debian/Ubuntu gateway (ARM or x86) | MQTT/HTTPS full · GPIO only if Linux GPIO is available |
Guides: Linux SBC quick start · raspberrypi examples
Cellular Modbus DTUs (MQTT serial bridge)
Autoconnecto is the Modbus master in the cloud. The DTU only moves bytes between MQTT and RS-485. Use MQTT work mode (modbus/tx / modbus/rx), not Transparent TCP.
| Hardware | Role | Status |
|---|---|---|
| PUSR / USR-DR154 | 4G MQTT ↔ RS-485 serial | Bench tested |
| Other MQTT-serial Modbus DTUs | Same role when the vendor exposes MQTT serial / Modbus tunnel topics you can map | Same path · confirm MQTT mode |
Guide: DR154 setup
PUSR and USR are the same DR154 line.
Climate sensor (bench tested)
| Role | Hardware | Status |
|---|---|---|
| Humidity / temperature | XY-MD02 (RS-485 Modbus RTU) | Bench tested with DR154 |
| Cellular DTU | PUSR / USR-DR154 | Bench tested |
Guide: DR154 + XY-MD02 · ClimateFleet
How Modbus meters work here
Any meter that speaks Modbus RTU on RS-485 can be polled once you set:
- Slave ID, baud, parity (match the meter)
- Holding or input registers from the meter’s own Modbus PDF
- Data type (for Multispan AVH-14-M1 that is float32 CDAB)
You do not need a new Autoconnecto feature per brand. You need the correct map. Poll through DR154 (cloud master) or an ESP32 Modbus edge / Linux Modbus gateway script.
Ready map published: Multispan AVH-14-M1
Other meters below: supported as Modbus slaves — enter the map from that model’s manual (or ask us to add a guide).
First energy Modbus stack (bench tested)
| Role | Hardware | Status |
|---|---|---|
| Energy meter | Multispan AVH-14-M1 | Bench tested · map published |
| Cellular DTU | PUSR / USR-DR154 | Bench tested |
Guide: Multispan AVH-14-M1 via DR154 · DR154 setup · EnergyFleet
Multispan Modbus multifunction meters
Same maker as the bench-tested AVH-14-M1. Confirm RS-485 Modbus is fitted on the exact order code (some Multispan variants list Modbus as optional / on request).
| Model | Notes |
|---|---|
| AVH-14-M1 | Bench tested. Float CDAB map in the AVH-14-M1 guide. |
| AVH-14N-M1 | RS-485 Modbus. Register layout differs from AVH-14-M1 (often 30000/40000 style) — do not reuse the M1 map. |
| AVH-16 / AVH-16-M1 | RS-485 Modbus · THD · import/export energy. Map from that PDF. |
| AVH-16+-M1 | RS-485 Modbus · THD · import/export. Map from that PDF. |
Other Modbus RTU energy / multifunction meters (India and common installs)
These families typically expose voltage, current, power, PF, frequency, and kWh over RS-485 Modbus RTU. Autoconnecto can poll them through the same DR154 (or ESP32 / Linux Modbus edge) path. Load the register table from the model datasheet.
| Maker | Example models | Protocol |
|---|---|---|
| Selec | MFM384, MFM384-R-C (DIN) | Modbus RTU |
| Secure Meters | Elite 500 (and Elite series with RS-485) | Modbus RTU; some with Modbus TCP option |
| Elmeasure | LG / multifunction panel and DIN series with RS-485 | Modbus RTU |
| Schneider Electric | iEM3255 and similar iEM / PowerLogic Modbus meters | Modbus RTU |
| Siemens | SENTRON PAC3200 / PAC family with Modbus | Modbus RTU / TCP |
| ABB | B24 and similar Modbus energy meters | Modbus RTU |
| Eastron | SDM630, SDM72D-M and SDM Modbus family | Modbus RTU |
| Carlo Gavazzi | EM340, EM540 | Modbus RTU |
| Janitza | UMG 96 and Modbus UMG meters | Modbus RTU / TCP |
| L&T / other panel MFMs | Any RS-485 Modbus RTU multifunction meter | Map from that PDF |
This is not a complete catalogue of every SKU worldwide. If the meter has a Modbus register map and RS-485 (or Modbus TCP to a serial/IP gateway), it fits the Autoconnecto Modbus path.
Also documented
| Hardware | Guide | Notes |
|---|---|---|
| ESP32 as Modbus edge (Wi‑Fi MQTT) | ESP32 Modbus edge | Edge is master; meters/sensors above as slaves |
| Linux Modbus / OPC UA gateway scripts | SDK integrations | SBC protocol bridges |
Want a named guide for your meter?
Send the Modbus PDF and baud/slave defaults to founder@autoconnecto.in. We add a written map when the path is proven, starting from the Multispan and India panel meters above.