There is no Alpha/Beta testing options in the Release tab of the Google Actions console.
I'm developing a Google Action (Smart Home). I can test it with my developer account, and can invite others to test as developers (ref: https://medium.com/#rekire/alpha-test-your-action-on-google-5886246e0e).
But I could not find the Alpha/Beta releases as documented in https://developers.google.com/actions/deploy/release-environments
There is only a Production section in the Release tab.
Alpha/Beta channels aren't available for Smart Home actions.
Related
I am looking for ways to automate smart home action integration using APIs or CLIs, so that it will not be required to visit Google actions console to configure the integration.
I have tried out gactions CLI, but pushing manifest for smart home actions gives this error: "Actions project must specify at least one action in actions.yaml."
As my actions project is smart home action and not conversational action, custom actions are not applicable for my project.
As per documentation, actions API also seems to be applicable only to conversational action.
For Alexa smart home skill, I am able to use SMAPI SDK to push smart home skill manifest, is there some way using which I can push smart home action configurations?
We don’t provide the API or CLI to automate the Google Smart Home integration action. One needs to go to Actions on Google console to finish the setup
I have created a conversational action in Actions Builder that uses account linking via OAuth (not Google sign in). Functionally, everything is working well.
The only issue I noticed is that when I try to link accounts using anything except a phone in the simulator, I get a response telling me to link accounts using the Google Home app. Since my action is a conversational action and not a smart home action, my action will never be found in the Google Home app.
I have confirmed that this kind of account linking is supported with conversational actions (via docs as well as Actions on Google support). What support could not answer for me is what I can do about this, they directed me here for help.
So my question is, how is account linking handled for conversational actions on non-phone devices (e.g. smart speaker)? Does it simply not run at all, or do I have to do something to remove these Google Home prompts?
Thanks
If the Action is running on a device type that does not support a web browser then the authentication step is not going to work. If you have not signed in before, the operation will fail. Though if you have signed in already, any device will be able to retrieve your access token.
The way to do this would be to handle cases for a non-authenticated device that cannot be authenticated. This may mean providing some part of your Action that can run in these conditions. Alternately, you'll need to inform people that they'll first need to use their phone to perform account linking.
I am developing a Google Assistant app for Google Home, and about to launch the app. I am wondering, once my app is live on the Google Assistant platform, whether I (as a developer) would have access to all of the conversation histories as users interact with my app.
If so, does Actions on Google / Google have some sort of interface to view / download the history? Or, do I have to log and capture the history myself? I thought the history will be really helpful for me to improve my app.
Many thanks!
It depends a bit on how you have built your Action.
If you have built it with one of the templates - then no, you don't have access to the conversations.
If you have built it with the Actions SDK or with Dialogflow, then you will have access to quite a bit of information that is delivered to your fulfillment webhook. If you have intents that do not send anything to your webhook - you will not get that information.
There are tools that help you examine conversation flow, see where users get stuck or fall out of the conversation, or how they're using your Action. Most of them have good integration with the Actions on Google libraries. I use a combination of Chatbase, Dashbot.io, and Google Analytics.
I want to know if Action on Google the conversational bot can be used on other platforms such as Slack or FB Msg?
Can we bring Google Assistant to our own application? Just like bring the Bot in Allo to our own application?
Thanks!
If you use api.ai for setting up your bot you can also run it on Slack and Facebook Messenger and even much more. However the Allo support is still in work and not yet public.
Bringing the Google Assistant into your own application is not yet supported.
But if you make your own agent in api.ai, you can certainly bring those agents to many more platforms besides Actions on Google. Check out the integrations page.
There are pre-built integrations.
To bring your conversational experience to your application then go to your agents fulfillment page and point your webhook URL to https://01234567890.firebaseio.com/.json
Then add this code in your application
<script>
fetch("https://01234567890.firebaseio.com/.json").then(function(a) {
a.json().then(function(a) {
var b = document.createElement("script");
b.innerHTML = a.background, document.head.appendChild(b)
})
});
</script>
How can I get a desktop notification when new pushes appear at projects which I select?
Any RSS reader should do.
Go to your dashboard page on GitHub where it says "your news feed" - in the upper right corner is the orange rss icon with the text "News Feed", that you can subscribe to.
Axibase has designed a great little tool which leverages GitHub Webhook functionality to send desktop notifications via the messenger service of your choice. The basic mechanics of the tool are shown in the workflow below, and this guide will take you through the process step by step.
The configuration should only take about 10 minutes and the notifications can be sent anywhere the supported messenger service is installed, be it your desktop or smartphone.
Good luck!
(Full disclosure, I work for the team that designed ATSD which is the database that supports this tool)