Plug-in installed successfully, config is valid, but log shows:

One of your plugins incorrectly registered an external accessory using the platform name (Camera-UniFi-Protect) and not the plugin identifier. Please report this to the developer!

I have 1 camera on Protect, it does not show up when manually adding an accessory to Home app.

I am running into this error when trying to connect UniFi Protect to homebridge. I see that camera-ffmpeg is a requirement for this plugin to work. Are there any additional configurations that need to be made in camera-ffmpeg, as this was what I suspect may be causing this error message. If I need to configure each camera, like camera-ffmpeg shows on their page, I am confused as to what this plugin helps with, so any clarification here would be much appreciated. Hope there is a more efficient solution, than having to configure each camera in the JSON file first, as that would be rather inefficient. Either way, I wanted to say thank you for taking time out to make this plugin. Hope I can get it to work. I do have RTSP turned on, on each camera, just to confirm that part.

I previsiously was using, and had it working, but didn't think it would work correct with UniFi Protect.

npm install -g ffmpeg

npm install -g homebridge-camera-ffmpeg-ufv

The error I am seeing when using your plugin:
Error: No RTSP channel found
at bootstrap.cameras.map.camera (/usr/local/lib/node_modules/homebridge-ufp/index.js:162:25)
at Array.map ()
at requestPromise.get.then.response (/usr/local/lib/node_modules/homebridge-ufp/index.js:154:40)
at tryCatcher (/usr/local/lib/node_modules/homebridge-ufp/node_modules/bluebird/js/release/util.js:16:23)
at Promise._settlePromiseFromHandler (/usr/local/lib/node_modules/homebridge-ufp/node_modules/bluebird/js/release/

First of all this plugin is awesome. I found this by you mentioning you forking from another homebridge UI plugin. This sucker fixed every single issue I was having with that other plugin. BUT :)

Is there a way to add audio? The other plugin thats the one thing that worked was audio haha

I am thoroughly stumped. Keep getting a LoginRequired error.

• I am using local IP as sever address
• same url routes to the CloudKey
• setup a dedicated login for home bridge, this login works using the same IP url
• when used as part of home bridge config, throws error below

Is this a bug, or am I missing something?

(node:640) UnhandledPromiseRejectionWarning: StatusCodeError: 412 - {"data":[],"meta":{"rc":"error","msg":"api.err.LoginRequired"}}
    at new StatusCodeError (/usr/local/lib/node_modules/homebridge-ufp/node_modules/request-promise-core/lib/errors.js:32:15)
    at Request.plumbing.callback (/usr/local/lib/node_modules/homebridge-ufp/node_modules/request-promise-core/lib/plumbing.js:104:33)
    at Request.RP$callback [as _callback] (/usr/local/lib/node_modules/homebridge-ufp/node_modules/request-promise-core/lib/plumbing.js:46:31)
    at Request.self.callback (/usr/local/lib/node_modules/homebridge-ufp/node_modules/request/request.js:185:22)
    at Request.emit (events.js:311:20)
    at Request.<anonymous> (/usr/local/lib/node_modules/homebridge-ufp/node_modules/request/request.js:1154:10)
    at Request.emit (events.js:311:20)
    at IncomingMessage.<anonymous> (/usr/local/lib/node_modules/homebridge-ufp/node_modules/request/request.js:1076:12)
    at Object.onceWrapper (events.js:417:28)
    at IncomingMessage.emit (events.js:323:22)
    at endReadableNT (_stream_readable.js:1204:12)
    at processTicksAndRejections (internal/process/task_queues.js:84:21)
(node:640) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:640) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.