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.
@monocle Test and install all went great! However when I try to Start the Monocle Gateway service:
root@nvr-doe:/usr/local/bin# sudo monocle-gateway --start
__ __ ___ _ _ ___ ___ _ ___ *
| \/ |/ _ \| \| |/ _ \ / __| | | __| *
| |\/| | (_) | .` | (_) | (__| |__| _| *
|_| |_|\___/|_|\_|\___/ \___|____|___| *
*
<<STARTING>> THE [MONOCLE-GATEWAY] SERVICE
/bin/sh: 1: systemctl: not found
Im running Ubuntu 14.04.5 LTS, which I just read “may not utilize systemd. the final version of Ubuntu 15.04 will use systemd by default.”
Could you provide some alternative instructions to Enable the Monocle Gateway service on system boot for pre Ubuntu 15.04 users? Some simple commands would be easier for me than re-installing/upgrading the o/s.
Thank you
@dirk
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.
Thanks, Robert
@dabware said in Running as service on RaspberryPi 2:
code=exited, status=217/USER
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
@GorLyk
The Alexa devices use/prefer TCP connection to the camera. So using rtsp://10.13.13.50:10554/tcp/av0_0 in theory would be better. (Except when using @proxy, that does use UDP connections)
Just to confirm, you are using the Monocle Gateway service installed locally and running on your network?
Have you tried using “@tunnel, @noaudio”? Please forward us a log using “@tunnel, @noaudio” and we can review it to see if there is anything obvious that is wrong.
Thanks, Robert
@johnanyul
The Monocle Gateway is required for all FireTV 4K and newer models. Amazon has enforced new restriction policies in these devices that require more sophisticated security, encryption, etc. The Monocle Gateway addresses these requirements.
Is the log data you provided all that you see after starting the gateway and asking Alexa to show you a camera feed? You should see additional connection attempts in the log from the Alexa devices and then further to the IP cameras. If you are not getting any Alexa connection attempts then something is wrong at the network layer. I would check to see if port 443 is getting blocked by firewall rules on the computer running the Monocle Gateway. Are the Alexa devices on the same network and should be able to access the Monocle Gateway at 192.168.30.7? Is the IP address “192.168.30.7” the correct local IP address that Monocle Gateway should be using to host its services?
I’m not sure why your antivirus is complaining about “nssm.exe”? You can find the source of that program here: https://nssm.cc/download . NSSM is a tool used to help create/remove/start/stop and mange NT services on Windows. You can also download the latest version directly from their website and see if the antivirus software seems to like it better. I’m guessing some antivirus software has probably used NSSM to install their malicious code as a Windows service and now the antivirus software is flagging NSSM even though it by itself is not the bad actor.
