Google NORA down?

leftymuller · 15 April 2021 10:13

NORA down and out ? can anybody confirm?

TotallyInformation · 15 April 2021 10:43

Looks like it

RadioFlyer · 15 April 2021 13:06

Same here.

FireWizard52 · 15 April 2021 15:10

I saw it for the first time yesterday evening. Later this morning Nora had recovered, but now down again.

andrei-tatar · 17 April 2021 16:13

Hey guys, the original NORA was never designed to handle thousands of users. I never imagined it with become that popular. I expected 100-200 users tops.

I designed a new Nora Smart NORA (lack of inspiration on naming) that should scale easily to tens of thousands of users.

You can try it out now:

FireWizard52 · 17 April 2021 21:22

This afternoon I moved my 25 devices from Nora to Smart Nora without any problem. Did some testing this evening and everything worked as before and so far I noticed no issues, except that it responds much faster to speech commands then Nora sometimes did.

Use it with Lights, Thermostat, Switch and Scene nodes.

Good job Andrei and thanks.

leftymuller · 18 April 2021 07:47

thanks mate.. I will change over to that now!

nygma2004 · 19 April 2021 06:56

@andrei-tatar Thank a lot for your work. I am also trying to migrate to SmartNora, but I am not able to install the node using the palette manager:

2021-04-19T06:48:49.275Z [err] npm
2021-04-19T06:48:49.276Z [err] WARN retry-axios@0.3.2 requires a peer of axios@* but none is installed. You must install peer dependencies yourself.
2021-04-19T06:48:49.289Z [err] npm
2021-04-19T06:48:49.289Z [err] WARN @firebase/auth-types@0.10.2 requires a peer of @firebase/util@0.x but none is installed. You must install peer dependencies yourself.
2021-04-19T06:48:49.302Z [err] npm
2021-04-19T06:48:49.302Z [err] WARN @firebase/auth-interop-types@0.1.5 requires a peer of @firebase/util@0.x but none is installed. You must install peer dependencies yourself.
2021-04-19T06:48:49.314Z [err] npm
2021-04-19T06:48:49.314Z [err] WARN node-red-project@0.0.1 No repository field.
2021-04-19T06:48:49.325Z [err] npm
2021-04-19T06:48:49.325Z [err] WARN node-red-project@0.0.1 No license field.
2021-04-19T06:48:49.326Z [err]

Have you seen anything similar? What is the best way of installing these dependencies?

I have a question about local control? It is not clear for me how it is supported for old devices. I have an original Google Home and a 7 inch Home Hub. How can I tell if those support local control?

nygma2004 · 19 April 2021 07:02

I think you can ignore my installation question, the new nodes have deployed and they appear to be working.

andrei-tatar · 19 April 2021 07:09

These are the devices that support local execution:

and how to check if local execution is working:

github.com

andrei-tatar/node-red-contrib-smartnora/blob/master/doc/faq/README.md#how-can-i-check-if-local-execution-is-working

## How can I migrate from the old NORA service
Unfortunately it's a manual process as this is a completely new service.
All the nodes in Smart NORA are backwards compatible with the old NORA nodes so just copying over the settings from each of the old nodes should do the trick.

The main difference in the new version is that the only accepted signin method is email + password and there is no more token copied from the main page.

## Some devices show no status in Google Home app and can only be controlled using voice
The widget that shows up for a device type in the Google Home application is not under our control. The Google Home application is developed and maintained by the team over at Google and we have no way of changing its behaviour. 

Also, devices that have secondary verification enabled can not be controlled via the touch interface of the Google Home application, only via voice.

## My Garage/Lock device is not showing up in Google Home
Google requested all Garage/Lock devices should require pin secondary verification setup for security reasons. If you have the latest `node-red-contrib-smartnora` package, the error should be visible under the node.

<img src="./missing_2fa.png">

In a future release there will be a checkbox in the node-red UI to opt-out of this security restriction once the user acknowledges the security risks.

## I have ghost devices in my Google Home application
This can happen if you use/change the group name in the Smart NORA configuration node. The group name is intended to be used if you have multiple instances of Node RED connected to the same Smart NORA account.

This file has been truncated. show original

nygma2004 · 19 April 2021 07:45

I have migrated to Smart Nora as well, and all seems to be working good. I will check the local execution in a few hours as mentioned.

FireWizard52 · 19 April 2021 20:04

@andrei-tatar

I have migrated to Smart Nora 2 days ago and have been checking, if my local execution is working. However I do not see, what your FAQ shows.
In my case, even after several hours, the picture is the same.

Screenshot_smartnora_local_execution

Does it require some configuration? Such as ports?
Currently the device shows (with nmap) the following open ports:

PORT STATE SERVICE
8008/tcp open http
8009/tcp open ajp13
8443/tcp open https-alt
9000/tcp open cslistener
10001/tcp open scp-config

These ports are different from the port you show in your FAQ.

Or don´t I have enough patience?

nygma2004 · 19 April 2021 20:31

Thanks for asking the same. I only migrated today, but I am seeing the same. Nothing says local execution. In fact my original Home is not even visible in the list, only my Home Hub.

rgerrans · 20 April 2021 00:30

I had to make sure my Node-Red server was on the same vlan as my Google devices to get it to work. I never could get it to work by forwarding ports through my firewall between vlans

andrei-tatar · 20 April 2021 06:40

I would try rebooting the Google Nest Hub. It usually picks up the scripts immediately after the reboot.

I guess it depends on how your network is setup. On my network (node-red instance and google home are all on the same LAN) there's no need for any extra config. BTW, what devices do you have registered? Some devices don't support local execution at all.

Are they on different networks? Is the chrome browser on the same network with them?
Alos, the chrome inspect window takes some time to populate the devices.

FireWizard52 · 20 April 2021 16:50

@andrei-tatar,

Thanks for your quick response.

I would try rebooting the Google Nest Hub . It usually picks up the scripts immediately after the reboot.

I did reboot the Nest Hub. Was necessary again, because of the annoying Google bug, that sometimes the device looses, after a couple of days, the voice response.
But rebooting the Nest Hub did not solve the problem. I even tested it with another Google Chrome browser, just to exclude browser issues. So after the reboot the result is still te same.
It finds the Google Nest Hub, but that is it.

I guess it depends on how your network is setup. On my network (node-red instance and google home are all on the same LAN) there's no need for any extra config.

The same here, everything is in the same network.

BTW, what devices do you have registered? Some devices don't support local execution at all.

I do have registered: switches, lights, thermostat and a scene.

I checked also the Chrome version, as it is said:

Chrome : Your local fulfillment app is executed within the context of a Chrome browser window running Chrome M80 or later with support for ECMAScript version ES2018.

My version is 90.04430.72, so that looks okay

Node.js : Your local fulfillment app is executed as a script within a Node.js process running Node v10.x LTS or later with support for ECMAScript version ES2018.

I use the latest NodeJs available for a Raspberry Pi 1B (v11.15)

And another in a TrueNas (FreeBSD) Jail.

In the config node "Local Execution Support" is activated as it is by Default.

Regards

andrei-tatar · 20 April 2021 17:11

Is the same google account setup in the Nest Hub as the one you linked in Google Home app to Smart NORA?

This one might not work with local execution depending on the jail network config.

nygma2004 · 20 April 2021 19:00

It is still the same issue for me. I have rebooted both the Home Hub and the old Home as well, but all I see if the following:

I have a single access point at home (a Sagemcom fiber router provided by T-Com). It is set up to use a different 2.4 and 5GHz SSID, but that is all. But that does not stop the devices to see each other.
I am not even sure why the Google Home is not showing, but it definitely works, I send message to it from Node-Red.
Nest sits on the 5Ghz wifi, the Home on the 2.4.

And one more interesting fact which is not related to Node-Red, but a few months ago my Home Hub stopped playing online content. If I play Youtube, Spotify or anything, it just drops out after 20 seconds and back to showing the images. But if I cast a video or audio on my local NAS, all working fine. Just saying in case anyone noticed the same.

But don't get me wrong, I am glad that the integration works in the first place, getting the local control work as well would be the icing on the cake.

FireWizard52 · 20 April 2021 19:08

Hi @andrei-tatar,

You asked:

Is the same google account setup in the Nest Hub as the one you linked in Google Home app to Smart NORA ?

The answer is Yes, it is the same account.

This one might not work with local execution depending on the jail network config.

Any hints on that?

andrei-tatar · 21 April 2021 06:53

There's an open issue on github about this: Local execution check (from faq). · Issue #16 · andrei-tatar/node-red-contrib-smartnora · GitHub

I'll ping Google and try to find out what's going on.

Topic		Replies	Views
Nora Google Assistant General	3	467	22 February 2021
Google Home in Nodered General	10	846	18 May 2021
Node red google home integration General	3	973	3 May 2020
Smart Nora 1.0.3 installation problem General	11	1384	24 April 2021
Request: Contrib-Nora Node Developers Developing Nodes	1	289	3 March 2021

Google NORA down?

Related topics