your guide is missing a path statment. in your firmware updater , for exsample /usr/bin/dfu-util will show the path is invail when you chick the test button. thats because your missing the path statment. when you login into your pi you need to add PATH=$PATH: /usr/bin/dfu-util for the firmware updater to vaildate the path. this will be true for the other firmware paths. PATH=$PATH:/your firmeware path

[blade359]

Hardware Setup Please board type and printer make and model.

Describe the problem Please provide a clear and concise description of what the problem is, including details of any error messages you receive (screenshots are helpful).

Log Files Attach the OctoPrint log and the Firmware Updater log Log files, which can be accessed under Settings -> Logging in OctoPrint, or in ~/.octoprint/logs/ on the host. Both octoprint.log and ~/.octoprint/logs/plugin_firmwareupdater_console.log should be included.

Additional context Add any other context about the problem here.

[benlye]

No, that's not the way it works. There's no need to modify the path at all.

(Also, when you create a Github issue, please don't put the entire description in the title. You can use the description for that.)

[github-actions[bot]]

This issue has been automatically locked because there was no further activity after it was closed. Please open a new issue for any related problems.