New K1C firmware v1.3.5.22 (Mono-color)

Today, while checking the firmware page, I came across this new version. Interestingly, it includes optimizations for the monochrome version, which I think is a good thing; it would be worth trying out.

However, for multi-color printing, the firmware remains unchanged, meaning the disconnection bug and the temperature issues when using different types of filament are still there.

At least this gives me some hope that they will release at least one more update for the multi-color system. As long as they fix the few existing bugs, they can stop providing support after that, but they shouldn’t just abandon it with those bugs unresolved.

V1.3.5.22 Firmware Update Notes:

1.Optimize video stream transmission security.

2.Optimize model fan control logic.

4 Likes

What the hell means “Optimize video stream transmission security”? Can not access via local area network anymore? If so, directly downgrade or kicking Creality fronend. With best regards from the Creality Helper Script.

5 Likes

Same issue for me,after the update my camera stream on LAN does not work any more :enraged_face:

5 Likes

I can’t access the camera after the update. Has anyone found a solution?

only cam working mobile app

3 Likes

Same problem here. I bought the K1C specifically because of the built-in camera, but after updating to firmware 1.3.5.22, I can no longer access the camera stream over my local network.

1 Like
Hello, why isn't my camera working after the update? 
1 Like

Same Problem after upgrading to v1.3.5.22

3 Likes

Is there no one competent who can help?

1 Like

I have tried to connect camera via Creality Print: successful.
I have tried to connect camera via Cloud-App: successful.
Once again I ry to connect via LAN-Stream: fail.
Downgrade firmware: YES, successful.
My K1, K1C, K1SE works now with the formaly firmware and when there will be a firmware for my k1 Max with 2 CFS-units, I deny this update. Maybe I will leave Creality after owning 4 CR-6SE, 3 Ende-3 V3 SE, one Ender-3 V3 KE and two LD-002R. I head snapmaker have a good toolchanger.

1 Like

same issue here :slightly_frowning_face:
the camera preview still works in Creality Slicer and surprisingly, it works locally (I disconnected the router from the internet, so at least now we know it’s not going through the chinese cloud) There’s most likely some hidden endpoint that provides access to the camera feed. I’m going to try reverse engineering how it connects to the printer.

1 Like

Same on my K1. And the green color… who wanted that?

Is this forum mainly for users helping each other, or do people from Creality also participate here, give advice, and monitor reported issues?

1 Like

update from my previous comment
I managed to reverse engineer the new camera connection and package it into a single python script

the firmware has not removed local camera access entirely - it moved the stream to WebRTC.
The script connects directly to the printer on the LAN, receives the H.264 stream and exposes it again in a browser.
It can also provide an old-style MJPEG stream and snapshots for compatibility.

I tested it on a K1 running firmware 1.3.5.22. Fortunately, no Creality cloud connection is required.

Repository: https://github.com/juljeryt/creality-cam

1 Like

Is this valid for the original K1 camera? @juljeryt69

Yes. If it doesn’t work, please send me logs/error that you get, so I can fix it. I only tested the script on linux.

You work is greatly appreciated but wouldn’t it be wonderful if Creality just fixed the firmware. I have downgraded also. I dont see enough benefit from the upgrade

True, with this update they’ve just made life more difficult for their users

How to downgrade a version? How do I downgrade? Is there a user guide?

Does anyone know where I can find the firmware version for the K1 that was released before 1.3.5.22? The firmware section on Creality’s support pages is a bit confusing.

Also, why don’t they add an option to automatically unload/eject the filament after a print finishes, or at least provide that function directly from Creality Print? It would be much more convenient than having to do it manually every time.

Is there any way to get Creality to fix this?

1 Like

Hello people,

After updating my K1 Max to firmware V1.3.5.22, the camera stopped working.

The issue affects both the Creality WebUI and Fluidd, so this does not appear to be a Fluidd-specific problem.

What I found

The camera is still detected correctly by the system:

  • CREALITY CAM (usb-13500000.otg_new-1.3):
  • /dev/video4
  • /dev/video5

The camera device exists and is accessible:

  • /dev/video4
  • /dev/video5

The process cam_app starts automatically and takes ownership of /dev/video4:

  • /usr/bin/cam_app -i /dev/v4l/by-id/main-video-4 -t 0 -w 1280 -h 720 -f 15 -c

cam_app.log shows that the camera is opened successfully:

  • input path: /dev/v4l/by-id/main-video-4
  • realpath: /dev/video4
  • size: 1280x720, fps:15

However, later in the log there are failure messages:

  • service will exit, ret = -1

Additional testing

I manually stopped the Creality camera services:

  • killall cam_app
  • killall cx_ai_middleware

and then started the MJPG streamer:

  • /etc/init.d/S50usb_camera restart

After doing this, mjpg_streamer successfully started:

  • /opt/bin/mjpg_streamer -b -i /opt/lib/mjpg-streamer/input_uvc.so -d /dev/video4 -r 1280x720 -f 15 -o /opt/lib/mjpg-streamer/output_http.so -p 8080

and the camera immediately started working again in Fluidd.

Conclusion

The camera hardware appears to be functioning correctly and the operating system still detects the camera properly.

The issue seems to be related to the new camera/video streaming implementation introduced in firmware 1.3.5.22. The cam_app service takes control of the camera but does not provide a working video stream, causing the camera to fail in both the Creality WebUI and Fluidd.

Could you please investigate whether there is a known issue with the camera streaming service in firmware 1.3.5.22?

Thank you.

I hope Creality sees this!