bmercier

Hello everyone, We will have a maintenance release this Sunday 12-03-2017 at 5:00 AM PDT. Unfortunately, we will have a downtime period of up to 2 hours. Maintenance - Add resources to all servers (Memory) - Update SSL Certificates New features - Amazon Echo Smart Home skill V3: Add ability to expose Scenes/Programs/State variables as either, a Scene or a Device (Light, Switch or Outlet). - Google Home Home Control: Add ability to expose Scenes/Programs/State variables as either, a Scene or a Device (Light, Switch or Outlet). Benoit

Hello everyone, We will have a maintenance release this Sunday 12-03-2017 at 5:00 AM PDT. Unfortunately, we will have a downtime period of up to 2 hours. Maintenance - Add resources to all servers (Memory) - Update SSL Certificates New features - Amazon Echo Smart Home skill V3: Add ability to expose Scenes/Programs/State variables as either, a Scene or a Device (Light, Switch or Outlet). - Google Home Home Control: Add ability to expose Scenes/Programs/State variables as either, a Scene or a Device (Light, Switch or Outlet). Benoit

I reproduced the problem. In the GH App, go to one of the 2 accounts, and disable the skill. It should not be enabled on both accounts. I think this is an edge case Google should detect. But the easiest for now is to activate Smart Home on only one of the 2 accounts. Benoit

Seno, This message appears, because of a specific error returned by Google: {"error":{"code":400,"message":"Request contains an invalid argument.","status":"INVALID_ARGUMENT"}}. By experimentation, the only case when this would happens is when Google Home does not recognize you (actually, the unique userId I'm sending). BUT, I looked at the logs and found something interesting. Following the SYNC request from ISY Portal, I see 2 syncs happening, after which the SYNC request from ISY Portal fails with the above error. Do you have 2 GH linked to the same ISY Portal user profile? I think the sync is actually working, despite the error message. Can you check if your new devices are indeed available in GH? If this message is caused by having 2 GH linked, I have to speak to Google. I may need to detect that, and not give an error to the user when it is actually working. Benoit

Seno, I have personally never seen that option in the the mobile app. The supported way to send spokens from ISY Portal to Google Home is to use ISY Portal. In the ISY Portal Google Home page, there is a button to send spokens. Benoit

Location specific requests like asking an Echo "Alexa, turn lights on" works with Alexa groups. As you guessed it, you need to have a group that contains your echo device, and the related lights. Now, all that allows you to do is to turn them all on or off. "Alexa, turn lights off" will turn off the light devices from that group only. Currently, there is no way to have the same spoken recognized using different groups. Whenever you request to turn on/off a specific device, the scope is not limited to the group the Echo is in. As an example, if you ask "Alexa, turn off bedroom", it will turn off that device, regardless of the group the device is assigned to, and regardless of the group in which that echo is. Benoit

Yes. Presently, scenes/programs/state vars are exposed as switches. The next update will allow you expose scenes/programs/state vars as either a switch or a light. Benoit

We are currently waiting for Amazon. Updates are sent to Amazon in real-time, but are not shown on the app. Benoit.

Yes, this is coming soon. Benoit

I'm aware of 2 limitations currently with Scenes; - When you say "Alexa, all lights off" (or on), it will only turn off regular devices, not scenes. - You can't turn off scenes in Routines. A work-around for the first one is to use an Alexa group, which does support scenes (On and Off). The second one is more annoying, I'm still waiting for Amazon. I'm not sure if a fix for the app is coming or not. If it does not, your suggestion is a good one. Benoit

In order to support multiple Echos with different spokens in each, you do need to use different Amazon accounts, one per Echo. Here's an example: 1. Amazon Echo A, using Amazon Account A, linked to ISY User Profile A, which is in a sub account with contains your first set of spokens A. 2. Amazon Echo B, using Amazon Account B, linked to ISY User Profile B, which is in a different sub account with contains your second set of spokens B. 3. Amazon Echo C, using Amazon Account C, linked to ISY User Profile C, which is in another different sub account with contains your third set of spokens C. On ISY Portal: You need a sub-account per Echo, with one ISY User Profile in each. Note that you can use your root account for one of your echo. You can edit your spokens by first selecting the sub-account, then use Select Tools/Connectivity/Amazon Echo. In the Alexa app: When you are logged in to the alexa app using Amazon Account A, you should only see your Amazon Echo A. You then enable the ISY Optimized for Smart Home V3 skill. When you do that, you may be prompted for your Amazon Account A first if you have been inactive for a while. If you do see the ISY Portal login, use your ISY Portal User Profile A. You need to do the same for Amazon Account B/ISY Portal User Profile B, and then Amazon Account C/ISY Portal User Profile C. My apologies everyone for the confusion I caused. Benoit

No, you don't. Your 2 echo can use the same Amazon account. When you enable the ISY skill in each, just link them to a different ISY Portal user profile. Benoit

Michael, Please try again. I just fixed something related to self-registration. Benoit

In ISY Portal, you can configure a virtual A/V device. On that virtual A/V device, you assign network resources to Alexa functions like "Play". Benoit

Please open a ticket with your UUID and a reference to this thread, or just PM me your UUID. Thanks, Benoit.

Stu, Make sure the user you created is an account admin. It will be an admin within the scope of the subaccount only, and therefore, will be able to add spokens. Here's the data relationship: Echo Smart Home Skill V3 -> Linked to ISY Portal user profile -> within an account -> ISY in that account -> Spokens belong to an account/ISY combination So: - Echo has the V3 skill enabled, which is linked to a user profile. - That user profile is within an account (or sub-account) - That account must have at least one ISY with an approved status. If there is more that one ISY in that account, the user's preferred ISY is used to identify which ISY to use. - Spokens belong to the ISY/Account combination Tip: To manage the spokens for that sub-account, you don't have to login with the user profile in that sub-account. A user profile in the root account has the right to edit spokens in sub-account. Just make sure to select the sub-account before editing spokens. Benoit

You no longer need multiple accounts, unless you want your echo in different accounts. With V3, when you link your echo ISY smart home skill, you link it to an ISY portal accounts. With V2, you were linking the ISY Smart Home skill with an Amazon account, which had to be set on an ISY Portal user profile. In other words, with V3, the account linking is direct. Benoit Sent from my iPhone using Tapatalk

Make sure your preferred ISY is set on "My Profile". When you enable the skill, you need to enter your ISY Portal user and password. Does that work fine? FYI, with V3, you no longer need to set the Amazon account in My Profile. Benoit

Please give us some feedback when you have played with it Benoit

Good catch. The exact way to ask is: "Alexa, change input to game on <device>", device being the spoken assigned to your virtual A/V. All Alexa A/V commands ends with "on <device>", except for turn on/turn off. So a sequence could be: Alexa, turn on tv Alexa, turn on home theater Alexa, turn on dvd player Alexa, change input to dvd player on home theater Alexa, increase volume on tv Alexa, play on dvd player Alexa, pause on dvd player Benoit

Yes, V3 is required. Benoit

There are 2 ways. If you want to run a sequence of event, Paul's approach is best. If you want to want granular control through Alexa, use the virtual A/V device. To do so, just click Add | A/V, then map your AVR commands. The last tab is used for the input select. For the input select specifically, you can map up to 8 inputs. As an example, under input 1, choose "Network resource", then select your network resources that changes the input to let's say "Game", then give that input a name: "Game". When you say "Alexa, change input to game", this will run the network resource. The virtual A/V does not have a concept of zone. However, you can create several A/V devices, one for each zone. Benoit

This has just been submitted to Amazon. ISY Programs are exposed using the "Alexa.PowerController", under the scenes category; This means that the On and Off should be available to routines IMHO. Benoit

The behavior you are experiencing with V3 is as expected. When in Auto mode, requesting a specific temp will set both the heat and cool setpoints. If in Fahrenheit, the deadband is 5 degrees, with heat being -2 and cool +3 from the requested setpoint. Those were the Amazon recommended numbers. As an alternative, I would suggest to: - Ask Alexa to increase temp by 2 degrees, which will increase both setpoints (just like in V2) - Set the mode to Heat or cool. When requesting a temp, the appropriate setpoint will be set accordingly. In Auto mode, I understand that a 5 degrees F deadband is a bit high. perhaps we could reduce that to 3 (-1 and +2) or 2 degrees (-1 and +1). But for sure, to be consistent with other Alexa enabled thermostats, Amazon is expecting our skill to work that way. We would not have passed certification otherwise. Benoit

Here's the updated changes: https://forum.universal-devices.com/topic/22951-v3-skill-new-features/ Benoit