bmercier

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

Hello Everyone, The maintenance is complete. When sending spokens to Google Home, if you get a PERMISSION_DENIED error, please unlink and relink with Universal Devices. That will solve it. Benoit

nathagt, This is an older topic, but just wanted to let you know that unlock by voice works with ISY locks. When you enable unlock, you need to enter a 4 digit code. When you ask Alexa to unlock, she will ask you for that code. Benoit

I see the account linking attempts, and everything looks good from here. I would suggest to either try with Amazon support or perhaps reset the echo. You could also try the following: Go to www.amazon.com Login Go to Your Account Under Other Account, click on Login With Amazon. If you see something relate to UDI, click to remove it. Benoit

I have no clue what the issue can be, but if you PM me your UUID, I will look at the logs and see if I can find anything suspicious. Please specify a date/time (with time zone) of a failed request. Benoit

Hello everyone, We will have a maintenance this Sunday 07-08-2018 at 5:00 AM PDT which will last for up to 2 hours. During this period, the subscription servers will be restarted, which will drop any active subscriptions. If you use Mobilinc, the app will automatically reconnect when it's back online. The main change is to introduce the new Google Home Report State feature. For now, these changes will not be visible. The Report State will send your device states to Google in real time, but only those for which you have created a spoken. This is similar to the Alexa Proactive State Report which is activated by the "Live Update" button. For Google Home though, there will be no toggle, it becomes active the minute the skill is enabled. Benoit

For GH, can you unlink and relink? Benoit

There has been no unplanned downtime for quite a while. Please open a ticket with your UUID(s), and the date/time of a failed request, and I will investigate the logs. Thanks, Benoit

Could it be that the set points are already to the calculated values? You could try asking for a different value, and see if they change. Or, it may be that Alexa misunderstands you and thinks you want to get the status. Please check in the web Alexa app, under settings | history, and see what she understands. Benoit Sent from my iPhone using Tapatalk