Hey everyone! We’re working on an app for Amplipi, if you’d like to try it out on Android there’s an APK here.
Update: the app has been released on the Google Play Store, get it here!
Update 2: the app has been updated to fix the MDNS problems some people were having, not if no AmpliPis are found over MDNS it checks to see if it can connect to the default hostname of “amplipi”, finally if that doesn’t work the user can enter an IP address manually.
Hi there - could you posted some screenshots?
Great work by the way!!
The android app is a wrapper around the web app that uses zeroconf to discover AmpliPis with 0.1.7+. No need to type those silly ip addresses any more! Here are a couple of screenshots:
Startup (scanning for AmpliPi):
AmpliPi view:
Just in case you didn’t see the post here, the app is live in the play store: https://play.google.com/store/apps/details?id=com.amplipishellapp.
My amplipi is on a different subnet from my phone, and I’ve been unable to get zeroconf to find the device. What flavor of zeroconf are you using? I’ve tried opening all the usual ports to no avail.
A possible improvement (although I’m not sure it would matter to 99% of your users) is to also look for the amplipi DNS name. It seems the app currently only uses zeroconf.
mDNS (the part of zeroconf we are using) doesn’t work across subnets. That’s a good suggestion to try the amplipi hostname though, we’ll see if we can add that.
It’s looking like we also need to add an option to specify the AmpliPi’s ip. I made an issue for it on GitHub
We are using a python library called zeroconf which interfaces to the default mdns daemon on Raspbian, avahi.
Looking into it this is also a problem with things like airplay. Here are some instructions I found on handling this generically: https://www.vivitek.eu/Download/Documents/Enabling_iOS_Mirroring_in_a_Multiple-subnet_Environment.pdf
Agreed, the ability to manually enter an IP would be a great fallback option. Hell, that would be good enough for me… I can type “amplipi” once. 
I am on the same 192.168.178.0/255.255.255.0 subnet (standard subnet of the fritz boxes produced by AVM) with my smartphone (Pixel 5, newest updates installed) as well with my chromebook and the app can’t even find the AmpliPi in both cases. Later this or next year I plan to add the AmpliPi to my Homeautomation subnet 10.0.0.0/255.0.0.0.
A manual setting of the device’s IP address in the app would be highly appreciated, indeed.
Hey there!
We actually just pushed this feature out a few minutes ago! You should be able to update your app and then when an AmpliPi isn’t detected you’ll be able to enter an IP address manually.
Works like a charm now. No settings required now, though. Thanks!
