Missing "On device testing"

google-home / smarthome-local

https://codelabs.developers.google.com/codelabs/smarthome-local

Apache License 2.0

28 stars 17 forks source link

Missing "On device testing" #4

Closed webcodercompl closed 4 years ago

webcodercompl commented 4 years ago

I don't see "On device testing" in Test tab

I'm not sure if the issues are connected, but I don't see anything more than this in Chrome DevTools:

Starting a virtual device with a google assistant on phone works (the firebase database is also refreshed) but I can't start local execution

devunwired commented 4 years ago

Thanks for your feedback! The Actions console UI recently changed with the v1.0.0 SDK release last week, and we hadn't quite gotten the codelab instructions updated to match. The codelab has now been updated to reflect the new console.

To answer the specific question, the testing URL is now on the Develop > Actions page with the rest of the Local Home SDK configuration.

webcodercompl commented 4 years ago

Thanks for your answer! I noticed that "Enable local fulfillment for smart home Actions" codelabs has been updated. Unfortunately, there are still a few references to the old Actions console UI eg.

The code in the repository uses the SDK version v0.2.0 - should something also be updated in the code due to the SDK update?

I'm trying to run the "app-done" version, unfortunately after I added testing URL in Develop > Actions I still don't see any local execution logs. (DevTools console looks as on my previous screen)

devunwired commented 4 years ago

Codelab should be up to date at this point.

The fact that you are able to launch Chrome DevTools inspector on your device tells me that your testing URL is being picked up correctly and it is running your local fulfillment app. If nothing else is happening, then your device is not triggering any IDENTIFY intents. This is most likely either because your scan configuration is incorrect/incomplete or the device you are looking to identify isn't present on the same network (or is unreachable).

tobi-coder commented 4 years ago

I have the same problem as @webcodercompl. I see only shell and SDK version. No identify intent. The devices are in the same network and reachable. Any other hints? Trying to get that working since hours.

devunwired commented 4 years ago

The virtual device will log a message each time a discovery payload is received. For the UDP broadcast in the codelab, this should happen roughly once every 60 seconds. If the virtual device is not seeing any traffic, then the scan configuration is likely incorrect or your device isn't properly linked to the same Google account as the test project.

tobi-coder commented 4 years ago

Thank you @devunwired. It was a stupid configuration mistake with the ports in the Action.