WS281x LEDs are very simple to wire with their 3 LEDs. There are three options of how to wire, each detailed below.

Raspberry Pi Wiring

The hardest part about wiring with a Raspberry Pi is connecting up the 3.3v logic from the Pi to the strip that wants 5v. There are several ways you can do this, which are described in more detail below.

No Level Shifting

It is possible to connect the LEDs up without any kind of level shifting, however mileage varies from strip to strip. I have one setup like this, and one with the full logic shifter. This can work because the spec of the LED strips means they need 0.7 * VDD(5v) which is ~3.5v. Close to the Pi's 3.3, so depending on how tight of a tolerance your strip has, this is possible.

Wiring is as follows:

• Pi GND to LED GND

• Pi to LED Data in

• Power supply GND to LED GND

• Power supply 5V to LED 5V

You can use a level shifting chip to convert the signals from 3.3v to 5v. Recommended one to use is a 74AHCT125, I have this and it works well.

Wiring of this is as follows:

• Common ground between:

  • Pi GND

  • LED GND

The diode method is a quick way to reduce the power supply voltage slightly, so that the LED strip can read the 3.3v.

Wiring is as follows:

• Pi to LED Data in

• Power supply 5V to 1N4001 diode anode (side without the stripe)

• 1N4001 diode cathode (side with the stripe) to LED 5V

I've tried to make this setup process as simple as possible, while it was already easy it is even easier with this guide.

Installation

Install the plugin via OctoPrint's bundled plugin manager or manually using this URL:

https://github.com/cp2004/OctoPrint-WS281x_LED_Status/releases/latest/download/release.zip

Once you have installed and enabled the plugin, OctoPrint will prompt you to restart the server.

Check you have the right hardware:

Next up: Wiring your LEDs

The plugin implements a SimpleAPI as provided by OctoPrint, which enables external access to the plugin's functionality.

It has a single endpoint, supporting a get request and posting a command.

SimpleAPI Get

GET http://octopi.local/api/plugin/ws281x_led_status

Get current state of the plugin, which includes the light status and the torch status.

Headers

POST http://octopi.local/api/plugin/ws281x_led_status

Send commands to the plugin, to make it do something.

Press the 4 buttons to check that each segment of your LEDs are working. Useful if the colours are showing wrong, some LEDs don't work or anything hardware related. Each button sets that colour to maximum intensity, to isolate the individual colours.

The popup box will run a configuration test on your OS. It tests for the same things that the , to allow you to verify everything is OK down the line.

At any time, you can run a test of the above settings, using the configuration test dialog. When you run the test, it will tell you if all of the steps are filled in correctly, and if they are not, prompt you to fix it with a click of a button.

This data is also logged to octoprint.log on startup, to help me with diagnosing issues reported to rule out this configuration being the problem.

Calculates the approximate power consumption of the LED strip. Useful to work out if your power supply is up-to-the task.

Each progress effect has some standard options, to customise them. Individual effects have additional options, listed alongside them.

• Enabled

• Progress Colour The colour to indicate the progress of whatever event is happening.

The 4 types of LED strips that the plugin supports are:

• WS2811 (including B variants)

• WS2812 (including B variants)

The plugin reacts to several events to display printing effects. For each of these effects, they have similar settings:

• Enable Whether the effect will run or not

• Effect One of the available

This documentation should tell you all you need to know about how to use the plugin. There's a lot of information here, please be sure to read some of it before opening issues in case the solution is here.

The plugin uses the Raspberry Pi's SPI interface to push data to the LED strip, rather than PWM since it doesn't need to be run as root to use SPI.

As a result of this, there are a couple of OS level configuration items that need to be handled. Luckily for you, the plugin makes this very easy for you to do by providing a UI to run the commands.

The setup wizard requires root access, and therefore the password for the Pi user if you have not configured passwordless sudo, as is default on OctoPi. This password is not stored, and is only used for the steps below.

• Add the

Open the plugin's entry in OctoPrint's settings interface, and you should be presented with this view:

Click on the 'LED Strip Settings' button in the top right. The key settings you should edit are listed below:

• Strip Type Select the type of strip you have connected to your Pi. Note: This may not be exactly what you were sold, sometimes they send variations. If you have issues, please try similar strip types here.

• Number of LEDs This should be easy, count the number of LEDs you have connected and enter the right number!

• Max Brightness This setting controls the maximum brightness that your LEDs should reach.

For more details on the rest of these settings, please see the

This documentation aims to explain all of the settings in the LED Strip Configuration dialog, so you can make the most use of them.

Commands should be formatted as such:

M150 [P{intensity}] [R{intensity}] [G{intensity}] [B{intensity}] [W{intensity}]

All of the parameters are optional, and can be included in any order. If an option is not included, its value is 0 - as a result sending an empty M150 command will turn the LEDs off.

Examples:

On a standard RGB WS281x strip, the W parameter sets an equal value of R, G and B on the LEDs.

If you have an RGBW strip and enable the 'Use dedicated white' setting, the W parameter will control the white LEDs only.

Sending any of R, G or B with the command takes priority over the W.

From OctoPrint's documentation:

@ commands (also known as host commands elsewhere) are special commands you may include in GCODE files streamed through OctoPrint to your printer or send as part of GCODE scripts, through the Terminal Tab, the API or plugins. Contrary to other commands they will never be sent to the printer but instead trigger functions inside OctoPrint.

The plugin reacts to some different @ commands, listed below:

These commands can be used in g-code scripts, or in custom controls in apps - see here for , or the guide on how to create a which also uses @ commands.

The plugin needs to be able to access 3 files to run. These are:

• /boot/config.txt

• /boot/commandline.txt

• /proc/device-tree/model

It also needs access to the underlying hardware to drive the LEDs. To do this it will need to run privileged with docker.

Add the following mappings to docker-compose.yml under the volumes: section of the OctoPrint service

To enable access to the hardware to drive the LEDs, the container must be run privileged:

The final file should look something like this Gist:

Using WS281x LEDs to create a flash for a timelapse

By using the power of @ commands it is very easy to make your LEDs react to other plugins that use GCODE scripts. For example, to make the LEDs flash for the timelapse, to light it up, you can use the following settings:

• Enable 'Torch mode is a toggle' in the WS281x LED Status settings, and set the torch effect to solid colour & bright white (and colour will do, but white is the most common!)

• OctoLapse Custom Camera Gcode Scripts

  • Before snapshot:

  • After Snapshot

That's it! Run OctoLapse in test mode to test it out.

This is going to be an ever-evolving page, as I learn of common issues people identify when setting up the plugin.

What type of issue are you facing?

These questions aim for self-diagnosis - there is no guarantee that your problem will be listed!

• No LED output at all

• Unstable LED output, flickering, random colours

First things first, make sure that your OS configuration test passes - the LEDs do not usually work without these tests passing.

It is likely that the OS level config is incorrect. To fix this, please head to the OS Configuration Test section (under 'Utilities') to run a test and fix the configuration.

The dependency the plugin relies on needs to be updated for every new Raspberry Pi board. This often happens quickly, but your install may be outdated. You can manually upgrade the dependency to the latest version:

Some strips do not like 3.3V signals, and if you do use 3.3v (without a level shifter) then please keep the wires to the LEDs fairly short to avoid voltage drop. Alternatively, use a level shifter if it seems that you are suffering from this issue.

Some GPIO touchscreens (and possibly some others?) use SPI to process data. This conflicts with this plugin's use of SPI to drive the LEDs and as a result you may not be able to use both.

Errors in the log file are similar to this:

Unfortunately, there is nothing you can do about this. If you know what you are doing, you may be able to run the LEDs using PWM but please note that this requires root access to the Raspberry Pi and for security reasons this is not recommended for OctoPrint.

You need a common ground between the LEDs, power supply and the Pi - this is the number one cause of flickering. Please check the to see how it should be done. You can also see the .

Adding a 470Ω resistor in the signal line can help. Some guides recommend this, in my experience it is not always required. Worth a try if you have unstable signal to the LEDs.

Mixed reports that using a sacrificial LED on a short wire (to avoid voltage drop) can be beneficial for the LED strip. See for more details. This solution is untested, only linked because it might be useful. Support for skipping the first LED on the animations is in the next release of the plugin.

Make sure you have the correct order of RGB strip selected in the strip settings. You can use the LED Strip test to help debug this issue quickly. The colour order and strip type you were sold is not necessarily what works, do not hesitate to change the strip type settings until it works!

My current theory behind this issue is bad power supply to the Raspberry Pi, which will create a throttled and unstable system. This can impact the precise timing the LEDs require and means they only display white.

To fix the issue, please use an adequate power supply with your Raspberry Pi. See the for details on the specification for power supplies for different models.

Make sure you restart the OctoPrint server, and reload the web interface. You should see the wizard pop up, or the light/torch icon in the navbar. I have had some reports of caching meaning the configuration wizard does not show.

This plugin requires a Raspberry Pi to run. It should run on any Linux-based OS on any Raspberry Pi, and it has detection mechanisms in place and will not load if the device it is installed on is not a Pi. This is logged, so you will see an explanation in the octoprint.log file if this is the case.

If you are using docker, then make sure you have followed the page to get the plugin to run.

Here's all the details of the additional features of the plugin, so you can effectively configure them.

Torch

The torch button can be turned on or off to clear up navbar space if you don't want it. It has the same settings as standard effects but with some added extras for a manual trigger.

Using @ commands to trigger the torch can enable cool integrations with other software, such as OctoLapse.

Toggle Mode

The torch button or @ command turns the torch on permanently, until it is turned off. This blocks any other effects.

Timed Mode

The torch button starts a timer to turn off after configurable length of time.

Active Times

The LED strip will turn on at the start time, off at the end time. Potentially useful if you don't want them on overnight.

Enable intercepting and using M150 commands. If not checked, these commands will be sent to the printer.

For documentation of the command, please see the

Debug logging logs a lot more information about the effect runner process. This will help massively when reporting issues on Github, so please enable it when reporting issues!

Native Integration

These apps have built in support for WS281x LED Status, allowing you to control your LEDs directly within them. Thank you to their respective developers for implementing support!

OctoApp has built in support for buttons that can turn your LEDs on and off or activate the 'torch' mode. It also has support for the 'automatic torch on when viewing the webcam' feature, so you can see your prints easily. See a quick demo of this in action, check out the video below:

Non-native integration

Not all apps can integrate with every plugin, so many of them choose to support Host @ Commands instead. This allows you, as the user to define custom controls that use these commands as you wish and use them in a variety of 3rd party apps.

Here are some examples of apps that support Host @ Commands:

Please select the area that most describes what you need help with:

• Configuration of the plugin

• Connecting LEDs and getting them to work

There's a lot of documentation here, that describes in detail the configuration options and the features of the plugin. Be sure to read the pages under the configuration section, such as

Probably the step that has the most problems, you're not alone here.

Please double check that you have wired the LEDs exactly as shown in the and double check all connections.

Next up is the , where there's a list of common problems identified with solutions. Please check there and make sure your problem isn't listed, or try some of the recommended solutions.

Really? You found a bug? Ok then, best make sure it is fixed.

Please open a bug report issue providing as much information as possible, including:

• (Always) octoprint.log file

• (Always)plugin_ws281x_led_status_debug.log file, preferably with enabled.

• Clear, easy steps to reproduce.

Please use the