I've been using this plugin for the past few years to mainly engage Torch Mode with a small, 12-LED ring situated around the lens of a PiCam. Yesterday, to overcome the "Old Python Nag", I used Imager 2.0 to build a new Octopi based on Octopi 1.1.0 (build 2025.12.01.130812). Made an OctoPrint backup of the working & fully-up-to-date Octopi 1.0.0 and restored it to the new Octopi 1.1.0.
After the restore, everything worked as expected on the new Octopi except the WS281X plugin. In the past, after similar upgrades, I've had to run the OS Config Test in the plugin's properties to enable SPI by commands added to /boot/config.txt and that was the case here. After using the OS Config Test to enable SPI and rebooting, the plugin was still inoperative. A look in the plugin's log and the Octoprint log showed that SPI was not enabled. When I looked in /boot/config.txt, I found the two commands entered by the plugin as well as the warning that the real config.txt had been moved to /boot/firmware/config.txt. It appears /boot/config.txt is now simply an empty placeholder. When I manually copied the commands to enable SPI to /boot/firmware/config.txt and restarted, the plugin immediately began to function properly again. However, after removing these commands from /boot/config.txt the OS Config Test once again fails because it believes SPI is not enabled while the plugin continues to work just fine. Sharing the experience to point out a much-liked plugin's need for a possible tweak to account for changes in Octopi.
Thanks,
Kevin