Google Home Mini - Nora is not available about node-red-contrib-nora HOT 13 OPEN

I have a similar Issue. The google home app on android can control all my Nora Devices, but the google home mini's in my house frequently complain that Nora Can't be reached

I am based in South East Asia, perhaps it is a server latency issue?

from node-red-contrib-nora.

I am based in South East Asia, perhaps it is a server latency issue?

Could be. Does node-red manage to establish a websocket connection to NORA and keep it open? Any strange messages in the node-red log?

from node-red-contrib-nora.

Today the same issue occurs me in Germany. NORA isn't reachable with my GHM and the GH App.

from node-red-contrib-nora.

You need to update the token in Node-RED with a new one from https://node-red-google-home.herokuapp.com/

Also, you need to unlink NORA (in your Google Home app) and link it again.

Sorry for the inconvenience... Everyone will need to do that.

from node-red-contrib-nora.

Hej @andrei-tatar thank you for your fast answer. Works like a charm.

from node-red-contrib-nora.

from node-red-contrib-nora.

@syoma755 it solves the problem "Nora is not reachable"

from node-red-contrib-nora.

I have relinked Nora to Node-Red and revoked Token. Also tried to find new devices in Nora binding in Google Home app - app reported, that Nora service successfully linked. I can control Nora devices from the Google Home app without a problem.

But there is still some problem:
I have two Google Home Minis in two rooms. On one the Nora is working now, but from time to time GHM is reporting that "Nora is not available". If command is repeated, it is usually executed.
But the other GHM continuously reports "Nora is not available" - I couldn't make it work so far.

Can you suggest what can be wrong? How to make my GHMs work correctly with NORA?

from node-red-contrib-nora.

@syoma755 are the google home minis on the same wifi? Is one significantly farther from the router?

Google will give the not responding error if it doesn't receive a reply in a window, but the respone window is pretty narrow, so if anything is delaying the packets (in my case being on the other side of the planet from the nora server) can cause this error, but usually I find that even when google says the service is unavailable the command still gets executed.

from node-red-contrib-nora.

The minis are in the same Wi-Fi, but in different rooms. The one, which doesn't work, is a bit farther from router, than the other.
The one thing, which might affect this, is that on non-working mini I have two accounts. But it's still in the same house and works fine with other appliances (I have also AC climate, connected via Smart Things to Google)

from node-red-contrib-nora.

Did you link nora to all the google accounts? That might be necessary. The other thing is that nora is giving out API keys associated with distinct accounts. Is your nora connector handling multiple IDs or just one?

from node-red-contrib-nora.

Did you link nora to all the google accounts?

I have no Idea why I should do it and how to check it. Off course I have linked NORA only to my main Google Account and using this account I have generated a token for Node-Red. But what should I do with second account? How to link it to Nora using same token, if in Google Home App I logged in under main account?

BTW The google response on non-working mini clearly states, that it can "knows" Nora, but can't execute any action.

from node-red-contrib-nora.

Yeah, that I dunno. Maybe if you used github to create your nora token you could use that same github account with both google home accounts?

from node-red-contrib-nora.