Manage multiple Screenly OSE Player in one web Interface
MIT License
Screenly OSE Monitoring is a web-based application that is simultaneously installed on a Screenly OSE Player or as standalone server solution.
With this tool, you can manage multiple Screenly OSE players in one web-interface.
In addition to its current display status, you can also manage the assets of a player. It is possible to activate or deactivate assets, add new ones, edit or simply delete them all from the player. Also it's possible to reboot the player directly or upload new assets to multiple players parallel. By installing an add-on on each player, it is also possible to display a "live feed" of the player's HDMI output and live-data from the system. This will then be displayed in the overview, as well.
SOMO v4.2 tested on Raspbian buster and bullseye
No errors were found in the tests. If you find a problem or bug, please report it: Open Issue List
IMPORTANT: The monitoring was designed to run on the local network with the Screenly OSE Player. Problems or restrictions may occur if the server is hosted externally or accessed from an external network!
Very simple installation:
bash <(curl -sL https://git.io/JttTW)
After the installation is the default login:
http://[ip-address]:9000 (when Screenly OSE is installed) http://[ip-address] (Server installation)
Username: demo Password: demo
For the update you only have to run the installer again. The installer checks if there is an old installation and saves it if necessary. From version 2.0 there are changes to the database structure which is prepared for future updates and no longer needs to be saved.
But please note that the Add-on may have to be reinstalled on the players. (Current for all older versions before version 2.0)
IMPORTANT: If monitoring is installed on a Raspberry Pi that does not have a Screenly OSE Player (standalone installation) the port changes from 9000 to 80. So the monitoring is accessible via the normal IP address!
bash <(curl -sL https://git.io/JttTW)
Link via Monitoring or here:
bash <(curl -sL https://git.io/Jf900)
There's something else that wasn't answered here? Then just have a look at the wiki-page. Maybe you will find an answer there.
Thanks for using this project! - didiatworkz