What is the problem?
I've been stuck using very old versions of Octoprint due to the way network config changed being detrimental to my ideal setup. This works, nothing is broken, but I want to update.
I have around 50 printers/CNC to manage, across several locations - my business' bureau service printers, R&D machines, my personal machines and printers belonging to customers.
At any time any of them can move between locations, so I have networking carefully set up to be identical at each site, with a whole subnet dedicated to Octopi devices.
The only way to manage the inventory stay sane is to:
- use static IP addresses for each Pi
- have the Pi itself force the static IP NOT the router.
- Be able to easily re-deploy new SD card images separately from the Pi and without having to locate it on the network.
What did you already try to solve it?
I've reviewed multiple how-tos and it seems like since octopi-network.txt was deprecated, there has been a philosophy change - maybe forced by changes to Raspbian/Pi OS - and now the 'right' place to change it on the Pi is from within the Linux filesystem. I've done this before and it's not a big deal for ONE pi.
But if I have 16 to update as I currently do? Nightmare.
For every one I appear to have to write a new SD image, put it in the Pi, FIND the dynamically allocated IP on my (local) router, PuTTY into it, navigate to the relevant config file, edit it in Vi and shut down.
This is WAY harder than:
- burn the same SD image to 16 SD cards on my desktop PC
- change 2 digits in a text file to match what's written on the SD card
- put the SDs back in the Pis on the printers with the same numbers
- Enjoy a beer and a TV programme in the time I saved compared to current!
Have you tried running in safe mode?
Additional information about your setup
CURRENT: OctoPrint 1.3.6 running on OctoPi 0.14.0, Raspberry Pi 0,1,2,3 & 4!
DESIRED: Latest Octoprint/Octopi into the future.
So this is not a moan, I propose to try to solve this in this way, and I'm seeking only constructive advice to achieve the goal I've stated:
- De-confuse myself regarding the current way people are setting a static IP - ideally both wired and wireless
- Filter and ignore ALL advice to 'just assign an IP on the Router' or similar
- Try to understand how octopi-network worked originally, and re-create this - which to me means creating a file in the Windows-readable 30mb partition, and setting up the linux system config file to read it to obtain its IP config info.
- resume my original process for redeploying Octopi
Has this already been done?
Is there a reason this CAN'T work? (IE forcing octopi-network.txt to be deprecated)?
Can anyone point me to how best to get the Linux config files to read a .txt file and grab the new details?
Thanks in advance for any info TOWARDS this goal not away from it!!!