I worked on one Google assistant, I used Dialog Flow and I constantly tested in the simulator.
But today I woke up, started the project, and the simulator does not show me Google actions (list or basic card), although I did not change anything in the project. enter image description here
Related
I'm trying to add a select channel trait.
what I did was that I followed the docs,
1- Add the ATTRIBUTES to the device I want to apply this feature on, for example, a TV device type
2- I guess we are all done as every other command works with my code
What I actually did was the following to the device database in Firestore
then added the
case "action.devices.commands.selectChannel":
in the
switch (execution.command) {}
code
then reloaded the device from the google home app
then when I try to call
"Change to ABC on my TV"
it says
'Sorry, I don't understand.'
and nothing appears on the logs
otherwise, everything is working perfectly,i.e setting the volume and On/Off.
what am I doing wrong, please?
UPDATE:
Today I tried command "action.devices.commands.returnChannel" and "action.devices.commands.relativeChannel" and they are working fine
and all three commands belongs to the same trait!
I've seen a lot of users complaining about this command on many sites
like the following 1,2,
could this be related,
I'm still in debug mode, would it be fixed when I publish my app
UPDATE #2
I tried it today with an android phone and it works fine with selectChannel command,
previously I was testing with an iPhone with google home and google assistant apps on their latest release, and the selectChannel is the only command that didn't work there.
Hope it's just related to the debugging mode
It is usually unexpected to have a trait / feature working on the Google Home App on Android but not on the iOS version, as their functionality is nearly identical. The accuracy on the speech to text conversion on both platforms might be different, which could be affecting the functionality. You can try out typing your request to see if that helps in any way.
Im using Google Maps with Flutter, i've followed all of the steps, and it worked perfectly, i had a map widget that i could use to browse, zoom and everything.
A few days later, after i started tinkering with Firebase Auth (for the same app), it stopped working, as a matter of fact, the app makes my (Xiaomi) phone crash and reboot when i enter the map screen, while it works completely fine on my emulator.
I tried to create another blank google console project and created the APIs from scratch, and created a blank flutter project and set everything up, but it still crashes my phone.
I tried this on a Samsung, the phone doesnt crash, but the map shows up a blank grey area.
What should i do ?
Need to Add Permission . User have to confirm the permission then you will able to view it
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.
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.
I have been using google actions with actions sdk and most of the functionality seems to work. However, I am facing consistent issues across a few alpha test users on the updates to the application.
I notice that the latest deployed to the cloud function is what seems to run on the Simulator but an old version appears when viewing on a phone. For example, the icon that I set in the images directory is just not showing (even after 2 days) on my phone while the latest appears in the Simulator. The same with some images from Cloud storage. I tried clearing the cache and storage from the Assistant app on my android phone. Yet the problem persists.
Is there some setting or disabling of cache that needs to be specified in the NodeJS based client code or in the actions console? Thanks.
Go to the Test tab and click on the Reset Test option, such as in the screenshot. It should work.
Has anyone noticed that the Simulator in the Actions on Google Console has been updated and it no longer is an accurate simulation of the assistant app on devices?
They added a display tab but it seems to not show all the output. My application often includes 2 chat bubbles in one response and the new simulator only displays one even though the tts for both is heard in the audio.
I have the same problem. Hope they don't remove the ability to add to responses. It would look terrible with only one line.