Add Alexa OctoPrint

[RICLAMER]

• 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?

Alexa OctoPrint

What does your plugin do?

It exposes selected OctoPrint and 3D printer actions as Philips Hue compatible devices that Alexa can discover and control directly over the local network. Supported actions include print control, motion, heating presets, emergency shutdown, configured files, and optional OctoPrint-Enclosure power/light outputs.

Where can we find the source code of your plugin?

https://github.com/RICLAMER/AlexaOctoPrint

The repository contains the public documentation and current source distribution package under plugin/.

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

Yes. OpenAI Codex assisted with implementation, tests, debugging, and English documentation. The maintainer defined the requirements and performed iterative testing against a physical Raspberry Pi, OctoPrint installation, Alexa devices, printer, and Enclosure outputs. The registration metadata includes the required ai-developed attribute.

Is your plugin commercial in nature?

No.

Does your plugin rely on some cloud services?

No cloud backend or Alexa skill is used for discovery or control. Runtime device communication stays on the LAN. GitHub is used only for package distribution and Software Update version checks.

Further notes

Version 0.1.7 was installed from the public archive and validated on OctoPrint 1.6.1 with Python 3.7.3. OctoPrint's forced Software Update check reports the installed and available versions as 0.1.7 and up to date.

Alexa's local Hue integration requires root Hue routes on port 80. On OctoPi, the documented setup keeps HAProxy as the only port 80 listener and selectively forwards the required paths to OctoPrint. The plugin does not modify system services automatically.

[jneilliii]

GitHub is used only for package distribution and Software Update version checks.

This is the most convoluted method of updating I've ever seen in a plugin hosted on GitHub. You would benefit by looking at other plugin examples and their repository rather than blindly trusting your AI code tools.

I feel like if you are going to use a "Proprietary" license that you should link to that license file in the plugin's description since it's not a common/known open source license.

Is there any information related to Alexa's local Hue integration that you can link to?

I'm not as familiar with haproxy configurations but looking at your example on the repo, I'm concerned about

use_backend alexaoctoprint_hue if METH_POST alexaoctoprint_api_create

will that not force all api posts to your backend?

Also, did you leak your own api key in that haproxy config example, or is the following line related to Alexa local Hue integration?

acl alexaoctoprint_api_user path -i /api/2WLEDHardQrI3WHYTHoMcXHgEspsM8ZZRpSKtBQr

These are just my initial notes, and I'm sure there will be more when someone can dig through the code and how it's implemented, but as it stands now with the zip file distribution on GitHub reviewing the plugin is over cumbersome (requires me downloading the zip, etc.) and therefore that needs to be addressed in my opinion before I'm going to spend the time to do a proper review.

[jacopotediosi]

Sorry, I've had enough just seeing that the repository contains a zip file instead of the actual sources and the API key leak Jim described above. I won't waste my time reviewing this PR and am voting for its closure.

[foosel]

@jacopotediosi agreed