no wireless?

[mikeblome]

I have jambox working via urlrelay and a wired connection on a Raspberrypi 4. A great setup that works out of the box! Now I'd also like to be able to use the device for general computing with wireless but there doesn't seem to be a wireless interface. I created a wireless connection via Preferences > Advanced Network Connection, but the icon in the upper right still says "No wireless interface". Under "Preferences > Configuration > Interfaces" I don't see an option for "Wireless." Is this expected? If so how to enable the wireless interface, and if not, how to troubleshoot?

[kdoren]

I disabled WiFi to keep people out of trouble, it really doesn't work for online jamming.
If you want to use WiFI, first you need to stop disabling it on boot:

sudo sed -i 's/^dtoverlay=disable-wifi/#dtoverlay=disable-wifi/' /boot/config.txt

Then, after first reboot, you need to set your country (it won't enable until you do that).
This is done by clicking the network up/down arrow icon on the taskbar at the very upper right.
Then after turning on WiFi, you can select a network and login.

[mikeblome]

Thanks!

[techtalktoll]

Actually glad the WiFi is disabled. Pi4 that I have x2 always pickup ticking noise from WiFi antenna when USB interface is plugged in. Only solution is to adjust antenna until it goes away. The UMC2 and Audiobox both produce this tick on both Pi4s. Took a while to find. Happens with both WiFi routers.

[kdoren]

@techtalktoll That's interesting, RF from the antenna causing noise in audio. Another reason to disable WiFi is that, even if you aren't using WiFi, it creates background CPU activity that can cause Xruns (audio frames getting dropped).

[mnopneal]

So, how awful bad is it? What I'm looking to do: at church we have a jambox in the sanctuary, and a linux jamulus server in the office. The sanctuary jambox is fed from our X32 digital audio mixer. I was looking to be able to put someone in the hall next to the sanctuary with a jambox to LISTEN to the internet audio Stream, and maybe adjust the stream mix with a tablet. So latency really isn't a problem. We just want them isolated from the sound in the sanctuary. Since it's all local LAN latency should be minimal.

[kdoren]

Thanks!. I think distributing a bootable image file takes a lot of pain away from end users. They start with exactly what I tested.

FYI even on wireless, noVNC should work [providing you first configure WiFi while connected with a wire]; you don't need a monitor unless you want one. If you are using a monitor, you'll want to change HDMI mode in /boot/config.txt for the larger screen.

If you have multiple jamboxes on same network, you should set them to different NODE_ID in /etc/urlrelay/urlrelay.conf, otherwise urlrelay.com won't know which box to redirect you to.

I haven't tested auto connect with wireless, but it should work. Might require an extra delay in startup script.

[mnopneal]

Hmmm. Even with going back to /boot/config and UNcommenting out the dtoverlay=wifi, and rebooting with the CAT-5 connected, it still doesn't seem to attempt to auto connect. I've attached the syslog file; it seems to have a pile of errors. Also jamulus conf file, which I had to rename to make Github happy. And the boot/config.txt - I'm confused on that since it seems like there are multiple assignments to dtoverlay - wouldn't the 2nd one wipe out the first? Is this supposed to be a delimited list? Or maybe I shouldn't think about this as a linear shell script?

config.txt
jamulus_start.conf.txt

syslog.log

[mnopneal]

BTW, this is using the 2021-11-20 image.

[kdoren]

in jamulus_start.conf, you set

JAMULUS_AUTOSTART=1
JAMULUS_SERVER=50.248.230.105

but later in the file, they are set again, which will overwrite the previous settings:

JAMULUS_AUTOSTART=0
JAMULUS_SERVER=

You'll need to delete or comment out the second section.

[mnopneal]

Well, it's obvious when you say it... in my defense I blame the tiny window. But, yes, that's it.