Git Product home page Git Product logo

homebridge-camera-ui's Introduction

homebridge-camera-ui

npm npm npm GitHub last commit verified-by-homebridge Discord Donate

homebridge-camera-ui allows you to expose cameras from camera.ui to HomeKit via Homebridge. camera.ui does not need to be installed separately. It is installed right away with homebridge-camera-ui

camera.ui is a NVR like PWA to control your RTSP capable cameras with:

  • Live Streams on Web
  • Camview: A resizable, drag & drop camera overview
  • Web Application with almost full PWA support like push notification and more
  • Multi-language: Easily expandable multi-language support
  • Motion Detection via video analysis, MQTT, FTP, SMT or HTTP.
  • Image Rekognition via AWS Rekognition
  • Notifications via Alexa, Telegram, Webhook and WebPush
  • Snapshot/Video: Save recording of snapshots/videos locally when motion is detected
  • Prebuffering: See the seconds before the movement event
  • User Interface: Beautiful and with love designed interface with 8 different color themes, dark mode and more
  • HSV Support (HomeKit Secure Video)
  • Config UI X Support

and much more...

Supported Languages:

🇩🇪 | 🇬🇧 | 🇳🇱 | 🇫🇷 | 🇹🇭 | 🇪🇸

Demo: https://streamable.com/3yce42

Installation

sudo npm install -g homebridge-camera-ui@latest

Documentation

Configuration

camera.ui installs itself in the homebridge directory under /var/lib/homebridge/camera.ui/

The database, recordings and a copy of the camera.ui config.json are stored locally in this folder and are never accessible to others. The settings can be changed directly via the interface or over homebridge-config-ui-x

Defaults

Once you have installed and configured it you can access the interface via http://localhost:8081.

The default username is master and the default password is master. When you log in for the first time, camera.ui will ask you to change your username and password.

Example Config (minimal)

{
   ...
    "platforms": [
        {
            "platform": "CameraUI",
            "name": "CameraUI",
            "port": 8081,
            "cameras": [ ... ]
        }
    ]
}

For a full config.json, please look at Example Config for more details.

Usage

Dashboard

The Dashboard is the main page of the interface and offers a variety of widgets to customize it as you like. The widgets will expand over time. At the moment the following widgets are available for the dashboard: Time, Weather, Uptime, Camera, Notifications, RSS Feed, Status, Charts (CPU Load, CPU Temperature, Memory Load), Shortcuts and Log

camera.ui

Cameras

Here are all cameras listed by room and show the current snapshot as a cover sheet

camera.ui

Camera

If you select a camera you can watch the livestream directly in the browser. With the camera.ui player you can pause the stream, turn audio on/off or reload the stream.

camera.ui

Recordings

All images or videos recorded by motion are listed here. If AWS Rekognition is used, the label for the recording is also displayed, as well as the date and time. Using the filter function, the recordings can be filtered as desired

camera.ui

Notifications

All motion events as well as system messages can be viewed here. Each notification has one or more labels to better categorize them. The filter function can also be used to filter the notifications as desired.

camera.ui

Camview

Camview displays all camera streams in tiles, hiding everything unnecessary. Camview is great for giving a direct insight into the cameras. Also here the streams can be paused by the camera.ui video player, audio can be switched on/off, streams can be reloaded or viewed in full mode.

camera.ui

Log

All events that occur in the backend can be monitored via the built-in log. In addition, the log can be also be cleared or downloaded here.

camera.ui

Config

Using the built-in editor you can easily edit your config.json. In addition, any errors are immediately displayed and thus avoided to save a faulty config.json

camera.ui

Utilization

"Utilization" shows you a graphical overview of the system utilization. Here you can see in real time how high the CPU utilization is, how high the CPU temperature is and how much memory is still free.

camera.ui

Settings

On the settings page you can make ALL settings regarding your config.json and database. All parameters defined in config.json are directly configurable from this page. If camera.ui runs via "Homebridge" you can also set Homebridge relevant parameters here.

camera.ui

HomeKit Secure Video (HSV)

HSV requires a Homebridge version of at least 1.4.0-beta.4 or higher. Otherwise HSV will not be enabled.

When the plugin is used with HSV, all recordings from HomeKit Secure Video are automatically transferred to camera.ui as well and stored for them. All camera.ui features like WebPush, Telegram notifications etc. will still work with HSV.

How to configure cameras for HSV

Motion detection

camera.ui offers a variety of options to detect and process motion.

Videoanalysis

camera.ui

With this option camera.ui connects to the stream and compares frame by frame if there are changes. The zones and sensitivity can be set in the interface.

HTTP

If the HTTP server is enabled for motion detection, calling the link can easily trigger motion.

Example:

http://localhost:8123/motion?My+Camera

MQTT

If you have set up the MQTT client (Settings > System > MQTT), you can set the required parameters such as "Motion Topic", "Message" etc. via the interface (Settings > Cameras > MQTT).

Motion Topic: The MQTT topic to watch for motion alerts. The topic (prefix/suffix) should be unique, it will be used to assign the motion detected message to the desired camera.

Motion Message: The message to watch for to trigger motion alerts.

The message can be a simple "string" (e.g. "ON"/"OFF) or a JSON object. If the MQTT message is a JSON object like:

{
  "id": "test",
  "event": {
    "time": 1234567890,
    "state": true,
  }
}

Then define the exact parameter under "Motion Message" so that camera.ui can read from it, eg:

"motionMessage": {
  "event": {
    "state": true
  }
}

SMTP

If the SMTP server is turned on and your camera is able to send an email when motion is detected, you can easily trigger motion through it, eg:

From: [email protected] To: [email protected]

Please note that the camera.ui SMTP server is set in the camera settings (ip/port).

FTP

If your camera is able to upload an image when motion is detected, then you can select the camera.ui FTP server as the destination. Very important here is. The path you enter via the camera's own settings page must be the camera name as defined in config.

Every time the camera tries to connect to the server, the camera.ui detects and takes the entered path to determine the camera.

Image Rekognition

If HomeKit Secure Video (HSV) is disabled, camera.ui also uses image rekognition with Amazon Web Services to analyse, detect, remember and recognize objects, scenes, and faces in images. You can enable for each camera the image rekogniton and you can even set labels for each camera. For each object, scene, and concept the API returns one or more labels. Each label provides the object name. For example, suppose the input image has a lighthouse, the sea, and a rock. The response includes all three labels, one for each object.

This makes it possible to analyze every movement before this is stored or sent as a notification.

To use image rekognition, you need to set up a AWS account with an IAM user. More Infos: AWS Image Rekognition

Notifications

camera.ui supports numerous notification options. Each of them can be conveniently set via the interface.

Since push notifications only work conditionally for websites (see PWA), you can easily work around this via third-party providers.

These would be e.g.

  • Telegram
  • Webhook
  • Alexa
  • Third party providers that support Alexa

Via Telegram, you even have the option to send picture or video along with text messages.

Supported clients

This plugin has been verified to work with the following apps/systems:

  • iOS > 11
  • Android
  • Windows 10
  • macOS Catalina 10.15
  • Apple Home
  • All 3rd party apps like Elgato Eve etc
  • Homebridge >= v1.1.6
  • Node >= 14

What you need for HomeKit Secure Video

  • An iPhone, iPad, or iPod Touch with iOS 13.2 or later.
  • The Home app set up on your iPhone, iPad, or iPod touch with the Apple ID that you use with iCloud.
  • A home hub set up on an iPad, HomePod, or Apple TV.
  • A supported iCloud storage plan

Browser

The following browsers are supported by this plugin:

  • Chrome - latest
  • Firefox - latest
  • Safari - 2 most recent major versions
  • iOS - 2 most recent major versions

MS Internet Explorer (any version) is not supported!

Supported Cameras

Every camera with an RTSP stream!

See Tested Cameras for more info.

FAQ

Please check our FAQ before you open an issue.

Contributing

You can contribute to this homebridge plugin in following ways:

  • Report issues and help verify fixes as they are checked in.
  • Review the source code changes.
  • Contribute bug fixes.
  • Contribute changes to extend the capabilities
  • Pull requests are accepted.

Troubleshooting

If you have any issues with the plugin then you can run this plugin in debug mode, which will provide some additional information. This might be useful for debugging issues. Just open your config ui and set debug to true!

https://github.com/SeydX/homebridge-camera-ui/wiki/Debug

If you have problems with the interface or found bugs, please post it directly at camera.ui

Wiki

Before you open a new issue, please read carefully the wiki: https://github.com/seydx/homebridge-camera-ui/wiki

License

MIT License

Copyright (c) 2020-2022 seydx

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

homebridge-camera-ui's People

Contributors

aklimov-work avatar dependabot-preview[bot] avatar dependabot[bot] avatar designorant avatar dotwee avatar eiryu avatar grzegorz914 avatar jtweaver avatar seydx avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

homebridge-camera-ui's Issues

Not Working for Yi Cameras, Homebridge installed on Mac via HomeBrew

Trying to get this plugin running for my 2 yi cameras, a dome cam 1080, and outdoor cam 1080.

System Info: Mac running macOS 10.14

Ffmpeg was installed via homebrew

plugin installed with: npm install -g homebridge-camera-ui@latest

Config for the plugin looks like this and the was validated by jsonlint:

 {
	"platform": "CameraUI",
	"debug": false,
	"videoProcessor": "ffmpeg",
	"cameras": [{
			"name": "Living Room",
			"active": true,
			"yihackv4": true,
			"videoConfig": {
				"source": "-rtsp_transport tcp -re -i rtsp://xxx.xxx.x.xxx/ch0_0.h264",
        "stillImageSource": "-i rtsp://xxx.xxx.x.xxx/ch0_0.h264",
        "maxWidth": 1920,
				"maxHeight": 1080,
				"maxFPS": 30
			}
		},
		{
			"name": "Walkout",
			"active": true,
			"yihackv4": true,
			"videoConfig": {
				"source": "-rtsp_transport tcp -re -i rtsp://yyy.yyy.y.yyy/ch0_0.h264",
        "stillImageSource": "-i rtsp://yyy.yyy.y.yyy/ch0_0.h264",
        "maxWidth": 1920,
				"maxHeight": 1080,
				"maxFPS": 30
			}
		}
	]
}

After running home bridge, these are the relevant outputs I see

[2019-07-24, 1:27:18 p.m.] Plugin /usr/local/lib/node_modules/homebridge-camera-ui requires Node version of ^8.9.1 which does not satisfy the current Node version of v12.6.0. You may need to upgrade your installation of Node.

[2019-07-24, 1:27:37 p.m.] [CameraUI] Initializing CameraUI platform...
[2019-07-24, 1:27:37 p.m.] [CameraUI] **************************************************************
[2019-07-24, 1:27:37 p.m.] [CameraUI] CameraUI v2.1.9 by SeydX
[2019-07-24, 1:27:37 p.m.] [CameraUI] GitHub: https://github.com/SeydX/homebridge-camera-mqtt
[2019-07-24, 1:27:37 p.m.] [CameraUI] Email: [email protected]
[2019-07-24, 1:27:37 p.m.] [CameraUI] **************************************************************
[2019-07-24, 1:27:37 p.m.] [CameraUI] start success...

[2019-07-24, 1:27:37 p.m.] [CameraUI] [INFO] Initalizing Living Room
[2019-07-24, 1:27:37 p.m.] [CameraUI] [INFO] Initalizing Walkout
[2019-07-24, 1:27:37 p.m.] [CameraUI] [INFO] Found 2 active camera(s) in config.json
[2019-07-24, 1:27:41 p.m.] Living Room is running on port #####.
[2019-07-24, 1:27:41 p.m.] Please add [Living Room] manually in Home app. Setup Code: ###-##-###
[2019-07-24, 1:27:41 p.m.] Walkout is running on port #####.
[2019-07-24, 1:27:41 p.m.] Please add [Walkout] manually in Home app. Setup Code: ###-##-###

[2019-07-24, 1:27:42 p.m.] [CameraUI] [ERROR] Living Room: An error occured while checking camera config!
[2019-07-24, 1:27:42 p.m.] [CameraUI] [ERROR] Walkout: An error occured while checking camera config!_

Then homebridge completes its boot up and displays the QR code. Everything else works fine and I was even able to add the cameras to homekit using the setup codes which were generated.

However, the cameras never displayed anything. Not preview tiles or stream, just a no response message.

After homebridge is running, these are the messages being output
[2019-07-24, 1:27:52 p.m.] [CameraUI] [INFO] Living Room: Snapshot from Living Room at 480x270
[2019-07-24, 1:27:52 p.m.] [CameraUI] [INFO] Walkout: Snapshot from Walkout at 480x270
[2019-07-24, 1:27:58 p.m.] [CameraUI] [ERROR] Living Room: An error occured while checking camera config!
[2019-07-24, 1:27:59 p.m.] [CameraUI] [ERROR] Walkout: An error occured while checking camera config!
[2019-07-24, 1:28:00 p.m.] [CameraUI] [INFO] Walkout: Snapshot from Walkout at 480x270
[2019-07-24, 1:28:00 p.m.] [CameraUI] [INFO] Living Room: Snapshot from Living Room at 480x270
[2019-07-24, 1:28:06 p.m.] [CameraUI] [INFO] Living Room: Snapshot from Living Room at 480x270
[2019-07-24, 1:28:06 p.m.] [CameraUI] [INFO] Walkout: Snapshot from Walkout at 480x270
[2019-07-24, 1:28:08 p.m.] [CameraUI] [INFO] Walkout: Snapshot from Walkout at 480x270
[2019-07-24, 1:28:15 p.m.] [CameraUI] [ERROR] Living Room: An error occured while checking camera config!
[2019-07-24, 1:28:15 p.m.] [CameraUI] [ERROR] Walkout: An error occured while checking camera config!
[2019-07-24, 1:28:20 p.m.] [CameraUI] [INFO] Walkout: Snapshot from Walkout at 480x270
[2019-07-24, 1:28:27 p.m.] [CameraUI] [INFO] Living Room: Snapshot from Living Room at 480x270
[2019-07-24, 1:28:31 p.m.] [CameraUI] [ERROR] Living Room: An error occured while checking camera config!
[2019-07-24, 1:28:31 p.m.] [CameraUI] [ERROR] Walkout: An error occured while checking camera config!
[2019-07-24, 1:28:33 p.m.] [CameraUI] [INFO] Living Room: Snapshot from Living Room at 480x270
[2019-07-24, 1:28:33 p.m.] [CameraUI] [INFO] Walkout: Snapshot from Walkout at 480x270
[2019-07-24, 1:28:41 p.m.] [CameraUI] [INFO] Start streaming video from Living Room with 1280x720@299kBit
[2019-07-24, 1:28:41 p.m.] [CameraUI] [INFO] Walkout: Snapshot from Walkout at 480x270
[2019-07-24, 1:28:42 p.m.] [CameraUI] [ERROR] Living Room: FFmpeg exited with code 1
[2019-07-24, 1:28:47 p.m.] [CameraUI] [INFO] Walkout: Snapshot from Walkout at 480x270
[2019-07-24, 1:28:47 p.m.] [CameraUI] [INFO] Living Room: Snapshot from Living Room at 480x270
[2019-07-24, 1:28:47 p.m.] [CameraUI] [ERROR] Living Room: An error occured while checking camera config!
[2019-07-24, 1:28:47 p.m.] [CameraUI] [ERROR] Walkout: An error occured while checking camera config!
[2019-07-24, 1:28:59 p.m.] [CameraUI] [INFO] Living Room: Snapshot from Living Room at 480x270
[2019-07-24, 1:29:03 p.m.] [CameraUI] [ERROR] Living Room: An error occured while checking camera config!
[2019-07-24, 1:29:03 p.m.] [CameraUI] [ERROR] Walkout: An error occured while checking camera config!
[2019-07-24, 1:29:12 p.m.] [CameraUI] [INFO] Walkout: Snapshot from Walkout at 480x270
[2019-07-24, 1:29:17 p.m.] [CameraUI] [INFO] Living Room: Snapshot from Living Room at 480x270
[2019-07-24, 1:29:19 p.m.] [CameraUI] [ERROR] Living Room: An error occured while checking camera config!
[2019-07-24, 1:29:19 p.m.] [CameraUI] [ERROR] Walkout: An error occured while checking camera config!
[2019-07-24, 1:29:28 p.m.] [CameraUI] [INFO] Living Room: Snapshot from Living Room at 480x270
[2019-07-24, 1:29:35 p.m.] [CameraUI] [ERROR] Living Room: An error occured while checking camera config!
[2019-07-24, 1:29:35 p.m.] [CameraUI] [ERROR] Walkout: An error occured while checking camera config!
[2019-07-24, 1:29:36 p.m.] [CameraUI] [INFO] Walkout: Snapshot from Walkout at 480x270
[2019-07-24, 1:29:40 p.m.] [CameraUI] [INFO] Living Room: Snapshot from Living Room at 480x270
[2019-07-24, 1:29:50 p.m.] [CameraUI] [INFO] Living Room: Snapshot from Living Room at 480x270
[2019-07-24, 1:29:51 p.m.] [CameraUI] [ERROR] Living Room: An error occured while checking camera config!
[2019-07-24, 1:29:51 p.m.] [CameraUI] [ERROR] Walkout: An error occured while checking camera config!
[2019-07-24, 1:29:51 p.m.] [CameraUI] [INFO] Walkout: Snapshot from Walkout at 480x270
[2019-07-24, 1:29:53 p.m.] [CameraUI] [INFO] Walkout: Snapshot from Walkout at 480x270
[2019-07-24, 1:30:07 p.m.] [CameraUI] [ERROR] Living Room: An error occured while checking camera config!
[2019-07-24, 1:30:07 p.m.] [CameraUI] [ERROR] Walkout: An error occured while checking camera config!
[2019-07-24, 1:30:13 p.m.] [CameraUI] [INFO] Walkout: Snapshot from Walkout at 480x270
[2019-07-24, 1:30:22 p.m.] [CameraUI] [INFO] Living Room: Snapshot from Living Room at 480x270
[2019-07-24, 1:30:23 p.m.] [CameraUI] [ERROR] Living Room: An error occured while checking camera config!
[2019-07-24, 1:30:23 p.m.] [CameraUI] [ERROR] Walkout: An error occured while checking camera config!
[2019-07-24, 1:30:34 p.m.] [CameraUI] [INFO] Living Room: Snapshot from Living Room at 480x270
[2019-07-24, 1:30:39 p.m.] [CameraUI] [ERROR] Living Room: An error occured while checking camera config!
[2019-07-24, 1:30:39 p.m.] [CameraUI] [ERROR] Walkout: An error occured while checking camera config!
[2019-07-24, 1:30:45 p.m.] [CameraUI] [INFO] Walkout: Snapshot from Walkout at 480x270
[2019-07-24, 1:30:55 p.m.] [CameraUI] [ERROR] Living Room: An error occured while checking camera config!
[2019-07-24, 1:30:55 p.m.] [CameraUI] [ERROR] Walkout: An error occured while checking camera config!
[2019-07-24, 1:30:56 p.m.] [CameraUI] [INFO] Walkout: Snapshot from Walkout at 480x270
[2019-07-24, 1:31:06 p.m.] [CameraUI] [INFO] Living Room: Snapshot from Living Room at 480x270
[2019-07-24, 1:31:11 p.m.] [CameraUI] [ERROR] Living Room: An error occured while checking camera config!
[2019-07-24, 1:31:11 p.m.] [CameraUI] [ERROR] Walkout: An error occured while checking camera config!
[2019-07-24, 1:31:27 p.m.] [CameraUI] [ERROR] Living Room: An error occured while checking camera config!
[2019-07-24, 1:31:27 p.m.] [CameraUI] [ERROR] Walkout: An error occured while checking camera config!
[2019-07-24, 1:31:38 p.m.] [CameraUI] [INFO] Walkout: Snapshot from Walkout at 480x270
[2019-07-24, 1:31:39 p.m.] [CameraUI] [INFO] Living Room: Snapshot from Living Room at 480x270
[2019-07-24, 1:31:43 p.m.] [CameraUI] [ERROR] Living Room: An error occured while checking camera config!
[2019-07-24, 1:31:43 p.m.] [CameraUI] [ERROR] Walkout: An error occured while checking camera config!
[2019-07-24, 1:31:51 p.m.] [CameraUI] [INFO] Walkout: Snapshot from Walkout at 480x270
[2019-07-24, 1:31:58 p.m.] [CameraUI] [INFO] Living Room: Snapshot from Living Room at 480x270
[2019-07-24, 1:31:59 p.m.] [CameraUI] [ERROR] Living Room: An error occured while checking camera config!
[2019-07-24, 1:31:59 p.m.] [CameraUI] [ERROR] Walkout: An error occured while checking camera config!
[2019-07-24, 1:32:15 p.m.] [CameraUI] [ERROR] Living Room: An error occured while checking camera config!
[2019-07-24, 1:32:15 p.m.] [CameraUI] [ERROR] Walkout: An error occured while checking camera config!
[2019-07-24, 1:32:31 p.m.] [CameraUI] [INFO] Walkout: Snapshot from Walkout at 480x270
[2019-07-24, 1:32:31 p.m.] [CameraUI] [ERROR] Living Room: An error occured while checking camera config!
[2019-07-24, 1:32:32 p.m.] [CameraUI] [ERROR] Walkout: An error occured while checking camera config!
[2019-07-24, 1:32:47 p.m.] [CameraUI] [ERROR] Living Room: An error occured while checking camera config!
[2019-07-24, 1:32:48 p.m.] [CameraUI] [ERROR] Walkout: An error occured while checking camera config!
[2019-07-24, 1:32:51 p.m.] [CameraUI] [INFO] Living Room: Snapshot from Living Room at 480x270
[2019-07-24, 1:33:02 p.m.] [CameraUI] [INFO] Living Room: Snapshot from Living Room at 480x270
[2019-07-24, 1:33:03 p.m.] [CameraUI] [ERROR] Living Room: An error occured while checking camera config!
[2019-07-24, 1:33:04 p.m.] [CameraUI] [ERROR] Walkout: An error occured while checking camera config!
[2019-07-24, 1:33:04 p.m.] [CameraUI] [INFO] Walkout: Snapshot from Walkout at 480x270
[2019-07-24, 1:33:20 p.m.] [CameraUI] [ERROR] Living Room: An error occured while checking camera config!
[2019-07-24, 1:33:20 p.m.] [CameraUI] [ERROR] Walkout: An error occured while checking camera config!
[2019-07-24, 1:33:31 p.m.] [SmartThings] Change Event: (Living Room Harmony) [CURRENTACTIVITY] is --
[2019-07-24, 1:33:31 p.m.] [SmartThings] Change Event: (TV - Apple TV [Harmony Activity]) [SWITCH] is off
[2019-07-24, 1:33:36 p.m.] [CameraUI] [ERROR] Living Room: An error occured while checking camera config!
[2019-07-24, 1:33:36 p.m.] [CameraUI] [ERROR] Walkout: An error occured while checking camera config!
[2019-07-24, 1:33:39 p.m.] [CameraUI] [INFO] Walkout: Snapshot from Walkout at 480x270
[2019-07-24, 1:33:43 p.m.] [CameraUI] [INFO] Living Room: Snapshot from Living Room at 480x270
[2019-07-24, 1:33:43 p.m.] [CameraUI] [INFO] Walkout: Snapshot from Walkout at 480x270
[2019-07-24, 1:33:45 p.m.] [CameraUI] [INFO] Living Room: Snapshot from Living Room at 480x270
[2019-07-24, 1:33:52 p.m.] [CameraUI] [ERROR] Living Room: An error occured while checking camera config!
[2019-07-24, 1:33:52 p.m.] [CameraUI] [ERROR] Walkout: An error occured while checking camera config!
[2019-07-24, 1:34:08 p.m.] [CameraUI] [ERROR] Living Room: An error occured while checking camera config!
[2019-07-24, 1:34:08 p.m.] [CameraUI] [ERROR] Walkout: An error occured while checking camera config!
[2019-07-24, 1:34:14 p.m.] [CameraUI] [INFO] Living Room: Snapshot from Living Room at 480x270
[2019-07-24, 1:34:24 p.m.] [CameraUI] [ERROR] Living Room: An error occured while checking camera config!
[2019-07-24, 1:34:24 p.m.] [CameraUI] [ERROR] Walkout: An error occured while checking camera config!
[2019-07-24, 1:34:40 p.m.] [CameraUI] [ERROR] Living Room: An error occured while checking camera config!
[2019-07-24, 1:34:40 p.m.] [CameraUI] [ERROR] Walkout: An error occured while checking camera config!
[2019-07-24, 1:34:53 p.m.] [CameraUI] [INFO] Walkout: Snapshot from Walkout at 480x270
[2019-07-24, 1:34:56 p.m.] [CameraUI] [ERROR] Living Room: An error occured while checking camera config!
[2019-07-24, 1:34:56 p.m.] [CameraUI] [ERROR] Walkout: An error occured while checking camera config!
[2019-07-24, 1:35:12 p.m.] [CameraUI] [ERROR] Living Room: An error occured while checking camera config!
[2019-07-24, 1:35:12 p.m.] [CameraUI] [ERROR] Walkout: An error occured while checking camera config!
[2019-07-24, 1:35:28 p.m.] [CameraUI] [ERROR] Living Room: An error occured while checking camera config!
[2019-07-24, 1:35:28 p.m.] [CameraUI] [ERROR] Walkout: An error occured while checking camera config!
[2019-07-24, 1:35:44 p.m.] [CameraUI] [ERROR] Living Room: An error occured while checking camera config!
[2019-07-24, 1:35:44 p.m.] [CameraUI] [ERROR] Walkout: An error occured while checking camera config!
[2019-07-24, 1:36:00 p.m.] [CameraUI] [ERROR] Living Room: An error occured while checking camera config!
[2019-07-24, 1:36:00 p.m.] [CameraUI] [ERROR] Walkout: An error occured while checking camera config!
[2019-07-24, 1:36:16 p.m.] [CameraUI] [ERROR] Living Room: An error occured while checking camera config!
[2019-07-24, 1:36:16 p.m.] [CameraUI] [ERROR] Walkout: An error occured while checking camera config!
[2019-07-24, 1:36:32 p.m.] [CameraUI] [ERROR] Living Room: An error occured while checking camera config!
[2019-07-24, 1:36:32 p.m.] [CameraUI] [ERROR] Walkout: An error occured while checking camera config!
[2019-07-24, 1:36:48 p.m.] [CameraUI] [ERROR] Living Room: An error occured while checking camera config!
[2019-07-24, 1:36:48 p.m.] [CameraUI] [ERROR] Walkout: An error occured while checking camera config!
[2019-07-24, 1:37:04 p.m.] [CameraUI] [ERROR] Living Room: An error occured while checking camera config!
[2019-07-24, 1:37:04 p.m.] [CameraUI] [ERROR] Walkout: An error occured while checking camera config!
[2019-07-24, 1:37:20 p.m.] [CameraUI] [ERROR] Living Room: An error occured while checking camera config!
[2019-07-24, 1:37:20 p.m.] [CameraUI] [ERROR] Walkout: An error occured while checking camera config!
[2019-07-24, 1:37:36 p.m.] [CameraUI] [ERROR] Living Room: An error occured while checking camera config!
[2019-07-24, 1:37:36 p.m.] [CameraUI] [ERROR] Walkout: An error occured while checking camera config!
[2019-07-24, 1:37:52 p.m.] [CameraUI] [ERROR] Living Room: An error occured while checking camera config!
[2019-07-24, 1:37:52 p.m.] [CameraUI] [ERROR] Walkout: An error occured while checking camera config!
[2019-07-24, 1:38:08 p.m.] [CameraUI] [ERROR] Living Room: An error occured while checking camera config!
[2019-07-24, 1:38:09 p.m.] [CameraUI] [ERROR] Walkout: An error occured while checking camera config!
[2019-07-24, 1:38:25 p.m.] [CameraUI] [ERROR] Living Room: An error occured while checking camera config!
[2019-07-24, 1:38:25 p.m.] [CameraUI] [ERROR] Walkout: An error occured while checking camera config!
[2019-07-24, 1:38:41 p.m.] [CameraUI] [ERROR] Living Room: An error occured while checking camera config!
[2019-07-24, 1:38:41 p.m.] [CameraUI] [ERROR] Walkout: An error occured while checking camera config!
[2019-07-24, 1:38:57 p.m.] [CameraUI] [ERROR] Living Room: An error occured while checking camera config!
[2019-07-24, 1:38:57 p.m.] [CameraUI] [ERROR] Walkout: An error occured while checking camera config!
[2019-07-24, 1:39:13 p.m.] [CameraUI] [ERROR] Living Room: An error occured while checking camera config!
[2019-07-24, 1:39:13 p.m.] [CameraUI] [ERROR] Walkout: An error occured while checking camera config!

Any ideas how to Fix this?

RTSP stream with FFMPEG gives error. In VLC ok

Hi,

I get a new camera today. This camera's stream URL is:

rtsp://user:[email protected]:554/realmonitor?channel=0&stream=0.sdp (from onvif-device-tool)

If I try this link in VLC it works fine (in VLC is sufficent to use rtsp://user:[email protected] but also works with the full URL). In FFMPEG I get nothing if I use the URL without quotes.

If I use ffmpeg -i "rtsp://192.168.1.109:554/realmonitor?channel=0&stream=0.sdp" I get:

Invalid data found when processing input

Now I'm a little bit confused what to do...

My cam is this:

https://www.amazon.de/gp/product/B07QS1LLL3/ref=ppx_yo_dt_b_asin_title_o01_s00?ie=UTF8&psc=1

Mqtt Motion Not triggered

Hey this Is my config for Version v2
"mqtt": {
"active": true,
"host": "192.168.0.50",
"port": 1883,
"topicPrefix": "siedle",
"topicSuffix": "cmnd",
"startMessage": "ring_E_D",
"stopMessage": "motion_stop",
"recordOnMovement": false,
"recordVideoSize": 10,
"interval": 1
}

And this for v3

"mqtt": {
"active": true,
"host": "192.168.0.50",
"port": 1883,
"topic": "siedle/cmnd",
"on_message": "ring_E_D"
},

But no motion is triggered when ring_E_D is sent to topic siedle/cmnd

Have issue with future versions?

Tried to install but seems to be not compatible with newer packages?

sudo npm i -g homebridge-camera-ui@latest
npm WARN deprecated [email protected]: core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
npm WARN notsup Unsupported engine for [email protected]: wanted: {"node":"^8.9.1","homebridge":"^0.4.49"} (current: {"node":"12.16.2","npm":"6.14.5"})
npm WARN notsup Not compatible with your version of node/npm: [email protected]

Any help appreciated.
Thank
Mic

QUESTION: How do I setup notifications for HomeKit?

In version 2.x I'm able to get notifications from HomeKit by monitoring a FTP target. My cams write images on movement to a folder on my FTP server. With version 3 it seems the FTP feature is dropped.

How are notifications handled now? With MQTT I've no experiences. What do I need?

Are there other possibilities for notifications from HomeKit?

Is H.265 supported?

Thanks for everything!
I have a couple HIKVision cameras that default to H.265 and once that happens, Homebridge no longer will stream the video. The snapshots work, but the video wont until I explicitly go into the camera and select H.264 as the stream.

Fatal error: cannot read property ‘active’ of ‘undefined’

Hi,

I installed homebridge-yi-camera and ran into the missing form-data module bug, which I solved by manually installing it.

On the next run, however, I got the following error:

[10/13/2019, 9:14:23 PM] [YiCamera] Initializing YiCamera platform...
[10/13/2019, 9:14:23 PM] TypeError: Cannot read property 'active' of undefined
    at new YiCamera (/usr/lib/node_modules/homebridge-yi-camera/src/platform.js:39:34)
    at Server._loadPlatforms (/usr/lib/node_modules/homebridge/lib/server.js:337:32)
    at Server.run (/usr/lib/node_modules/homebridge/lib/server.js:90:36)
    at module.exports (/usr/lib/node_modules/homebridge/lib/cli.js:59:10)
    at Object.<anonymous> (/usr/lib/node_modules/homebridge/bin/homebridge:17:22)
    at Module._compile (internal/modules/cjs/loader.js:945:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:962:10)
    at Module.load (internal/modules/cjs/loader.js:798:32)
    at Function.Module._load (internal/modules/cjs/loader.js:711:12)
    at Function.Module.runMain (internal/modules/cjs/loader.js:1014:10)
    at internal/main/run_main_module.js:17:11
[10/13/2019, 9:14:24 PM] Got SIGTERM, shutting down Homebridge...

config.json Is parsing alright on JSON Lint, and the only things I changed were the names and IPs of the 2 cameras I’ve included.

Can anyone help?

Implement proper vcodec copy support via characteristics.

This is just a thought and basicly a crossposting from an issue posted at homebridge-camera-ffmpeg.

homebridge-camera-ui allows to set vcodec copy to speed up the stream without re-enconding. This fails if homekit requests a stream with resolution, bitrate, etc. that conflicts with just copying the stream, i.e. my yi outdoor cam works fine on my iPhone, but not on my iPad with vcodec copy.

Homekit supports video stream configuration via characteristics: HAP-Specification-Non-Commercial-Version.pdf - Video Attributes:

The Video attributes allow the accessory to indicate supported resolutions, frame rates etc., This information is encoded as a tlv8- the list of types for the value of this TLV are as follows [...]

Can we force Homekit to request the streams in their native resolution via characteristics, so we can use vcodec copy?

problem on view camera

I have a problem on view camera.
since yesterday I used https://github.com/Sunoo/homebridge-camera-ffmpeg

now, when I switch on your plugin my camera is not active.

my previuos config:
{
"name": "Camera FFmpeg",
"cameras": [
{
"serialNumber": "ZZZZZZZZ",
"videoConfig": {
"vcodec": "h264",
"source": "-rtsp_transport tcp -re -i rtsp://[email protected]/h264_stream",
"debug": true,
"maxFPS": 30,
"maxHeight": 720,
"maxStreams": 2,
"maxWidth": 1280,
"audio": true
},
"model": "Ezviz Mini Plus",
"name": "Cam Conigli"
}
],
"platform": "Camera-ffmpeg"
},

my actual config:
{
"name": "CameraUI",
"port": 8282,
"auth": "form",
"theme": "auto",
"language": "auto",
"debug": false,
"reset": false,
"mqtt": {
"active": false
},
"http": {
"active": false,
"localhttp": false
},
"ssl": {
"active": false
},
"cameras": [
{
"name": "Cam Conigli",
"manufacturer": "Ezviz",
"model": "Ezviz Mini Plus",
"serialNumber": "xxxxxx",
"unbridge": false,
"videoConfig": {
"source": "-rtsp_transport tcp -vcodec h264_mmal -i rtsp://admin:[email protected]/Streaming/Channels/1",
"stillImageSource": "-i rtsp://[email protected]/Streaming/Channels/1/picture",
"maxWidth": 1920,
"maxHeight": 1080,
"maxFPS": 15,
"maxBitrate": 500,
"vcodec": "h264_omx",
"packetSize": 564,
"audio": true
}
}
],
"platform": "CameraUI"
}

rstp stream worked ... tested.. but no live view... where I am wrong?

Room entry not saving, and not presenting saved rooms into dropdown of cameras "Select Room"

Describe the bug

Within the General tab, when trying to add additional rooms, the additions arent saved between viewing sessions.

I am also unable to select the rooms within the Cameras tab, Select Room to assign the camera to a room.

To Reproduce

Each time I start a new session, the list of rooms I have entered arent there. When tabbing between and back to General the rooms stay, but when closing the session down don't save and arent available next time.

Expected behavior

Enter additional rooms, click apply and they stay as options.

Be able to use the additional rooms to assign them to a camera within the cameras tab.

Logs
If available, attach the log where the bug is vissible

Screenshots
If applicable, add screenshots to help explain your problem.
image
image

Environment

  • Node.js Version: vX.X
  • Homebridge Version: vX.X
  • Camera UI Version: vX.X
  • Operating System: XXX
  • Browser: XXX

FFmpeg exited with code 1

Getting an error from ffmpeg but I cannot figure out what is really causing a code 1 exit.

When I try to run the ffmpeg command from the terminal it works perfectly.

Here is the ffmpeg command generated but the plugin and works fine when run from the terminal.

ffmpeg -re -i "rtsp://username:[email protected]:554/live/ch00_1" -map 0:0 -vcodec libx264 -pix_fmt yuv420p -r 10 -f rawvideo -tune zerolatency -vf scale=1280:720 -b:v 299k -bufsize 299k -maxrate 299k -payload_type 99 -ssrc 11697191 -f rtp -srtp_out_suite AES_CM_128_HMAC_SHA1_80 -srtp_out_params pg1/hpQHmNazokuBM4w+/4kDczM3bfQtjWgXQTDN "srtp://192.168.1.202:63855?rtcpport=63855&localrtcpport=63855&pkt_size=1316" -map 0:1 -acodec libfdk_aac -profile:a aac_eld -flags +global_header -f null -ar 16k -b:a 24k -bufsize 24k -ac 1 -payload_type 110 -ssrc 1848011 -f rtp -srtp_out_suite AES_CM_128_HMAC_SHA1_80 -srtp_out_params rpZzU9cGR8sdAF6G7uzKLOrpb1ee1tgySxn4Nez0 "srtp://192.168.1.202:52756?rtcpport=52756&localrtcpport=52756&pkt_size=1316" -loglevel debug out.flv 2> out.txt

This is my config

{
            "videoProcessor": "ffmpeg",
            "debug": true,
            "cameras": [
                {
                    "name": "Camera UI",
                    "active": true,
                    "videoConfig": {
                        "source": "-re -i rtsp://username:[email protected]:554/live/ch00_1",
                        "maxStreams": 2,
                        "maxWidth": 1280,
                        "maxHeight": 720,
                        "maxFPS": 10,
                        "maxBitrate": 300,
                        "vcodec": "libx264",
                        "packetSize": 1316,
                        "audio": true
                    }
                }
            ],
            "platform": "CameraUI"
        }

Here is the log generated in homebridge when the streaming starts

[9/28/2020, 2:04:58 AM] [CameraUI] [INFO] Start streaming video from Spy Camera UI with 1280x720@299kBit
2020-09-27T16:04:58.194Z CameraUI Camera UI: ffmpeg -re -i rtsp://username:[email protected]:554/live/ch00_1 -map 0:0 -vcodec libx264 -pix_fmt yuv420p -r 10 -f rawvideo -tune zerolatency -vf scale=1280:720 -b:v 299k -bufsize 299k -maxrate 299k -payload_type 99 -ssrc 11697191 -f rtp -srtp_out_suite AES_CM_128_HMAC_SHA1_80 -srtp_out_params pg1/hpQHmNazokuBM4w+/4kDczM3bfQtjWgXQTDN srtp://192.168.1.201:63855?rtcpport=63855&localrtcpport=63855&pkt_size=1316 -map 0:1 -acodec libfdk_aac -profile:a aac_eld -flags +global_header -f null -ar 16k -b:a 24k -bufsize 24k -ac 1 -payload_type 110 -ssrc 1848011 -f rtp -srtp_out_suite AES_CM_128_HMAC_SHA1_80 -srtp_out_params rpZzU9cGR8sdAF6G7uzKLOrpb1ee1tgySxn4Nez0 srtp://192.168.1.201:52756?rtcpport=52756&localrtcpport=52756&pkt_size=1316 -loglevel debug
2020-09-27T16:04:58.253Z CameraUI ffmpeg version 4.3.1 Copyright (c) 2000-2020 the FFmpeg developers
  built with Apple clang version 11.0.3 (clang-1103.0.32.62)
  configuration: --prefix=/usr/local/Cellar/ffmpeg/4.3.1-with-options_3 --enable-shared --cc=clang --host-cflags= --host-ldflags= --enable-gpl --enable-libaom --enable-libdav1d --enable-libmp3lame --enable-libopus --enable-libsnappy --enable-libtheora --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libx265 --enable-libfontconfig --enable-libfreetype --enable-frei0r --enable-libass --enable-demuxer=dash --disable-libjack --disable-indev=jack --enable-opencl --enable-videotoolbox --disable-htmlpages --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libfdk-aac --enable-libgme --enable-libgsm --enable-libmodplug --enable-libopenh264 --enable-libopenjpeg --enable-librav1e --enable-librsvg --enable-librtmp --enable-librubberband --enable-libsoxr --enable-libspeex --enable-libsrt --enable-libssh --enable-libtesseract --enable-libtwolame --enable-libvidstab --enable-libvmaf --enable-libwavpack --enable-libwebp --enable-libxml2 --enable-libxvid --enable-libzimg --enable-libzmq --enable-openssl --enable-nonfree --enable-decklink --extra-cflags=-I/usr/local/include --extra-ldflags=-L/usr/local/include --enable-version3 --enable-libopencore-amrnb --enable-libopencore-amrwb

2020-09-27T16:04:58.253Z CameraUI   libavutil      56. 51.100 / 56. 51.100
  libavcodec     58. 91.100 / 58. 91.100
  libavformat    58. 45.100 / 58. 45.100
  libavdevice    58. 10.100 / 58. 10.100
  libavfilter     7. 85.100 /  7. 85.100
  libswscale      5.  7.100 /  5.  7.100
  libswresample   3.  7.100 /  3.  7.100
  libpostproc    55.  7.100 / 55.  7.100
Splitting the commandline.
Reading option '-re' ... matched as option 're' (read input at native frame rate) with argument '1'.
Reading option '-i' ... matched as input url with argument 'rtsp://username:[email protected]:554/live/ch00_1'.
Reading option '-map' ... matched as option 'map' (set input stream mapping) with argument '0:0'.
Reading option '-vcodec' ... matched as option 'vcodec' (force video codec ('copy' to copy stream)) with argument 'libx264'.
Reading option '-pix_fmt' ... matched as option 'pix_fmt' (set pixel format) with argument 'yuv420p'.
Reading option '-r' ... matched as option 'r' (set frame rate (Hz value, fraction or abbreviation)) with argument '10'.
Reading option '-f' ... matched as option 'f' (force format) with argument 'rawvideo'.
Reading option '-tune' ...
2020-09-27T16:04:58.254Z CameraUI  matched as AVOption 'tune' with argument 'zerolatency'.
Reading option '-vf' ... matched as option 'vf' (set video filters) with argument 'scale=1280:720'.
Reading option '-b:v' ... matched as option 'b' (video bitrate (please use -b:v)) with argument '299k'.
Reading option '-bufsize' ...
2020-09-27T16:04:58.254Z CameraUI  matched as AVOption 'bufsize' with argument '299k'.
Reading option '-maxrate' ...
2020-09-27T16:04:58.255Z CameraUI  matched as AVOption 'maxrate' with argument '299k'.
Reading option '-payload_type' ...
2020-09-27T16:04:58.255Z CameraUI  matched as AVOption 'payload_type' with argument '99'.
Reading option '-ssrc' ...
2020-09-27T16:04:58.256Z CameraUI  matched as AVOption 'ssrc' with argument '11697191'.
Reading option '-f' ... matched as option 'f' (force format) with argument 'rtp'.
Reading option '-srtp_out_suite' ...
2020-09-27T16:04:58.256Z CameraUI  matched as AVOption 'srtp_out_suite' with argument 'AES_CM_128_HMAC_SHA1_80'.
Reading option '-srtp_out_params' ...
2020-09-27T16:04:58.256Z CameraUI  matched as AVOption 'srtp_out_params' with argument 'pg1/hpQHmNazokuBM4w+/4kDczM3bfQtjWgXQTDN'.
Reading option 'srtp://192.168.1.201:63855?rtcpport=63855&localrtcpport=63855&pkt_size=1316' ... matched as output url.
Reading option '-map' ... matched as option 'map' (set input stream mapping) with argument '0:1'.
Reading option '-acodec' ... matched as option 'acodec' (force audio codec ('copy' to copy stream)) with argument 'libfdk_aac'.
Reading option '-profile:a' ... matched as option 'profile' (set profile) with argument 'aac_eld'.
Reading option '-flags' ...
2020-09-27T16:04:58.257Z CameraUI  matched as AVOption 'flags' with argument '+global_header'.
Reading option '-f' ... matched as option 'f' (force format) with argument 'null'.
Reading option '-ar' ... matched as option 'ar' (set audio sampling rate (in Hz)) with argument '16k'.
Reading option '-b:a' ...
2020-09-27T16:04:58.257Z CameraUI  matched as option 'b' (video bitrate (please use -b:v)) with argument '24k'.
Reading option '-bufsize' ...
2020-09-27T16:04:58.257Z CameraUI  matched as AVOption 'bufsize' with argument '24k'.
Reading option '-ac' ... matched as option 'ac' (set number of audio channels) with argument '1'.
Reading option '-payload_type' ...
2020-09-27T16:04:58.257Z CameraUI  matched as AVOption 'payload_type' with argument '110'.
Reading option '-ssrc' ...
2020-09-27T16:04:58.258Z CameraUI  matched as AVOption 'ssrc' with argument '1848011'.
Reading option '-f' ... matched as option 'f' (force format) with argument 'rtp'.
Reading option '-srtp_out_suite' ...
2020-09-27T16:04:58.258Z CameraUI  matched as AVOption 'srtp_out_suite' with argument 'AES_CM_128_HMAC_SHA1_80'.
Reading option '-srtp_out_params' ...
2020-09-27T16:04:58.258Z CameraUI  matched as AVOption 'srtp_out_params' with argument 'rpZzU9cGR8sdAF6G7uzKLOrpb1ee1tgySxn4Nez0'.
Reading option 'srtp://192.168.1.201:52756?rtcpport=52756&localrtcpport=52756&pkt_size=1316' ... matched as output url.
Reading option '-loglevel' ... matched as option 'loglevel' (set logging level) with argument 'debug'.
Finished splitting the commandline.
Parsing a group of options: global .
Applying option loglevel (set logging level) with argument debug.
Successfully parsed a group of options.

2020-09-27T16:04:58.258Z CameraUI Parsing a group of options: input url rtsp://linkrjr:[email protected]:554/live/ch00_1.
Applying option re (read input at native frame rate) with argument 1.
Successfully parsed a group of options.
Opening an input file: rtsp://username:[email protected]:554/live/ch00_1.

2020-09-27T16:04:58.260Z CameraUI [tcp @ 0x7f9660404640] No default whitelist set

2020-09-27T16:04:58.260Z CameraUI [tcp @ 0x7f9660404640] Original list of addresses:
[tcp @ 0x7f9660404640] Address 192.168.1.28 port 554
[tcp @ 0x7f9660404640] Interleaved list of addresses:
[tcp @ 0x7f9660404640] Address 192.168.1.28 port 554
[tcp @ 0x7f9660404640] Starting connection attempt to 192.168.1.28 port 554

2020-09-27T16:04:58.278Z CameraUI [tcp @ 0x7f9660404640] Successfully connected to 192.168.1.28 port 554

2020-09-27T16:04:58.339Z CameraUI [rtsp @ 0x7f9662008200] SDP:
v=0
s=streamed by the macro-video rtsp server
t=0 0
a=control:*
a=range:npt=0-
a=x-qt-text-nam:streamed by the macro-video rtsp server
c=IN IP4 0.0.0.0
m=video 0 RTP/AVP 96
b=AS:500
a=rtpmap:96 H264/90000
a=fmtp:96 profile-level-id=TeAo;packetization-mode=1;sprop-parameter-sets=J03gKI1oBQBboQAAAwABAAADAGQPFCKg,KO4BNJI=
a=control:track1


2020-09-27T16:04:58.339Z CameraUI Failed to parse interval end specification ''
[rtsp @ 0x7f9662008200] video codec set to: h264
[rtsp @ 0x7f9662008200] RTP Packetization Mode: 1
[rtsp @ 0x7f9662008200] Extradata set to 0x7f9661204d90 (size: 37)

2020-09-27T16:04:58.340Z CameraUI [rtp @ 0x7f9661204c00] No default whitelist set

2020-09-27T16:04:58.340Z CameraUI [udp @ 0x7f96612052c0] No default whitelist set

2020-09-27T16:04:58.340Z CameraUI [udp @ 0x7f96612052c0] end receive buffer size reported is 393216

2020-09-27T16:04:58.340Z CameraUI [udp @ 0x7f9661205380] No default whitelist set

2020-09-27T16:04:58.340Z CameraUI [udp @ 0x7f9661205380] end receive buffer size reported is 393216

2020-09-27T16:04:58.383Z CameraUI [rtsp @ 0x7f9662008200] setting jitter buffer size to 500

2020-09-27T16:04:58.383Z CameraUI [rtsp @ 0x7f9662008200] hello state=0

2020-09-27T16:04:58.406Z CameraUI [h264 @ 0x7f966200be00] nal_unit_type: 7(SPS), nal_ref_idc: 1
[h264 @ 0x7f966200be00] nal_unit_type: 8(PPS), nal_ref_idc: 1

2020-09-27T16:04:58.569Z CameraUI [h264 @ 0x7f966200be00] nal_unit_type: 7(SPS), nal_ref_idc: 1
[h264 @ 0x7f966200be00] nal_unit_type: 8(PPS), nal_ref_idc: 1

2020-09-27T16:04:58.691Z CameraUI [h264 @ 0x7f966200be00] nal_unit_type: 7(SPS), nal_ref_idc: 1
[h264 @ 0x7f966200be00] nal_unit_type: 8(PPS), nal_ref_idc: 1

2020-09-27T16:04:58.692Z CameraUI [h264 @ 0x7f966200be00] nal_unit_type: 5(IDR), nal_ref_idc: 1

2020-09-27T16:04:58.692Z CameraUI [h264 @ 0x7f966200be00] Format yuv420p chosen by get_format().
[h264 @ 0x7f966200be00] Reinit context to 1280x720, pix_fmt: yuv420p

2020-09-27T16:04:58.736Z CameraUI [h264 @ 0x7f966200be00] nal_unit_type: 1(Coded slice of a non-IDR picture), nal_ref_idc: 1

2020-09-27T16:05:00.488Z CameraUI     Last message repeated 5 times
[rtsp @ 0x7f9662008200] All info found
[rtsp @ 0x7f9662008200] rfps: 24.666667 0.016347
[rtsp @ 0x7f9662008200] rfps: 24.750000 0.009251
    Last message repeated 1 times
[rtsp @ 0x7f9662008200] rfps: 24.833333 0.004214

2020-09-27T16:05:00.488Z CameraUI     Last message repeated 1 times
[rtsp @ 0x7f9662008200] rfps: 24.916667 0.001237
[rtsp @ 0x7f9662008200] rfps: 25.000000 0.000319
[rtsp @ 0x7f9662008200] rfps: 25.083333 0.001460
    Last message repeated 1 times
[rtsp @ 0x7f9662008200] rfps: 25.166667 0.004660
    Last message repeated 1 times
[rtsp @ 0x7f9662008200] rfps: 25.250000 0.009919
    Last message repeated 1 times
[rtsp @ 0x7f9662008200] rfps: 25.333333 0.017237
[rtsp @ 0x7f9662008200] rfps: 50.000000 0.001275

2020-09-27T16:05:00.488Z CameraUI Input #0, rtsp, from 'rtsp://username:[email protected]:554/live/ch00_1':
  Metadata:
    title           : streamed by the macro-video rtsp server
  Duration: N/A, start: 0.460000, bitrate: N/A

2020-09-27T16:05:00.488Z CameraUI     Stream #0:0, 28, 1/90000: Video: h264 (Main), 1 reference frame, yuv420p(progressive, left), 1280x720, 0/1, 50 fps, 25 tbr, 90k tbn, 100 tbc
Successfully opened the file.
Parsing a group of options: output url srtp://192.168.1.201:63855?rtcpport=63855&localrtcpport=63855&pkt_size=1316.
Applying option map (set input stream mapping) with argument 0:0.

2020-09-27T16:05:00.488Z CameraUI Applying option vcodec (force video codec ('copy' to copy stream)) with argument libx264.
Applying option pix_fmt (set pixel format) with argument yuv420p.
Applying option r (set frame rate (Hz value, fraction or abbreviation)) with argument 10.
Applying option f (force format) with argument rawvideo.
Applying option vf (set video filters) with argument scale=1280:720.
Applying option b:v (video bitrate (please use -b:v)) with argument 299k.
Applying option f (force format) with argument rtp.
Successfully parsed a group of options.
Opening an output file: srtp://192.168.1.201:63855?rtcpport=63855&localrtcpport=63855&pkt_size=1316.

2020-09-27T16:05:00.489Z CameraUI [srtp @ 0x7f9660504ec0] No default whitelist set

2020-09-27T16:05:00.489Z CameraUI [rtp @ 0x7f966050a180] No default whitelist set
[udp @ 0x7f966050a400] No default whitelist set

2020-09-27T16:05:00.489Z CameraUI [udp @ 0x7f966050a4c0] No default whitelist set

2020-09-27T16:05:00.489Z CameraUI Successfully opened the file.
Parsing a group of options: output url srtp://192.168.1.201:52756?rtcpport=52756&localrtcpport=52756&pkt_size=1316.
Applying option map (set input stream mapping) with argument 0:1.
Stream map '0:1' matches no streams.
To ignore this, add a trailing '?' to the map.

2020-09-27T16:05:00.489Z CameraUI [AVIOContext @ 0x7f966050a580] Statistics: 0 seeks, 0 writeouts

[9/28/2020, 2:05:00 AM] [CameraUI] [ERROR] Spy Camera UI: FFmpeg exited with code 1

Any help is very appreciated.

Images/Videos via Telegram

This plugin sends also captured images/videos (if setted up in config.json) via Telegram.

Can you please explain how to do this? I like to send captured images via Telegram. Telegram is up and running and i receive textmessages. But i like to have some images and/or videos ;)

A.

Almost succeed to add an HTTP camera mjpeg stream

Hi,
I'm trying to add an http camera, and it almost worked !! ffmpeg is able to open the stream. That's basically an mjpeg stream.
I can see the snapshot in homekit, I can even see the stream in the cameraui page. But I can't see the stream in Homekit. No visible error message.
Any idea ?
Thanks for your help
BTW I'm not able to see ffmpeg logs in the homebridge log window, even if I select ffmpeg debug

FFmpeg process

It seems, that some user (atm only macOS) has problems with hanging ffmpeg processes.

If you are also using macOS and has problems with hanging ffmpeg processes, pls report it here!

Every log, screenshot or anything else that helps me to debug is welcome!

I also need the information about the operating system, Homebridge version and CameraUI version

SeydX

NOT AN ISSUE -

Hi,

It seems to be an interesting project. But I'm trying to understand what's the benefit of using this plugin vs the standard @KhaosT camera ffmpeg plugin apart from the MQTT motion functionality?

Does it support OMX acceleration?

Updating Homebridge

Tried installing and i get the below error

The plugin "homebridge-camera-ui" requires a Homebridge version of ^1.2.0 which does not satisfy the current Homebridge version of 1.1.6. You may need to update this plugin (or Homebridge) to a newer version. You may face unexpected issues or stability problems running this plugin.

As far as i know i have latest stable version for now.Do i need to update so i can use the plugin?

How to remove this plugin ?

Hello, impossible for me to remove this plugin ?

`pi@raspberrypi:~ $ sudo npm remove homebridge-yi-camera
npm WARN [email protected] No repository field.

audited 961 packages in 83.766s

8 packages are looking for funding
run npm fund for details

found 0 vulnerabilities
`

Local camera offline

Describe the bug
The camera is working ok on homebridge and it stream ok in homekit BUT it´s always offline on camera.ui web interface
The soketPort is define for the camera.

To Reproduce
use local camera (in the same rpi running homebridge and cameraui
video source: "source": "-re -f video4linux2 -i /dev/video0"

Expected behavior
I hope it shows the stream as it works on homekit, but it doesn´t.

Logs

Installation warn (several times tray during some weeks):
node-pre-gyp WARN Using needle for node-pre-gyp https download
node-pre-gyp WARN Tried to download(404): https://github.com/kelektiv/node.bcrypt.js/releases/download/v5.0.0/bcrypt_lib-v5.0.0-napi-v3-linux-arm-glibc.tar.gz
node-pre-gyp WARN Pre-built binaries not found for [email protected] and [email protected] (node-v83 ABI, glibc) (falling back to source compile with node-gyp)
make: Entering directory '/usr/local/lib/node_modules/homebridge-camera-ui/node_modules/bcrypt/build'
CC(target) Release/obj.target/nothing/../node-addon-api/nothing.o
AR(target) Release/obj.target/../node-addon-api/nothing.a
COPY Release/nothing.a
CXX(target) Release/obj.target/bcrypt_lib/src/blowfish.o
CXX(target) Release/obj.target/bcrypt_lib/src/bcrypt.o
CXX(target) Release/obj.target/bcrypt_lib/src/bcrypt_node.o
SOLINK_MODULE(target) Release/obj.target/bcrypt_lib.node
COPY Release/bcrypt_lib.node
COPY /usr/local/lib/node_modules/homebridge-camera-ui/node_modules/bcrypt/lib/binding/napi-v3/bcrypt_lib.node
TOUCH Release/obj.target/action_after_build.stamp
make: Leaving directory '/usr/local/lib/node_modules/homebridge-camera-ui/node_modules/bcrypt/build'

[email protected] install /usr/local/lib/node_modules/homebridge-camera-ui/node_modules/ffmpeg-for-homebridge
node install.js

Get this error on homebridge log when launching cameraui web interface

[11/23/2020, 10:01:14 AM] [CameraUI] [Interface] Cámara Salón: An error occured during pinging
[11/23/2020, 10:01:14 AM] [CameraUI] TypeError: Cannot read property 'includes' of undefined
at Object.getHost (/usr/local/lib/node_modules/homebridge-camera-ui/app/lib/ping.js:36:13)
at Object.ping (/usr/local/lib/node_modules/homebridge-camera-ui/app/lib/ping.js:9:25)
at Object.pingCamera (/usr/local/lib/node_modules/homebridge-camera-ui/app/models/cameras.js:37:28)
at /usr/local/lib/node_modules/homebridge-camera-ui/app/controller/dashboard.js:14:26
at Layer.handle [as handle_request] (/usr/local/lib/node_modules/homebridge-camera-ui/node_modules/express/lib/router/layer.js:95:5)
at next (/usr/local/lib/node_modules/homebridge-camera-ui/node_modules/express/lib/router/route.js:137:13)
at Route.dispatch (/usr/local/lib/node_modules/homebridge-camera-ui/node_modules/express/lib/router/route.js:112:3)
at Layer.handle [as handle_request] (/usr/local/lib/node_modules/homebridge-camera-ui/node_modules/express/lib/router/layer.js:95:5)
at /usr/local/lib/node_modules/homebridge-camera-ui/node_modules/express/lib/router/index.js:281:22
at Function.process_params (/usr/local/lib/node_modules/homebridge-camera-ui/node_modules/express/lib/router/index.js:335:12)
[11/23/2020, 10:01:14 AM] [CameraUI] [Interface] Cámara Salón: Offline
GET /dashboard 200 1770.244 ms - -

Screenshots
If applicable, add screenshots to help explain your problem.

Environment

  • Node.js Version: v14.15.0
  • Homebridge Version: -tested on v1.2.3, v.1.3.0-beta.25 and stable version 1.1.6
  • Camera UI Version: v3.4.1
    Operating System: Raspbian GNU/Linux 10 (buster)
    Kernel: Linux 5.4.72-v7+
    Architecture: arm
    -Browser any

error starting Homebridge .4.50

Hi,

I have this issue:

[2019-9-13 18:21:12] Loaded config.json with 0 accessories and 1 platforms.
[2019-9-13 18:21:12] ---
[2019-9-13 18:21:12] Loaded plugin: homebridge-camera-ui
module.js:550
throw err;
^

Error: Cannot find module 'form-data'
at Function.Module._resolveFilename (module.js:548:15)
at Function.Module._load (module.js:475:25)
at Module.require (module.js:597:17)
at require (internal/module.js:11:18)
at Object. (/usr/lib/node_modules/homebridge-camera-ui/src/accessories/camera.js:14:18)
at Module._compile (module.js:653:30)
at Object.Module._extensions..js (module.js:664:10)
at Module.load (module.js:566:32)
at tryModuleLoad (module.js:506:12)
at Function.Module._load (module.js:498:3)

video parameters + snap shot shot feature

nice plugin!

  • Is it possible to add support for ffmpeg video config parameters such as h264_omx for rpi user?
    like packetSize, vcodec and such
  • Is it possible to add snap shot feature?

Help to turn on/off At Home using webhook

Describe the bug
Not a bug, looking for help.
Trying to use webhook to turn on/off At Home mode

Idea is to add a http or webhook button in homebridge to control this after knowing what I’m missing

Expected behavior
I'd like this section shows you exactly the link to use (including IP or whatever’s missing if so) so dumb users like me can just copy/paste

Screenshots
image
image

Environment

  • Node.js Version: v14.15.5
  • Homebridge Version: v1.2.5
  • Camera UI Version: v3.1.5
  • Operating System: homebridge installed on Rpi using official image
  • Browser: trying to send webhook from Chrome in Windows 10

FFmpeg hangs up

Hi,

How I'm gonna get the same behaviour as in the previous version?
I do have 3 YI hacked cameras and in the previous 2.2.0 version, I've received by an motion information on the iphone (statusdisplay) with the screenshot of the cam pic. I'm running mosquitto locally and each YI camera has got his MQTT settings for motion mqtt information. Based on that a video is going to be created under the old situation with the v 2.2.0. What is the correct way to configure that? See below my adjusted configuration for the new version 3.0.2 copied from the revious version for each camera the necessary mqtt section:
Please not I'm just running one YI cam for testing purposes:

  {
        "platform": "CameraUI",
        "name": "CameraUI",
        "port": 3333,
        "auth": "form",
        "language": "EN",
        "debug": true,
        "reset": false,
        "mqtt": {
            "active": true,
            "host": "localhost",
            "port": 1883,
            "topic": "homebridge/motion",
            "on_message": "ON"
        },
        "options": {
            "videoProcessor": "ffmpeg",
            "interfaceName": "en1",
            "ffmpegExecPath": "/usr/local/bin/ffmpeg"
        },
        "cameras": [
            {
                "name": "Garden",
                "motion": true,
                "videoConfig": {
                    "source": "-rtsp_transport tcp -err_detect ignore_err -re -i rtsp://x:[email protected]/ch0_1.h264",
                    "stillImageSource": "-i http://x:[email protected]:8080/cgi-bin/snapshot.sh?res=low&base64=no",
                    "maxStreams": 5,
                    "maxWidth": 1920,
                    "maxHeight": 1080,
                    "maxFPS": 30,
                    "maxBitrate": 1024,
                    "vcodec": "copy",
                    "packetSize": 1316,
                    "audio": false,
                    "debug": true
                },
                "mqtt": {
                    "active": true,
                    "host": "localhost",
                    "port": 1883,
                    "username": "",
                    "password": "",
                    "topicPrefix": "yicam2",
                    "topicSuffix": "motion",
                    "startMessage": "motion_start",
                    "stopMessage": "motion_stop",
                    "recordOnMovement": true,
                    "recordVideoSize": 60,
                    "interval": 0
                }
            }
        ]

Many thanks,

efkayx

Connecting on port 80

When switching parameter "yihackv4" to "true" the following error occured:
2020-05-18T09:34:23.768Z CameraUI Error: connect ECONNREFUSED 192.168.2.124:80 at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1141:16) 2020-05-18T09:34:38.769Z CameraUI gartenkamera: api request 46 : GET http://192.168.2.124/cgi-bin/get_configs.sh?conf=system [5/18/2020, 11:34:38 AM] [CameraUI] [ERROR] gartenkamera: An error occured while checking camera config!

CameraUI tries to connect on port 80, but the camera is working at port 8080. Whats wrong?
Switching back to ""yihackv4": true," gives no more error and no connections at port 80.

The corresponding part of my config:
{ "platform": "CameraUI", "debug": true, "videoProcessor": "ffmpeg", "cameras": [ { "name": "gartenkamera", "active": true, "yihackv4": true, "videoConfig": { "source": "-rtsp_transport tcp -re -i rtsp://192.168.2.124/ch0_0.h264", "stillImageSource": "http://192.168.2.124:8080/cgi-bin/snapshot.sh", "maxStreams": 2, "maxWidth": 1280, "maxHeight": 720, "maxBitrate": 300, "vcodec": "copy", "maxFPS": 10 }, "mqtt": { "active": true, "host": "192.168.2.148", "port": 1883, "username": "", "password": "", "topicPrefix": "yicam", "topicSuffix": "motion", "startMessage": "motion_start", "stopMessage": "motion_stop", "recordOnMovement": true, "recordVideoSize": 60, "interval": 0 } }, { "name": "nestkameranord", "active": true, "yihackv4": false, "videoConfig": { "source": "-rtsp_transport tcp -re -i rtsp://192.168.2.126/ch0_0.h264", "stillImageSource": "http://192.168.2.126:8080/cgi-bin/snapshot.sh", "maxStreams": 2, "maxWidth": 1280, "maxHeight": 720, "maxBitrate": 300, "vcodec": "copy", "maxFPS": 10 } }

enabling audio causes live stream to fail

Hey! @seydx FANTASTIC plugin!! I will 100% be donating as soon as I can figure this issue out!!!!

So I have 2 Yi 1080p Dome Cams (hacked) and I have set up the RTSP stream and the video works however as soon as I enable audio and try to put the audio RTSP stream it fails to play the stream in HomeKit and in CameraUI.
How should I go about getting the audio to work?

Here is the config for one of the cameras (this config is set to audio disabled and that's when the live stream works)
"name": "Front of House",
"videoConfig": {
"source": "-i rtsp://192.168.2.35/ch0_0.h264",
"audio": false,
"debug": true

here is the config for the same camera when the audio is enabled
"name": "Front of House",
"videoConfig": {
"source": "-i rtsp://192.168.2.35/ch0_0.h264",
"audio": true,
"debug": true

once i do that and restart homebridge as soon as i open the homekit cam i get this error in homebridge:
[Camera FFmpeg] FFmpeg exited with code: 1 and signal: null (Error)
[Camera FFmpeg] [Front of House] Stopped video stream.

Now i know I'm missing something because in the Yi Hack has a UI by going to its IP and when i go to the RTSP tab there is enable audio and a stream dedicated to it but i do not know where to input that into the config of this plugin.
Here is what the RTSP stream for the audio of my camera looks like:

rtsp://192.168.2.35/ch0_2.aac

Please help me out. :)

FTP login every second

Not sure if this is an issue, but I found that there is a successful login attempt to FTP server every second. Is this intended?

I'm using this setup:

  • OS: Raspbian buster
  • homebridge v1.0.4
  • homebridge-camera-ui v2.1.9
  • vsftpd 3.0.3-12

And the following config in homebridge:

"ftp": {
	"absolutePath": "PATH_TO_TOLDER",
	"active": true,
	"host": "IP",
	"interval": 120,
	"movementDuration": 20,
	"recordOnMovement": true,
	"recordVideoSize": 30,
	"username": "USERNAME",
	"password": "PASSWORD",
	"secure": false
}

Send screenshot to Telegram when movement is detected

Hi.

I think it would be great to have the option, as configuration option, to send a screenshot immediately when movement is detected and then send the video as now it does. That's because it is faster to send a screenshot and you can get an idea of what happens while waiting for the video.

Regards.

No camera issue seen and error in logs.

I have installed latest oznu Homebridge package on my Synology but after setting up I'm receiving the following errors in the logs:

[INFO] Start streaming video from Outside with 1280x720@299kBit
[6/17/2019, 10:20:12 PM] [CameraUI] [ERROR] Outside: An error occurs while making stream request
[6/17/2019, 10:20:12 PM] [CameraUI] [ERROR] Outside: FFmpeg exited with code -2

I can add the cameras fine in Home app but see no preview or output when clicking in the camera.

HOOBS - Got SIGTERM, shutting down Bridge..

Describe the bug

After installation of a plug-in
HOOBS - Got SIGTERM, shutting down Bridge...

The problem appears when updating the web gui.

Config :

{
"platform": "CameraUI",
"plugin_map": {
"plugin_name": "homebridge-camera-ui"
},
"name": "CameraUI",
"auth": "form",
"theme": "auto",
"language": "Auto",
"debug": true,
"reset": false,
"mqtt": {
"active": true,
"host": "192.168.1.74",
"port": 1883,
"username": "mqtt",
"topic": "homebridge/motion"
},
"http": {
"active": false,
"localhttp": false
},
"ssl": {
"active": false
},
"cameras": [
{
"name": "Camera 1",
"videoConfig": {
"source": "-i rtsp://xxxxx:[email protected]:554/cam/realmonitor?channel=1&subtype=0",
"stillImageSource": "-i rtsp://xxxx:[email protected]:554/cam/realmonitor?channel=1&subtype=0",
"maxStreams": 2,
"motion": true,
"vcodec": "copy",
"maxWidth": 1920,
"maxHeight": 1080,
"socketPort": 8100,
"maxFPS": 30,
"debug": true
}
}
],
"options": {
"videoProcessor": "ffmpeg",
"interfaceName": "enp0s31f6"
}
}

Logs

12.12.2020, 14:29:17 Error: spawn ffmpeg ENOENT
at Process.ChildProcess._handle.onexit (internal/child_process.js:269:19)
at onErrorNT (internal/child_process.js:465:16)
at processTicksAndRejections (internal/process/task_queues.js:80:21)12.12.2020, 14:29:17 Got SIGTERM, shutting down Bridge...12.12.2020, 14:29:17 Catching error on dropMembership: {"errno":-99,"code":"EADDRNOTAVAIL","syscall":"dropMembership"}12.12.2020, 14:29:17 Catching error on dropMembership: {"errno":-99,"code":"EADDRNOTAVAIL","syscall":"dropMembership"}12.12.2020, 14:29:19 Catching error on dropMembership: {"errno":-99,"code":"EADDRNOTAVAIL","syscall":"dropMembership"}12.12.2020, 14:29:19 Catching error on dropMembership: {"errno":-99,"code":"EADDRNOTAVAIL","syscall":"dropMembership"}

Screenshots
If applicable, add screenshots to help explain your problem.

Environment

  • Node.js Version: 14.15.1
  • Homebridge Version: HOOBS 3.3.1
  • Camera UI Version: 3.1.5
  • Operating System: Ubuntu 20.04.1 LTS
  • Browser: Firefox 83

node version check error

installed v10.15.3, requires ^8.9.1, but the following warning appears in log

Plugin /usr/local/lib/node_modules/homebridge-camera-ui requires Node version of ^8.9.1 which does not satisfy the current Node version of v10.15.3. You may need to upgrade your installation of Node.

Localization problem

2020-12-12_15-00-36

Config :

{
"platform": "CameraUI",
"plugin_map": {
"plugin_name": "homebridge-camera-ui"
},
"name": "CameraUI",
"auth": "form",
"theme": "auto",
"language": "Auto",
"debug": true,
"reset": false,
"mqtt": {
"active": true,
"host": "192.168.1.74",
"port": 1883,
"username": "mqtt",
"topic": "homebridge/motion"
},
"http": {
"active": false,
"localhttp": false
},
"ssl": {
"active": false
},

Environment

Node.js Version: 14.15.1
Homebridge Version: HOOBS 3.3.1
Camera UI Version: 3.1.5
Operating System: Ubuntu 20.04.1 LTS
Browser: Firefox 83

Ping and /change not work

Hi ,

I must be doing something really wrong as i can see any cameras in the ui ( but all offline)
The weirdest thing of all is that now i have duplicates in my HOME app

Heres my config

{
"name": "CameraUI",
"port": 3333,
"auth": "none",
"language": "en",
"debug": false,
"reset": false,
"mqtt": {
"active": false
},
"http": {
"active": false,
"localhttp": false
},
"ssl": {
"active": false
},
"cameras": [
{
"name": "Master Bedroom",
"videoConfig": {
"source": "-rtsp_transport tcp -i rtsp://XXXXXXXX/unicast",
"stillImageSource": "-i rtsp://XXXXXXXX/unicast",
"audio": true,
"socketPort": 8100
}
},
{
"name": "Aeglis Room",
"videoConfig": {
"source": "-rtsp_transport tcp -i rtsp://XXXXXXXX/unicast",
"stillImageSource": "-i rtsp://XXXXXXXX/unicast",
"audio": true,
"socketPort": 8100
}
},
{
"name": "Office",
"videoConfig": {
"source": "-rtsp_transport tcp -i rtsp://XXXXXXXX/unicast",
"stillImageSource": "-i rtsp://XXXXXXXX/unicast",
"audio": true,
"socketPort": 8100
}
}
],
"platform": "CameraUI"

Ios14 homekit for Yi camera

Hello, is it possible to have select activity zone and face recognition options available in homekit for Yi camera? I already have a setup with motion alert working but couldn't figure out how to select activity zone and face recognition from homekit. Thanks.

HomeKit

Can’t see recordings

Hi, first thanks for such amazing plugin, congratulations, one of the best 👍

I have mi Yi can working, I can see notifications and small clips (not always) from camera and notifications sections, but if I click on recordings I get an error:
5B7115D8-C807-4B3F-9B21-15735F75EF91

Also the notifications compared to recordings inside SD are different.

What am I missing? Any help is appreciated :)

Error: Cannot access 'user' before initialization

I'm receiving this error when visiting the web UI after updating the plugin. 

I'm using "auth": "none".

I have tried "reset": true but this now just remains set to true constantly now, and the error still occurs.

How to set the save path for recordings

Hi,

all recordings from the GUI will be saved in /homebridge/node_modules/homebridge-camera-ui/app/public/recordings.

How to change the destination??

Because: I use HomeBridge in Docker. Everytime I restart the Docker Image, all recordings will be deleted.

ismartgate camera

I have this camera:
https://shopeurope.ismartgate.com/ip-cameras/33-indoor-ip-camera-8437012951778.html

i have issue about connecting live stream to the camera.
the only thing I have succes about is stil image link. which is:
http://admin:[email protected]:88/cgi-bin/CGIProxy.fcgi?cmd=snapPicture2&usr=admin&pwd=admin&
I got this from:
https://www.ispyconnect.com/man.aspx?n=ismart+gate

but i don't have the live feed url anybody got this working ?
I have tested many many different url / RTSP links no luck so far.

Error 500 Cannot read property 'includes' of undefined

Hi, I‘m getting the error above after login to the web UI. Any idea how to solve this?

Here is some debug log:
POST / 302 153.601 ms - 60
GUI checkAuth /cameras +73ms
GUI TypeError: Cannot read property 'includes' of undefined
GUI at router.get (/usr/local/lib/node_modules/homebridge-camera-ui/app/routes/cameras.js:38:17)
GUI at Layer.handle [as handle_request] (/usr/local/lib/node_modules/homebridge-camera-ui/node_modules/express/lib/router/layer.js:95:5)
GUI at next (/usr/local/lib/node_modules/homebridge-camera-ui/node_modules/express/lib/router/route.js:137:13)
GUI at Route.dispatch (/usr/local/lib/node_modules/homebridge-camera-ui/node_modules/express/lib/router/route.js:112:3)
GUI at Layer.handle [as handle_request] (/usr/local/lib/node_modules/homebridge-camera-ui/node_modules/express/lib/router/layer.js:95:5)
GUI at /usr/local/lib/node_modules/homebridge-camera-ui/node_modules/express/lib/router/index.js:281:22
GUI at Function.process_params (/usr/local/lib/node_modules/homebridge-camera-ui/node_modules/express/lib/router/index.js:335:12)
GUI at next (/usr/local/lib/node_modules/homebridge-camera-ui/node_modules/express/lib/router/index.js:275:10)
GUI at Function.handle (/usr/local/lib/node_modules/homebridge-camera-ui/node_modules/express/lib/router/index.js:174:3)
GUI at router (/usr/local/lib/node_modules/homebridge-camera-ui/node_modules/express/lib/router/index.js:47:12) +5ms
GUI TypeError: Cannot read property 'includes' of undefined
GUI at router.get (/usr/local/lib/node_modules/homebridge-camera-ui/app/routes/cameras.js:38:17)
GUI at Layer.handle [as handle_request] (/usr/local/lib/node_modules/homebridge-camera-ui/node_modules/express/lib/router/layer.js:95:5)
GUI at next (/usr/local/lib/node_modules/homebridge-camera-ui/node_modules/express/lib/router/route.js:137:13)
GUI at Route.dispatch (/usr/local/lib/node_modules/homebridge-camera-ui/node_modules/express/lib/router/route.js:112:3)
GUI at Layer.handle [as handle_request] (/usr/local/lib/node_modules/homebridge-camera-ui/node_modules/express/lib/router/layer.js:95:5)
GUI at /usr/local/lib/node_modules/homebridge-camera-ui/node_modules/express/lib/router/index.js:281:22
GUI at Function.process_params (/usr/local/lib/node_modules/homebridge-camera-ui/node_modules/express/lib/router/index.js:335:12)
GUI at next (/usr/local/lib/node_modules/homebridge-camera-ui/node_modules/express/lib/router/index.js:275:10)
GUI at Function.handle (/usr/local/lib/node_modules/homebridge-camera-ui/node_modules/express/lib/router/index.js:174:3)
GUI at router (/usr/local/lib/node_modules/homebridge-camera-ui/node_modules/express/lib/router/index.js:47:12) +16ms
GET /cameras 500 643.038 ms - 3810
GET /stylesheets/switch.css 304 10.150 ms - -
GET /stylesheets/style.css 304 11.558 ms - -
GET /javascripts/switch.js 304 12.595 ms - -
GET /images/yi_logo.png 304 2.531 ms - -

Dummy switches don't showup

Hi,

I'm running homebridge on a MacOs machine.
I've connected an rtsp wyse camera and a raspberry http camera streaming mjpeg.

I'm not able to see the dummy switches in the homekit app.

Here is my config.json file:

        {
            "name": "CameraUI",
            "port": 8591,
            "auth": "none",
            "language": "en",
            "debug": true,
            "reset": true,
            "mqtt": {
                "active": false
            },
            "http": {
                "active": false,
                "localhttp": false
            },
            "ssl": {
                "active": false
            },
            "options": {
                "videoProcessor": "/usr/local/lib/node_modules/homebridge-nest-cam/node_modules/ffmpeg-for-homebridge/ffmpeg",
                "ffmpegExecPath": "/usr/local/lib/node_modules/homebridge-nest-cam/node_modules/ffmpeg-for-homebridge/ffmpeg"
            },
            "cameras": [
                {
                    "name": "GarageCam",
                    "manufacturer": "Wyze",
                    "motion": true,
                    "doorbell": true,
                    "switches": true,
                    "unbridge": true,
                    "videoConfig": {
                        "source": "-i rtsp://xxxxx:[email protected]/live",
                        "maxWidth": 0,
                        "maxHeight": 0,
                        "maxFPS": 0,
                        "vcodec": "copy",
                        "audio": true,
                        "debug": true,
                        "socketPort": 8100
                    }
                },
                {
                    "name": "PiZeroCam",
                    "manufacturer": "Raspberry",
                    "model": "PiZero",
                    "motion": true,
                    "doorbell": true,
                    "switches": true,
                    "unbridge": true,
                    "videoConfig": {
                        "source": "-i http://xxx.xxx.x.xx:xxxx/",
                        "maxWidth": 1024,
                        "maxHeight": 768,
                        "maxFPS": 15,
                        "vcodec": "copy",
                        "debug": true,
                        "socketPort": 8101
                    }
                }
            ],
            "platform": "CameraUI"
        }

Thanks

update for FFmpeg installation on macOS via Homebrew

the latest release of FFmpeg changed the wording of the option from using "with" to "enabled"

thus the instruction would become:

brew install ffmpeg --enable-fdk-aac --enable-ffplay --enable-libass --enable-libvorbis --enable-libvpx --enable-rtmpdump --enable-openh264 --enable-tools

Automation

Hello, can we see the cameras as devices and create automation in homekit with this plugin?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.