I have a Raspberry Pi running Home Assistant (Hassio actually) and it is communicating with Google to make the lights go on and off using Google Assistant. To do that I have followed the cook book on the home assistant website. When Hassio updated from an API password to Oauth, I created a new project, because I had some issues with discovering devices.
In the current situation, when I ask Google to turn on the lights, it turns on the light, but also states that [lastprojectname] is not reachable. I did remove the project from the Google Actions console, but it does still show up in the Google Home app. I unlinked the account there, but still the same issue. So the old project is still in the linkable account list.
When I ask Google to turn on the lights in the 'office' (for example), it states, 'OK turning off 4 lights' while there are only 2. The lights are not in the app anymore, the account is not linked. Very weird. Any ideas?
This happens to me some of the time (I'm also using Home Assistant, but just starting with Google Assistant integration). When it happens, I just link, and then re-unlink the app. It usually sticks the second time.
I know that's the equivalent of "turn it off, then turn it back on", but it works, and I don't have a better solution :|
Related
We've been having trouble keeping Wonder available on Google Assistant and Home. We keep resubmitting and then find out there's some bug that gets us taken down.
One thing that has made it hard is that we cannot test Wonder in the simulator in the Actions Console. Here is what a session looks like: Wonder test session
When I expand the last message I see the following error: Cannot use standard Google Assistant features in the Simulator
Is there any way you could help us get this fixed?
The Google Assistant available in the simulator has a subset of the features of the assistant available in your phone or Google Home device. If you want to use the entire set of voice interactions, please use the assistant on your physical devices. If you want to test your smart home action, you can use Test Suite.
Also note that Google Home projects do not support dialogflow anymore. I see you have the dialogflow-es-fulfillment tag in your project. If your project is set up as a dialogflow project, you might need to set up a new Smart Home project on the actions on google console.
In my developer account, I can succesfully test the app using the simulator.
I also sucessfully deployed an Alpha version, and waited 24 hours.
However the opt-in link doesn't work. Every time I navigate to it, I see:
We can't find what you're looking for at the moment. Please try again later.
YES, I have the activity controls all enabled
YES, I have a google home device connected to this account
YES, I am the developer of this action, and have verified permissions
in IAM
This is driving me bananas. Does anyone have any suggestions on how to get it to appear?
The problem is that I was not opening these links using Google Assistant (I was trying to open them using Safari). The documentation says "open on mobile", but it doesn't tell you to use the Google Assisant.
If you have iOS, make sure you download Google Assistant!
I know this is an old question, but for the past few days I have been in the same situation with no answers to be found on the internet.
The situation is represented in the image below:
My opt-in link was the following:
https://assistant.google.com/services/a/uid/uuid?hl=en
Removing the trailing ?hl=en at the end of the link worked for me.
The Action's settings have become available via the link https://assistant.google.com/services/a/uid/uuid?hl=en after Alpha deployment.
Still, the Action doesn't look good in the Actions explore menu and settings button is missing.
I accidentially moved to the new Actions on Google dashboard. Since then my project does not really work anymore.
I changed the json structure and uploaded a new version that is now running fine on the simulator.
Unfortunately, my Google Home device is not recognizing that such an action exists. This was working before when using the old actions on google api.
Ciao
Fabio
The invocation name has changed when testing apps on the Google Home device.
You should now say
Talk to my test app
I had implemented leaderboard in google play store console. But after implementing when I see the play store console it shows:
One or more APIs that are required for game services to work have been turned off in the API console. We recommend to turn them on again to ensure your game is working properly.
Also the leaderboard not working.
I had this same issue, and when I clicked the Turn APIs button back on, it would show the error again after a page refresh.
I got in contact with Google and they said that a few other developers were experiencing this issue and that they would email me back once they had made progress finding out what's wrong
Now then - because this all happened around the time I was re-linking a project into Google Play Games Services, I thought I had messed something up. Being restless I decided just now to create a new keystore file, and generate a fresh SHA-1 fingerprint. I was able to enter the newly generated code on the API Manager console, under the Credentials tab.
For some reason, it worked; I am now able to sign via Google and access the high-scores page.
Might be worth a try?
Our company designs museum and visitor center exhibitory, and my main job is designing touch screen kiosk applications. Enamored by Vidya's introduction to Kiosk Apps using Chrome boxes, I quickly had my boss procure one for testing. I have since gained a firm grasp of Chrome App structure going though Google's tutorials (manifest files, MVC, etc) and have found the performance of our little HP Chromebox plus HTML5 development to be pretty impressive. I'm developing on my Macbook using Chrome Canary to run and test the apps.
I'm adding in this background information so you can better understand my goals. We of coarse need these apps to launch full screen upon power up. No login or user installation is desired. I prepare the boxes in my office, install them at the exhibit, the end. We certainly don't want our multimedia apps to be sitting up on the Chrome Web Store for others to download and install.
So, I've gotten to the point where I want to install a simple kiosk app on our HP Chromebox. Unfortunately Vidya did not go into detail on this part. The page from her article only touches upon adding kiosk_enabled" : true to the manifest file.
So here's what I've tried so far: I've moved my app folder onto an SD card and moved it from there onto our HP Chromebox into the "Downloads" folder (apparently the only folder). I sign into Chrome Browser on the box with my company account (do I have to do this?) and load up chrome:extensions. I click "load unpacked extension..." and select my app folder. The app installs and I am able to manually launch it by clicking "Launch". Next, I click the "Manage kiosk applications..." button and enter the app ID into the field. This is where I get stuck. Clicking "Add" produces an "Invalid Application" error.
Looking around the web I have found lots of confusing information:
I must "Wipe" the Chromebox in order to use a Ctrl+Alt+K key command to truly enable kiosk mode. (Google's instructions on how to do this stops with Samsung and Asus 'boxes, I have an HP, not to mention the "Manage Kiosk Applications" button is already visible to me).
I must upload my App to the Webstore as either public or unlisted, and then download and install it onto my Chromebox. Really? I don't want to sell my app or make it available to anyone. It is only meant to run in our exhibit. Our apps could be gigs of data with HD videos!
I must make my Chromebox "Managed" or "Enterprise" or "Enroll" it for Work and Education Administration. In most cases, we'll be installing one or two of the 'boxes to allow users to navigate though static HTML pages. I don't have a need to manage a fleet remotely (at least not yet). So, the aforementioned complications seem unnecessary, and expensive if I understand things correctly.
Can someone point me to the definitive process for achieving my goal of an auto starting, full screen kiosk application on my Chromebox?
I'm not an expert on this but kiosk apps are defined by "kiosk_enabled": true in manifest.json. What's important to know, though, is that from what I've seen they can work in three different modes:
If they are installed as an unpacked extension (for example, in development) they will be available as apps in your logged in environment and run but full screen mode. They're essentially "normal" apps except that they are full screen.
If they are installed using the "Manage kiosk applications..." button then they are available without logging in. On the log in screen at the bottom you'll be able to see the app and click to start it without logging in. However they won't start automatically. AFAIK you also can't load an unpacked extension in this way.
If you enable "kiosk mode" for Chrome OS then you can make kiosk apps auto start. At least on the Asus CB you do have to do the CTRL-ALT-K keystroke BEFORE you log in for the first time. This is for an unmanaged device. Now, when you load the app using "Manage kiosk applications..." in chrome://extensions and hover your mouse over it in the dialog you should seen a "enable auto-start" or similar button. You need to select this. Now, when you restart the system the app should automatically start. If you want to cancel this just as the app is loading you can press CTRL-ALT-S. A message indicates this on the screen, too.
Hope that helps,
Simon
Can't help you with anything related to kiosk, but you can generate a CRX file from the Extensions page on your development system, get that onto the Chromebox, put the Extensions page of the Chromebox into developer mode, and then drag the CRX to the Extensions page and drop it. You should see a dialog asking you if you want to install it. This is a completely different form of install than loading an unpacked extension and may get around whatever limitations you're seeing.
UPDATE: (1) Extensions page on Chromebox doesn't have to be in Developer Mode, (2) CRX to be dragged must be in the Downloads directory, not on Google Drive. Didn't test external device (SD card or USB drive).
In order to add your app from Manage Kiosk Applications, you will need to publish your app to the Chrome Web Store. If you don't want your app to be public you can publish it as Unlisted, which means that anyone with the link can install it. Unfortunately, if the app is published as Private you will not be able to add it as a kiosk app. [source]
Beyond that, the only thing you need to do to create a kiosk app is to include "kiosk_enabled": true in your manifest.json file.