I am trying to link my Smart Home action and it is not working for some specific accounts. I have traced out some logs on our server and found that our API is taking longer for some of the accounts which have more number of devices connected than usual.
So when I try to link the Smart Home Action on the Google Home App, it loads for like 10 seconds and then lands back to the previous screen without getting linked.
My question is, Is there a default timeout for the requests that Google Home is sending at my end, which I am exceeding?
You can visit the following link https://developers.google.com/assistant/smarthome/develop/troubleshooting#platform_error_codes and if scroll down to the description for RESPONSE_TIMEOUT error code then it is mentioned that the timeout period for sending a response is 9 seconds for most requests.
If this is not the exact error you are facing then it might be because testing hasn't been enabled on the project. To fix in case this is the issue, AoG Console > Develop > Account Linking > Test (Upper Right Corner).
Related
I am trying to execute Test Suite to certify, but I receive an error when executing the action. I can't find anything in the Google Cloud log. Everything works fine using Google Assistant on my phone and Nest.
enter image description here
A 503 error code means that the requested service is temporarily unavailable at the moment. You can wait for some time before trying again & make sure that your Smart Home Actions are linked with an account & testing is enabled for your actions. For instructions on how to set up your account for testing, check this link.
If the issue still persists, open up a ticket on our Public Issue Tracker.
Project Overview:
I have made a Web System by using Django+AngularJS.
The Web System is basically an Authentication Portal, User logs in and does the stuff etc.
Problem Statement:
The problem I am facing is that I have logged out my system successfully and closed the browser. Then I visit the Web Page after a week, when I opened the Link https://www.foo.xyz so normally Login Page should Appear but instead of that it directs me to the Home of the System, which is not normal.
And it keeps happening until and I cleared the Browser's Cache, Restarted the Browser and Reopened the link.
(I used Chrome and Firefox and I am facing the issue in both of them.)
What I need:
First, thing is that I don't why does this happen?
Second, how can I fix it permanently?
As I don't know how you made your web system, I'm going to be assuming a few things here.
Your page keeps the authentication information in cache, so that's why the page goes to the home and doesn't once the cache is deleted. If you want this not to happen, you're gonna need to find some way to auto-remove the authentication from the cache after x amount of time.
I have website developed using nodejs and react server side rendering.
When i am trying to scrape my website with facebook debugger, facebook takes more than 10 sec and times out. However I noticed that my web server responds to facebook scraper request within few milliseconds.
Also, Page performance is fine and it serves in less than 2 secs at max.
Note: FB debugger can scrape my website homepage (which is static file) without any issues. Not sure what is causing facebook debugger to timeout.
Any ideas?
I had path which was blocking the request, fixing that but fixed the issue.
#souhailhimself thank you for pointing in the right direction.
I am new to Nancy and am playing with the tracing and other diagnostics details. The documentation at https://github.com/NancyFx/Nancy/wiki/Diagnostics states that I should be able to hit the diagnostics dashboard by using the address http:///_nancy. My app is running at http://127.0.0.1:55368/ but when I enter http://127.0.0.1:55368/_nancy, I am getting a 404 status code. Is there something else I need to do to enable the diagnostics page in nancyfx version 0.23.2? My app is only a simple api and does not use views.
Thanks
UPDATE
The documentation on the page listed above states:
Without the password you will be presented with a page telling you that the dashboard needs to be configured in order for you to use it, along with instructions on how to perform the configuration.
However, I received a 404 instead. Once I configured a password in the bootstrapper as per the docs, the login screen showed up.
If you are running your app in Release mode, you'll just get a 404 straight away. See this issue: https://github.com/NancyFx/Nancy/issues/625
and commit: https://github.com/NancyFx/Nancy/commit/002bb9573c5ccd2437233f5bd518762c0ee77b35
Updates so that StatisConfiguration.IsRunningDebug is public. The
DiagnosticsHook will not check that flag before returning the
diagnostics help view. If true then it will return NotFound instead.
Steps to Reproduce (unexpected behavior in bold):
I successfully create an app contact via the Python Starter App
I successfully subscribe to timeline notifications
I take a photo with Glass
I share that photo with my app contact
The photo is duplicated on the timeline
The app's callbackUrl is never pinged (yet POSTing manually via curl works fine)
Attempting to delete the duplicated photo card makes the Glass OS glitch out until reboot
Posting some sample code with actual URLs may help us spot a possible error, but two things you may want to look into as you're debugging:
Don't forget that the URL in your contact must be HTTPS. HTTP URLs are not supported.
Check the contact object that is returned when you create the contact. It may be worth checking to make sure the URL and everything else is as you expect it to be... and then test against THAT URL.
Can you also clarify what you mean by "glitch out" in this case?