-
-
Notifications
You must be signed in to change notification settings - Fork 27
NEST plug in not working fully in Homekit Home.app #279
Comments
I have added those error codes to the Error Codes Wiki. Essentially they mean that the device running homebridge is unable to connect to Nest, not because of Nest but because of the device itself. Usually, this occurs when someone is running Pihole or some other type of antivirus/spam tool. |
I have all Mac... no virus protection at all..
Jonathan Broskey
[email protected]
… On Sep 29, 2020, at 5:18 AM, Brandon McFarlin ***@***.***> wrote:
I have added those error codes to the Error Codes Wiki <https://github.com/Brandawg93/homebridge-nest-cam/wiki/Error-Codes>. Essentially they mean that the device running homebridge is unable to connect to Nest, not because of Nest but because of the device itself. Usually, this occurs when someone is running Pihole or some other type of antivirus/spam tool.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#279 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALE2VKCYE62ZGR2IRGCYKUDSIHGA5ANCNFSM4R5F2DNA>.
|
I'm not sure what other help I can provide from a plugin standpoint. Something internally is not allowing your homebridge service to connect to the Nest website. Not sure where you are located, but for me I'm in the US so the url homebridge is looking for is |
% ping nexusapi-us1.camera.home.nest.com Looks to work. hmmm |
I tried using the terminal script this time instead of manually scrubbing the chrome developer menu.. I got it to work as far as seeing the widget in Home.app refresh.. but again once I clicked on the preview I got the not responding. |
ECONNREFUSED means that something on your local network refused the connection to Nest. Usually, it's the router's firewall. |
I edited my last comment. I hit return too fast. |
[9/29/2020, 3:19:06 PM] [Nest-cam] [NexusStreamer] Connected seems ok, no error on the homebridge side... just the home.app opening up the widget |
The cameras could be cached in Homebridge. That's why you're still seeing them. |
I saw your edit. Try running homebridge in debug mode (homebridge -D) and see if anything stands out. |
How would I do that if I am running the UI version? |
found it NVM |
[9/29/2020, 3:27:25 PM] [Nest-cam] Updating info for Dining Room Streaming [9/29/2020, 3:27:32 PM] [Nest-cam] AUDIO: ffmpeg version 4.3.1 Copyright (c) 2000-2020 the FFmpeg developers [9/29/2020, 3:27:33 PM] [Nest-cam] [NexusStreamer] Connected [9/29/2020, 3:27:36 PM] [Nest-cam] VIDEO: Stream mapping: [9/29/2020, 3:27:36 PM] [Nest-cam] VIDEO: [swscaler @ 0x7fef98008000] deprecated pixel format used, make sure you did set range correctly [9/29/2020, 3:27:36 PM] [Nest-cam] VIDEO: [libx264 @ 0x7fefd2809400] using SAR=1/1 [9/29/2020, 3:27:36 PM] [Nest-cam] VIDEO: [libx264 @ 0x7fefd2809400] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX FMA3 BMI2 AVX2 [9/29/2020, 3:27:36 PM] [Nest-cam] VIDEO: [libx264 @ 0x7fefd2809400] profile Constrained Baseline, level 3.1, 4:2:0, 8-bit [9/29/2020, 3:27:36 PM] [Nest-cam] VIDEO: Stream #0:0: Video: h264 (libx264), yuv420p, 1280x720 [SAR 1:1 DAR 16:9], q=-1--1, 30 fps, 90k tbn, 30 tbc [9/29/2020, 3:27:36 PM] [Nest-cam] VIDEO: frame= 26 fps=0.0 q=17.0 size= 380kB time=00:00:00.83 bitrate=3740.4kbits/s dup=1 drop=0 speed=1.36x [9/29/2020, 3:27:39 PM] [Nest-cam] AUDIO: Stream #0:0: Audio: aac, 8000 Hz, mono, s16, 48 kb/s [9/29/2020, 3:27:39 PM] [Nest-cam] VIDEO: frame= 71 fps= 20 q=17.0 size= 957kB time=00:00:02.33 bitrate=3360.2kbits/s dup=1 drop=0 speed=0.665x [9/29/2020, 3:27:39 PM] [Nest-cam] AUDIO: Output #0, rtp, to 'srtp://10.0.4.104:61514?rtcpport=61514&localrtcpport=51847&pkt_size=188': [9/29/2020, 3:27:40 PM] [Nest-cam] VIDEO: frame= 80 fps= 19 q=17.0 size= 1048kB time=00:00:02.63 bitrate=3260.0kbits/s dup=1 drop=0 speed=0.641x [9/29/2020, 3:27:48 PM] [Nest-cam] RETURN AUDIO: Stream #0:0: Audio: aac, 16000 Hz, mono, s16 [9/29/2020, 3:27:48 PM] [Nest-cam] RETURN AUDIO: Stream mapping: [9/29/2020, 3:27:49 PM] [Nest-cam] AUDIO: size= 51kB time=00:00:14.79 bitrate= 28.2kbits/s speed=1.61x [9/29/2020, 3:28:02 PM] [Nest-cam] VIDEO: [libx264 @ 0x7fefd2809400] frame I:2 Avg QP:17.00 size:141316 [9/29/2020, 3:28:02 PM] [Nest-cam] VIDEO: Exiting normally, received signal 15. [9/29/2020, 3:28:02 PM] [Nest-cam] Stopped streaming session! |
could it be the "ffmpeg" ? |
I wouldn't think so. That debug output looks good to me. Seems like the ENOTFOUND and ETIMEOUT errors are gone. Just no streaming? |
correct no stream :-( |
What version of homebridge are you using? I've heard that the latest version (v1.2.3) has some issues with streaming and that reverting to v1.1.6 fixes them. |
Node.js version - v14.12.0 Version 1.2.3 |
The homebridge team has reverted the latest version of homebridge from 1.2.3 back to 1.1.6. Reverting should fix this issue until the homebridge team releases an official fix. |
I reverted to 1.1.6 and it did not solve the issue.
Jonathan Broskey
[email protected]
… On Oct 7, 2020, at 10:37 AM, Brandon McFarlin ***@***.***> wrote:
The homebridge team has reverted the latest version of homebridge from 1.2.3 back to 1.1.6. Reverting should fix this issue until the homebridge team releases an official fix.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#279 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALE2VKDMTA6BTH64MNZ2JGTSJSRN3ANCNFSM4R5F2DNA>.
|
I have the same issue. The strange thing is that if I open the Home app and just leave it open with 'Favorite cameras' view, the thumbnails do update every 10-11 seconds. But if I tap to stream, there's the loading circle and then it times out with camera not responding. I tried reverting to 1.1.6 and also the latest beta 1.3.0 beta 14 - none of these fixed this. I checked debug log and there's no errors. Is this definitely a homebridge issue and not with the plugin? I checked their git and don't see any relevant issues, unless I'm missing it ? Nevermind found the relevant issue: homebridge/homebridge#2681 |
I'm fairly certain it's a homebridge issue as most all the other camera plugins have the same issue. It doesn't affect everyone, just a small subset of users. The homebridge team is aware of the issue, though. |
Hello Brandawg93, I just want to add this error into here as well. And the only way to fix this is to reboot the Homebridge server. I am running the Homebridge server as docker on Qnap NAS though, Homebridge version v1.2.3; FFmpeg version v4.3.1 built-in (I did not install any other FFmpeg so it should be built-in with Homebridge-Nest plugin). [Nest] API observe: error Error [ERR_HTTP2_STREAM_ERROR]: Stream closed with error code NGHTTP2_INTERNAL_ERROR |
Just wanted to add that I’m seeing the same issue. Only on one out of 7 cams, though! Super strange. I’ll keep an eye on the thread and the homebridge issue. Thanks for the awesome plugin! I use this many times a day to get a PIP of my toddler’s room. Super nice. |
Wanted to add an update - I was having the same issue, but finally saw things fixed this last time I ran Things I was doing, in case this helps anyone:
Hopefully someone's having the same issue and tweaking firewall settings helps solve things as it did for me! |
Homebridge v1.2.4 was just released. If the release fixes this issue, please let me know here. |
I just update to v1.2.4 and still having the same issue. Running over Docker Container (amd64): OS | Alpine Linux (3.12.1) Pings works fine: Logs showing the same behavior [12/6/2020, 9:15:31 AM] [Nest-cam] [NexusStreamer] Connected Thumbnails works fine |
Anyone know if this is fixed in v1.1.7? |
Mine started having this same NexusStreamer issue 5 days ago. Reset the Nest token and cookie, and updated homebridge to 1.2.5, downgraded to 1.1.6, but still nothing fixed it. Meant to mention for @Brandawg93, I was having the issue initially in 1.1.7. Cycled back to 1.1.7 after my journey forwards and backwards, and still having the same issue. |
@bobster16, there may be a potential fix by @Supereg implemented into the latest beta of Homebridge (v1.3.0) could you try that and let me know if it fixes your issue? |
@Brandawg93 Updated to 1.3.0-beta.41. Got the same issues but had a little more info. Pasting the log below. I will gladly switch to debug mode and send that novel over if it will help. 04/01/2021, 15:47:16] [Nest-cam] [NexusStreamer] Connected |
...and now it's working this morning. The logs say it is still slow to respond, but I'm getting a live feed. “¯_(ツ)_/¯“ |
@bobster16 Thanks for the heads up. My guess is that you unintentionally downloaded beta 40. NPM likes to cache releases so if you do something like |
@Brandawg93 I had selected .41 in the UI and the log shows my call for .41 instead of just calling the latest generic beta. I reviewed the logs from overnight and it looks like a few ETIMEDOUTs from the Nest-Cam plugin. Not sure if a reconnect made it happy again. There were also a few ECONNRESETs from the Nest plugin. Slightly unrelated, but happened around some of the timeouts. |
Ok. Those are usually due to rate limiting on Nest's side. Glad to hear it's working for you! If anything changes, just let me know, and I'll take a look |
Same issue here. However installing .42 did not resolve it. I did some debugging to try to discover what is happening. Hopefully it can help resolve the problem.
see tcpdump when requesting stream while not on local network root@jetstream:~# tcpdump -i eth0 -n | grep unrea |
Has this been resolved yet? How do I turn on more comprehensive debugging for the Nest Cams plugin? I see no errors in the regular logs but no cameras are being listed at all in the Home Bridge logs. I see the cams listed in the Accessories list but nothing is appearing in HomeKit. The Settings is correct because it listed my username correctly. |
This has not been resolved because it is not a plugin issue. It sounds like you may need to delete your accessory cache. If that doesn't work, I'd recommend redoing your homebridge setup. |
Just wondered if this is similar in any way. However my cameras do work but not all the time. Sometimes they connect and work other times I get a no responding error. |
Clearing accessory cache for the camera only seemed to resolve my issue. Was getting the conversion error in logs and not responding in home app. Using HB UI 4.37.0 and nest-cam 7.1.0, nest hello. |
For anyone still having issues with this, I was able to fix my setup by going to |
Even after selecting the correct network interface, I am still seeing SRTP output to an address that is NOT part of my network. It is not getting the correct interface for the stream so that I can access it. |
Ok. The plugin uses the IP address supplied by Homebridge/HomeKit. If everything is up-to-date, then there is nothing I can do from a plugin standpoint to force it to stream to the correct IP address. |
Absolutely get that. Do you know the area of the Homebridge that is determining the IP? Would love to track that down and for now hardcode it and provide feedback to that team. As always, your support is fabulous, even when it is not the fault of your plugin. |
To offer a little more clarity, the original issue for this thread was due to the new Ciao library (introduced in homebridge v1.3.0) not broadcasting mDNS properly. Forcing it in the settings allows the user to control the IP address broadcasted by mDNS. Your situation is a little different. When you attempt to stream from a device, that device sends its IP address via HomeKit to Homebridge where I pick it up and tell the plugin to stream to it. That IP address will change each time you use a different device to stream and is supplied by HomeKit. I don't think there is much the Homebridge team will be able to do to help, but maybe they could offer a little more insight. |
The clarity helped. It appears that my issue is that Homekit is picking up the IP address of my IOS VPN and not the internal IP for the WiFi and sending that to Homebridge for RTP. If I disconnect from the VPN it works. Even though all other local connections work just fine, this specific video stream seems to now work. Thanks for the clarity!! I can stop pulling out what hair I had left. |
If anyone still has this issue after updating Homebridge to v1.3.1 and forcing the correct IP in settings, feel free to submit a new issue. |
Before Submitting an Issue
https://github.com/Brandawg93/homebridge-nest-cam/wiki/Troubleshooting
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
Describe the bug
I had to configure it using the chrome trick by grabbing the token and the cookie. So I see things in Home.app but when I click on the Nest widget it just spins and never fully shows the video live or Audio. I'm not sure what to do. I did have an error at 1 point "ENOTFOUND" but no clue why I got that. see below...it also seems to be slowing down my network.
[9/28/2020, 6:16:03 PM] [Nest-cam] Error checking alerts: ETIMEDOUT
Troubleshoot here: https://github.com/Brandawg93/homebridge-nest-cam/wiki/Error-Codes
[9/28/2020, 6:16:13 PM] [Nest-cam] Error checking alerts: ETIMEDOUT
Troubleshoot here: https://github.com/Brandawg93/homebridge-nest-cam/wiki/Error-Codes
[9/28/2020, 6:16:23 PM] [Nest-cam] Error checking alerts: ETIMEDOUT
Troubleshoot here: https://github.com/Brandawg93/homebridge-nest-cam/wiki/Error-Codes
[9/28/2020, 6:16:34 PM] [Nest-cam] Error checking alerts: ETIMEDOUT
Troubleshoot here: https://github.com/Brandawg93/homebridge-nest-cam/wiki/Error-Codes
[9/28/2020, 6:16:44 PM] [Nest-cam] Error checking alerts: ETIMEDOUT
Troubleshoot here: https://github.com/Brandawg93/homebridge-nest-cam/wiki/Error-Codes
[9/28/2020, 6:16:49 PM] [Nest-cam] Error checking alerts: ENOTFOUND
Troubleshoot here: https://github.com/Brandawg93/homebridge-nest-cam/wiki/Error-Codes
[9/28/2020, 6:16:59 PM] [Nest-cam] Error checking alerts: ETIMEDOUT
Troubleshoot here: https://github.com/Brandawg93/homebridge-nest-cam/wiki/Error-Codes
[9/28/2020, 6:17:09 PM] [Nest-cam] Error checking alerts: ETIMEDOUT
Troubleshoot here: https://github.com/Brandawg93/homebridge-nest-cam/wiki/Error-Codes
[9/28/2020, 6:17:19 PM] [Nest-cam] Error checking alerts: ETIMEDOUT
Troubleshoot here: https://github.com/Brandawg93/homebridge-nest-cam/wiki/Error-Codes
[9/28/2020, 6:19:31 PM] [Nest-cam] [NexusStreamer] Connected
[9/28/2020, 6:21:27 PM] [Nest-cam] [NexusStreamer] Connected
[9/28/2020, 6:21:37 PM] [Nest-cam] [NexusStreamer] Disconnected
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I except that when I click on the camera I see live video and audio
Please answer these questions before submitting this issue:
The text was updated successfully, but these errors were encountered: