title: Firebase websocket protocol, am I missing something?
body: <p>I am working on an experimental c# nest client using websockets on an embeded
  hardware. My problem is that nest doesn't seem to want to communicate with me
  after the initial handshake.</p>
  
  <p><strong>wss://developer-api.nest.com/.es?v=5 HTTP1.1</strong></p>
  
  <p>wssClient | Handshake header: Upgrade: websocket<br>
     wssClient | Handshake header: Connection: Upgrade<br>
     wssClient | Handshake header: Sec-WebSocket-Accept: 2TSbkk9Kv0soMbpA0fGrtQUWoyI=<br>
     wssClient | Handshake header: <br>
     wssClient | Expected sec key: 2TSbkk9Kv0soMbpA0fGrtQUWoyI=<br>
     wssClient | Response sec key: 2TSbkk9Kv0soMbpA0fGrtQUWoyI=<br>
     wssClient | Connected<br>
      nest-cli | connection state changed: Connected<br>
     wssClient | Text frame received: 81 7E 00 95  ..<br>
      nest-cli | &lt; <strong>{"t":"c","d":{"t":"h","d":{"ts":1422883899173,"v":"5","h":"firebase-apiserver03-tah01-iad01.dapi.production.nest.com:9553","s":"session-425920698"}}}</strong><br>
      nest-cli | > <strong>{"t":"d","d":{"r":1,"a":"auth","b":{"cred":"c.R...MK0"}}}</strong><br>
     wssClient | Sending data frame: 81 7E 00 C2 ...<br></p>
  
  <p>after the client sends the credential frame (just like the Firebase.js client) I get no reply from nest ..
  no redirection nor confirmation of authentication</p>
  
  <p>is this behavior deliberate (somehow detects that its peer is not firebase) 
  or I am doing something wrong ?</p>
  
  <p>Thank you</p>