Kobra X firmware 1.2.0.6: MQTT connects successfully but no telemetry (temperatures stay at 0°C, camera unavailable) #87

Closed
opened 2026-07-06 22:36:49 +00:00 by fbbacelar · 3 comments

Description

I am trying to use KX-Bridge with my Anycubic Kobra X running firmware 1.2.0.6.

KX-Bridge starts correctly, connects to the printer, and OrcaSlicer successfully connects through the Moonraker interface.

However, after the connection is established, the printer does not appear to provide any usable status information or respond to commands issued from KX-Bridge.

As a result:

  • Nozzle temperature always stays at 0.0°C
  • Bed temperature always stays at 0.0°C
  • Print progress remains at 0%
  • Printer state never changes
  • Camera reports "Stream unavailable"
  • Commands such as turning the printer light on/off are transmitted by KX-Bridge but the printer does not react.

Could you please confirm whether firmware 1.2.0.6 is currently supported by KX-Bridge?


Steps to Reproduce

  1. Install KX-Bridge 0.9.27 on Windows.
  2. Extract credentials using:
extract_credentials.exe --write-env
  1. Put the printer into LAN Mode.
  2. Start KX-Bridge.
  3. Connect OrcaSlicer using the Moonraker interface.
  4. Open the KX-Bridge web interface.
  5. Try to:
    • Turn the printer light on/off.
    • Start the camera.
    • Monitor temperatures.

Expected Behavior

After the MQTT connection is established, I expect KX-Bridge to:

  • Show current nozzle and bed temperatures.
  • Update the printer state.
  • Control the printer light.
  • Display the camera stream.
  • Make the same information available to OrcaSlicer.

Actual Behavior

The connection itself appears to be successful.

  • TLS connection succeeds.
  • MQTT authentication succeeds (CONNACK rc=0).
  • The printer appears as Ready.
  • OrcaSlicer reports that the Moonraker connection is working.

However:

  • Temperatures remain at 0.0°C.
  • The printer state never changes.
  • The camera returns "Stream unavailable".
  • Sending the light control command produces no visible reaction from the printer.

Environment

  • Printer: Anycubic Kobra X
  • Printer Firmware: 1.2.0.6
  • KX-Bridge Version: 0.9.27
  • OrcaSlicer Version: 2.4.1
  • Operating System: Windows 10/11
  • Installation: Windows Binary

Logs

I will attach the complete log.

The attached log includes the following actions:

  • Successful MQTT connection.
  • Opening the KX-Bridge web interface.
  • Sending the command to turn the printer light ON.
  • Sending the command to turn the printer light OFF.
  • Attempting to start the camera.
  • Receiving "Stream unavailable".

Although the log shows the corresponding MQTT TX commands, the printer does not react, and no printer state, temperature, or camera data becomes available.

(Log attached as a file.)


Question

Could you please confirm whether Anycubic Kobra X firmware 1.2.0.6 is fully supported?

If support is expected, is there any additional debugging I can enable or provide?

If firmware 1.2.0.6 introduced changes to the MQTT topics or protocol, I would be happy to test a development build or provide any additional logs that might help.

Additional observation

The issue occurs consistently.

I also tested:

  • Cloud Mode (KX-Bridge cannot establish a working connection)
  • LAN Mode (connection succeeds)

Only LAN Mode allows a successful MQTT connection, but the printer still does not provide status information or react to commands.

Additional Note

While trying to set up KX-Bridge, I noticed that the YouTube tutorial links referenced by the project are currently set to Private and are not accessible.

If this is intentional, please ignore this note. Otherwise, you may want to update or restore those videos, as they would likely help new users with the initial setup.

Thank you very much for developing KX-Bridge.

## Description I am trying to use KX-Bridge with my Anycubic Kobra X running firmware **1.2.0.6**. KX-Bridge starts correctly, connects to the printer, and OrcaSlicer successfully connects through the Moonraker interface. However, after the connection is established, the printer does not appear to provide any usable status information or respond to commands issued from KX-Bridge. As a result: - Nozzle temperature always stays at **0.0°C** - Bed temperature always stays at **0.0°C** - Print progress remains at **0%** - Printer state never changes - Camera reports **"Stream unavailable"** - Commands such as turning the printer light on/off are transmitted by KX-Bridge but the printer does not react. Could you please confirm whether **firmware 1.2.0.6** is currently supported by KX-Bridge? --- ## Steps to Reproduce 1. Install KX-Bridge **0.9.27** on Windows. 2. Extract credentials using: ```bash extract_credentials.exe --write-env ``` 3. Put the printer into **LAN Mode**. 4. Start KX-Bridge. 5. Connect OrcaSlicer using the Moonraker interface. 6. Open the KX-Bridge web interface. 7. Try to: - Turn the printer light on/off. - Start the camera. - Monitor temperatures. --- ## Expected Behavior After the MQTT connection is established, I expect KX-Bridge to: - Show current nozzle and bed temperatures. - Update the printer state. - Control the printer light. - Display the camera stream. - Make the same information available to OrcaSlicer. --- ## Actual Behavior The connection itself appears to be successful. - TLS connection succeeds. - MQTT authentication succeeds (`CONNACK rc=0`). - The printer appears as **Ready**. - OrcaSlicer reports that the Moonraker connection is working. However: - Temperatures remain at **0.0°C**. - The printer state never changes. - The camera returns **"Stream unavailable"**. - Sending the light control command produces no visible reaction from the printer. --- ## Environment - **Printer:** Anycubic Kobra X - **Printer Firmware:** 1.2.0.6 - **KX-Bridge Version:** 0.9.27 - **OrcaSlicer Version:** 2.4.1 - **Operating System:** Windows 10/11 - **Installation:** Windows Binary --- ## Logs I will attach the complete log. The attached log includes the following actions: - Successful MQTT connection. - Opening the KX-Bridge web interface. - Sending the command to turn the printer light **ON**. - Sending the command to turn the printer light **OFF**. - Attempting to start the camera. - Receiving **"Stream unavailable"**. Although the log shows the corresponding MQTT **TX** commands, the printer does not react, and no printer state, temperature, or camera data becomes available. *(Log attached as a file.)* --- ## Question Could you please confirm whether **Anycubic Kobra X firmware 1.2.0.6** is fully supported? If support is expected, is there any additional debugging I can enable or provide? If firmware **1.2.0.6** introduced changes to the MQTT topics or protocol, I would be happy to test a development build or provide any additional logs that might help. ### Additional observation The issue occurs consistently. I also tested: - Cloud Mode (KX-Bridge cannot establish a working connection) - LAN Mode (connection succeeds) Only LAN Mode allows a successful MQTT connection, but the printer still does not provide status information or react to commands. ## Additional Note While trying to set up KX-Bridge, I noticed that the YouTube tutorial links referenced by the project are currently set to **Private** and are not accessible. If this is intentional, please ignore this note. Otherwise, you may want to update or restore those videos, as they would likely help new users with the initial setup. Thank you very much for developing KX-Bridge.
fbbacelar added the
bug
label 2026-07-06 22:36:49 +00:00

I also updated the firmware and had the same issues as you described.

Once I openend Anycubic Slicer Next and it connected once to the printer, the bridge also could establish a connection. It seems to be stable now, even without ASN.

I also updated the firmware and had the same issues as you described. Once I openend Anycubic Slicer Next and it connected once to the printer, the bridge also could establish a connection. It seems to be stable now, even without ASN.
Owner

have the latest firmware on the printer, and I'm not having any problems. The most common issues that could be causing your symptoms are: 1. AnyCubic Slicer running at the same time as the bridge, or another tool that intercepts the MQTT topics; 2. The printer not in LAN mode; and 3. A poor network connection.
Do you have the option to test the latest nightly build as a Docker container?

have the latest firmware on the printer, and I'm not having any problems. The most common issues that could be causing your symptoms are: 1. AnyCubic Slicer running at the same time as the bridge, or another tool that intercepts the MQTT topics; 2. The printer not in LAN mode; and 3. A poor network connection. Do you have the option to test the latest nightly build as a Docker container?
Author

I found the solution.

The symptoms were:

  • Successful MQTT connection (CONNACK rc=0)
  • Printer shown as Ready
  • Temperatures stuck at 0°C
  • Camera reporting "Stream unavailable"
  • Commands sent but no visible response from the printer

The problem was resolved by removing the printer from the KX-Bridge web interface and adding it again.

After re-adding the printer:

  • Nozzle and bed temperatures are reported correctly.
  • Printer status updates correctly.
  • Camera works.
  • Commands are executed correctly.

For reference, this was my initial setup with firmware 1.2.0.6. I never used KX-Bridge with an older firmware version, so I cannot say whether the issue is related to the firmware update itself or simply to the initial printer configuration.

Hopefully this helps anyone experiencing the same symptoms.

I found the solution. The symptoms were: - Successful MQTT connection (`CONNACK rc=0`) - Printer shown as **Ready** - Temperatures stuck at 0°C - Camera reporting "Stream unavailable" - Commands sent but no visible response from the printer The problem was resolved by removing the printer from the KX-Bridge web interface and adding it again. After re-adding the printer: - Nozzle and bed temperatures are reported correctly. - Printer status updates correctly. - Camera works. - Commands are executed correctly. For reference, this was my initial setup with firmware **1.2.0.6**. I never used KX-Bridge with an older firmware version, so I cannot say whether the issue is related to the firmware update itself or simply to the initial printer configuration. Hopefully this helps anyone experiencing the same symptoms.
Sign in to join this conversation.
3 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: viewit/KX-Bridge-Release#87
No description provided.