Skip to content

Add plugin Prusa Chamber Light - #1494

Merged
jneilliii merged 4 commits into
OctoPrint:gh-pagesfrom
Aryeh95:add-chamberlight
Oct 6, 2026
Merged

jneilliii merged 4 commits into
OctoPrint:gh-pagesfrom
Aryeh95:add-chamberlight

Conversation

@Aryeh95

@Aryeh95 Aryeh95 commented Oct 6, 2026 •

Copy link
Copy Markdown
Contributor
  • You have read the "Registering a new Plugin" guide.
  • You want to and are able to maintain the plugin you are registering, long-term.
  • You understand why the plugin you are registering works.
  • You have read and acknowledge the Code of Conduct.

What is the name of your plugin?

Prusa Chamber Light (identifier chamberlight)

What does your plugin do?

Turns the chamber light of a Prusa CORE One on and off from OctoPrint (navbar button and sidebar panel).

The Buddy firmware has no documented G-code for the chamber light. Its M151 command sets a temporary custom colour on the chamber LED strip for D milliseconds, and on the CORE One only the white channel of that strip is wired, so M151 R0 G0 B0 D4294967295 keeps the light off and M151 ... D0 hands control back to the printer's own brightness settings. The plugin re-applies "off" when OctoPrint reconnects after a printer restart.

Optionally (off by default, marked experimental), it sets the light's brightness through Prusa Connect, because no G-code reaches the brightness setting. This uses the same request the Connect website makes and the user's own Prusa account login (an OAuth refresh token the user pastes in, renewed automatically). The README explains that this is an unofficial API and that the token is stored in config.yaml.

Where can we find the source code of your plugin?

https://github.com/Aryeh95/OctoPrint-PrusaChamberLight

Was any kind of genAI (ChatGPT, Copilot etc) involved in creating this plugin?

Yes. The code was written with Claude Code. I directed it, reviewed it and tested it on my own CORE One. The approach comes from reading the Prusa-Firmware-Buddy source and from capturing the request the Prusa Connect website sends.

Is your plugin commercial in nature?

No.

Does your plugin rely on some cloud services?

Only the optional brightness feature, which talks to Prusa Connect (connect.prusa3d.com) and Prusa Account (account.prusa3d.com) over HTTPS. It is off by default; on/off works locally over USB with no internet access. If Prusa Connect is unreachable, only the brightness control reports an error. The registration file sets the cloud attribute for this reason.

Further notes

Tested with a CORE One on firmware 7.0.0, on OctoPrint 1.11.8 and 2.0.0rc5. The plugin is not affiliated with Prusa Research.

@jacopotediosi jacopotediosi left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for your contribution!

Both plugin sources and this PR look good.

@jneilliii
jneilliii merged commit 8236552 into OctoPrint:gh-pages Oct 6, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

4 participants