Here's the reference document from Smyth about the TCP server:
A16-IP-command-server-May-2020-1.pdf
There are two tables. One is a
complete set of all the buttons on the IR remote. The other table is where the value add comes in:
- Direct input source selection
- User A and User B Preset selection (numeric, e.g. 1-16)
- Firmware info
- Levels (with updates every 0.5 seconds orso)
- User A and user B info (volume, active input, preset name, hpeq, layout etc etc) - this is the only source of data that can replace looking at the screen
- HT angles
- Speaker map which shows the layout, active speakers, and where you can solo or mute any of them
That's all there is. There is nothing there which would assist in anything under the Settings (HPEQ, PRIR etc). All of that will still be
controllable using the equivalent of the IR remote buttons, but in my testing this is simply best left to the IR remote itself as it responds the fastest. IR commands over TCP (in an app) have about a half second minimum delay, whereas on the IR remote you can get it down to as fast as your fingers can push the buttons.
One thought i did have is to add a built-in IP cam stream viewer. One could then take any IP camera (or a raspberry pi + a webcam) and point that to the display, configure the IP camera address in the app alongside the A16 IP, and then you'd have visibility of the screen within the android/ios app. But it's really a hack, so it would be optional.