Welcome, Guest

NOTE: This is a "Community" forum. Please be mindful that community members are here to help as part of a community effort. We therefore appreciate your effort in keeping this forum a happy place!

If you have a specific issue (e.g. hardware, failure) and want help from our support team, please use our tech support portal (Support menu - > Contact Us).
Thanks a lot of your help in making a better community.

Page:
1

TOPIC:

Device Console + Flex + Raspberry Pi 4 2 months 3 days ago #64961

madrac
Topic Author
Offline
New Member
Posts: 8
Thank you received: 2

Yesterday, I updated my Flex firmware and Audio driver to begin using the new device console. I also updated minidsp-rs on my Raspberry Pi 4 to the latest version (0.1.9). Based on what I read, I think this version (or the previous, 0.1.8) are needed to see the Flex in DC via the Pi.

However, I am still not seeing the Flex in the DC. I'm not sure what I'm missing (or does one have to use the minidsp wifi dangle as per the manual)?

ezBEQ still works via my Pi from both my laptop & cell phone. Similarly, I can still connect wirelessly via the Pi to the Flex with the old plug in & entering the IP address.

Although I'm not certain it is needed (or is just for the minidsp cell phone app), I even tried editing the /etc/minidsp/config.toml mentioned in the ezBEQ thread (pg 156, mrene): advertise = { ip = "xxx.xxx.x.xxx", name="yyyy" }
I tried typing it in directly under the tcp server bind address as well as just removing the # & editing ip/name in the line already in the config file. In either case, I did reboot the pi.

I did search this thread and the ezBEQ thread mentioned above but didn't see anything else other than what I did/tried.

Any suggestions on how to get the Flex to show up in the DC via Pi?

Please Log in or Create an account to join the conversation.

Device Console + Flex + Raspberry Pi 4 1 month 2 weeks ago #65155

madrac
Topic Author
Offline
New Member
Posts: 8
Thank you received: 2

I was able to get the DC working with the Pi.

If anyone else is having issues, here is what I did:

On the Pi, edit: /etc/miniDSP/config.toml as follows. You may need to change the file's permission to "owner and group", not "owner" to edit.

# If desired, an api can be exposed over the local network
[http_server]
# bind_address = "127.0.0.1:5380"
# Replace the previous line by this one in order to allow connections from other hosts
bind_address = "0.0.0.0:5380"

# TCP servers can be setup to support using the native "plugin" apps to manage the device
[[tcp_server]]
# bind_address = "127.0.0.1:5333"
# Replace the previous line by this one in order to use the plugin app from another machine
bind_address = "0.0.0.0:5333"

#

Advertise the following address for the official minidsp mobile app
# advertise = { ip = "192.168.1.100", name="Living Room Pi" }
advertise = { ip = "xxx.xxx.x.xxx", name="yyyyyy" }

where xxx.xxx.x.xxx is IP address of your miniDSP and yyyyy is the name you want to advertise.

To find the IP address, open a terminal on the Pi. Enter the command: hostname -I
The IP address is the first part of the output.

Next, on the Pi, edit /lib/systemd/system/minidsp.service. Again, you may need to change permission (it wouldn't let me), so I opened a terminal and ran the following command: sudo pcmanfm.

Add the following line under Service:
[Service]
ExecStartPre=/bin/sleep 30

I rebooted my Pi after that. Voila, can now see my Flex in the device console.

Please Log in or Create an account to join the conversation.

Last edit: by madrac.

Page:
1

Support

Community Forum

Community Support

Flex series

Device Console + Flex + Raspberry Pi 4