Google Home Debugging Tools: Event logs

if your smart home integration seems to be working incorrectly you'll want to look at your project logs to see what the exact error is let's take a closer look at the process of accessing these event logs and using them as debugging tools for this we'll go to our logs explorer this tool does have two main sections a query field to write queries to search through your logs the one on top and a query results window that shows the logs matching your queries on the query field i'll write partner response missing device in quotation marks then run my query as you see it was able to identify the error log matching this execution flow you can click on it to expand the fields as you see the log provides some useful information like what was the device type the device trait associated with this execution what's the latency as well as the request id that you can follow up in your own server as well each of our error logs you'll see a status field with a status type which matches our error code and an external debug string which contains the error description this one says json response does not include the device so there might be something wrong when we were preparing our json response you saw an example conducting a string match as a filter similar to this we can also fetch certain fields within the log like is success equals false and device type equals light will give us the error codes coming from lights as you see we can combine these prompts with boolean operators such as and or not and numeric fields you can use comparisons latency millisecond greater than 300 will get you the logs that has a higher latency numbers for example google does provide the query library by the way that has many different examples you can see the link below to follow up on that for more tips on using event logs check out the resources below if you have any questions or if you want to see what everyone is building join us on reddit or follow us on twitter hope to see you there