Help

Setting up logrrr and the optional local services

Getting started

logrrr works from UniFi Protect's own webhook: get an API key, add an alarm in Protect's Alarm Manager, and plates start arriving. The steps are on the home page and, once you've signed up, on the Setup page in your console.

What logrrr stores

logrrr stores the detection events UniFi Protect delivers to it. Protect doesn't retry a webhook that fails, so an event logrrr never received can't be recovered later. logrrr isn't a backup of your NVR: keep your NVR's own retention set to what you need, and watch the Cameras page in the console, which flags a camera that hasn't sent an event for over a day.

The optional local services

For full video clips as well as snapshots, you can run two small Windows services on a computer on the same network as your UniFi Protect console. They're optional: the webhook alone delivers plate reads with a snapshot.

• The Downloader saves each event's media from your Protect console to a local folder. It only talks to your console, never to logrrr.
• The Uploader sends that saved media up to logrrr, using an uploader API key.

The installer (LogrrrSettings, the Downloader and the Uploader) isn't published yet. This page will link to it, with its checksum, as soon as the first release is out.

Troubleshooting

Problem	What usually fixes it
The UniFi login test fails in LogrrrSettings	Use a local admin account on the Protect console, not a Ubiquiti cloud (SSO) account. Check the console's IP address, and that the computer can reach it (same network or VLAN, no firewall in between). See creating a local account.
Windows says "Windows protected your PC" when you run the installer	The installer isn't code-signed yet, so SmartScreen warns about it. Choose More info, then Run anyway. Check the file's SHA-256 against the one on the download page first.
A service shows Stopped, or won't start	Antivirus sometimes blocks the services because they aren't code-signed yet. Allow the logrrr install folder in your antivirus, then start the service again from LogrrrSettings. The service's log file usually says why it stopped.
Clips don't convert to WebM	The Downloader converts clips with the bundled ffmpeg.exe, in the ffmpeg folder inside the logrrr install folder. Antivirus sometimes quarantines it (a common false positive). Clips still download as -clip.mp4 meanwhile; only the WebM copy is skipped, and it's retried later. Restore the file, or reinstall, and allow the logrrr install folder in your antivirus.
Nothing is uploading	In the console, open Settings → API keys and look at the uploader key's Last used. If it's old, check the Uploader is running and that the key in LogrrrSettings, Step 2, matches an active key.

Log files

Both services write one plain-text log per day in a Logs folder inside the media folder you chose (by default C:\UnifiProtectMedia):

• C:\UnifiProtectMedia\Logs\LogrrrUnifiProtectDownloader_YYYY-MM-DD.log
• C:\UnifiProtectMedia\Logs\LogrrrUnifiProtectUploader_YYYY-MM-DD.log

Attach the day's logs when you email ahoy@logrrr.com. Nothing deletes old logs yet, so you can remove them yourself whenever you like.

Uninstalling

Use Windows Settings → Apps → Installed apps, and uninstall logrrr. Uninstalling removes logrrr's settings and the stored uploader key, so if you reinstall, you start again from the Getting Started tab. Your media folder (and its Logs folder) stays where it is; delete it yourself if you don't need it. Revoke the uploader key in the console too.

Developers

Management API keys (console → Settings → API keys) read your data through the logrrr API. The API reference is at api.logrrr.com/docs.