Prusa Core One Chamber Temp

What is the problem?

No Chamber temperature on the Prusa Core One

The printer itself works great with Octoprint, but would love to be able to read the chamber temp. Anyone get this working?

Thanks

You need to have a g-code to get that temperature from the printer.

This is because Prusa didn't follow existing "standards" in reporting those temperatures on the serial line. I worked with someone the other day in Discord and came up with a single file plugin fix until this PR gets merged by Prusa to resolve the problem (recommend you go comment in this issue thread that it needs to be merged).

Copy/paste this URL into plugin manager > get more > ...from URL and click install.

https://gist.githubusercontent.com/jneilliii/cd10ecdb024dc1346b558dfa275916b9/raw/d813ac9252d0142dd50e893fb76cb7f31b1a77d8/PrusaBuddyChamberFix.py

Then just make sure you printer profile has heated chamber checkbox enabled.

2 Likes

@jneilliii - I installed your plugin as mentioned above and I see the chamber temp, however the "target" temp shows as 0. If I look at the display on the Core One, it says the "target" is 35. Am I missing something?

screenshot 2025-06-24 at 08.48.08

It's an issue with how prusa is reporting this information. There is an open pull request to make this work natively and I assume that includes target temp data.

1 Like

Hi.

FWIW, I hacked up jneilliii's script a bit to make it pay attention to the M141 chamber gcodes as well.

It does help somewhat w/ the "WTH is it doing?" at the start of a print while its waiting for the chamber to heat up...

https://gist.githubusercontent.com/zzqzzqzzq/02dc80e49b072e1612058645828a4bee/raw/0d290e834265d810c4a1471d407339f1164cbb41/PrusaBuddyChamberFix.py

Be certain to remove the old one first, as if you somehow get both of them enabled at the same time, they conflict. And it doesn't deal well with cancellations. (Unsurprisingly, as there's no M141 S0 in that case.)

HTH,

David