In working with artists and students we are finding significant barrier in connecting to the Raspberry Pi over the local network.
Consider using a cloud based console that uses websockets to communicate between the web console and the device.
The web console is already web sockets based so "all" that needs to be done is some kind of match making service.
Once the Raspberry Pi is connected to internet it gets an access code and displays this.
Performers then use the access code to connect and send the relevant commands (start stream to specific url, stop stream, restart, shutdown) and display the progress.
In working with artists and students we are finding significant barrier in connecting to the Raspberry Pi over the local network.
Consider using a cloud based console that uses websockets to communicate between the web console and the device.
The web console is already web sockets based so "all" that needs to be done is some kind of match making service.
Once the Raspberry Pi is connected to internet it gets an access code and displays this.
Performers then use the access code to connect and send the relevant commands (start stream to specific url, stop stream, restart, shutdown) and display the progress.