Zebra Printers – Known Issue: Unable to Restart MQTT Connection 1 or Connection 2

Publish Date: 27-Aug-2024 Last Modified Date: 16-May-2025 SOTI Connect
900 0

Summary

This article addresses a known issue affecting supported MQTT Zebra printers operating on Link-OS versions 6.8, 6.8.1, 6.9, and 7.0. When attempting to restart MQTT Connection 1 or Connection 2 via SOTI Connect, the action is not executed by the printer.

Related SOTI ONE Platform Products

SOTI Connect

Related Device OS

Link-OS

Issue Description

For MQTT Zebra printers operating on Link-OS versions 6.8, 6.8.1, 6.9, and 7.0, there is a known issue where the action to Restart MQTT Connection 1 or Connection 2 does not execute on the printer. Although the command is sent, it has no effect on the printer.

Environment

The issue affects Link-OS versions 6.8, 6.8.1, 6.9, and 7.0, and occurs on both SOTI Connect cloud and on-premise server versions.

Symptoms

Expected Result:

When the action to Restart MQTT Connection 1 or Connection 2 is sent from SOTI Connect, the printer should disconnect and then reconnect to the MQTT server.

Actual Result:

When the action to Restart MQTT Connection 1 or Connection 2 is sent from SOTI Connect, it has no impact on the printer.

Prevention

Since the issue is present across recent versions of the SOTI Connect server and the latest firmware versions of Zebra Link-OS, including 6.8, 6.8.1, 6.9, and 7.0, it cannot be prevented for this specific action.

Cause

The issue has been reported to Zebra and will be address in a Zebra Link-OS upgrade.

Issue Resolution

The issue has been reported to Zebra, however, issue resolution hasn't been determined.

Workarounds

As a workaround, the command to Reboot the printer can be performed from SOTI Connect. This will cause the printer to disconnect and reconnect to the MQTT server achieving what is performed by Restart MQTT Connection 1 or Connection 2.

Note: This action, however, will have the printer disconnect and reconnect completely from the Wi-Fi or LAN network and not just from the MQTT server.

Was this helpful?