Keep receiving “(my app name) isn't responding right now. Please try again soon” on my actions on google simulator, I’ve tried almost all the solution that I found on the internet and ended up with this, I decided to copy the code from google https://developers.google.com/assistant/df-asdk/helpers#calling_the_helper it works just the permission one , for the permission handler it doesn’t work it seems like if I do not put the default response in dialogflow It wouldn’t work so I don’t want that default response because it keeps saying that response, and when I removed it , it gave me an error ,but in the debug tap it shows everything(display name, location etc.)
Related
I created a smart home action using action-on-google and nodeJs, and it works fine. When you say turn on switch off, it sends MQTT request to my server, means that onExecute function works fine but the problem is that google doesn't respond to my command by OK it says "sorry it looks like your device not available right now", I observed also that my device is always offline in Google home app. Is it required to work with firebase and get device state from there?
Firebase is one of web services allowed to store a device's states. You can feel free to use other web services.
If your device is offline, it may be because your Google Home App hasn't received your device's states.
Here are two paths for Google Home App receiving your device's data:
Google Server will send a action.devices.QUERY intent and callback your function (e.g. onQuery) to get the data of your device through your fulfillment, see action.devices.QUERY.
Thus, please print logs in the onQuery function and make sure that your function works fine.
Your smart home action must use the API of reportStateAndNotification to update your device's data in the Home Graph, see Method: devices.reportStateAndNotification.
If Google Assistant gives you "Sorry, device is not available right now", it probably is because the Google server hasn't received correct information from your fulfillment. Please follow the suggestions above and try it again.
If you're still having issues, check your logs to identify the particular issue for that device.
I want to highlight an issue that I am encountering with video indexer. On my machine, whenever I try to login to video indexer ( either microsoft or gmail account), it shows me blank dashboard like the one below:
I have tried running it on other browsers and incognito as well (clearing browser cookies too). But nothing works on my machine. However, the same works fine when I log in through my other machine. Any help will be appreciated.
Make sure you try incognito mode without any browser plugins/extensions.
Can you open the browser console and see if you are getting any errors or network issues?
Looks like the GRAPH API is hitting a 401.
This is used to return the currently logged in user.
Since you are saying it is working in another machine fine.
The possibility I can think of is because of Conditional Access Policy(Location based mostly).
There could be some policies(for Security) that can be set at the tenant level which is making the Graph API to error out with 401.
The one machine is within the compliance (trusted network/vpn/domain joined etc.) where as the other one is not compliant. Hence the error.
I had an app that was working fine with inapp purchase - I still was in test mode but it was fine.
Then I decided to go to production but got issues - in the meantime nI had lost my certificate keys, so I had to use another package name, upload a new app on Google play and use new certificate credentials.
Anyway.
I did the exact same thing with this new app, and I also add the inapp purchase package, but when I launch the app I have this error :
Error while retrieving the informations from the server ([DF-AA-20])
Any idea of why I have this error message ?
I checked the inapp package name several times and it's ok...
What could be the issue ?
I've been trying to solve this for hours...
Thanks for your help.
I was able to solve the issue by doing these steps:
- I copied the public key found in "Services & API" google account and added it in my code
- I published the app in alpha mode and had to wait until it was really "published", and not "pending publishing"
Now it's working fine and I'm able to make test purchases.
But then I deleted the test account and tried to make a real purchase, and I'm having this error:
"Error: Impossible to buy this article"
Does anybody had this issue ?
Thanks
The _actions_on_google_ context stopped appearing in the contexts section, and I think this may be a clue to what's gone wrong.
It's just stopped doing anything, it'll get the required parameter then the JSON says it's sent it to webhook but there's only the 'secure' context in that (I remember seeing an actions on google one by default). When I remove my custom context it doesn't help, and I've updated firebase.
How do I get this back?
I think the issue was that I had deleted something in the code, maybe the }); at the end.
If you have the same issue, go OCD through your code and match everything together to check it's all good.
I am following this Echo Bot Tutorial, and have gone through all of the basic steps regarding setup and registration. I am following the steps (near the bottom) regarding local testing, and have been using ngrok successfully.
I was able to add my Skype Bot as a contact, and I also have the latest version of the Skype app (Mac). When I send a message to the bot via the Skype app, I see the message appear in the debug notes in my terminal window. So I know that the messages I type are coming through.
I also see this:
skype-sdk.MessagingServiceClientV2 Sending message to 8:username with content Hey 8:username. Thank you for your message: "test".
However, I do not see any kind of reply in my Skype application. My expectation is that the bot would echo back my message to me.
My questions are:
1) When testing locally using the ngrok method described in the tutorial, should I be able to see activity from the Skype bot (in terms of messages to me)?
2) I am guessing this may be some an authentication issue? How can I best troubleshoot things, and get the Skype bot to actually respond in the Skype app?
I feel like I am incredibly close to getting this working, in that the messages I send are coming through... but the messages I expect from the Skype bot are not coming through. Any help or ideas greatly appreciated!
Found the fix, and posting it here should anyone else run into the same issue.
During the setup process, when I was using the Application Registration Portal, I selected the wrong string as my Application Secret.
Originally, I clicked on Generate New Key Pair, which resulted in a new entry appearing in the admin labeled Private Key. I used this string as my App Secret.
However, it appears that what I should have done was click on Generate New Password and used *that string instead**. Just gave it a try, and my bot is now responding back to me locally (in the Skype app), when testing with ngrok.
I think this particular distinction could have been made clearer in the documentation, as I lost a great deal of time due to this one oversight. Oh well, at least I can start developing now...