bmercier

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

Our Alexa Skill V3 was just released earlier today. Here's the main features & changes 1 - Proactive state update; this will allow to see the state of your devices on the echo mobile app in real-time. 2 - A/V Support 3 - Color bulb support (Aeotec, Fibaro) 4 - Slow devices like lock will no longer return an error, unless it's very long. 5 - Locks will tell you if the lock is Jammed, or if the battery is low. 6 - Thermostat behavior in Auto mode is completely different. Proactive state update: This will require the live update to be active. When you go to your Amazon Echo device list, make sure to enable the "Live update". NOTE: This is not working at this time. - Stay tuned. Color bulb support: When you have a Z-Wave color bulb, you get 2 Z-Waves devices in ISY with an address of ZW999_1 and ZW999_186. If you intend to use colors with Alexa, please use the device ending with _186 device in ISY Portal. Thermostat Auto mode behavior: When in Auto mode and requesting a specific temp, the V2 skill attempted to change the appropriate setpoint. Now the V3 skill will change BOTH setpoints, one below the requested temp, one above the requested temp. How to enable the new skill: In order to use the new skill, please disable the V2 skill, forget all devices, then enable the V3 skill and discover your devices. Otherwise, your devices will contain duplicates.

We are entirely dependant on Amazon at this time. I believe it's a matter of hours before the V3 skill becomes available. We could also enable the V2 skill for Canada, but a change to the skill would have to go through the same process, so it would not be faster. Benoit

I use both, but I don't think it matters. I believe the issue is something on the user profile which identifies if it's a canadian or american user. I don't know if that could be a reason, but I have a ship-to address in the US (A cross-border service address). Benoit

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