问题
When using the simulator in the Actions Console, I get the response: "Since your voice wasn’t recognized, I can’t do that right now. Check the Voice Match settings in the Google Home app."
The account under which I am developing has no devices registered, intentionally. This account is used specifically and only for development.
Why does the simulator respond like this, and how can I fix it? The account has no "Google Home app".
I have another (personal) account which I've used to develop the Action initially. The simulator works fine there. Now I'm trying to move the development to an "official" corporate account, and the simulator fails completely.
回答1:
I can confirm I'm getting exactly the same occurrence here. Doesn't matter what device type is selected as being used. Similarly was working fine a couple of days ago. Looks like Google has broken something with account linking and the Actions on Google Simulator. I did however read somewhere that best practice you should be delivering some functionality that does not require account linking. That way you will still get explore ratings from users who visit your assistant but refuse to sign in. However that doesn't fix the core issue of testing functionality that requires sign-in using Actions console simulator.
来源：https://stackoverflow.com/questions/57080125/simulator-responds-with-voice-not-recognized