Homebridge-Nest failed today after working for quite some time. #107

davidtennant8082 · 2017-01-07T04:18:32Z

I've had home bridge up and running for well over a year now with limited issues. Haven't done much in the way of updating. I tried to reinstall assuming there could be an update since I last did it and the error remains. Checked with the nest developer site and checked the authorization token and set that back up incase that was causing an issue and have checked permissions there. Everything seems fine...

Here is what it is failing with currently...
XserveServer:~ Tennant$ homebridge
[1/6/2017, 11:07:38 PM] Loaded plugin: homebridge-nest
[1/6/2017, 11:07:38 PM] Registering platform 'homebridge-nest.Nest'
[1/6/2017, 11:07:38 PM] ---
[1/6/2017, 11:07:38 PM] Loaded config.json with 0 accessories and 1 platforms.
[1/6/2017, 11:07:38 PM] ---
[1/6/2017, 11:07:38 PM] Loading 1 platforms...
[1/6/2017, 11:07:38 PM] Initializing Nest platform...
[1/6/2017, 11:07:38 PM] Fetching Nest devices.
/usr/local/lib/node_modules/homebridge-nest/node_modules/firebase/node_modules/faye-websocket/node_modules/websocket-driver/node_modules/websocket-extensions/lib/websocket_extensions.js:133
this._pipeline.processIncomingMessage(message, callback, context);
^

TypeError: Cannot read property 'processIncomingMessage' of undefined
at instance.processIncomingMessage (/usr/local/lib/node_modules/homebridge-nest/node_modules/firebase/node_modules/faye-websocket/node_modules/websocket-driver/node_modules/websocket-extensions/lib/websocket_extensions.js:133:19)
at instance._emitMessage (/usr/local/lib/node_modules/homebridge-nest/node_modules/firebase/node_modules/faye-websocket/node_modules/websocket-driver/lib/websocket/driver/hybi.js:442:22)
at instance._emitFrame (/usr/local/lib/node_modules/homebridge-nest/node_modules/firebase/node_modules/faye-websocket/node_modules/websocket-driver/lib/websocket/driver/hybi.js:405:19)
at instance.parse (/usr/local/lib/node_modules/homebridge-nest/node_modules/firebase/node_modules/faye-websocket/node_modules/websocket-driver/lib/websocket/driver/hybi.js:144:18)
at instance.parse (/usr/local/lib/node_modules/homebridge-nest/node_modules/firebase/node_modules/faye-websocket/node_modules/websocket-driver/lib/websocket/driver/client.js:56:58)
at IO.write (/usr/local/lib/node_modules/homebridge-nest/node_modules/firebase/node_modules/faye-websocket/node_modules/websocket-driver/lib/websocket/streams.js:80:16)
at TLSSocket.ondata (_stream_readable.js:528:20)
at emitOne (events.js:77:13)
at TLSSocket.emit (events.js:169:7)
at readableAddChunk (_stream_readable.js:146:16)
at TLSSocket.Readable.push (_stream_readable.js:110:10)
at TLSWrap.onread (net.js:523:20)

tobeychris · 2017-01-07T07:04:31Z

I am seeing the same thing:

root@HomeBridge3:~ # homebridge
*** WARNING *** The program 'node' uses the Apple Bonjour compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see <http://0pointer.de/avahi-compat?s=libdns_sd&e=node>
*** WARNING *** The program 'node' called 'DNSServiceRegister()' which is not supported (or only supported partially) in the Apple Bonjour compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see <http://0pointer.de/avahi-compat?s=libdns_sd&e=node&f=DNSServiceRegister>
[1/7/2017, 1:59:49 AM] Loaded plugin: homebridge-nest
[1/7/2017, 1:59:49 AM] Registering platform 'homebridge-nest.Nest'
[1/7/2017, 1:59:49 AM] ---
[1/7/2017, 1:59:49 AM] Loaded config.json with 0 accessories and 1 platforms.
[1/7/2017, 1:59:49 AM] ---
[1/7/2017, 1:59:49 AM] Loading 1 platforms...
[1/7/2017, 1:59:49 AM] Initializing Nest platform...
[1/7/2017, 1:59:49 AM] Fetching Nest devices.
/usr/local/lib/node_modules/homebridge-nest/node_modules/firebase/node_modules/faye-websocket/node_modules/websocket-driver/node_modules/websocket-extensions/lib/websocket_extensions.js:133
    this._pipeline.processIncomingMessage(message, callback, context);
                  ^

TypeError: Cannot read property 'processIncomingMessage' of undefined
    at Extensions.processIncomingMessage (/usr/local/lib/node_modules/homebridge-nest/node_modules/firebase/node_modules/faye-websocket/node_modules/websocket-driver/node_modules/websocket-extensions/lib/websocket_extensions.js:133:19)
    at Client._emitMessage (/usr/local/lib/node_modules/homebridge-nest/node_modules/firebase/node_modules/faye-websocket/node_modules/websocket-driver/lib/websocket/driver/hybi.js:442:22)
    at Client._emitFrame (/usr/local/lib/node_modules/homebridge-nest/node_modules/firebase/node_modules/faye-websocket/node_modules/websocket-driver/lib/websocket/driver/hybi.js:405:19)
    at Client.parse (/usr/local/lib/node_modules/homebridge-nest/node_modules/firebase/node_modules/faye-websocket/node_modules/websocket-driver/lib/websocket/driver/hybi.js:144:18)
    at Client.parse (/usr/local/lib/node_modules/homebridge-nest/node_modules/firebase/node_modules/faye-websocket/node_modules/websocket-driver/lib/websocket/driver/client.js:56:58)
    at IO.write (/usr/local/lib/node_modules/homebridge-nest/node_modules/firebase/node_modules/faye-websocket/node_modules/websocket-driver/lib/websocket/streams.js:80:16)
    at TLSSocket.ondata (_stream_readable.js:555:20)
    at emitOne (events.js:96:13)
    at TLSSocket.emit (events.js:188:7)
    at readableAddChunk (_stream_readable.js:176:18)
    at TLSSocket.Readable.push (_stream_readable.js:134:10)
    at TLSWrap.onread (net.js:551:20)

tobeychris · 2017-01-07T07:07:28Z

I have tried a fresh install of everything, redoing the token process, even making a new product in the Nest API.
If I remove the token then homebridge will fall-back to the legacy API (assuming credentials are there), but then you lose cameras and possibly other functionality,

emilkwaaitaal · 2017-01-07T09:02:38Z

Same here. Not working since today. Same error message as the others...

davidtennant8082 · 2017-01-07T12:37:00Z

Looks like it occurred for some people under issue 106 which was closed as if just started working on its own.
#106

The thought was an issue on Nests end.

tobeychris · 2017-01-07T16:32:40Z

I agree. Definitely something on Nest's end. I guess the question is if this is temporary like #106 or a permanent change in their APIv2.

davidtennant8082 · 2017-01-07T16:37:09Z

I had also tried a complete reinstall before posting. Have it back up and running using the legacy API for the time being.

digitalkyle · 2017-01-07T19:50:45Z

only the legacy api seems to be working for me as well. not sure if nest servers or whats up.

Muzach · 2017-01-08T07:12:16Z

Same issue here. If Nest's v2 API has some intermittent failures it would be nice to have this js defensive so it doesn't crash homebridge...

PencilDH · 2017-01-08T11:38:20Z

Hello I will just add that I am having the same issue, does anyone understand why this is happening? As we all have Dev accounts we could start logging this issue with nest if this is defiantly their problem?

I also second the option to make the script more robust so it doesn't crash the home bridge server... Yesterday I didn't know how to turn off the light at home, I had to go and turn them off using the wall switches, imagine?! 👎

pedroserano · 2017-01-08T17:28:05Z

+1

rtoohil · 2017-01-08T18:00:57Z

Interestingly, I can make curl calls and get responses back just fine. I haven't dug into the code enough to understand the difference between the standard read API calls and the calls that the plugin is making, but the API itself seems fine (using the same token that I generated initially during the plugin setup).

One thing I noticed -- the error coming from faye-websocket-node is similar to this issue: faye/faye-websocket-node#38

The firebase that is used by homebridge-nest is v2.3.2, which includes a version of faye-websocket from before that fix. I made that (one-line) fix by hand (rather than upgrading both firebase and faye-websocket), and homebridge started up fine and is working.

So, my guess is that a change has happened on the Nest end with how they handle closing out websocket clients. The older version of faye-websocket doesn't handle this well, returns that error, and that error isn't caught anywhere.

If I get some time later today, I'll put together a quick pull request that updates firebase to a more recent version (which will pull in a more recent version of faye-websocket), but that will require a bit of testing to make sure that the firebase methods haven't changed much between versions.

In the meantime, if you make that one line change, it should get everything back up and running (at least it has for me, at least for the last hour)

digitalkyle · 2017-01-08T18:53:26Z

Thank Ryan, it got ride of the error but now it won't go past the fetching nest devices. I believe the websocket is the root cause of this error

conradhagemans · 2017-01-09T09:45:03Z

For now I removed the Nest platform in config.json of Homebridge. Homebridge runs again fine.
Hopefully there will be an update of the NPM Nest module.

PencilDH · 2017-01-09T11:07:29Z

@conradhagemans You can just make it fall back to legacy API by removing the token and it will work as usual no need to remove the whole device!

smolyneux · 2017-01-10T20:45:36Z

I found upgrading the version of websocket-driver used (similar to @rtoohil ’s suggestion) from 0.5.2 to 0.5.3 solved the issue for me. Running the below commands:

cd /usr/local/lib/node_modules/homebridge-nest/node_modules/firebase/node_modules/faye-websocket/node_modules/

sudo rm -rf websocket-driver

cd ../

sudo npm install [email protected] --save

And restarting Homebridge should allow you to continue using the newer API via a token.

emilkwaaitaal · 2017-01-10T21:54:53Z

Works indeed again with upgrade of websocket-driver. Thank you Smolyneux!

davidtennant8082 · 2017-01-10T22:14:44Z

Upgrading as per smolyneux worked as well.

I had to edit the config file as to get it to run on the legacy API, I had to remove all but the user name and password, but had just save multiple copies so that was just cut an paste the file in place and load it.

Marked as closed with the solution of updating the websocket-driver!

simonrb2000 · 2017-01-10T22:45:40Z

Sorry to open this up again but is this working now with the new API after updating the web socket as instructed above? I'm using the legacy API at the moment.

davidtennant8082 · 2017-01-10T22:46:52Z

It's working with the new API for me as of right now.

simonrb2000 · 2017-01-10T23:15:25Z

Excellent - thank you. I might update. Out of curiosity what's the difference between the old and new api within HomeKit? Using the Legacy one now for a couple of days and not seen any difference. I know the old API isn't being developed anymore but neither is the new one by looks of it.

Cheers

Muzach · 2017-01-11T01:33:36Z

Thanks @smolyneux! This worked for me too.

simonrb2000 · 2017-01-12T13:07:20Z

I have done above steps and it worked for a couple of minutes and its not working.. Please advise if its still working your end..

Cheers

Update:- I run this via forever and I think it times out and tries to restart the script as it takes a while to grab the nest info and finish loading homebridge. I won't use forever lol

davidtennant8082 · 2017-01-13T01:11:17Z

Still working perfectly post updating websocket-driver.

In the troubleshooting steps originally of nuking and reinstalling everything I now have my two nest protects working with HomeKit too as I was running such an old version of the nest plugin that it only worked with the thermostat prior to the failure.

rtoohil · 2017-01-14T11:55:43Z

#109

Pull request with working shrinkwrap.

lnlyssg · 2017-01-14T21:27:48Z

I tried the websocket-driver fix but now have the same problem as @digitalkyle - homebridge won't start up as it seems to get stuck at the fetching stage. FWIW my websocket-driver module is under /usr/lib/node_modules/homebridge-nest/node_modules/firebase/node_modules/faye-websocket/node_modules/ on Ubuntu if that makes any difference....

simonrb2000 · 2017-01-14T23:41:12Z

That's exactly the problem I had yesterday that I posted about earlier. I removed it from my config and ran homebridge overnight without it then this morning I put the next info back in the config file exactly the same and it worked?!? Bizarre - although Homebridge has crashed today though which doesn't usually happen. On 14 Jan 2017, at 21:27, Jim <[email protected]<mailto:[email protected]>> wrote: I tried the websocket-driver fix but now have the same problem as @digitalkyle<https://github.com/digitalkyle> - homebridge won't start up as it seems to get stuck at the fetching stage. FWIW my websocket-driver module is under /usr/lib/node_modules/homebridge-nest/node_modules/firebase/node_modules/faye-websocket/node_modules/ on Ubuntu if that makes any difference.... - You are receiving this because you commented. Reply to this email directly, view it on GitHub<#107 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/APQCADTwsgv2CITUO2dwaNDxCwxEMd4Oks5rST3VgaJpZM4LdU4b>.

PencilDH mentioned this issue Jan 8, 2017

Homebridge-nest crashing homebridge (this just started happening) #106

Closed

davidtennant8082 closed this as completed Jan 10, 2017

BlaydeRunner08 mentioned this issue Jan 17, 2017

Just started getting an error "TypeError: Cannot read property 'processIncomingMessage' of undefined" #110

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Homebridge-Nest failed today after working for quite some time. #107

Homebridge-Nest failed today after working for quite some time. #107

davidtennant8082 commented Jan 7, 2017

tobeychris commented Jan 7, 2017

tobeychris commented Jan 7, 2017

emilkwaaitaal commented Jan 7, 2017

davidtennant8082 commented Jan 7, 2017

tobeychris commented Jan 7, 2017

davidtennant8082 commented Jan 7, 2017

digitalkyle commented Jan 7, 2017

Muzach commented Jan 8, 2017

PencilDH commented Jan 8, 2017 •

edited

Loading

pedroserano commented Jan 8, 2017

rtoohil commented Jan 8, 2017

digitalkyle commented Jan 8, 2017

conradhagemans commented Jan 9, 2017

PencilDH commented Jan 9, 2017

smolyneux commented Jan 10, 2017 •

edited

Loading

emilkwaaitaal commented Jan 10, 2017

davidtennant8082 commented Jan 10, 2017 •

edited

Loading

simonrb2000 commented Jan 10, 2017

davidtennant8082 commented Jan 10, 2017

simonrb2000 commented Jan 10, 2017

Muzach commented Jan 11, 2017

simonrb2000 commented Jan 12, 2017 •

edited

Loading

davidtennant8082 commented Jan 13, 2017

rtoohil commented Jan 14, 2017

lnlyssg commented Jan 14, 2017

simonrb2000 commented Jan 14, 2017 via email

Homebridge-Nest failed today after working for quite some time. #107

Homebridge-Nest failed today after working for quite some time. #107

Comments

davidtennant8082 commented Jan 7, 2017

tobeychris commented Jan 7, 2017

tobeychris commented Jan 7, 2017

emilkwaaitaal commented Jan 7, 2017

davidtennant8082 commented Jan 7, 2017

tobeychris commented Jan 7, 2017

davidtennant8082 commented Jan 7, 2017

digitalkyle commented Jan 7, 2017

Muzach commented Jan 8, 2017

PencilDH commented Jan 8, 2017 • edited Loading

pedroserano commented Jan 8, 2017

rtoohil commented Jan 8, 2017

digitalkyle commented Jan 8, 2017

conradhagemans commented Jan 9, 2017

PencilDH commented Jan 9, 2017

smolyneux commented Jan 10, 2017 • edited Loading

emilkwaaitaal commented Jan 10, 2017

davidtennant8082 commented Jan 10, 2017 • edited Loading

simonrb2000 commented Jan 10, 2017

davidtennant8082 commented Jan 10, 2017

simonrb2000 commented Jan 10, 2017

Muzach commented Jan 11, 2017

simonrb2000 commented Jan 12, 2017 • edited Loading

davidtennant8082 commented Jan 13, 2017

rtoohil commented Jan 14, 2017

lnlyssg commented Jan 14, 2017

simonrb2000 commented Jan 14, 2017 via email

PencilDH commented Jan 8, 2017 •

edited

Loading

smolyneux commented Jan 10, 2017 •

edited

Loading

davidtennant8082 commented Jan 10, 2017 •

edited

Loading

simonrb2000 commented Jan 12, 2017 •

edited

Loading