brandawg93 / homebridge-nest-cam Goto Github PK

I see there’s some code for motion detection tagged WIP... any chance of enabling it sooner than later?

Hey,

Thanks for all the updates; really great to see this plugin getting all this love.
After updating yesterday to v0.0.2, I'm noticing that my cameras are more often than not showing "not responding" when I click into the camera. Checking my homebridge logs, I don't see any errors though. Also I know on the main description you identified that thumbnails not refreshing is an issue with the iPhone, but actually before v0.0.2 my thumbnails (as in before clicking into the camera in the Home app) updated quote frequently (in the bottom right corner, I would see how many seconds elapsed since the past update). However ever since v0.0.2 and now I'm on v1.1.0, my thumbnails don't update at all and when I click into the camera, I get the spinning wheel and then the "no response" message. Cameras are on in nest app of course.

Any ideas?

When using Google Credentials to login, and using homebridge-nest for thermostat and protect usage, together with this plugin, I'm unable to add the camera to Homekit through the Home app. I use the default Homebridge code/QR and I get, "Accessory already added". Not sure what the potential issue could be.

Hi - I installed your plugin successfully, activated and set up the appropriate Google credentials. In my log I see (I'm using HOOBS):

[Homebridge] [3/29/2020, 11:00:41 AM] [Nest-cam] Create camera - Family Room Cam
[Homebridge] [3/29/2020, 11:00:41 AM] [Nest-cam] Create camera - Front Door Cam
[Homebridge] [3/29/2020, 11:00:41 AM] [Family Room Cam] is running on port 36313.
[Homebridge] [3/29/2020, 11:00:41 AM] [Front Door Cam] is running on port 34691.

However, I can't see these accessories anywhere to add to any Rooms, they do not show up in Unassigned Accessories. I'm sure that I'm missing something basic. ;-)

Updated from version 0.0.26 to 1.1.0 today. When utilizing version 1.1, the video thumbnail no longer updates. The video stream works perfectly if I tap on it and will start playing right away. I tried rebooting phone and my two Catalina Macs with the Home app but that does not resolve the issue. Going back to version 0.0.26 and restarting the Homebridge instance corrects the issue and the thumbnail will update itself once a minute. The issue also occurs if I try to update to version 0.0.27.

I am hosting Homebridge on a Windows 10 computer with npm 6.13.4 and node 12.16.1. Each plugin I run has it's own Homebridge instance, so only nest-cam2 and config-ui-x run in this instance.

Any troubleshooting thoughts?

"plugins": [
    "homebridge-nest-cam2",
    "homebridge-config-ui-x"
],

Thanks for all the great work reverse-engineering the NEST API!

It'd be great if you can also expose a toggle switch in Homekit for the camera.

Could you post instructions on how to get audio working? I am new at this and it is not clear to me how to get audio working from my nest cameras.

thank you, love the progress you are making.

Is there a way to dial up the sensitivity of motion detection on Nest Cameras? I'm finding my autiomation responses slow.

Thanks, and great work on this!

I noticed that while connecting from outside of home network I still get the thumbnail, but the video is not streaming. The client device is trying to connect for some time and then gives up. It looks like the ffmgep process is actually starting on the hombridge side, but for some reason it is not getting to the client device:

  410 ?        Ssl    9:11 homebridge                                          
 6294 ?        S      0:01  \_ ffmpeg -use_wallclock_as_timestamps 1 -i - -c:v libx264 -an -pix_fmt yuv420p -preset ultrafast -tune zerolatency -payload_type 99 -ssrc 2086046 -f rtp -srtp_out_suite AES_CM_128_HMAC_SHA1_80 -srtp_out_par...

If the client device is located in the home network it works as expected. At the same time, other cameras (with native HomeKit support) work just fine in either case.
Is it just my experience?

Updated to v0.0.27 about an hour ago. Started seeing

[Nest-cam] Unexpected API Error - 404

Tried restarting phone, removed homebridge from Apple Home then re-added. Still seeing the errors show up in Homebridge logs and while I can add the cameras okay, the cameras don't return anything in the app, the thumbnails show a "no response" error.

I noticed a few updates ago that having the Nest Hello in your favorites also adds a button. Tapping the button doesn't do anything, but I can't remove it from my favorites without it taking the camera with it. Is there a way to split this up as two different devices, even though the button doesn't do anything?

always getting this error when using windows system (Windows 10 with ffmpeg installed and added to path):

Error: spawn ffmpeg ENOENT at Process.ChildProcess._handle.onexit (internal/child_process.js:267:19) at onErrorNT (internal/child_process.js:469:16) at processTicksAndRejections (internal/process/task_queues.js:84:21)

repo homebridge-camera-ffmpeg has similar error but could be fixed by giving exact path of ffmpeg.exe

"videoProcessor": "C:\\Softwares\\ffmpeg\\bin\\ffmpeg.exe"

hopefully this repo could add this configuration parameter too.

Dear,

I was wondering how the plugin is fetching the stream. Comparing the Nest App vs. Nest Web, I see a major difference in delay of the video (~1 sec vs. 5 sec). Which stream is the plugin using, because in HomeKit my stream also shows a delay of ~5 seconds. Is there a way to optimize this?

I am using a Raspberry Pi (3), and have ffmpeg installer ("ffmpegCodec": "h264_omx")

Thanks a lot!

I'm using a custom compiled ffmpeg version (as oppose to apt binary package). When installing the last version of homebridge-nest-cam2 (1.1.9) I get the following error:

~/.npm# npm -g update homebridge-nest-cam2 --unsafe-perm

> [email protected] install /usr/lib/node_modules/homebridge-nest-cam2/node_modules/ffmpeg-for-homebridge
> node install.js

Downloading ffmpeg from https://github.com/homebridge/ffmpeg-for-homebridge/releases/latest/download/ffmpeg-debian-x86_64.tar.gz
100% - Download Complete
/root/.npm/_ffmpeg_for_homebridge/ffmpeg: error while loading shared libraries: libmvec.so.1: cannot open shared object file: No such file or directory
An error occured while testing the downloaded ffmpeg binary.
+ [email protected]
added 16 packages from 6 contributors and updated 1 package in 4.231s

Apparently it is trying to install another binary and it is missing some dependency.

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

Hi,
With this nest-cam2 I have an error.
I use h264_omx,
with nest-cam, I didn't have error.

Sat, 25 Jan 2020 11:44:27 GMT Accessory [Backyard] Processing characteristic set: [{"aid":1,"iid":23,"value":"ARBbtp/vDqtIWZgeri24SYdnAxkBAQACDDE5Mi4xNjguMy43MQMC0dQEAlHOBCUCEJMRWxA+gt1uUe1LXtu5EE4DDpRHHvqCdaYgvz9JyqtnAQEABSUCEMdpVeZjF7gfZaKiMUmm5XEDDp6fmZSFQjmeMVasB234AQEA"}]
Sat, 25 Jan 2020 11:44:27 GMT Accessory [Backyard] Setting Characteristic "Setup Endpoints" to value ARBbtp/vDqtIWZgeri24SYdnAxkBAQACDDE5Mi4xNjguMy43MQMC0dQEAlHOBCUCEJMRWxA+gt1uUe1LXtu5EE4DDpRHHvqCdaYgvz9JyqtnAQEABSUCEMdpVeZjF7gfZaKiMUmm5XEDDp6fmZSFQjmeMVasB234AQEA
Sat, 25 Jan 2020 11:44:27 GMT StreamController
Session: <Buffer 5b b6 9f ef 0e ab 48 59 98 1e ae 2d b8 49 87 67>
ControllerAddress: 192.168.3.71
VideoPort: 54481
AudioPort: 52817
Video Crypto: 0
Video Master Key: <Buffer 93 11 5b 10 3e 82 dd 6e 51 ed 4b 5e db b9 10 4e>
Video Master Salt: <Buffer 94 47 1e fa 82 75 a6 20 bf 3f 49 ca ab 67>
Audio Crypto: 0
Audio Master Key: <Buffer c7 69 55 e6 63 17 b8 1f 65 a2 a2 31 49 a6 e5 71>
Audio Master Salt: <Buffer 9e 9f 99 94 85 42 39 9e 31 56 ac 07 6d f8>
Sat, 25 Jan 2020 11:44:27 GMT EventedHTTPServer [::ffff:192.168.3.71] HTTP Response is finished
Sat, 25 Jan 2020 11:44:27 GMT EventedHTTPServer [::ffff:192.168.3.71] HTTP request: /characteristics?id=1.23
Sat, 25 Jan 2020 11:44:27 GMT HAPServer [51:C4:89:E4:E9:21] HAP Request: GET /characteristics?id=1.23
Sat, 25 Jan 2020 11:44:27 GMT Accessory [Backyard] Getting value for Characteristic "Setup Endpoints"
Sat, 25 Jan 2020 11:44:27 GMT StreamController Setup Read
Sat, 25 Jan 2020 11:44:27 GMT Accessory [Backyard] Got Characteristic "Setup Endpoints" value: ARBbtp/vDqtIWZgeri24SYdnAgEAAxkBAQACDDE5Mi4xNjguMy41NwMC0dQEAlHOBCUBAQACEJMRWxA+gt1uUe1LXtu5EE4DDpRHHvqCdaYgvz9JyqtnBSUBAQACEMdpVeZjF7gfZaKiMUmm5XEDDp6fmZSFQjmeMVasB234BgRJ+RQABwRUUi8A
Sat, 25 Jan 2020 11:44:27 GMT EventedHTTPServer [::ffff:192.168.3.71] HTTP Response is finished
Sat, 25 Jan 2020 11:44:27 GMT EventedHTTPServer [::ffff:192.168.3.71] HTTP request: /characteristics
Sat, 25 Jan 2020 11:44:27 GMT HAPServer [51:C4:89:E4:E9:21] HAP Request: PUT /characteristics
Sat, 25 Jan 2020 11:44:27 GMT Accessory [Backyard] Processing characteristic set: [{"aid":1,"iid":21,"value":"ARUCAQEBEFu2n+8Oq0hZmB6uLbhJh2cCNAEBAAIJAQECAgECAwEAAwsBAgAFAgLQAgMBHgQXAQFjAgTfKznMAwIrAQQEAAAAPwUCYgUDLAEBAgIMAQEBAgEAAwEBBAEeAxYBAW4CBCZcE3UDAhgABAQAAKBABgENBAEA"}]
Sat, 25 Jan 2020 11:44:27 GMT Accessory [Backyard] Setting Characteristic "Selected RTP Stream Configuration" to value ARUCAQEBEFu2n+8Oq0hZmB6uLbhJh2cCNAEBAAIJAQECAgECAwEAAwsBAgAFAgLQAgMBHgQXAQFjAgTfKznMAwIrAQQEAAAAPwUCYgUDLAEBAgIMAQEBAgEAAwEBBAEeAxYBAW4CBCZcE3UDAhgABAQAAKBABgENBAEA
Sat, 25 Jan 2020 11:44:27 GMT StreamController Write SelectedStreamConfiguration
[1/25/2020, 12:44:27 PM] [Nest-cam] waiting for socket to connect
[1/25/2020, 12:44:27 PM] [Nest-cam] [NexusStreamer] Connected
[1/25/2020, 12:44:28 PM] [Nest-cam] [NexusStreamer] OK
[1/25/2020, 12:44:28 PM] [Nest-cam] [NexusStreamer] Redirect
[1/25/2020, 12:44:28 PM] [Nest-cam] [NexusStreamer] Redirecting...
[1/25/2020, 12:44:28 PM] [Nest-cam] waiting for socket to connect
[1/25/2020, 12:44:28 PM] [Nest-cam] [NexusStreamer] Disconnected
[1/25/2020, 12:44:28 PM] [Nest-cam] [NexusStreamer] Connected
[1/25/2020, 12:44:29 PM] [Nest-cam] [NexusStreamer] OK
[1/25/2020, 12:44:29 PM] [Nest-cam] [NexusStreamer] Playback Begin
[1/25/2020, 12:44:35 PM] [Nest-cam] ERR_STREAM_DESTROYED
[1/25/2020, 12:44:35 PM] [Nest-cam] [NexusStreamer] Disconnected

Are Nest accounts still supported? Or migration to Google account would be required?

Would it be possible?

Sunoo/homebridge-camera-ffmpeg#338

_{Sent with GitHawk}

Pretty surprised that nest account support has been removed. Installing this update will break many working installations.

Google is not forcing people to migrate to google accounts. Surely a way of testing (via a small group of users wishing to remain on nest accounts) could have been found.

Describe the bug

To Reproduce
Steps to reproduce the behavior:
Fresh installation(s), manual login procedure. The doorbell function did give a notification, but the video will not stream.

Expected behavior
Live video feed from the nest hello

Include with your bug report this version info:

node --version
v12.18.1
homebridge --version
1.1.1

[6/19/2020, 7:58:24 PM] [Nest-cam] [NexusStreamer] OK
[6/19/2020, 7:58:25 PM] [Nest-cam] [NexusStreamer] Playback Begin
[6/19/2020, 7:58:31 PM] [Nest-cam] Checking for alerts on Front Door
[6/19/2020, 7:58:33 PM] [Nest-cam] RETURN AUDIO: received first frame
[6/19/2020, 7:58:38 PM] [Nest-cam] Received (unsupported) request to reconfigure to: {"width":1280,"height":720,"fps":30,"max_bit_rate":299,"rtcp_interval":0.5}
[6/19/2020, 7:58:41 PM] [Nest-cam] Checking for alerts on Front Door
[6/19/2020, 7:58:43 PM] [Nest-cam] [RETURN AUDIO] ffmpeg exited with code: 0 and signal: null (error)
[6/19/2020, 7:58:43 PM] [Nest-cam] Stopped streaming session!
[6/19/2020, 7:58:43 PM] [Nest-cam] [NexusStreamer] Playback End
[6/19/2020, 7:58:43 PM] [Nest-cam] [AUDIO] ffmpeg exited with code: null and signal: SIGKILL (AUDIO Stream stopped!)
[6/19/2020, 7:58:43 PM] [Nest-cam] [VIDEO] ffmpeg exited with code: null and signal: SIGKILL (VIDEO Stream stopped!)
[6/19/2020, 7:58:43 PM] [Nest-cam] [NexusStreamer] Disconnected
[6/19/2020, 7:58:45 PM] [Nest-cam] Updating info for Front Door
[6/19/2020, 7:58:51 PM] [Nest-cam] Checking for alerts on Front Door
[6/19/2020, 7:59:01 PM] [Nest-cam] Checking for alerts on Front Door
[6/19/2020, 7:59:11 PM] [Nest-cam] Checking for alerts on Front Door
[6/19/2020, 7:59:21 PM] [Nest-cam] Checking for alerts on Front Door
[6/19/2020, 7:59:31 PM] [Nest-cam] Checking for alerts on Front Door
[6/19/2020, 7:59:41 PM] [Nest-cam] Checking for alerts on Front Door
[6/19/2020, 7:59:45 PM] [Nest-cam] Updating info for Front Door
[6/19/2020, 7:59:51 PM] [Nest-cam] Checking for alerts on Front Door
[6/19/2020, 8:00:01 PM] [Nest-cam] Checking for alerts on Front Door
[6/19/2020, 8:00:11 PM] [Nest-cam] Checking for alerts on Front Door
[6/19/2020, 8:00:21 PM] [Nest-cam] Checking for alerts on Front Door
[6/19/2020, 8:00:31 PM] [Nest-cam] Checking for alerts on Front Door

Hey there... I've completed the initial install, including ffmpeg. It seems my token, cookies, etc parameters are correct as I can see the name of my Nest camera returning in the log below "Garage (Bikes)" however, I am unclear what the rest of the error is indicating. Suffice it to say, I am unable to see the camera in HOOBS and am unclear how to advance my troubleshooting.

5/16/2020, 3:16:02 PM [Nest-cam] Configuring accessory Garage (Bikes)
5/16/2020, 3:16:02 PM [Nest-cam] Error fetching cameras: 
5/16/2020, 3:16:02 PM [Nest-cam] TypeError: accessory.configureController is not a function
    at NestCamPlatform.configureAccessory (/home/hoobs/.hoobs/node_modules/homebridge-nest-cam2/dist/index.js:135:19)
    at response.items.forEach (/home/hoobs/.hoobs/node_modules/homebridge-nest-cam2/dist/index.js:222:26)
    at Array.forEach (<anonymous>)
    at NestCamPlatform.addCameras (/home/hoobs/.hoobs/node_modules/homebridge-nest-cam2/dist/index.js:208:28)
    at process._tickCallback (internal/process/next_tick.js:68:7)

HOOBS Core 3.2.3
Node: 10.18.0

Thanks in advance for creating this plugin and the assistance.

well i am getting only static image and then on this image starts a counting1,2,3,4,5...etc its seconds and then minutes etc.
when i open the cam on full screen i get an endless loading in the middle of that static image.
i ve checked the ffmpeg...changed path... uninstall...reinstall... dont know what i ve done wrong. really i am not an expert but i can follow instructions well and i am confused.
i m attaching some photos .

Hi there.

Is it possible to disable in the config.json the newly added button for the Nest Hello?

Thanks for your work on this.

Error keeps throwing since update to homebridge-nest-cam v2.3.2 every 10 seconds. It appears to be superficial. I am not noticing any issue other than a 1%-2% increase in CPU load.
"TypeError: Cannot read property 'filter' of undefined at NestCam.checkAlerts (/usr/local/lib/node_modules/homebridge-nest-cam/src/nestcam.ts:108:50) at processTicksAndRejections (internal/process/task_queues.js:97:5)"

Raspbian GNU/Linux Buster (10)
Node.js Version: v12.16.3
Npm Version: v6.14.4

_

[5/23/2020, 8:35:52 AM] [Nest-cam] Configuring accessory Driveway

[5/23/2020, 8:35:52 AM] [Nest-cam] Configuring accessory Patio
[5/23/2020, 8:35:52 AM] [Nest-cam] Setting Field Test to false
[5/23/2020, 8:35:52 AM] [Nest-cam] Authenticating via Google.
[5/23/2020, 8:35:57 AM] Homebridge is running on port 51434.
[5/23/2020, 8:36:02 AM] [Nest-cam] Checking for alerts on Driveway
[5/23/2020, 8:36:02 AM] [Nest-cam] Updating info for Driveway
[5/23/2020, 8:36:02 AM] [Nest-cam] Checking for alerts on Patio
[5/23/2020, 8:36:02 AM] [Nest-cam] Updating info for Patio
[5/23/2020, 8:36:03 AM] [Nest-cam] TypeError: Cannot read property 'filter' of undefined at NestCam.checkAlerts (/usr/local/lib/node_modules/homebridge-nest-cam/src/nestcam.ts:108:50) at processTicksAndRejections (internal/process/task_queues.js:97:5)
[5/23/2020, 8:36:12 AM] [Nest-cam] Checking for alerts on Driveway
[5/23/2020, 8:36:12 AM] [Nest-cam] Updating info for Front Yard
[5/23/2020, 8:36:12 AM] [Nest-cam] Checking for alerts on Patio
[5/23/2020, 8:36:12 AM] [Nest-cam] Updating info for Patio
[5/23/2020, 8:36:13 AM] [Nest-cam] TypeError: Cannot read property 'filter' of undefined at NestCam.checkAlerts (/usr/local/lib/node_modules/homebridge-nest-cam/src/nestcam.ts:108:50) at processTicksAndRejections (internal/process/task_queues.js:97:5)

_

Hey,

Thanks for all the updates (by the way I don't know how to categorize this as a feature request and not an issue so apologies if I did that incorrectly).
I saw that recently we got the ability to use motion sensing if the camera is turned on. I was wondering if down the line it'd be possible for us to change the config.json to turn off those motion sensing accessories? I already have motion sensors from different smart home platforms in many of my rooms so this one is kind of redundant.

Thanks again!

Would be great if there was a capability to send all Nest cam video files to an ftp or network drive. Or Even just video clips triggered by motion events. Is this the right project for that?

I have looked into the audio issue and have two choices:

1. I can add audio support and force everyone with ffmpeg to recompile with libfdk_aac codec.

2. I can leave audio support out for a much easier setup.

For now, I am going with #2. Audio may work if you uncomment out this line of code, but it doesn't work for everyone. If anyone can find a better way, please let me know here or submit a pull request.

Before Submitting
Please check Nest Status before submitting a bug.

Describe the bug
My Nest cam indoor and Hello are crashed and I had to delete the camera's from Apple Homekit. (I thought)
After deleting the camera's I create a new api cookie etc from nest.google
In the command line the plugin told me to (re) -add the camera's with the PIN to HomeKit, but HomeKit can't find the camera's for the second time.

what I've tried:
Uninstall the plugin but it doesn't work.
Install the plugin
Create new cookie files api from nest.com
restart HomeBridge
restart RPi

is there an easy solution for? I don't want to lose my configuration and setup.

Thanks guys! I love the plugin :)

Describe the bug
Got this error in homebridge: Error checking alerts: 403
The Nest Hello is not working anymore.

To Reproduce
Steps to reproduce the behavior:

1. Tried to reboot the Docker container, did not work

Expected behavior

Last Working Version
homebridge-nest-cam v2.3.4

Include with your bug report this version info:

node --v12.16.3
homebridge --1.1.0

Make sure you have the latest LTS from https://nodejs.org
and the latest packages: npm upgrade -g homebridge homebridge-nest-cam

Also include debug log output from startup through seeing the issue:
homebridge -D

Good evening, I have a nest account with two houses, there are 2 cameras, an indoor cam and a nest hello. I configured the plugin correctly and when I start homebridge it tells me that it created the two "office" and "door" cameras with two different ports and tells me to add them to the home app with the configuration code. The problem is that as soon as I go to add a new accessory to the home app I only find the nest hello so "door" and the other "office" camera won't find me even after hours. Before adding the nest hello the "office" camera worked in homekit then I removed everything and reaching everything I can no longer add the second one. Maybe it only supports one camera and can't add two?

any way to access QuietTime of Nest Hello with plugin? still don't understand why Google doesn't allow scheduled quiet time and that setting is kind of buried.

I have homebridge running through my personal DNS server and have noticed a major uptick in DNS requests since I setup homebridge-nest-cam. I am seeing ~100k requests/day going to (each).

nexusapi-us1.camera.home.nest.com
webapi.camera.home.nest.com

That by farm exceeds any other requests I have at home by a factor of 10. Though it's not really hurting anything, I know for a lot of users depending on their ISP, DNS requests like that could cause them to get blocked for short times as it could be considered an attack (Plus it's just pure inefficient)

I current run 4 Cams (1 IQ Outdoor, 1 Outdoor, 1 Indoor and a Hello Cam)

Include with your bug report this version info:

node --version
v12.16.3
homebridge --version
1.1.0
homebridge-nest-cam v2.3.3

docker --version
Docker version 19.03.9, build 9d988398e7

Before Submitting
Please check Nest Status before submitting a bug.

Describe the bug

To Reproduce
Steps to reproduce the behavior:
1.

Expected behavior

Include with your bug report this version info:

node --version
homebridge --version

Make sure you have the latest LTS from https://nodejs.org
and the latest packages: npm upgrade -g homebridge homebridge-nest-cam2

Also include debug log output from startup through seeing the issue:
homebridge -D

Can we have an option to allow video capture at 5 fps (or lower) to reduce CPU consumption in Raspberry PI's ?

Describe the bug
V1.1.9 bundles ffmpeg-for-homebridge. After upgrading, the performance of the stream got worse and was very laggy using the COPY codec.

To Reproduce
Install v1.1.9 and view camera

Expected behavior
Better performance than previous releases that didn’t bundle ffmpeg-for-homebridge

Node v10.18.0
HOOBS v3.1.22
Manually compiled ffmpeg

ffmpeg version N-96534-gde1b2aa796 Copyright (c) 2000-2020 the FFmpeg developers
built with gcc 8 (Raspbian 8.3.0-6+rpi1)
configuration: --prefix=/usr/local --arch=armel --target-os=linux --enable-omx-rpi --enable-nonfree --enable-gpl --enable-libfdk-aac --enable-mmal --enable-libx264 --enable-decoder=h264 --enable-network --enable-protocol=tcp --enable-demuxer=rtsp
libavutil      56. 38.100 / 56. 38.100
libavcodec     58. 67.100 / 58. 67.100
libavformat    58. 36.100 / 58. 36.100
libavdevice    58.  9.103 / 58.  9.103
libavfilter     7. 71.100 /  7. 71.100
libswscale      5.  6.100 /  5.  6.100
libswresample   3.  6.100 /  3.  6.100
libpostproc    55.  6.100 / 55.  6.100

ffmpeg version in ffmpeg-for-homebridge

ffmpeg version 4.2.git-47773f7 Copyright (c) 2000-2020 the FFmpeg developers
built with gcc 6.3.0 (Raspbian 6.3.0-18+rpi1+deb9u1) 20170516
configuration: --pkgconfigdir=/build/workspace/lib/pkgconfig --prefix=/build/workspace --pkg-config-flags=--static --extra-cflags=-I/build/workspace/include --extra-ldflags=-L/build/workspace/lib --extra-libs='-lpthread -lm' --enable-static --disable-debug --disable-shared --disable-ffplay --disable-doc --enable-openssl --enable-gpl --enable-version3 --enable-nonfree --enable-pthreads --enable-libvpx --enable-libmp3lame --enable-libopus --enable-libtheora --enable-libvorbis --enable-libx264 --enable-runtime-cpudetect --enable-libfdk-aac --enable-avfilter --enable-libopencore_amrwb --enable-libopencore_amrnb --enable-filters --enable-decoder=h264 --enable-network --enable-protocol=tcp --enable-demuxer=rtsp --enable-omx-rpi --enable-mmal
libavutil      56. 40.100 / 56. 40.100
libavcodec     58. 68.102 / 58. 68.102
libavformat    58. 38.100 / 58. 38.100
libavdevice    58.  9.103 / 58.  9.103
libavfilter     7. 75.100 /  7. 75.100
libswscale      5.  6.100 /  5.  6.100
libswresample   3.  6.100 /  3.  6.100
libpostproc    55.  6.100 / 55.  6.100

The invite link for the Discord channel in the README is expired.

Are there plans to add doorbell support? Motion sensors are not enough. I would love a ring sensor/ and notifications.

The new api supports it, would this be possible?

After no changes to my config, i am now receiving the following errors in the Homebridge log file:

[6/12/2020, 12:52:02 PM] [Nest-cam] Error fetching cameras:
[6/12/2020, 12:52:02 PM] [Nest-cam] TypeError: Cannot read property 'includes' of undefined
at NestCamPlatform.configureAccessory (/usr/local/lib/node_modules/homebridge-nest-cam/src/index.ts:182:35)
at /usr/local/lib/node_modules/homebridge-nest-cam/src/index.ts:273:16
at Array.forEach ()
at NestCamPlatform.addCameras (/usr/local/lib/node_modules/homebridge-nest-cam/src/index.ts:254:15)
at processTicksAndRejections (internal/process/task_queues.js:97:5)
at NestCamPlatform.didFinishLaunching (/usr/local/lib/node_modules/homebridge-nest-cam/src/index.ts:335:7)

Please help

Steps to reproduce the behavior:

1. Restart Homebridge
2. View log file

Include with your bug report this version info:

node --12.18.0
homebridge --1.1.0

The optional settings are no longer reflected properly in HomeKit. I have the following in my config.json

            "motionDetection": true,
            "streamingSwitch": false,
            "doorbellAlerts": true,
            "doorbellSwitch": false,
            "disableAudio": false

However, the doorbell switch is still showing along with the streaming switch.

This has been happing for the last few versions released. If I enable the streaming switch the config.json changes to true but the accessory remains.

Thanks!

I was able to add the accessories last night but after they were added, in Homekit they showed as No Response on the screen display. I then deleted the application from Homebridge and tired to add them again... Sadly they aren't showing up as discoverable under Near by accessories. How do I see them again on near by accessories? How do I show images? (i am using a raspberry pi and installed Camera FFMPEG Omx but still didnt see a change when I added h264_omx

Hi, I'm fan of your plugin. But the streaming on my RPi with plugin installed inside my docker is not working well. It starts to stream the video but stalls after a short amount of time. I'd like to know if there is a possibility to use hardware transcoding within a docker?

I'm unable to add my cameras to my Homekit as I get "Accessory already added" when I scan the QR code.

Homebridge v 1.0.3
Node.js v 12.16.2
Npm v 6.14.4

When I restart Homebridge, this is what I see in the logs:

[4/29/2020, 8:27:20 AM] [Nest-cam] Create camera - Camera 1
[4/29/2020, 8:27:20 AM] [Nest-cam] Create camera - Camera 2
[4/29/2020, 8:27:20 AM] One of your plugins incorrectly registered an external accessory using the platform name (Nest-cam) and not the plugin identifier. Please report this to the developer!
[4/29/2020, 8:27:20 AM] Camera 1 is running on port xxxxx.
[4/29/2020, 8:27:20 AM] Please add [Camera 1] manually in Home app. Setup Code: xxx-xx-xxx
[4/29/2020, 8:27:20 AM] Camera 2 is running on port xxxxx.
[4/29/2020, 8:27:20 AM] Please add [Camera 2] manually in Home app. Setup Code: xxx-xx-xxx

With the Ring doorbell plugin I am able to have a two way conversation with the person at the Ring doorbell camera via the camera via in my native Home app on iPhone / iPad since I am using the HOOBS Certified “Ring” 8.2.0 plugin for HOOBS (homebridge ouT of the box).

However with the “Nest Cam” plugin 2.3.4 for HOOBS, while I can see and hear the live video feed, the Talk feature seems to be disabled since the mic icon is missing. Therefore I need to open the Nest app which defeats the purpose of the HOOBS integration (which works well in the Ring side, why not on the nest plugin?).

Will this functionality be added in the near future?

Any help is appreciated.

When I go to add my cameras to Home, they do not appear. They have successfully been discovered and created in my log, but don't show up beyond that. I do get a warning, but I don't know if it's related or not.
(node:14112) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
I have added another camera accessory from a different plugin to the config to make sure cameras were being exposed at all, and it works fine. I am running on Windows.

Describe the bug
Problem configuring homekit automations based on camera motion detected or motion stops detecting events.
The events are not lasting long enough. I would expect the triggered state to remain unchanged during the cool down period. or at least be longer than the check interval.
If current behavior is by design, is it possible to include the alert length in the configuration where it could be user defined.

To Reproduce
Steps to reproduce the behavior:

1. Constant behavior that motion state will revert to false 5 sec after event

Expected behavior
Triggered motion events remain true during cool down period

Last Working Version
2.1.0
Was working prior to number of alert fixes for motion. or the addition of the fixed Alert_length
Include with your bug report this version info:

node --12.18.0
homebridge --1.1.0

Make sure you have the latest LTS from https://nodejs.org
and the latest packages: npm upgrade -g homebridge homebridge-nest-cam

seems like it may be tied to this section of code
triggerMotion(accessory: PlatformAccessory): void {
const self = this; // eslint-disable-line @typescript-eslint/no-this-alias
this.setMotion(accessory, true);
this.motionDetected = true;
setTimeout(async function () {
self.setMotion(accessory, false);
}, ALERT_LENGTH);

setTimeout(async function () {
  self.motionDetected = false;
}, this.alertCooldown);

}

Hi,

In the recent update v2.2.0, a new button is added if the user has a Nest Hello doorbell. It's unconfigured by default, we can add actions to that button.

But the problem is that I don't know what I can do with that button, and I can't hide it if I don't need it.

I tried to use it for turning on/off the video streaming, but it doesn't work well (and I have to use Nest app to reset the streaming).

So could you add an option to hide that button? I've disabled most of the features except audio, but the button is still there.

Thanks!

After installing v2.0, my previously working setup stopped working and I got this error:

5/11/2020, 4:40:27 PM [Nest-cam] Configuring accessory Living Room
5/11/2020, 4:40:27 PM [Nest-cam] Error fetching cameras: 
5/11/2020, 4:40:27 PM [Nest-cam] TypeError: accessory.configureController is not a function
    at NestCamPlatform.configureAccessory (/home/hoobs/.hoobs/node_modules/homebridge-nest-cam2/dist/index.js:135:19)
    at response.items.forEach (/home/hoobs/.hoobs/node_modules/homebridge-nest-cam2/dist/index.js:222:26)
    at Array.forEach (<anonymous>)
    at NestCamPlatform.addCameras (/home/hoobs/.hoobs/node_modules/homebridge-nest-cam2/dist/index.js:208:28)
    at process._tickCallback (internal/process/next_tick.js:68:7)

I uninstalled and reinstalled the plugin without success.

I’m currently running HOOBS 3.2.3 on a Raspberry Pi 3 Model B.

Describe the bug

Homebridge log reports the following error every 10 seconds:

Error checking alerts: 403

To Reproduce
Steps to reproduce the behavior:

1. Install homebridge-nest-cam v.3.0.1 and configure it

Expected behavior

No errors.

After upgrading to the lastest release when I try to select a individual camera in Apple Home I get a error message that there was “No response” this camera is not responding and Homebridge restarts.