Hi
I setup up a fresh debian 9 and install your script
but i got a blank page
i think a webserver is needed, to get them work

Best regards
HunterZeroSix

The installation process takes a very long time.
Here you have to check if and how you can speed up this process.

Would it be possible in the settings to add a monitor name, as Screenly OSE does, and then this name could be displayed later in the contents as Screenly OSE does?

Is there any way to easily uninstall Screenly OSE monitoring?

First off, thanks for the great addon to Screenly! Your effort is much appreciated. It works flawlessly with the exception of the video/HDMI addon. Instead of showing the expected screen, it shows 2/3rds of the screen, but with an overlay of vertical grey lines.

I am running screenly on a Pi4 using screenly version 0.18.2.

I'm not sure if my problem is caused by the response time of a screen. All my screens are connected via LTE Modem in an VPN Network. The screens ar often shown as offline, or when i klick them the are shown to be offline -but the are not!
Is there a way to wait for example 1 second for response of a screen?

Thanke you in advance,
Schubi

Wizard after the instalation

• Change Username/Password
• Add own player on request
• Change default settings

I'm testing the monitor and all seems to work just fine. I only cannot see any display image. It no image and seems lik it points to http://ipaddr:9020/screen/screenshot.png?0.5201491354745875

If I try to open url it gives me nginx not found 404 page.

Anything I missed in install ?

Thanks and congrats for your work

1. Add checkbox (and select/deselect all) on assests screen for multiple changes: start and end datetime, delete, active/inactive.

2. Add players groups - example: Dining rooms[player1,player5], All[player1,player2,player3,player4,player5], Firt floor[player1,player2], Second floor [player3,player4,player5]
   its for better managment and for "add asset to multiple device".

3. Add option active/inactive, start, end, for new created asset - before upload. "Inactive" is important! .

Hello !

I already said it, but this project is very interesting and useful.

Here is my issue :
When trying to upload a Youtube video by using its link, it's trying to display the whole Youtube page instead of the Video.

Expected Behavior

By example, I want to display and ear this video on my Screenly player :
https://www.youtube.com/watch?v=h-jxgXxRgnM

Using the web interface of my Screenly player, that's work like a charm.

Current Behavior

When I create an asset from SOMO, and adding the Youtube URL, here is the result

I'm not a dev so I can't help you resolving this :(

Thanks !
Matthias

Your issue may already be reported!
Please search on the issue tracker before creating one.

Expected Behavior

Change settings to new values and save

Current Behavior

Settings won't be changed

Possible Solution

Your Environment

• Screenly OSE Monitoring Version: v3.1
• Screenly OSE Version: Release v0.18.2
• Raspbian Version: buster
• Browser Name and version:
• Operating System and version (desktop or mobile):

Since Screenly OSE v0.18 there is a reboot/shutdown function in the API

Your issue may already be reported!
Please search on the issue tracker before creating one.

Expected Behavior

Install Screenshot addon

Current Behavior

Error 404

Possible Solution

Fix the URL

Your Environment

• Screenly OSE Monitoring Version: v3.0
• Screenly OSE Version: Release v0.18.2
• Raspbian Version: buster

Your issue may already be reported!
Please search on the issue tracker before creating one.

Expected Behavior

It's possible to set screenly ose to use SSL. When the player is set to SSL its not possible to connect the player with the monitor.

Current Behavior

The monitor runs in a HTTP 301 redirect and throws an error.

Possible Solution

I'm not sure if this is a good fix but it works.

https://github.com/didiatworkz/screenly-ose-monitor/blob/e157f34aa61223a7b0a5da77996f1f5d63111685/assets/php/player.php#L123

to

if(($httpcode>=200 && $httpcode<300) || $httpcode==401 || $httpcode==301) return true;

And
https://github.com/didiatworkz/screenly-ose-monitor/blob/e157f34aa61223a7b0a5da77996f1f5d63111685/assets/php/image.php#L30

to
if(($httpcode>=200 && $httpcode<300) || $httpcode==401 || $httpcode==301) return true;

Steps to Reproduce (for bugs)

1. Set Player to use SSL. (Run /screenly/bin/enable_ssl.sh)
2. Add the Player
3. Error Occurs and Image is Offline

Context

HTTPS did not work.

Your Environment

• Screenly OSE Monitoring Version: v3.3
• Screenly OSE Version: production@d12df55
• Raspbian Version: Buster
• Browser Name and version: Chrome 86.0.4240.75
• Operating System and version (desktop or mobile): Desktop

Single player upload button disappear if 1 file (multiple files per attempt session) out of the list has size greater than MB allowed in setting. Button will not reappear even if the large file is removed from the list. The page must be reloaded again. Most people knows SOMO would raised the limit to start but for new comers it could be head scratching.

system = debian buster RPI4 with latest SOMO and SOMA installed.

Tested all the functions from outside local network over ssh reverse tunnel to monitor:9000

Almost everything works fine, however image preview of the screens doesn't work. Do you know any way that I can change the image url so that not going directly to the ip adress of the screen?

I've read in some answer you gave to other post that you're implementing php-ssh2. Can this be a solutions for the issue ?

Thanks

First of all, you have implemented a super project here. I also had the idea to create a script to manage Screenly OSE players. I would have built the whole thing just the other way around. As a client to server model.
I also like your approach.
The only disadvantage is that the players must be directly accessible.

Long speech short sense. Great project and nice that you share it with us.

Now to my concern.

Change Display Settings

It would be super useful to change some Display Settings over SOMO.
I know it's only used once, but then you don't have to manually connect to the Raspberry and change those settings.

The following Settings would be nice.

Display Oversan

extractet from /boot/config.txt

# uncomment this if your display has a black border of unused pixels visible
# and your display can output without overscan
#disable_overscan=1

Display Rotation

https://pimylifeup.com/raspberry-pi-rotate-screen/

Changes on this file /boot/config.txt, requires a reboot.

What's your question?

Is it possible to make an connection to another location, because our office is at another location?

Would it be possible to make a specific user only view and manage a specific list of players?

Only an admin user should be able to create, modify and delete this user -> players relationship.

I am unable to upload or add assets via URL. Whenever I attempt to, it says that my login information is incorrect.

I have tried deleting and adding the pi again and changing the username and password to see if it I could get it to work but I haven't found a solution yet. The only way I'v gotten it to add the assets is by disabling the password authentication for one my screenly and it work perfectly; but I don't want have to disable it permanently.

I don't think I'm entering the password/username wrong since I am able to see the other assets and the plugin feed.

TASK [Gathering Facts] ********************************************************* fatal: [localhost]: FAILED! => {"ansible_facts": {}, "changed": false, "msg": "T he following modules failed to execute: setup\n setup: MODULE FAILURE\nSee stdo ut/stderr for the exact error\n"}

Adding new assets in monitor page only allow URL.
Is it possible to upload a video or image ? Where should we look fo add it in the code?

Thanks

Hi
is it possible to add a screen via a SSH Tunnel or VPN

What do you think about it?
I found this manual https://www.rustimation.eu/index.php/reverse-ssh-tunnel-schritt-fur-schritt/

Best regards
HunterZeroSix

When editing some asset the duration neither the start/end date are saved.

When I load a youtube video via screenly-ose-monitor it fails to pull the content like it does while adding youtube content via direct screenly-ose interface.

Thank you again for your time on this!
Neil

Trying to install on a RPi Zero W and I'm getting the following error,

Building wheels for collected packages: cryptography
  Building wheel for cryptography (PEP 517) ... error
  ERROR: Command errored out with exit status 1:
   command: /usr/bin/python3 /usr/local/lib/python3.7/dist-packages/pip/_vendor/pep517/_in_process.py build_wheel /tmp/tmplcdqaktk
       cwd: /tmp/pip-install-n1v0y4ja/cryptography_76b199cb0c7a45aa8b0570d35377e5cb
  Complete output (161 lines):
  running bdist_wheel
  running build
  running build_py
  creating build
  creating build/lib.linux-armv6l-3.7
  creating build/lib.linux-armv6l-3.7/cryptography
  copying src/cryptography/utils.py -> build/lib.linux-armv6l-3.7/cryptography
  copying src/cryptography/fernet.py -> build/lib.linux-armv6l-3.7/cryptography
  copying src/cryptography/exceptions.py -> build/lib.linux-armv6l-3.7/cryptography
  copying src/cryptography/__about__.py -> build/lib.linux-armv6l-3.7/cryptography
  copying src/cryptography/__init__.py -> build/lib.linux-armv6l-3.7/cryptography
  creating build/lib.linux-armv6l-3.7/cryptography/x509
  copying src/cryptography/x509/oid.py -> build/lib.linux-armv6l-3.7/cryptography/x509
  copying src/cryptography/x509/ocsp.py -> build/lib.linux-armv6l-3.7/cryptography/x509
  copying src/cryptography/x509/certificate_transparency.py -> build/lib.linux-armv6l-3.7/cryptography/x509
  copying src/cryptography/x509/name.py -> build/lib.linux-armv6l-3.7/cryptography/x509
  copying src/cryptography/x509/general_name.py -> build/lib.linux-armv6l-3.7/cryptography/x509
  copying src/cryptography/x509/extensions.py -> build/lib.linux-armv6l-3.7/cryptography/x509
  copying src/cryptography/x509/base.py -> build/lib.linux-armv6l-3.7/cryptography/x509
  copying src/cryptography/x509/__init__.py -> build/lib.linux-armv6l-3.7/cryptography/x509
  creating build/lib.linux-armv6l-3.7/cryptography/hazmat
  copying src/cryptography/hazmat/_oid.py -> build/lib.linux-armv6l-3.7/cryptography/hazmat
  copying src/cryptography/hazmat/_types.py -> build/lib.linux-armv6l-3.7/cryptography/hazmat
  copying src/cryptography/hazmat/_der.py -> build/lib.linux-armv6l-3.7/cryptography/hazmat
  copying src/cryptography/hazmat/__init__.py -> build/lib.linux-armv6l-3.7/cryptography/hazmat
  creating build/lib.linux-armv6l-3.7/cryptography/hazmat/bindings
  copying src/cryptography/hazmat/bindings/__init__.py -> build/lib.linux-armv6l-3.7/cryptography/hazmat/bindings
  creating build/lib.linux-armv6l-3.7/cryptography/hazmat/primitives
  copying src/cryptography/hazmat/primitives/_asymmetric.py -> build/lib.linux-armv6l-3.7/cryptography/hazmat/primitives
  copying src/cryptography/hazmat/primitives/hmac.py -> build/lib.linux-armv6l-3.7/cryptography/hazmat/primitives
  copying src/cryptography/hazmat/primitives/hashes.py -> build/lib.linux-armv6l-3.7/cryptography/hazmat/primitives
  copying src/cryptography/hazmat/primitives/poly1305.py -> build/lib.linux-armv6l-3.7/cryptography/hazmat/primitives
  copying src/cryptography/hazmat/primitives/_serialization.py -> build/lib.linux-armv6l-3.7/cryptography/hazmat/primitives
  copying src/cryptography/hazmat/primitives/keywrap.py -> build/lib.linux-armv6l-3.7/cryptography/hazmat/primitives
  copying src/cryptography/hazmat/primitives/constant_time.py -> build/lib.linux-armv6l-3.7/cryptography/hazmat/primitives
  copying src/cryptography/hazmat/primitives/cmac.py -> build/lib.linux-armv6l-3.7/cryptography/hazmat/primitives
  copying src/cryptography/hazmat/primitives/__init__.py -> build/lib.linux-armv6l-3.7/cryptography/hazmat/primitives
  copying src/cryptography/hazmat/primitives/_cipheralgorithm.py -> build/lib.linux-armv6l-3.7/cryptography/hazmat/primitives
  copying src/cryptography/hazmat/primitives/padding.py -> build/lib.linux-armv6l-3.7/cryptography/hazmat/primitives
  creating build/lib.linux-armv6l-3.7/cryptography/hazmat/backends
  copying src/cryptography/hazmat/backends/interfaces.py -> build/lib.linux-armv6l-3.7/cryptography/hazmat/backends
  copying src/cryptography/hazmat/backends/__init__.py -> build/lib.linux-armv6l-3.7/cryptography/hazmat/backends
  creating build/lib.linux-armv6l-3.7/cryptography/hazmat/bindings/openssl
  copying src/cryptography/hazmat/bindings/openssl/binding.py -> build/lib.linux-armv6l-3.7/cryptography/hazmat/bindings/openssl
  copying src/cryptography/hazmat/bindings/openssl/_conditional.py -> build/lib.linux-armv6l-3.7/cryptography/hazmat/bindings/openssl
  copying src/cryptography/hazmat/bindings/openssl/__init__.py -> build/lib.linux-armv6l-3.7/cryptography/hazmat/bindings/openssl
  creating build/lib.linux-armv6l-3.7/cryptography/hazmat/primitives/ciphers
  copying src/cryptography/hazmat/primitives/ciphers/algorithms.py -> build/lib.linux-armv6l-3.7/cryptography/hazmat/primitives/ciphers
  copying src/cryptography/hazmat/primitives/ciphers/aead.py -> build/lib.linux-armv6l-3.7/cryptography/hazmat/primitives/ciphers
  copying src/cryptography/hazmat/primitives/ciphers/base.py -> build/lib.linux-armv6l-3.7/cryptography/hazmat/primitives/ciphers
  copying src/cryptography/hazmat/primitives/ciphers/__init__.py -> build/lib.linux-armv6l-3.7/cryptography/hazmat/primitives/ciphers
  copying src/cryptography/hazmat/primitives/ciphers/modes.py -> build/lib.linux-armv6l-3.7/cryptography/hazmat/primitives/ciphers
  creating build/lib.linux-armv6l-3.7/cryptography/hazmat/primitives/kdf
  copying src/cryptography/hazmat/primitives/kdf/concatkdf.py -> build/lib.linux-armv6l-3.7/cryptography/hazmat/primitives/kdf
  copying src/cryptography/hazmat/primitives/kdf/x963kdf.py -> build/lib.linux-armv6l-3.7/cryptography/hazmat/primitives/kdf
  copying src/cryptography/hazmat/primitives/kdf/kbkdf.py -> build/lib.linux-armv6l-3.7/cryptography/hazmat/primitives/kdf
  copying src/cryptography/hazmat/primitives/kdf/pbkdf2.py -> build/lib.linux-armv6l-3.7/cryptography/hazmat/primitives/kdf
  copying src/cryptography/hazmat/primitives/kdf/hkdf.py -> build/lib.linux-armv6l-3.7/cryptography/hazmat/primitives/kdf
  copying src/cryptography/hazmat/primitives/kdf/__init__.py -> build/lib.linux-armv6l-3.7/cryptography/hazmat/primitives/kdf
  copying src/cryptography/hazmat/primitives/kdf/scrypt.py -> build/lib.linux-armv6l-3.7/cryptography/hazmat/primitives/kdf
  creating build/lib.linux-armv6l-3.7/cryptography/hazmat/primitives/twofactor
  copying src/cryptography/hazmat/primitives/twofactor/utils.py -> build/lib.linux-armv6l-3.7/cryptography/hazmat/primitives/twofactor
  copying src/cryptography/hazmat/primitives/twofactor/totp.py -> build/lib.linux-armv6l-3.7/cryptography/hazmat/primitives/twofactor
  copying src/cryptography/hazmat/primitives/twofactor/hotp.py -> build/lib.linux-armv6l-3.7/cryptography/hazmat/primitives/twofactor
  copying src/cryptography/hazmat/primitives/twofactor/__init__.py -> build/lib.linux-armv6l-3.7/cryptography/hazmat/primitives/twofactor
  creating build/lib.linux-armv6l-3.7/cryptography/hazmat/primitives/asymmetric
  copying src/cryptography/hazmat/primitives/asymmetric/ed448.py -> build/lib.linux-armv6l-3.7/cryptography/hazmat/primitives/asymmetric
  copying src/cryptography/hazmat/primitives/asymmetric/rsa.py -> build/lib.linux-armv6l-3.7/cryptography/hazmat/primitives/asymmetric
  copying src/cryptography/hazmat/primitives/asymmetric/utils.py -> build/lib.linux-armv6l-3.7/cryptography/hazmat/primitives/asymmetric
  copying src/cryptography/hazmat/primitives/asymmetric/ec.py -> build/lib.linux-armv6l-3.7/cryptography/hazmat/primitives/asymmetric
  copying src/cryptography/hazmat/primitives/asymmetric/dh.py -> build/lib.linux-armv6l-3.7/cryptography/hazmat/primitives/asymmetric
  copying src/cryptography/hazmat/primitives/asymmetric/x448.py -> build/lib.linux-armv6l-3.7/cryptography/hazmat/primitives/asymmetric
  copying src/cryptography/hazmat/primitives/asymmetric/dsa.py -> build/lib.linux-armv6l-3.7/cryptography/hazmat/primitives/asymmetric
  copying src/cryptography/hazmat/primitives/asymmetric/ed25519.py -> build/lib.linux-armv6l-3.7/cryptography/hazmat/primitives/asymmetric
  copying src/cryptography/hazmat/primitives/asymmetric/x25519.py -> build/lib.linux-armv6l-3.7/cryptography/hazmat/primitives/asymmetric
  copying src/cryptography/hazmat/primitives/asymmetric/__init__.py -> build/lib.linux-armv6l-3.7/cryptography/hazmat/primitives/asymmetric
  copying src/cryptography/hazmat/primitives/asymmetric/padding.py -> build/lib.linux-armv6l-3.7/cryptography/hazmat/primitives/asymmetric
  creating build/lib.linux-armv6l-3.7/cryptography/hazmat/primitives/serialization
  copying src/cryptography/hazmat/primitives/serialization/pkcs12.py -> build/lib.linux-armv6l-3.7/cryptography/hazmat/primitives/serialization
  copying src/cryptography/hazmat/primitives/serialization/pkcs7.py -> build/lib.linux-armv6l-3.7/cryptography/hazmat/primitives/serialization
  copying src/cryptography/hazmat/primitives/serialization/base.py -> build/lib.linux-armv6l-3.7/cryptography/hazmat/primitives/serialization
  copying src/cryptography/hazmat/primitives/serialization/ssh.py -> build/lib.linux-armv6l-3.7/cryptography/hazmat/primitives/serialization
  copying src/cryptography/hazmat/primitives/serialization/__init__.py -> build/lib.linux-armv6l-3.7/cryptography/hazmat/primitives/serialization
  creating build/lib.linux-armv6l-3.7/cryptography/hazmat/backends/openssl
  copying src/cryptography/hazmat/backends/openssl/ed448.py -> build/lib.linux-armv6l-3.7/cryptography/hazmat/backends/openssl
  copying src/cryptography/hazmat/backends/openssl/ocsp.py -> build/lib.linux-armv6l-3.7/cryptography/hazmat/backends/openssl
  copying src/cryptography/hazmat/backends/openssl/rsa.py -> build/lib.linux-armv6l-3.7/cryptography/hazmat/backends/openssl
  copying src/cryptography/hazmat/backends/openssl/utils.py -> build/lib.linux-armv6l-3.7/cryptography/hazmat/backends/openssl
  copying src/cryptography/hazmat/backends/openssl/ciphers.py -> build/lib.linux-armv6l-3.7/cryptography/hazmat/backends/openssl
  copying src/cryptography/hazmat/backends/openssl/hmac.py -> build/lib.linux-armv6l-3.7/cryptography/hazmat/backends/openssl
  copying src/cryptography/hazmat/backends/openssl/encode_asn1.py -> build/lib.linux-armv6l-3.7/cryptography/hazmat/backends/openssl
  copying src/cryptography/hazmat/backends/openssl/ec.py -> build/lib.linux-armv6l-3.7/cryptography/hazmat/backends/openssl
  copying src/cryptography/hazmat/backends/openssl/aead.py -> build/lib.linux-armv6l-3.7/cryptography/hazmat/backends/openssl
  copying src/cryptography/hazmat/backends/openssl/decode_asn1.py -> build/lib.linux-armv6l-3.7/cryptography/hazmat/backends/openssl
  copying src/cryptography/hazmat/backends/openssl/hashes.py -> build/lib.linux-armv6l-3.7/cryptography/hazmat/backends/openssl
  copying src/cryptography/hazmat/backends/openssl/poly1305.py -> build/lib.linux-armv6l-3.7/cryptography/hazmat/backends/openssl
  copying src/cryptography/hazmat/backends/openssl/dh.py -> build/lib.linux-armv6l-3.7/cryptography/hazmat/backends/openssl
  copying src/cryptography/hazmat/backends/openssl/x448.py -> build/lib.linux-armv6l-3.7/cryptography/hazmat/backends/openssl
  copying src/cryptography/hazmat/backends/openssl/backend.py -> build/lib.linux-armv6l-3.7/cryptography/hazmat/backends/openssl
  copying src/cryptography/hazmat/backends/openssl/dsa.py -> build/lib.linux-armv6l-3.7/cryptography/hazmat/backends/openssl
  copying src/cryptography/hazmat/backends/openssl/ed25519.py -> build/lib.linux-armv6l-3.7/cryptography/hazmat/backends/openssl
  copying src/cryptography/hazmat/backends/openssl/x25519.py -> build/lib.linux-armv6l-3.7/cryptography/hazmat/backends/openssl
  copying src/cryptography/hazmat/backends/openssl/cmac.py -> build/lib.linux-armv6l-3.7/cryptography/hazmat/backends/openssl
  copying src/cryptography/hazmat/backends/openssl/__init__.py -> build/lib.linux-armv6l-3.7/cryptography/hazmat/backends/openssl
  copying src/cryptography/hazmat/backends/openssl/x509.py -> build/lib.linux-armv6l-3.7/cryptography/hazmat/backends/openssl
  running egg_info
  writing src/cryptography.egg-info/PKG-INFO
  writing dependency_links to src/cryptography.egg-info/dependency_links.txt
  writing requirements to src/cryptography.egg-info/requires.txt
  writing top-level names to src/cryptography.egg-info/top_level.txt
  reading manifest file 'src/cryptography.egg-info/SOURCES.txt'
  reading manifest template 'MANIFEST.in'
  no previously-included directories found matching 'docs/_build'
  warning: no previously-included files found matching 'vectors'
  warning: no previously-included files matching '*' found under directory 'vectors'
  warning: no previously-included files matching '*' found under directory '.github'
  warning: no previously-included files found matching 'release.py'
  warning: no previously-included files found matching '.coveragerc'
  warning: no previously-included files found matching 'codecov.yml'
  warning: no previously-included files found matching '.readthedocs.yml'
  warning: no previously-included files found matching 'dev-requirements.txt'
  warning: no previously-included files found matching 'tox.ini'
  warning: no previously-included files found matching 'mypy.ini'
  warning: no previously-included files matching '*' found under directory '.zuul.d'
  warning: no previously-included files matching '*' found under directory '.zuul.playbooks'
  writing manifest file 'src/cryptography.egg-info/SOURCES.txt'
  copying src/cryptography/py.typed -> build/lib.linux-armv6l-3.7/cryptography
  running build_ext
  generating cffi module 'build/temp.linux-armv6l-3.7/_padding.c'
  creating build/temp.linux-armv6l-3.7
  generating cffi module 'build/temp.linux-armv6l-3.7/_openssl.c'
  running build_rust

      =============================DEBUG ASSISTANCE=============================
      If you are seeing a compilation error please try the following steps to
      successfully install cryptography:
      1) Upgrade to the latest pip and try again. This will fix errors for most
         users. See: https://pip.pypa.io/en/stable/installing/#upgrading-pip
      2) Read https://cryptography.io/en/latest/installation.html for specific
         instructions for your platform.
      3) Check our frequently asked questions for more information:
         https://cryptography.io/en/latest/faq.html
      4) Ensure you have a recent Rust toolchain installed:
         https://cryptography.io/en/latest/installation.html#rust
      5) If you are experiencing issues with Rust for *this release only* you may
         set the environment variable `CRYPTOGRAPHY_DONT_BUILD_RUST=1`.
      =============================DEBUG ASSISTANCE=============================

  error: can't find Rust compiler

  If you are using an outdated pip version, it is possible a prebuilt wheel is available for this package but pip is not able to install from it. Installing from the wheel would avoid the need for a Rust compiler.

  To update pip, run:

      pip install --upgrade pip

  and then retry package installation.

  If you did intend to build this package from source, try installing a Rust compiler from your system package manager and ensure it is on the PATH during installation. Alternatively, rustup (available at https://rustup.rs) is the recommended way to download and update the Rust compiler toolchain.

  This package requires Rust >=1.41.0.
  ----------------------------------------
  ERROR: Failed building wheel for cryptography
Failed to build cryptography
ERROR: Could not build wheels for cryptography which use PEP 517 and cannot be installed directly
[ SOMO ] Start preperation for installation
[ SOMO ] Remove old git repository if exists
[ SOMO ] Clone repository
Cloning into '/tmp/monitor'...
remote: Enumerating objects: 166, done.
remote: Counting objects: 100% (166/166), done.
remote: Compressing objects: 100% (103/103), done.
remote: Total 5609 (delta 86), reused 113 (delta 56), pack-reused 5443
Receiving objects: 100% (5609/5609), 54.93 MiB | 771.00 KiB/s, done.
Resolving deltas: 100% (2838/2838), done.
Checking out files: 100% (733/733), done.
[ SOMO ] Create /var/www/monitor folder
[ SOMO ] Set installation parameter
[ SOMO ] Start installation
sudo: ansible-playbook: command not found
Failed to restart nginx.service: Unit nginx.service not found.

So did I understand this correctly, if I want to install the monitoring to my server and connect the players to it, I have to also install Screenly to the server?

Is there a limit to how many displays that can be added? I have 22 displays and have 21 of them displaying. When I add the last one it says it was added successfully but doesn't show up under players.

Expected Behavior

Currently, SOMO does not detect an installation of the development branch of Screenly-OSE (which has been suggested by their own devs to be installed in order to solve certain problems - for me, that is unsupported HTML5/CSS rendering issues with the UZBL browser).

Current Behavior

SOMO will happily install itself, and I was able to get it to run atop a pre-installed OSE Dev branch, but since it couldn't detect OSE properly that was already running on the raspberry pi (it said it was found, but...), it took control of port 80, which (in this case) it shouldn't have. OSE was then inaccessible until it was accessed via SSL, but SOMO still couldn't communicate with it as it was not found.

Steps to Reproduce (for bugs)

1. Install Screenly-OSE as according to the SOMO Wiki.
2. During installation of Screenly-OSE, choose the development branch over the "Stable" branch
3. Once complete, install SOMO.
4. See error

Context

Screenly-OSE's development has slowed a bit, but the development branch seems to be the more appropriate version than the stable branch from my own usage/testing. That said, I know there's also a Balena branch, so I don't know how difficult it might be to support all of the various versions of Screenly-OSE (I don't know if it can detect the Balena version).

Your Environment

• Screenly OSE Monitoring Version: Assuming v4.1 (used the curl-based bash script)
• Screenly OSE Version: Assuming the update to Spring 10.1 (used the curl-based bash script)
• Raspbian Version: Buster as downloaded via Raspberry Pi imager (Lite), after an apt update and apt upgrade.

If SOMO will only be supporting the stable, standard version of Screenly-OSE (an acceptable stance) - could the README.md of the project at least be updated? Thank you! This project is awesome. I really want to be able to use it, but appreciate those who can thanks to your work.

its possible to select more than one image, but just uploading one image ...

Not a bug. I need help getting the monitoring site displayed at port 80. Port 80 now shows the nginx welcome screen because i have installed ose-monitoring as a stand alone version.

Just changing the /etc/nginx/sites-enabled/monitoring.conf from "listen 9000;" to "listen 80;" doesn't do the trick, it seems?

It is installed on "Debian Buster with Raspberry Pi Desktop" x86 version...

Thanks a lot! And really nice work btw. :)

First off, I'm a big fan of the program you made, it has made managing my screenly pis so much easier.

I'm not sure if this should be filed under a bug report or not since It may not be the fault of the program itself but when I go to update my pi, I get this error:

TASK [monitoring : Install packages] ***********************************************************
fatal: [localhost]: FAILED! => {"changed": false, "msg": "Failed to update apt cache: E:The repository 'https://packagecloud.io/wott/agent/raspbian stretch Release' does no longer have a Release file."}

I'm think either the link is dead or there's problem on my end connecting to the repository.

Please let me know what you think.

When i try to install ın ubuntu 18:04 ihave this error message. I wanna try to install standalone system.

TASK [monitoring : Create .monitor directory] ************************************************************************************************************************************************************************************************
fatal: [localhost]: FAILED! => {"changed": false, "gid": 0, "group": "root", "mode": "0755", "msg": "chown failed: failed to look up user pi", "owner": "root", "path": "/home/pi/.monitor", "size": 4096, "state": "directory", "uid": 0}

PLAY RECAP ***********************************************************************************************************************************************************************************************************************************
localhost : ok=1 changed=0 unreachable=0 failed=1 skipped=0 rescued=0 ignored=0

/dev/fd/63: line 79: /root/.monitor/latest_monitor: No such file or directory
Device "wlan0" does not exist.

Thanks

My apology for posting the other post of related topic on pull request (github newbie!).

The reality: Screenly ose latest version will redirect all http request to https port 443. this means they are moving to more secure option and in a way abandoning port 80.

The request: Can we make let end user access SOMO web UI easier by changing port 9000 to port 80. So if we run DNS locally we can allow end users to access SOMO with something short and simple like "Front.TV" on url rather than "Front.TV:9000"

the problem: Somo still seem to send API request to port 80 by default. But then Screenly ose redirect them to 443 anyway. So how can we force all API from SOMO to Screenly ose to go straight to 443 and leave port 80 to SOMO.

If that required a lot of recoding then how about we disable screenly ose 443 and put somo on 443?

Mang

What's your question?

It does not show me the image of what the player is playing

Enable monitoring to run as a separate instance on a server.

Rotate site when there more player as 12

I like the add-on since it allows me to see how my assets are displaying, but I was wondering if there was possible to disable or deactivate the add-on. It is really nice to have but, outside of when I initially add my assets, I would rather just have it say if the pi is active or not most of the time.

I know that you can already control how often you receive a screenshot. I don't have much experience in programming for pis so I honestly do not how hard it would be to implement, but the way I'm imagining this would be an option in the setting or a button when you view the pi's assets that allows you to disable the add-on just for that select pi.

I think you've done an amazing job and, like I said, I have no idea how hard it would be to do, so if you wanted to, you could honestly just complete disregard this and I honestly would not mind it one bit lol. I just thought that this could be neat addition if you were look for suggestions.

Could there be a filter, with its corresponding sorting, in the main view?

During the installation process, the script return an error and at the end of the process, the app isn't access.

I attach text file with the messages returned by the script.
Install_Somo.txt
Install_Somo.txt

Your Environment

I get the same error with or without apt update & apt upgrade before.

• Screenly OSE Monitoring Version: Version 4.1
• Screenly OSE Version: NOne
• Raspbian Version: Raspbian GNU/Linux 10 (buster)
• Browser Name and version: Google Chrome Versión 90.0.4430.212
• Operating System and version (desktop): Windows 10 Pro version 21H1

Manage different users with group rights

There is an error when Screenly OSE Monitoring gets an asset from a player, when reading and displaying some future dates.

Screenly OSE Monitoring.docx

Manage all Add-on in one overview

• show Add-on Version
• show installed/not
• one click installation via php-ssh2 remotely

Being able to order the playlist assets would be just great

Hello together,

after the release of V4.0 it's possible to change the language of the whole system.

For that, I need some co-workers who can translate the system in other languages.
Are you interested? - Then write me an email at [email protected] and tell me which language you can support.
I will contact you as soon it's impossible.

Thank you in advance

i have current screenly ose Sprint 10.1 Release. fresh install of somo. upload and multiupload seem to work but asset is not playing. switching to web interface i can disable the asset but when re-enable it cause this error: "Server Error: int() argument must be a string or a number, not 'NoneType'"

uploaded 3 videos size 12mb, 30 mb, and 34mb - upload is a lot faster than web interface... but the 34mb didn't make it into the system even though it show as done.

further inspection: start time is not set properly (asset uploaded in early AM and set start time at PM. Duration is not set correctly (default all upload at 10 second) which is not the actual duration

uploaded the same 3 files via web interface (screenly ose) and they all goes in fine and the suspected speed and all play as normal.

Would it be possible to add or edit assets to multiple devices at once?

There's a UWP app available for OSE that supports this, but it's not great.

Hello, i have problem with upload videos larger then approx 100mb.
For example i using 1,2Gb MP4 video.
Iam trying in Firefox and Chrome browsers.
If I upload the video directly to the player, it will upload fine.
See gif please:

Monitor info:

Hi! first congratulations on the work, this is helping me a lot I wanted to know if you have any tips regarding my scenario.
I use a debian server in the cloud with the screenly monitor installed, the communication between the pi and the monitor is done through a vpn. The system can see the pi normally, even the addon works perfectly, but does not succeed on the assets, a message No Screenly API detected! - No data could be collected ...
Has anyone gone through this situation?
I'm Brazilian, sorry for my bad English