Local execution check (from faq). about node-red-contrib-smartnora HOT 17 CLOSED

I published version 1.0.3 of the package and update the FAQ. Will close this issue for now.

from node-red-contrib-smartnora.

I think none of your devices support local execution:
https://developers.google.com/assistant/smarthome/concepts/local#supported-devices

from node-red-contrib-smartnora.

Think you are right. However strange google nest audio is not supported while nest mini is.
I will connect a nest mini to check this.

from node-red-contrib-smartnora.

Same with a nest mini attached. This is a supported device, so something else is the problem.

from node-red-contrib-smartnora.

I have the same problem

from node-red-contrib-smartnora.

I'll ping the guys over at Google and try to find out what's going on.
Maybe the local execution is rolled out slower...

from node-red-contrib-smartnora.

Maybe it's a security thing and not all users can see/debug the running scripts. Can any of you guys enable logging at trace level in node-red and see if you do get local-execution traces in the node-red logs?
https://nodered.org/docs/user-guide/runtime/logging

There should be messages like:

[nora][local-execution] Received discovery packet, sending reply

from node-red-contrib-smartnora.

I have the same problem as mentioned above.

I enabled logging at trace level and I get repeatedly the following log:

21 Apr 10:23:38 - [trace] [nora][local-execution] Received discovery packet, sending reply
21 Apr 10:24:10 - [trace] [nora][local-execution] Received discovery packet, sending reply
21 Apr 10:24:19 - [trace] [nora][local-execution] Received discovery packet, sending reply
21 Apr 10:24:38 - [trace] [nora][local-execution] Received discovery packet, sending reply
21 Apr 10:25:10 - [trace] [nora][local-execution] Received discovery packet, sending reply

I have 3 nora configs in node-red.

from node-red-contrib-smartnora.

Ok, in that case I got it wrong in the FAQ. Probably not all users are able to see/debug the scripts.
That's why the local exection log is set to trace. There were way too many messages generated in the logs.

@JaspervanKol if you trigger a command (turn on a light or something) from assistant or Google Home, do you also get a log similar to [nora][local-execution] Executing {command} - device: {deviceId}?

from node-red-contrib-smartnora.

I triggered a light with my google home device and got this in the logs:

21 Apr 10:44:53 - [trace] [nora][local-execution] Executing action.devices.commands.OnOff - device: <default>|975f5836:f4d518
21 Apr 10:44:53 - [trace] [nora][local-execution][975f5836:f4d518] executed action.devices.commands.OnOff

Does this mean local execution is working @andrei-tatar?

from node-red-contrib-smartnora.

Yes! :)

I will update the FAQ.

from node-red-contrib-smartnora.

from node-red-contrib-smartnora.

@geertvercamer what devices do you have? Not all devices support local execution. (secondary verification devices, garage door, lock).

from node-red-contrib-smartnora.

from node-red-contrib-smartnora.

So I changed the code so that devices that receive commands over local execution will have the status color switched to blue.
I'll try to update the FAQ later today and release this new version.

from node-red-contrib-smartnora.

from node-red-contrib-smartnora.

@geertvercamer you just need to create multiple configurations (using the same credentials).
One with pin, one without pin and assign each one accordingly to each device.

In a future release, the pin configuration will be moved per device, but that's a big chunk of work.

from node-red-contrib-smartnora.