Hi,
i have pi5, too. did you install octoprint.deploy or the normal octoprint? i have installed the deploy like it is described on github. but i can't run it.... wether i write octopi.local or the ip-adress or something else.
'octopi.local' will not work because you have not installed OctoPi.
octoprint_deploy installs OctoPrint - it's the same software, the first is just a script to automatically set it up for you.
I would recommend trying to use the IP address. If you are struggling to get it working, please make a post with as much detail as possible either here on the forums or on the OctoPrint discord server.
Hello guys
OctoPrint - the actual 3D print host software - works anywhere that runs Python, so you can install it yourself on normal RPi OS.
In fact, I have Octoprint working "almost" fine, after running OctoPrint_deploy script.
BUT, plugins that manage GPIO (eg. GPIO Status, GPIO Control, OctoRelay) doesn't work anymore (due to another change on RPi5 Hardware that can't addressed by RPi.GPIO).
Does anyone knows any upgraded plugin that can control RPi5 GPIO?
Thanks.
Have you tried PSU Control plugin yet? It uses a different underlying module for controlling GPIO that might work, although it's only going to control one pin.
Hi,
Thank you for your help 
I didn't use that plugin. Used now 
I was able to control the pins with System control and de pinctrl commands.
It is just one pin, but is better than none!
I'm struggling now with the opto-module relays I've bought (7!), that are Low Trigger models.
For some reason, they go ON with the High, Low and None values at the IN pin, It just go OFF disconnecting the pin, or connecting it to the source 5V pin. I can't figure out why (would be wrong labelled pins on the module...?)!
I have another model (Hight trigger) that works ok.
Can anybody give me any ideas to test and fix this?
Thanks!
I'm having the same issue (totally new to all this) - I've installed the program using octoprint_deploy, but i don't know how to actually run it after that lol.
octoprint_deploy usually gives you the address to access at the end of the wizard doesn't it, or in one of its utility options maybe? IIRC it's something like http://<ip>/instance_name_given_during_setup/ assuming you used the haproxy option.
Does anyone know if a stable version of octopi for raspberry pi 5 is being currently worked on? I have been struggling with getting the usb webcam running, serial disconnects and my network stability in my printing location.
I'm trying to decide if I just get a different pi and save the pi 5 for a different project. I know a diffrent pi can't solve all these issues but the more problems I can eliminate the better.
Thanks
I'm not having any luck either trying to deploy octopi on my PI 5 either. Any idea as to when it might be supported so I can just make a image and have it work. So frustrated that I'm thinking of giving up on the pi 5 and getting a pi 4.....
Full support for the RPi 5 requires hardware in the hands of both the OctoPrint and the OctoPi developers and some amount of time for them to do their magic. From personal experience, finding all the hardware required is still not straight forward unless one is willing to spend more on shipping than the cost of some of the items.
In the meantime, daily OctoPi builds for the RPi 5 are available, octoprint_deploy is available, and help with specific, well documented issues can be found in this forum.
With that being said, an RPi 5 is way more powerful than is necessary to run OctoPrint and one (or more) cameras. An RPi 3 or an RPi 4 are both very capable and available. An RPi Zero 2 is supported (although I personally prefer one of the other two).
Another option (which I have tried) is a Libre Le Potato. It is very similar to the RPi 3B or 3B+ with 2GB of memory instead of 1GB and support for an eMMC disk but needs a USB dongle for WiFi. Using octoprint_deploy was successful as was adding a USB camera. This option does require "tinkering" similar to what is required now for an RPi 5.
Using a solution "more powerful" than required leads one down the road of adding yet another application because there is excess capacity until one day, the 3D prints are exhibiting artifacts (blobs and zits) often caused by "some other application" preventing OctoPrint from delivering gcode in a timely fashion to the printer. The Raspberry Pi OS is not a real-time OS so one cannot guarantee the performance of any single application.
1 Like
Thanks for the reply. I have managed to fix my network issues and I think I have the camera working. I had to update the boot/octopi.txt to match my usb camera's resolution and frame rate exactly. If I'm this far I don't think I'll be buying another device just to go through it all again.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.