We’re excited to announce a new action for pisound’s button! Running the usual install commands from http://blokas.io is enough to update!
Triple-clicking it will reconfigure the WiFi of RPI3 board to behave as an Access Point (a.k.a. Wireless Router), as well as start ‘touchosc2midi’ monitor which will be ready to listen and forward MyOsc data as MIDI to other software such as puredata.
By default, the AP will appear as ‘pisound’, and the default password is ‘blokaslabs’ (without quotes). You can change the name and password by modifying /usr/local/etc/pisound/hostapd.conf Keep in mind that this file gets backed up and overwritten after reinstalling the pisound-btn software.
The default IP address of RPI3 is 172.24.1.1 which you can use for ssh, VNC or wireless OSC / MIDI data! That means that you can easily interact with your system using just your laptop or phone, no more wires apart from power supply is needed! And it gets better, if the LAN cable is connected to RPI3, it will share the Internet with the connected devices.
Triple-clicking again will revert to regular WiFi behavior.
Hi. I just started to work with pisound and the first hurdle seem to be the triple click AP mode. I does not work. Is there a AP trouble guide somewhere? Thanks
Hi Giedrius. Thanks for your fast reply. I am using a pi3 / onboard wifi with the latest raspbian. I am not sure why it did not work in the beginning but now after some fideling and restarts AP mode works great.
Thought I’d add my experience with the triple click WiFi
First the clicks require to be pretty rapid, or they may be interpreted as single ones.
Secondly, initially it wouldn’t work. This was because I already had Wifi set up in wpa_supplicant.conf for auto connection, and this stopped the script from starting the access point correctly. The solution was to clear out the wpa_supplicant.conf network information I had added so that on startup WiFi was NOT automatically connected to my existing wireless hub. Then the triple click got the access point going correctly.
The pisound is a great bit of kit. I’ve just ordered a second one!
My pisound also doesn’t put out any wifi hotspot with triple button clicks…
i have edited wpa_supplicant.conf as blank file as advised above. however, triple button click doen’t work…
any help is appreciated.
my pisound is up to date
I have a similar issue with triple button.
Im auto connected to my Wireless router, and the triple button doesnt activate hotspot.
Does it only work when auto connect is disabled?
Im using the newest PATCHBOX. Any idea? Thanks!
If you have changed the default WiFi hotspot password, make sure you use a password that is between 8 and 63 characters, otherwise the hostapd will refuse to run. A check for this will be implemented soon in patchbox config utility.
You can check for errors by running:
sudo systemctl status hostapd
sudo journalctl -u hostapd
Hi Giedrus,
Thanks Ive tried but no luck so far, also checked the post, but cant find the hostapd file.
here is what both commands give back. Im running Patchbox
hostapd.service - Advanced IEEE 802.11 AP and IEEE 802.1X/WPA/WPA2/EAP Authenticator
Loaded: loaded (/lib/systemd/system/hostapd.service; disabled; vendor preset: enabled)
Active: inactive (dead)
Jul 24 18:22:12 patchbox hostapd[7059]: wlan0: STA 78:4f:43:73:96:ea IEEE 802.11: associated
Jul 24 18:22:12 patchbox hostapd[7059]: wlan0: STA 78:4f:43:73:96:ea RADIUS: starting accounting session C19C02C6CC208CA5
Jul 24 18:22:12 patchbox hostapd[7059]: wlan0: STA 78:4f:43:73:96:ea WPA: pairwise key handshake completed (RSN)
Jul 24 18:23:02 patchbox hostapd[7059]: wlan0: STA 38:ca:da:a2:24:83 IEEE 802.11: associated
Jul 24 18:23:02 patchbox hostapd[7059]: wlan0: STA 38:ca:da:a2:24:83 RADIUS: starting accounting session 738FB55C039FB25D
Jul 24 18:23:02 patchbox hostapd[7059]: wlan0: STA 38:ca:da:a2:24:83 WPA: pairwise key handshake completed (RSN)
Jul 24 18:31:09 patchbox hostapd[7059]: wlan0: STA 78:4f:43:73:96:ea WPA: group key handshake completed (RSN)
Jul 24 18:31:09 patchbox hostapd[7059]: wlan0: STA 38:ca:da:a2:24:83 WPA: group key handshake completed (RSN)
Jul 24 18:32:15 patchbox systemd[1]: Stopping Advanced IEEE 802.11 AP and IEEE 802.1X/WPA/WPA2/EAP Authenticator…
Jul 24 18:32:15 patchbox systemd[1]: Stopped Advanced IEEE 802.11 AP and IEEE 802.1X/WPA/WPA2/EAP Authenticator.
Journalctl:
– Logs begin at Wed 2019-07-24 01:43:12 BST, end at Wed 2019-07-24 18:40:09 BST. –
Jul 24 18:12:22 patchbox systemd[1]: Starting Advanced IEEE 802.11 AP and IEEE 802.1X/WPA/WPA2/EAP Authenticator…
Jul 24 18:12:22 patchbox hostapd[5610]: Configuration file: /etc/hostapd/hostapd.conf
Jul 24 18:12:22 patchbox hostapd[5610]: Failed to create interface mon.wlan0: -95 (Operation not supported)
Jul 24 18:12:22 patchbox hostapd[5610]: wlan0: Could not connect to kernel driver
Jul 24 18:12:22 patchbox hostapd[5610]: Using interface wlan0 with hwaddr b8:27:eb:9a:4c:78 and ssid “patchbox”
Jul 24 18:12:23 patchbox hostapd[5610]: wlan0: interface state UNINITIALIZED->ENABLED
Jul 24 18:12:23 patchbox hostapd[5610]: wlan0: AP-ENABLED
Jul 24 18:12:23 patchbox systemd[1]: Started Advanced IEEE 802.11 AP and IEEE 802.1X/WPA/WPA2/EAP Authenticator.
Jul 24 18:13:52 patchbox hostapd[5612]: wlan0: STA 38:ca:da:a2:24:83 IEEE 802.11: associated
Jul 24 18:13:52 patchbox hostapd[5612]: wlan0: STA 38:ca:da:a2:24:83 RADIUS: starting accounting session DE19CC3EB26CCD7D
Jul 24 18:13:52 patchbox hostapd[5612]: wlan0: STA 38:ca:da:a2:24:83 WPA: pairwise key handshake completed (RSN)
Jul 24 18:16:00 patchbox systemd[1]: Stopping Advanced IEEE 802.11 AP and IEEE 802.1X/WPA/WPA2/EAP Authenticator…
Jul 24 18:16:00 patchbox systemd[1]: Stopped Advanced IEEE 802.11 AP and IEEE 802.1X/WPA/WPA2/EAP Authenticator.
Jul 24 18:21:09 patchbox systemd[1]: Starting Advanced IEEE 802.11 AP and IEEE 802.1X/WPA/WPA2/EAP Authenticator…
Jul 24 18:21:09 patchbox hostapd[7056]: Configuration file: /etc/hostapd/hostapd.conf
Jul 24 18:21:09 patchbox hostapd[7056]: Failed to create interface mon.wlan0: -95 (Operation not supported)
Jul 24 18:21:09 patchbox hostapd[7056]: wlan0: Could not connect to kernel driver
Jul 24 18:21:09 patchbox hostapd[7056]: Using interface wlan0 with hwaddr b8:27:eb:9a:4c:78 and ssid “patchbox”
Jul 24 18:21:10 patchbox hostapd[7056]: wlan0: interface state UNINITIALIZED->ENABLED
Jul 24 18:21:10 patchbox hostapd[7056]: wlan0: AP-ENABLED
Jul 24 18:21:10 patchbox systemd[1]: Started Advanced IEEE 802.11 AP and IEEE 802.1X/WPA/WPA2/EAP Authenticator.
Jul 24 18:22:12 patchbox hostapd[7059]: wlan0: STA 78:4f:43:73:96:ea IEEE 802.11: associated
Jul 24 18:22:12 patchbox hostapd[7059]: wlan0: STA 78:4f:43:73:96:ea RADIUS: starting accounting session C19C02C6CC208CA5
Jul 24 18:22:12 patchbox hostapd[7059]: wlan0: STA 78:4f:43:73:96:ea WPA: pairwise key handshake completed (RSN)
Jul 24 18:23:02 patchbox hostapd[7059]: wlan0: STA 38:ca:da:a2:24:83 IEEE 802.11: associated
Jul 24 18:23:02 patchbox hostapd[7059]: wlan0: STA 38:ca:da:a2:24:83 RADIUS: starting accounting session 738FB55C039FB25D
Jul 24 18:23:02 patchbox hostapd[7059]: wlan0: STA 38:ca:da:a2:24:83 WPA: pairwise key handshake completed (RSN)
Jul 24 18:31:09 patchbox hostapd[7059]: wlan0: STA 78:4f:43:73:96:ea WPA: group key handshake completed (RSN)
Jul 24 18:31:09 patchbox hostapd[7059]: wlan0: STA 38:ca:da:a2:24:83 WPA: group key handshake completed (RSN)
Jul 24 18:32:15 patchbox systemd[1]: Stopping Advanced IEEE 802.11 AP and IEEE 802.1X/WPA/WPA2/EAP Authenticator…
Jul 24 18:32:15 patchbox systemd[1]: Stopped Advanced IEEE 802.11 AP and IEEE 802.1X/WPA/WPA2/EAP Authenticator.
So Im sorry to use this thread now as I think its related to here,
but since I deleted my WIFI information from wpa_supplicant.conf,
and re-registered my WIFI settings, it takes up to 1 minute to connect to Pisound through my Routers Wifi. Hotspot connection works normal though. What could have caused this? It was working perfectly before? I have no idea where to look @Giedrius
Anyway hope its clear enough described.
Check if there’s any high CPU usage processes, on receiving SSH connection, a new process is supposed to be spawned, if the system does not have enough resources available immediately, it will get delayed.
We’ll try to reproduce the issue on a fresh setup and see whether we can improve something there.