bmercier

Quick tip: When you are on the A/V dialog, move you mouse over the field label. It shows a sample wording to invoke the action.

Suggestions: Try "Alexa, change input to <input> on <device>". This one is known to work. Try different input name. game works. Alexa can be picky on the input names, and it has to exactly match one of the inputs. Look at the history. Make sure she understood the input name like you intended. Benoit

That's the correct thing to do. The forget is optional. At first, you said you had unlinked and relinked, which you don't have to.

Live update is a different thing. All it does is open a permanent subscription with the ISY and sends device states to Amazon. It only sends the state for which there is a spoken. When a new spoken is created, it needs to be discovered.

Had you try to "discover" devices? When you add spoken on ISY Portal, they need to be discovered by Alexa. The easiest is to ask "Alexa, discover my devices". Benoit

Try with standard input names such as "game", "cable". Benoit

I'd suggest to expose the variable as a device instead. The added benefit is that a variable exposed as a device can have a brightness level which translates to the variable value. In other words, turning on the "variable" to 50% will set it to 50. Benoit

Just to be sure, are you using the same Amazon account for both echo? Or do you have a different one for both home? You need to have one per residence. Setting up a second residence is the same process as your primary one, but you have to have: Different echos for both homes (I assume you don't move them between houses) 2 Different Amazon accounts. One used for the primary residence, one used for the secondary residence. 2 Different ISY Portal user profiles. Each one must have the preferred ISY set to the appropriate ISY. They can both be in the same ISY Portal account. Then, when you link, you have to login to alexa.amazon.com using the Amazon account related to the residence you want to configure, and link to the appropriate ISY Portal user profile. Doing this should not affect the other residence if it uses a different amazon account. Benoit

What do you mean? An ISY is not "linked" to anything. An Amazon account links to an ISY Portal User profile, which is "linked" to an ISY (by specifying the preferred ISY). If you are referring to the "Amazon account linked to" box under "My Profile", please disregard. It is no longer used when using the V3 skill. Are you referring to the account linking when you enable the skill in the Alexa app? Benoit

Absolutely. Just to clarify, here's how things are linked together. If both homes have their own Echo and their own ISY, you don't even need sub-accounts. Echo A uses Amazon account A, which is linked to ISY Portal user A. This ISY Portal User A needs to have ISY A as his preferred ISY. Echo B uses Amazon account B, which is linked to ISY Portal user B (Can be in same account as ISY Portal User A). This ISY Portal User B needs to have ISY B as his preferred ISY. That's it. Benoit.

A variable is exposed to Google Home as if it was a dimmer. So as you already know, you can set it to a specific value by asking to turn it on to a specific percentage. You can ask something like: Okay Google, what is the kitchen brightness? This will tell you the actual variable value. This is not too intuitive, but it works. Benoit

No, there are no plans at this time. It's more complex to implement because a node has custom controls. Therefore, the AV UI would need to allow selection of the node, plus one of the valid controls taken from the nodedef. Perhaps if there are many users who requests it, we would revisit this feature. Benoit

Try to turn on/turn off the scene from the admin console. This is essentially what the echo does when turning on or off a scene. Benoit Sent from my iPhone using Tapatalk

When I tried again yesterday, somehow I had a sort of reCaptcha I had to enter, then it worked. Not sure why I had that. Initially, I though Amazon might have solved something. This behavior leads me to think it may be something related to the Amazon profile somewhere. This might be an issue with a cookie or cache too, but I doubt it because when it was not working, I had tried 3 browsers and experienced the same issue. I tried IE and Firefox, which I very rarely use. I think a support call to Amazon might help.

Oh, good to know Thanks, Benoît Sent from my iPhone using Tapatalk

I'm not sure that what you did helped. I had the problem. Retried many times. Then tonight it suddenly worked. I think Amazon solved something in the last few hours. Benoit

It seems to be working now. At least for me. @andersol, can you retry and let me know? Benoit

I tried it and I'm seeing the same problem. There seems to be an issue at Amazon. I'm contacting Amazon support. Benoit

Sure, that is possible Sent from my iPhone using Tapatalk

There has been no changes to AV for quite a while Sent from my iPhone using Tapatalk

You probably don't need ISY Portal for this. Given that the remote is probably on the same network as the ISY, I would suggest to directly connect to your ISY, and pass the credentials in the URL, if the remote supports it. Otherwise, perhaps an IFTTT recipe with a custom applet that has "IF" GET URL triggered "Then" Maker channel which connects to the ISY Portal inbound event. I don't know if there is an "IF" who could accept a simple GET request. Benoit

Not ideal, and may not work in all browsers. I'm not sure exactly what exactly what you want to achieve, but the idea of using an IFTTT inbound event is a great idea. I would look at a solution that involves sending a POST request. Perhaps a web page, CURL, etc. Benoit

That won't work from a browser - The HTTP method has to be a POST, not GET. Benoit

Oops, this is indeed for Alexa. Too much context switching So you were asking about the "open" and "close". We have no control over that. Alexa interprets the voice, and calls our API. Because she does not understand open/close, our API is not called. Benoit

There is an API to unlock the door, and it is already implemented. There is no API to allow the unlock. You have to go the the GH App, edit the device, enable unlock by voice, and choose a PIN. Benoit