Monocle Gateway is a small service that runs on your local network to coordinate communication, encryption and security between your Alexa enabled devices and local IP cameras. The Monocle Gateway is a replacement for the previous proxy workaround service and is fully integrated with the Monocle platform.
Just a quick update, the following commands have been added to the install.sh script in the upcoming 0.0.4 release to address this issue.
# Set group ownership and permissions of config directory
chgrp -f -R monocle /etc/monocle
chmod -f -R g+rw /etc/monocle
When the install script runs, it does create a monocle system user account (a user account with no logon capabilities) as well as a monocle group. So the commands above simply set the group ownership to the monocle group and file permissions to allow read and write access to the monocle group.
@dabware said in Running as service on RaspberryPi 2:
Technically speaking we only support the RPi3B and higher due to concerns over limited processing capabilities on the older models. However, we are happy to try to get it working so that you can evaluate the solution and determine for yourself if a more powerful/newer model is required for your specific needs.
It looks like the service is failing to load due to the user account that the service is trying to start with. The install script should have created a system user account (a user account with no logon privileges) named “monocle”. Another user pointed out a file permissions issue in the current install script where the “monocle” user does not have sufficient READ access to the /etc/monocle/monocle.token file.
If you would like to open a support ticket at: https://monoclecam.com/contact we would be happy to provide you access to the unreleased version of the Monocle Gateway that includes the fix for the permissions issue.
Thank You, Robert