Test Device not visible in Home Control Section of Google Home

[arihantdaga]

Hi, Thanks for this very good sample. I tried setting up this with my project. Although i am facing this issue, i am unable to test it. It's very strange, I used it with 2 different google accounts, one with arihant.ekism@gmail.com and another with kiotcommunications@gmail.com. Surprisingly my test device is not appearing in the Google Home app when account is linked with kiotcommunications@gmail.com (I created the app also with this account only).

But its appearing in home control section in Home App when i am setting up the app with my personal email (arihant.ekism@gmail.com) and logging in the Home App also with the same account.

Acn you please help me here, as in why i am unable to test it when using email - kiotcommunications@gmail.com

[tsungmin]

got the same problem . u_u

[malard]

my assumption here is that you can only test on the same account that you created the app on.

[arihantdaga]

@malard I tried to test on the same account only. But problem is when i am creating and testing with one account it's working, and not working when creating and testing with another account.

[malard]

are you using the same app? I believe during testing you can only attach an app to the account you created it on. Otherwise you need to move it to preview

[vijmax]

Iam using the same account on the mobile (Home Control), Ubuntu server and actions console. Iam able to test the nodejs setup via mock application. But not able to view the application on my mobile home control.

~/demo/actionssdk-smart-home-nodejs-master/smart-home-provider$ gactions --verbose test --action_package action.json --project bulb-test Checking for updates... Successfully fetched update metadata Finished checking for updates -- no updates available Pushing the app for the Assistant for testing... POST /v2/users/me/previews/bulb-test:updateFromAgentDraft?updateMask=previewActionPackage.actionPackage.actions%2CpreviewActionPackage.actionPackage.conversations%2CpreviewActionPackage.actionPackage.types%2CpreviewActionPackage.startTimestamp%2CpreviewActionPackage.endTimestamp HTTP/1.1 Host: actions.googleapis.com User-Agent: Gactions-CLI/2.0.7 (linux; amd64; stable/6f4c996f8ee63dc5760c7728f674abe37bfe5fc4) Content-Length: 570 Content-Type: application/json Accept-Encoding: gzip

{"name":"users/me/previews/bulb-test","previewActionPackage":{"actionPackage":{"actions":[{"description":"We have the bulb test running now","fulfillment":{"conversationName":"welcome"},"intent":{"name":"actions.intent.MAIN","trigger":{"queryPatterns":["talk to bulbs"]}},"name":"MAIN"},{"deviceControl":{},"fulfillment":{"conversationName":"automation"},"name":"actions.devices"}],"conversations":{"automation":{"name":"automation","url":"https://bulb.priyan.xyz/ha"},"welcome":{"name":"welcome","url":"https://bulb.priyan.xyz"}}},"name":"users/me/previews/bulb-test"}} Reading credentials from: creds.data Successfully pushed the app for the Assistant for testing Your app for the Assistant for project bulb-test is now ready for testing on Actions on Google enabled devices or the Actions Web Simulator at https://console.actions.google.com/project/bulb-test/simulator/ ~/demo/actionssdk-smart-home-nodejs-master/smart-home-provider$

[smishra2]

There are a few places where you need to use the same Google account:

• Actions console
• gActions credentials (to double check this, remove the creds.data file in the same directory as gactions)
• In the Google Assistant settings on your mobile device

Are you using the same account in all places?

[vijmax]

I double checked all the 3 locations. They are signed in with the same gmail ID. Earlier there was a problem with oauth key (i used the one from demo directly). I switched that to the oauth generated from my google account. The actions console can now reach the fulfillment server. On the mobile side, the app does not get listed still. Is there any connection with oauth keys for this ? I wiped my mobile and signed in just with the test email ID i was using with the project (just to rule out multiple login ID's were creating problem), it did not help

[PertDeveloper]

I had the same issue but then realised that I had updated the action package for the production app and did not push the action package for testing.We need to use this command : gactions test --action_package {package name} --project {project name}

Earlier I had used "gactions update --action_package {package name} --project {project name}" command, this was my mistake.....so just make sure that your pushing the action package to testing environment, hope this helps

[vijmax]

I had already tried gactions test. The verbose output is

~/demo/actionssdk-smart-home-nodejs-master/smart-home-provider$ gactions --verbose test --action_package action.json --project bulb-test Checking for updates... Successfully fetched update metadata Finished checking for updates -- no updates available Pushing the app for the Assistant for testing... POST /v2/users/me/previews/bulb-test:updateFromAgentDraft?updateMask=previewActionPackage.actionPackage.actions%2CpreviewActionPackage.actionPackage.conversations%2CpreviewActionPackage.actionPackage.types%2CpreviewActionPackage.startTimestamp%2CpreviewActionPackage.endTimestamp HTTP/1.1 Host: actions.googleapis.com User-Agent: Gactions-CLI/2.0.7 (linux; amd64; stable/6f4c996f8ee63dc5760c7728f674abe37bfe5fc4) Content-Length: 570 Content-Type: application/json Accept-Encoding: gzip

{"name":"users/me/previews/bulb-test","previewActionPackage":{"actionPackage":{"actions":[{"description":"We have the bulb test running now","fulfillment":{"conversationName":"welcome"},"intent":{"name":"actions.intent.MAIN","trigger":{"queryPatterns":["talk to bulbs"]}},"name":"MAIN"},{"deviceControl":{},"fulfillment":{"conversationName":"automation"},"name":"actions.devices"}],"conversations":{"automation":{"name":"automation","url":"https://bulb.priyan.xyz/ha"},"welcome":{"name":"welcome","url":"https://bulb.priyan.xyz"}}},"name":"users/me/previews/bulb-test"}} Reading credentials from: creds.data Successfully pushed the app for the Assistant for testing Your app for the Assistant for project bulb-test is now ready for testing on Actions on Google enabled devices or the Actions Web Simulator at https://console.actions.google.com/project/bulb-test/simulator/ ~/demo/actionssdk-smart-home-nodejs-master/smart-home-provider$

[vijmax]

Oh ... that MAIN action was an effort to see what exactly happening after reading the Actions SDK documentation and how to get it running. It never worked without that as well ...

~/demo/actionssdk-smart-home-nodejs-master/smart-home-provider$ ~/tools/gactions --verbose test --action_package action.json --project bulb-test Checking for updates... Successfully fetched update metadata Finished checking for updates -- no updates available Pushing the app for the Assistant for testing... POST /v2/users/me/previews/bulb-test:updateFromAgentDraft?updateMask=previewActionPackage.actionPackage.actions%2CpreviewActionPackage.actionPackage.conversations%2CpreviewActionPackage.actionPackage.types%2CpreviewActionPackage.startTimestamp%2CpreviewActionPackage.endTimestamp HTTP/1.1 Host: actions.googleapis.com User-Agent: Gactions-CLI/2.0.7 (linux; amd64; stable/6f4c996f8ee63dc5760c7728f674abe37bfe5fc4) Content-Length: 312 Content-Type: application/json Accept-Encoding: gzip

{"name":"users/me/previews/bulb-test","previewActionPackage":{"actionPackage":{"actions":[{"deviceControl":{},"fulfillment":{"conversationName":"automation"},"name":"actions.devices"}],"conversations":{"automation":{"name":"automation","url":" https://bulb.priyan.xyz/ha"}}},"name":"users/me/previews/bulb-test"}} Reading credentials from: creds.data Successfully pushed the app for the Assistant for testing Your app for the Assistant for project bulb-test is now ready for testing on Actions on Google enabled devices or the Actions Web Simulator at https://console.actions.google.com/project/bulb-test/simulator/

On Fri, Jun 16, 2017 at 4:59 PM, PertDeveloper notifications@github.com wrote:

@vijmax https://github.com/vijmax I think you need to change your action.json file. For smart home actions,I think you don't need a MAIN intent, this would suffice : { "actions": [ { "name": "actions.devices", "deviceControl": {

}, "fulfillment": { "conversationName": "automation" }, "signInRequired": true }

], "conversations": { "automation": { "name": "automation", "url": "my_service_endpoint" } } }

I am not sure if the main intent can be there but it works fine for me without the main intent

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/actions-on-google/actionssdk-smart-home-nodejs/issues/1#issuecomment-309002770, or mute the thread https://github.com/notifications/unsubscribe-auth/AH3F3W9G8mQw6CFZBzlSQgHMNUkP1j8iks5sEmc3gaJpZM4NgIDo .

-- Regards, Vijayan V

[codeface]

Hi @vijmax Did you manage to get any further with this? I've encountered a similar problem where one google account (not the owner of the project, but a separate account I set up for testing) is able to see the test device in the list, but other google accounts (having gone through exactly the same steps) are not.

[vijmax]

Nope ... i have been trying to get in touch with google to check on the issue. There is no update still.

[mwidlok]

@codeface @vijmax I have exactly same problem as yours - I've contacted google, this is what they've said:

"Multiple developers have reached out to us saying that they can't see their test app in the list of devices under the Home Control section. So, there is a possibility that the issue could be on our end and we are looking into it at the moment. I will reach out to you with the status of it as soon as we have an update."

[codeface]

@mwidlok @vijmax Thanks both. I've also raised an issue with Google. For now, we're testing using the main account that 'owns' the project, and one other google account where testing mysteriously works. Interestingly, the non-owner account that does work for testing is an account that was previously used to do some playing around with creating conversation (i.e. non-smarthome) actions, so I wonder if some special setting on that account was activated during that previous development period.

[mwidlok]

@codeface Hi, have you managed to solve this problem? I'm still waiting for a google response - their support sucks.

[codeface]

@mwidlok Hi there, we're still working around the issue by testing on the same account that 'owns' the action. I don't think we had a response from Google yet - I'll post on here if we get one.

[vijmax]

Google guys gave me one google account where the application can get listed now. I used that account that hosted this project after putting in the https changes. It worked like a magic So the fundamental problem of why apps dont get listed in certain accounts is a mystery getting resolved.

[vijmax]

Forgot to mention ... there is one mistake in the instructions still ... node smart-home-provider-cloud.js smart-home-pub="https://your_domain.com" should be changed to node smart-home-provider-cloud.js smart-home="https://your_domain.com"

[arihantdaga]

@vijmax " mystery getting resolved." ? ? What's the solution.. ?

[marziman]

@vijmax I ve the same problem! I cant see my action under home control in the google asisstant app. Thats really annoying..I cant test the user oAuth flow.. Wwhere did you place your issue??

Thanks

[marziman]

@smishra2,

I ve finished the action for openHAB, a really loved opensource home automation platform. I also cant see the action in the assistant companion app. It doesnt appear under the services, so I cant test the oAuth User flow. Can you please support? Or should I contact google support? I am based in germany, but I dont think this should be a problem. The websimulator say "This action is not support in simulation" and under home control I cant choose the service..Do you have an idea?

Thanks and BR Mehmet

[marziman]

Sorry to say, but it feels that nobody cares about this blocking topic. What I cant understand is, why did you release it if there are so basic bugs included? Actually I tried this process with 3 newly created accounts. None of them worked: The test app is never visible in Home Control section of the Google assistant companion app.

An aswer of the maintainers of this project would be highly appreciated.

BR Mehmet

[mwidlok]

I've reported it to google support twice within past 3 weeks - All the answers I've received say that they have escalated problem. Right now I'm stuck, because I can't develop smart home google home assistant app to my client.

[Fleker]

If you're experiencing an issue, can you provide some information about your device setup?

• What is the language and localization for your device?
• What is the language and localization for your Google account
• Is the primary account on your phone (the first one in an account picker) the same as the account used to create the action?

[mwidlok]

@Fleker

• English (US), Poland
• Polish, Poland
• Yes

[marziman]

@Fleker,

• English US
• German, Germany
• Yes

You can find my issue fully described here: https://stackoverflow.com/questions/45234171/smarthome-app-action-doesnt-appear-in-google-assistant-companion-app-under-home

[mgf909]

@smishra2 - Sachit can you advise on this? Seems to be holding up several implementations and frustrating devs and users alike!

[Fleker]

It seems like most users are encountering an issue with seeing their test devices not appearing in the Google Home app. When you deploy your Action Package to the Actions on Google console, are you:

• Starting your smart home server locally
• Updating action.json with the URL https://<random-string>.ngrok.io/ha and deploying
• Going to the Actions on Google console
• Selecting Edit in the Overview and updating the Authorization URL to https://<random-string>.ngrok.io/ha
• Saving this update
• Returning to the Overview
• Select the Test button

[mwidlok]

Yes

[vijmax]

There seems to be a problem with region or specific accounts. I had followed the same process on my personal account and a account given by google. It failed to work on my personal account.

[emilerj]

I am faced with the problem as you are. I have sent email to Smart Home team, but they just explained:

"Smart Home Apps not showing in the list of Apps under the Home Control section on the Google Home App is a known issue and we're currently looking into it. I will reach out to you as soon as I have an update on that."

But over the past three weeks, I still not get any feedback from Smart Home team. It seems very strange, and nobody care about this.

[emilerj]

If somebody could provide a available test account, it will be very great.

[mgf909]

Very disappointing that Google cant sort this out....

[Fleker]

For those having issues:

If you create a more general Actions on Google project and started to test it, are you able to invoke it through the Google Assistant on your phone (ie. "talk to ")?

[Fleker]

In order to provide greater assistance to affected users, can you send me an email with your AoG project id and the email you used to create the project? Thanks.

[mwidlok]

@Fleker Could you please follow these steps and tell us if it works?

1. Create a completely new google account
2. Use this account to create a new project under google actions console
3. Add Actions SDK to this project and use gactions cli to update project
4. Fill the Account Linking
5. Click TEST

Do you see your test app inside Home Control Section in Google Home iOS app?

I've done this steps dozen times, it never worked. However it's working with my personal google account that have been created a years ago. But as you probably understand, I can't provide my personal account data to the client so that he can test the app :)

[Fleker]

I want to thank everyone for their responses. After looking at the affected users, it seems like there is not a single issue, but several separate issues. We will be working with these users to resolve their problems. ● Only one agent can be tested at a time. Make sure you are only testing the agent you want. ● Test agents expire after three days. Make sure you rerun gactions test to redeploy your test agent. Devices will still be connected even though the agent has expired. ● If your agent is still not showing up, make sure that you have run gactions test with the gActions CLI ● You cannot have a conversation with the Smart Home agent using the web simulator. You can only issue direct commands like “turn on/off my lights”. This issue will be closed. Further issues should be filed if problems persist. We will be updating the documentation to answer some common issues users have. You can refer to our FAQs and our documentation for implementation help and a support form if you have a specific issue for your project.

[Fleker]

@mwidlok I'll try with a test account and see if the behavior changes.

[marziman]

@Fleker I dont understand why you close this issue, without really providing a solution. I dont want to stress this, but it is really not working.

[coder-woo]

@marziman i'm in china.I ve the same problem! waiting for a solution

[coder-woo]

@marziman Interestingly, add a test account, i can see the service(app) in the google home which loggin with the test account.But still not show in the main account that 'owns' the project.

[marziman]

Hi at all,

I ve reopened an issue since Google team closed this without a solution. It is really strange for me and also no good sign. If Google wants to be competitive, their platform should be on the same level as Alexa. Where I never faced problems to see the Skill in the Alexa companion app.

https://github.com/actions-on-google/actionssdk-smart-home-nodejs/issues/25