Obvious;y if you have got the GUI running then the details are in the admin section under Network Info
Yes finding the IP address in such a situation can be a bit of a pain… the .local name space is certainly a partial solution but I’ve found it to be involved to set up on Windows and I’ve not managed to get it working on Android.
Getting a mechanism to reliably ( and that really is the issue) dump out the IP address requires a fairly wide knowledge of the possible failure modes and given the possible hardware configurations we are dealing with it’s probably better that we concentrate the limited resource on other areas because I can vouch for the fact that once you have got a log on you forget very quickly about the ip address issue and just get on with stuff…
The router connected to the zynth often has an interface that will let you see the ip address and that is how I have discovered particularly shy zynth’s and then off course there is the ping command which will allow you to examine the local name space, but I would get yourself onto named addresses (zynthian.local) as quickly as possible because it really is the most repeatable approach especially in the DHCP world that most local routers live in and it’s a bit deflating to have to play hunt the ip after a brief network re allocation.
If anyone has a way of getting names to work on android browsers I’d be very happy…
the Service browser app reveals the _workstation._tcp details which helps but the browsers resolutely refuse to resolve the address…