Octopi as Acsess Point

I am trying to set up octoprint on a raspberry pi as an aces point because I am going to do a demonstration for a church youth group so I wont be able to use a WiFi network to connect. My printer is reliant on octoprint. I saw it set up like that in this video but I don't know how to set it up in that configuration and I wasn't able to find a tutorial. Does Anyone know how to do this?

Don't know if the plugin still works or not, but I assume the above link's instructions for linux should still be relevant.

you may want to check out the Mr. Beam forks of those projects though, as it seems they are recently updated.

You could also try this one

I have this page from Raspberry Pi bookmarked:

I am trying to install netconnectd_mrbeam. On the step where you run the flowing command I get an error.

sudo hostapd -dd /tmp/hostapd.conf
hostapd: command not found

I am not sure what is causing this but I have not been able to fix it.

Did you do the first step:

Prepare the system

Install the hostapd, dnsmasq, logrotate and rfkill packages:

sudo apt-get install hostapd dnsmasq logrotate rfkill

Yes I did. I tried running running it again and got this.
Screenshot 2021-09-03 144417


sudo apt update

If you get this error

E: Repository 'http://raspbian.raspberrypi.org/raspbian buster InRelease' changed its 'Suite' value from 'stable' to 'oldstable'
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.


sudo apt-get update --allow-releaseinfo-change


That worked. I made it to this point where I got an error. I am new to Linux so I have no idea what to do here.
Screenshot 2021-09-03 154710

looks like you're missing setuptools in your python environment. Should be able to fix with sudo python3 -m pip install --upgrade pip setuptools wheel.

Also, just noticed that the commands listed on the mr beam readme is cloning the original repo and not their fork.

git clone https://github.com/foosel/netconnectd

should be

git clone https://github.com/mrbeam/netconnectd_mrbeam

Why don’t you simply add a static ip and use a network cable, since it’s going to be something temporary?

I realize that you have spent a great deal of time trying to set this up. If this demonstration is just a one time thing, and you want to minimize the custom setup, why not just grab your wi-fi router and bring it with you to the demonstration. Power on your router, computer and printer and they should all connect (except there will be no interbnet access) and printing should happen just as if you were home.

1 Like

That's a great idea. I initially thought this would be easier. Thanks for your replies.

Another suggested quick fix is to just physically connect your computer to the Pi with Cat 5 cables and a hub.

Good luck.

For a direct connection, both machines will need static IP addresses.

You can even eliminate the hub if you use a crossover cable or either one or both ethernet adapters support auto-sensing.

What ip would you use for that?

It wouldn't really matter as long as they are on the same network, so something as mundane as and should work.