Repository navigation
Add plugin Prusa Chamber Light - #1494
Merged
Merged
Conversation
Aryeh95
force-pushed
the
add-chamberlight
branch
from
October 6, 2026 05:25
0085e5c to
63b0f71
Compare
jacopotediosi
approved these changes
Oct 6, 2026
jacopotediosi
left a comment
Member
There was a problem hiding this comment.
Thanks for your contribution!
Both plugin sources and this PR look good.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
M151command sets a temporary custom colour on the chamber LED strip forDmilliseconds, and on the CORE One only the white channel of that strip is wired, soM151 R0 G0 B0 D4294967295keeps the light off andM151 ... D0hands 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 thecloudattribute 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.