I’ll try and let you know
one thing that I forgot to mention that when I turn on the Raspberry with the Balena os image, my raspberry does not appear anywhere on the dashboard, do you know what the problem could be?
A simple reflash with the add device dialogue could help.
This is good advice! It’s reasonably common for devices to be flashed with unmanaged OS images which don’t connect to the dashboard by default, but those obtained via the ‘Add device’ modal in the dashboard will.
The Screenshots show the output of the balena push fleetname command. The good news here: your device is not the source of the errors that are showing up there.
A complete output from the command would help me analyzing what failed, but have a look at the lines that say: [Error] Error: The command "/bin/sh -c pip install --no-cache-dir -r /tmp/requirements.txt' returned with non-zero code: 1
This indicated, that the build process failed executing /bin/sh -c pip or simply pip.
From the folder path given in your screenshots, I assume you are running this on a windows machine, in a windows cmd.
After consulting my favorite search engine, I found following issue on screenlys github page.
There is already a commit for this issue regarding a dependency for screenly-ose. For now, you could patch the change yourself by editing the stated file as follows: requirements/requirements.txt
In the file change celery==5.2.2 to celery==4.4.7. Then try again with balena push ...
