Initial thoughts on the web interface

I received my unit this week and wanted to share my thoughts about the web interface.

The focus of the interface seems to be the inputs rather than the zones. For a party I can see being focused on inputs and which zones or groups to play that input in. For my day-to-day usage I would focus on a room and decide which input to play in that room. The presets can help with this for common usage patterns, but for some users those may be hard to create. It might be helpful to have a “create preset from current state” option, rather than requiring users to do so via the API.

One other interface note: Volume at 0 seems to not be the same as off. Perhaps that was done to encourage people to use the mute option and get the unit to go into standby mode.

That’s all for now. Everything working well otherwise and very happy. I’ll add some automation such as HASPone interfaces or even simple volume controls in each room and likely use the web interface less in the long term.

Thanks.

-jim

1 Like

Thanks for the feedback! The interface we have right now is pretty close to a representation of the hardware.

We know going forward we are going to need to make it more group/zone centric and are trying to work out what it should look like. We are tracking this idea on GitHub: Feature: Add Zone and Group Based Views · Issue #211 · micro-nova/AmpliPi · GitHub

Also I really like that idea for presets. We will think about adding that in the future.

Oops, I forgot to touch on the volume at 0 not being the same as mute issue. We are fixing that in the firmware in Mute preouts and auto-standby in firmware by Lohrer · Pull Request #235 · micro-nova/AmpliPi · GitHub.

1 Like