Kobra X firmware 1.2.0.6: MQTT connects successfully but no telemetry (temperatures stay at 0°C, camera unavailable) #87
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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:
Could you please confirm whether firmware 1.2.0.6 is currently supported by KX-Bridge?
Steps to Reproduce
Expected Behavior
After the MQTT connection is established, I expect KX-Bridge to:
Actual Behavior
The connection itself appears to be successful.
CONNACK rc=0).However:
Environment
Logs
I will attach the complete log.
The attached log includes the following actions:
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:
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.
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.
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?
I found the solution.
The symptoms were:
CONNACK rc=0)The problem was resolved by removing the printer from the KX-Bridge web interface and adding it again.
After re-adding the printer:
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.