@scrypted/arlo-local NPM

Arlo Local Plugin for Scrypted

Requires use of arlo-cam-api commit f2cd800 (Docker 1676081273) or later.

The Arlo Local Plugin connects Scrypted to your Arlo camera or Audio Doorbell locally, allowing you to access these Arlo devices in Scrypted without relying on their cloud offering in any way. This plugin is in a BETA state and NO WARRANTY IS EXPRESSED OR IMPLIED.

This plugin must be used in conjuction with the Arlo Cam API and has been tested with Arlo Pro 2 cameras, Arlo Audio Doorbells, and a VMB4000r3 Base Station. It should work for other devices that are required to connect directly to the Arlo Base Station. It will not work with devices that have been configured to connect directly to Wi-Fi using Arlo's configuration wizard.

Features Supported

motion notifications
battery status (when on battery)
snapshots (as-requested when plugged in, rate-limited on battery to after motion is detected or after status update is received)
live video streaming
live audio support, including muting audio
Arlo subscription-quality streams without fees or the cloud (higher bitrate and sub-second latency!)
supports all HomeKit Secure Video (HKSV) features including AI person, vehicle, animal, and package detection, face recognition, etc.; also reports battery status and camera information to HomeKit
motion and binary sensor support from Audio Doorbells
new in 0.5.0: RTCP Receiver Reports to prevent the camera from falling into an infinite streaming loop when using UDP

Future Features (maybe)

audio notifications
bi-directional audio support/intercom
sensitivity and volume adjustments
arm and disarm
set charged and PIR sensor indicator preferences
integrate Arlo Cam API into plugin directly (or run as a separate plugin)
better Audio Doorbell support

Background Context

Arlo does not provide access directly to an RTSP stream, as the devices are typically connected to the Arlo Base Station. However, through the magic of reverse engineering, GitHub user Meatballs1 has developed some software that simulates the base station so that you can control the devices via a REST API. That software has been extended and modified for use with this plugin.

However, that's only one part of the equation. You must also get your devices onto a Wi-Fi network that you control, which can be very tricky.

Once the devices are on your Wi-Fi and talking with your simulated base station, this plugin will contact the base station to get information about the devices and to issue them commands (such as take a snapshot). The plugin will connect to the devices directly to stream video via RTSP.

Installation

Plugin Installation

Install this plugin using the Scrypted interface. Head to the plugin settings to grab the webhook URLs which will be used in the next step.

Do not fill out your server information yet.

Server and Network Configuration

Follow these steps in the arlo-cam-api repository to configure your network for use with the devices and create your fake Arlo Base Station.

WARNING: this is tricky and takes some Linux and networking knowledge.

Plugin Configuration

After you've configured your fake Base Station, set up your network, and connected the devices to your Wi-Fi, you're ready to hook up the plugin!

Head back to the plugin configuration in Scrypted and put your Arlo Cam API's server information in the Base Station API Host field. This should be something like http://192.168.1.100:5000. After clicking save, your devices should be discovered within a couple of seconds.

Device Configuration

If your camera only supports UDP, check the box to Prevent Infinite Streaming on UDP. This is not needed if your camera supports TCP. You can tell if your camera supports TCP if you get a video feed when trying to stream using the default settings.

Congratulations! You finally made it! Your Arlo devices are ready to use locally.

Final Steps

If you wish, add the HomeKit plugin and pair your cameras to HomeKit secure video. Or use the rebroadcasted RTSP stream from the Streams menu mentioned above to pipe the camera feed somewhere else. The world is your oyster!

Troubleshooting and Limitations

Things will break. This is not stable yet. These devices were never meant to do this and are fickle as hell. Some of these limitations may be able to be fixed in future updates, but here are some tips in the meantime:

If you have multiple Wi-Fi access points, the cameras tend to hold on to one. You may want to reboot your camera right next to the access point you want it to connect to. If you have the ability to modify the Minimum RSSI then you can also do that to try and force cameras onto the right access point. Or if you have the ability to lock a camera to an access point in your network software, that can work. However, like mentioned above, you may need to have whatever access points you want the cameras to use to all share the same Wi-Fi channel.
If you are using UDP and getting ECONNREFUSED errors in the plugin/camera console, this means your camera is already sending a stream to another socket. This can happen if the camera doesn't receive the TEARDOWN command from Scrypted. Ensure you have turned on Prevent Infinite Streaming on UDP, then reboot your cameras by pulling the battery (or you can try killing their network connection for a few minutes).
The live stream can be pretty jittery for UDP cameras. Make sure you have VERY strong Wi-Fi coverage for the cameras.
You can't control the devices without using the REST API directly. They are defaulted to always "armed" which means they will always send a motion notification to Scrypted. Video quality is defaulted to "subscription". Additionally, if the camera "re-registers" with the API, your settings will be overwritten.
The camera streams have no authentication mechanism, and they are sent unencrypted over the wire. Use them only on a network you own and trust, as anybody could theoretically listen to the traffic and reconstruct the video by sniffing the packets.