TRB143 – M-Bus data missing from MQTT payload despite successful data acquisition

Hello,

We are experiencing an issue with the Teltonika TRB143 when sending data collected from M-Bus devices to an external MQTT broker using the Data to Server functionality.

The system operated reliably for several months. However, approximately six weeks ago, problems started occurring. We have since upgraded the TRB143 to the latest available firmware versions, but the issue persists. The currently installed firmware is RutOS R_00.07.24.7.

Problem description

Initially, the device operates correctly and publishes MQTT messages containing the expected M-Bus measurements. However, after some time, the MQTT messages continue to be delivered to the broker, but the measured values are missing from the payload.

Importantly, the M-Bus service continues to operate normally, and data acquisition appears to be successful:

  • The Successful requests counter continues to increase.
  • The Database entries counter also continues to increase.
  • MQTT messages continue to be published to the broker.
  • The MQTT connection remains established.

This suggests that the M-Bus data is being collected and stored correctly, but is not being included in the MQTT payload by the Data to Server service.

Rebooting the TRB143 temporarily resolves the problem, and the MQTT payload once again contains the expected M-Bus measurements. However, the issue eventually reoccurs.

Current MQTT configuration:
Broker: private
Port: 8883
QoS: 1
Enable secure connection: Disabled
UCI configuration: data_sender.2.mqtt_tls=‘0’

Despite TLS being disabled, packet captures using tcpdump clearly show TLS Application Data records (17 03 03 ...) in both directions.

Questions

  1. Is this a known issue in RutOS or the datasender service, where M-Bus data is successfully acquired and stored in the database but stops appearing in MQTT payloads?

  2. What could cause the Data to Server service to stop retrieving M-Bus measurements even though the Successful requests and Database entries counters continue to increase?

  3. Is there a way to enable detailed DEBUG logging for datasender, particularly for database queries, payload generation, MQTT PUBLISH operations and PUBACK acknowledgements?

  4. Does datasender automatically enable TLS when connecting to port 8883, even when mqtt_tls=0?

  5. Is there a recommended way to restore normal operation without rebooting the entire device, for example by restarting only the datasender service?

  6. Are there any known fixes or workarounds for this behavior in recent firmware releases?

Since the system worked correctly for several months and the problem appeared only recently, we would also appreciate any information about possible software regressions or known issues affecting the integration between M-Bus data acquisition, the internal database and the Data to Server MQTT service.

We can provide configuration files, system logs and TCP packet captures if required.

Thank you for your assistance.

Best regards

kamils

As a follow-up to my previous report, I found additional information in the data_sender.log file included in the Troubleshoot archive.

The Mbus_collection statistics show:

  • M-Bus input: success: 0, err: 440

  • JSON formatter: success: 0, err: 0

  • MQTT output: success: 0, err: 0

  • Collection status: running: true

This suggests that the issue occurs in the M-Bus input plugin, before MQTT publishing is attempted.

Restarting the data_sender service does not resolve the issue; only a complete device reboot restores data publishing.

Could you please investigate why the M-Bus input plugin continuously reports errors despite successful M-Bus readings?

Hello,

Same issue here on multiple TRB143. The issue started after upgrading installed firmware from TRB1_R_00.07.11.3_WEBUI version to TRB1_R_00.07.24.6_WEBUI.

Few days after the issue started TRB1_R_00.07.24.7 has been released but didn’t fix the issue.

Thanks in advance for any help or pointers you can provide.

Best regards,

Louis

Hello Louis,

The latest update from Teltonika regarding this issue is available here:

Best regards
kamils