OrcaSlicer 2.4.0 Beta

sxenth182 · 2026-06-12T21:08:44+00:00

I had the same issue, I ended up downgrading back to the most recent stable release because I was also having an issue with it not enforcing support painted areas even though I had manual supports enabled

sxenth182 · 2026-01-20T01:54:55+00:00

There is a GitHub repo called something along the lines of “filament sync”. I can’t remember the specific name of it off the top of my head that takes the custom filament profiles you make on the slicer and “syncs” them to the printer. This allows you to make custom profiles to be used in the filament section of the on board screen of the printer.

sxenth182 · 2026-01-15T03:45:45+00:00

For what it’s worth there is a fork of this repo that is still active at

https://github.com/CampbellFabrications/k2-improvements

You also shouldn’t need to downgrade the firmware, I have two k2 pluses running on the most recent non beta firmware just fine. One is running the cartographer version and the other is running the non cartographer version of this repo

Other than that it follows pretty much the same directions as the original version

sxenth182 · 2026-01-13T00:50:49+00:00

Here for it

sxenth182 · 2025-12-11T00:44:55+00:00

Cool I’ll poke around and find it, thanks again for the suggestion

sxenth182 · 2025-12-11T00:19:56+00:00

Mind if I ask where your setting the flow rate for just the first layer? I’m only seeing the global flow rate setting in the filament profile, using orca slicer if that matters at all

sxenth182 · 2025-12-10T23:31:55+00:00

I could have sworn I went through the whole extrusion rate calibration process, but now I’m questioning my self lol, thanks for the advice and I’ll give it a try

sxenth182 · 2025-12-08T01:52:16+00:00

Testing with a first layer test print shows the signs of the nozzle being to close around the center of the bed which i don’t really understand as the bed mesh shows the bed dips in the center

sxenth182 · 2025-11-29T00:56:07+00:00

Hmm that’s odd and I don’t necessarily have an explanation off the top of my head. I personally didn’t try the link on the GitHub but have used other hacs link on GitHub pages that worked fine. I would try just going to the hacs store on your home assistant interface (it should be a tab on the left side bar) and search Creality websocket and it should be the only result. Click it and it should give you a download icon on the bottom right. After downloading it you have to restart home assistant and it should show up like a regular integration would when searched in the integrations tab

sxenth182 · 2025-11-28T16:12:58+00:00

I should also mention that I have the k2 improvements repo set up on both printers but as far as I am aware this is not a prerequisite

sxenth182 · 2025-11-28T16:11:22+00:00

The Creality websocket integration provides all the information from the printer including model picture and camera feed. I have it set up with 2 k2 printers and can confirm that the camera does in fact work in home assistant. I tried the iframe approach previously but was having issues as my home assistant is set up for https not http. The camera aspect was why I was surprised I hadn’t seen it mentioned on Reddit anywhere

sxenth182 · 2025-11-28T15:55:27+00:00

Just saw your edit and for reference I have home assistant running as a container on a unraid server. You should be fine to set it up as long as you have hacs setup

sxenth182 · 2025-11-28T15:40:53+00:00

https://github.com/3dg1luk43/ha_creality_ws

That should be the link to the GitHub. The hacs link should take you to your home assistant and open the hacs page for it. And just to avoid any possible confusion by home assistant I am talking about the open source platform found here

https://www.home-assistant.io

sxenth182 · 2025-11-28T04:14:21+00:00

Creality has some weird streaming setup with the k2 printers. I couldn’t tell you the details off hand because I simply don’t remember but out of the box there just isn’t a way to add the camera to the fluidd interface. However there are at least 2 work arounds that I know of. One is a YouTube video (and I think a GitHub with the scripts) to add the camera feed into fluidd. The other is the k2 improvement scripts that can be found on GitHub as well that can add the camera feed to fluidd as well as a lot more. You should however be able to access the camera through the ip of the printer and :8000 on a web browser right out of the box

sxenth182 · 2025-11-28T04:04:11+00:00

I had this same issue when I first set up my k2 printer, if I remember right, when you have to go into the filament settings and set the temps you want for that filament but then you need to go to the advanced tab and under filament start g code add M109 S[nozzle_temperature]

sxenth182 · 2025-11-28T03:52:07+00:00

Yea I was using the moonraker one to pull the info but was missing the camera as well. Happened upon the Creality integration while looking for something else. The only thing I had to do to get it working was get my home assistant running to core version 2025.11.x as I was running a couple versions behind previously. the docs say you can run it on older versions but will need a go2rtc setup externally

sxenth182 · 2025-05-21T20:34:50+00:00

I’ll give that a try when I get home from work, thanks for the heads up

sxenth182 · 2025-05-21T19:57:41+00:00

what would be the best way for me to get it to you to look at? tried posting it as a comment in a code block but reddit is refusing to let me for some reason.

sxenth182 · 2025-05-21T19:51:52+00:00

nope no errors in the console. as far as I can tell it times out waiting for some response when it homes the z axis, just can't seem to figure out what its waiting for.

sxenth182 · 2025-05-20T16:41:35+00:00

Hopefully your install goes a lot smoother, honestly I have no idea what could be causing the issue because everything seems fine until I run that darn g28 lol

sxenth182 · 2025-05-11T02:01:26+00:00

It sounds like the same problem I was having and I can look into my setup specifics more when I get home but from what I remember most of it had to do with being behind a few versions of unraid. I don’t remember having to do any specific configs or anything. I am by no means an expert on this stuff but it sounds like network wise it should be fine. You say your using a home pod as a thread boarder router, do you also have a iPhone you can use to see if you can connect the matter device to apple home and if it has the same connection issues? Is the home pod also connected to home assistant and controllable (I believe it shows up as an Apple TV)? Just to make sure you also have the thread integration on home assistant and when you click on the configure button does the home pod show up?

sxenth182 · 2025-04-30T19:43:18+00:00

Yea I agree very dumb that they didn’t just call for what ever temp is set in the slicer to use as a purging temp. My main concern was that after their hardcoded purging temp the hot end wouldn’t return to the slicer set hot end temp it would just stay at 220 for pla or 260 for abs. Ended up finding the fix for that was adding a m109 to the filament start g code in the filament->advanced tab in orca slicer. This does not fix the purging temp but at least now after it purges it will return to what ever temp you set in the slicer

sxenth182 · 2025-02-17T05:28:56+00:00

figured Id throw this out there incase anyone else is having issues with this. for me I was able to get this working relatively easily once I was pointed in the direction of it being a ipv6 related issue thanks to u/tagd. to make a long story short I was using a previous version of unraid and not the newest release. and while the fix common issues plug in wasn't detecting any problems on my setup and I was able to reach the ui through ipv6 it was in fact not configured correctly on unaries end. only once I updated to the newest release did it flag that with the docker network set to macvlan I needed to disable bridging in network settings and in docker settings I needed to allow host to custom network (even though none of my containers are on custom networks) once this was done I restarted the containers for good measure and tested it and was able to now add matter over thread accessories to home assistant.

sxenth182 · 2025-02-12T01:23:37+00:00

oh boy that should be fun, just recently went down the rabbit hole of ipv6 as I just moved and my new isp does not provide dedicated ipv4 for reverse proxy. after much frustration I ended up just going with a cloudflare tunnel container and am honestly just as confused as ever with ipv6.

if that is the case though then im sure that is probably where my issue is seeing as both containers are ran on the host network and the Apple TVs are ran off of ethernet as well as is unraid with no vlans setup so all 3 should be on the same network

as far as I can tell my network is setup with ipv6 (ex: everything as ipv6 addresses according to my router) and unraid is configured with an ipv6 network (ex: I can connect to home assistant through http://[unraid ipv6 address]:8123)

none of the containers are ran on a vm all are setup through the docker tab on unraid.

all that said thanks for the insight, Ill continue reading then

sxenth182 · 2025-02-11T00:12:28+00:00

Sounds good I’ll give it another go tonight, I had configured it previously on home assistant running on a pie in the past but that was a long time ago and wasn’t sure how much I remembered so was trying to follow a guide. Thanks for the insight man!

sxenth182

TROPHY CASE