bmercier

Hello everyone, To be more specific, I've been told this morning that our skill was approved and instructions have been sent to the certification team to proceed, and as such, it may be live today. Benoit.

I'm being told that the behavior you are experiencing (not seing the skill in canada) is normal. That did not explain why I have access to US skills though. But anyhow, I was told our V3 skill is approved and is about to go live. It is available in canada. Benoit.

I have reported the issue to Amazon. Benoit

I'm located in Canada and can see the skill. It seems like you can't see US skills. I searched for a parameter that perhaps would prevent you from seeing them, but I could not find anything. I know that Alexa skills now can be enabled for English Canada. Our V3 skills which is coming out soon is. Our V2 skill did not have that option when it was released. Anyone else in Canada who can't see the skill? Benoit

You should be able to see the skill. Try this; Go to: alexa.amazon.com Click on Skills Search for "ISY" You should see "ISY Optimized for Smart Home V2" Benoit

Seno, The updating option in GH App, we have no control over that. The updating option in ISY Portal should work though. I'm not sure what the issue is. When we link, we also send a unique user ID to Google. Then, when using the update function in ISY Portal, we call a Google API and send that ID. The ISY Portal error message "Error sending your spokens. Is Google Home linked?" is the result of a google error indicating that the unique ID is not found (Which is an indication that the id used had not been linked, hence the message about the link). So, is this an ISY Portal bug? Possible. Is it Google that is loosing that reference somehow? Possible too. I will add some logging to find out for sure, and will ask to try again. Thanks, Benoit

When you unlink/re-link, yes. When only updating, it should not. Benoit

For now, rooms set in ISY Portal are not used by Google Home. It's useful only for you to categorize in ISY Portal. Eventually, this will be used by Google Home, but they don't use it yet. Benoit

Could you try to unlink/re-link? When we link, this sends a unique ID to Google. Then, when we synchronise, I pass that ID to Google. The error that we see happens when Google reports that it could not find the ID. Benoit

Yes, i think so. But with so many error reports, there may be an issue, I will investigate further. Benoit

Hi Michael, Please make sure to be logged it with the same ISY Portal user that you used for linking. Benoit

Jimbo, Seno, The email address used to login to ISY portal is irrelevant. In the Google Home App, when you link with Universal devices, you need to enter an ISY Portal user and password. When you want to sync in ISY Portal, you must be logged in using the same ISY Portal user and password. @Jimbo, room support, although available in the API, is not yet implemented at Google. I got a confirmation from a Google engineer. Whenever they support it, we will. Benoit

Seno, For GH, in order for the Sync to work, you need to be logged it with the same ISY Portal user profile used when you linked. If it does not work, there might be something else going on as several users seems to have issues too. For Alexa, you don't need Smarthome skill V3. For sure, you are not using it as it is not released yet. You are probably using V2. You can check in alexa.amazon.com, click on "Smart Home" then "Smart Home Skills". Benoit

Hi Seno, What is the error message exactly? No new spokens should not cause an error message. GH and Echo uses completely separate UI, APIs and database tables. Are you having an issue with Alexa also? Benoit

"Devices are not available" is related to the ISY devices lookup. When you choose to add a device from ISY, the list of available devices comes from that lookup. A typical case where you could see that is when you get into the Google Home spokens window, but ISY is offline. Normally, you can't get to that window if it the ISY is offline, but there is a delay before it is detected. Benoit

This message normally means that the ISY Portal user profile you are currently using is not recognized by Google Home. Are you using the same user profile that you used when linking Google Home? Could you try to unlink, re-link, then request a sync on ISY Portal? Benoit

This is fixed now. Thanks for reporting it. Benoit

Yes, PST. FYI, this is live now. Benoit

Hi Seno, I don't know what you noticed last week, but yes, this will allow to add or update devices to Google Home without having to unlink/re-link. Benoit

Hello everyone, We will have a small maintenance tomorrow 11-12-2017 at 5:00 AM PDT which will last a few minutes. During this period, no downtime is planned. Changes: In your Google Home spokens page, a new button will allow you to send your devices to Google Home. You will no longer have to unlink/re-link. With kind regards, Benoit

Hi Seno, What device did you try to turn on that did not respond? I see that you have only 3 devices for GH, and a lot more for Alexa. I see the device discovery for GH Worked, and I don't see any failed requests for any device actions Benoit

Please try again. There was a bug introduced recently that is now fixed. Z-Wave devices should now appear correctly. Benoit

What type of devices are they? Can you let me know what is the device address? Some device types are filtered.

Hello everyone, We will have a maintenance this Sunday 10-29-2017 at 5:00 AM PDT which will last 1 hour. During this period, ISYs will drop their connection from ISY Portal for a duration of anywhere between a few seconds to a maximum of about 2-3 minutes. There are no visible changes planned. The maintenance is mostly to apply security and stability fixes. With kind regards, Benoit

There must be other ways to say it. At the API level, I can assure you this is supported. Unfortunately, the speech recognition is not perfect, Benoit