pnoker
dc2164f46e
a live-stack sweep of all 36 drivers surfaced five sdk-level defects that left reads dead or the whole fleet unbootable: - drop the empty spring.main stub in the shared driver profile; the boot 4.1 binder rejects null-valued keys and every driver died at startup with a bind exception - rename the schedule enable flag to enable to match what every driver application.yml actually spells; with the old enabled key the read and custom quartz jobs were silently never scheduled - treat proto3 zero-versions as unset when reconciling registration so a driver restart re-registers instead of failing the optimistic lock with 'driver version conflict' - ignore the driver's own registration event that can be consumed before applymetadata finishes instead of logging an error - initialize jdbc/serial connection maps eagerly: the registration event handler invalidates pools and nped on a lazy-null map - ble: exclude the guava 18 pin dragged in by bluetooth-manager - kafka: use the starter (boot 4 split autoconfigurations out of the bare jar) and read the compose-provided bootstrap variable - lwm2m: pin californium to the 3.x api leshan m14 needs and configure an explicit coap endpoint - mqtt: replace the orphaned spring-integration gateway with a paho publisher so the send path exists again - boot sweep result: 36/36 drivers start, 0 errors
DC3 Driver MQTT
Overview
dc3-driver-mqtt is the MQTT protocol driver of the IoT DC3 platform. It is intended to subscribe to configured MQTT
topics, parse incoming payloads as device point values, and forward commands to devices via MQTT publish.
⚠️ Work in progress. This driver is currently a skeleton — protocol-level I/O is not yet fully implemented (
health()always reports online andread()is a reference stub; see the TODO markers inMqttDriverCustomServiceImpl). Treat it as a starting template, not a production-ready driver.
Module Information
- Group ID: io.github.pnoker
- Artifact ID: dc3-driver-mqtt
- Driver Name: MQTT Driver
Point Attributes
| Attribute | Description |
|---|---|
| Command Topic | MQTT topic for sending write commands |
| Command QoS | MQTT QoS level for command messages (0/1/2) |
Command Attributes (write)
| Attribute | Description |
|---|---|
| Command Topic | MQTT topic for sending write commands |
| Command QoS | MQTT QoS level for command messages (0/1/2) |
| Payload Template | Template for the command payload |
Event Attributes
| Attribute | Description |
|---|---|
| Source Topic | MQTT topic to receive events from |
| Event Code Path | Path to the event code in payload |
| Payload Path | Path to the event payload |
The module application.yml is authoritative for attribute codes, types, default values, scheduling, health, and local
buffering. Keep this README aligned when those user-facing settings change.
Prerequisites
An MQTT broker must be running. The dev profile connects to the RabbitMQ MQTT plugin (dc3-rabbitmq:2883), which ships
with the base stack:
make up-db
EMQX is available as an alternative via the optional stack (docker-compose-optional.yml, port 31883); point
MQTT_BROKER_HOST / MQTT_BROKER_PORT at whichever broker you use.
Running Locally
1. Start Infrastructure and Center Services
make up-db
make up-dev GROUP=core
2. Build and Run
mvn -s .mvn/settings.xml -pl dc3-driver/dc3-driver-mqtt -am package
java -jar dc3-driver/dc3-driver-mqtt/target/dc3-driver-mqtt.jar
Testing
Run the module tests from the repository root:
mvn -s .mvn/settings.xml -pl dc3-driver/dc3-driver-mqtt -am test
Related Modules
dc3-common-driver— Driver SDK for registration, scheduling, and RabbitMQ integrationdc3-common-mqtt— MQTT client configuration and utilities