bmercier

There is no notion of rooms in the smart home API. That was initially developed for Google Home, when the same UI handled both Echo and Google Home. This was left only for convenience or organizing the spokens. Amazon can handle rooms using groups. Using groups in V2 was not recommended. In V3, it's slighty better. It's still multiple API calls for as many devices as there are in the group. But the API now allows for "aysnchronous responses", and our implementation is able to detect the use of groups and handle delays properly which prevents triggering alerts. But still, turning off 30 lights at bedtime will take time to complete. A program or scene would be much faster. Benoit

The new Smart Home skill is developed. At this point, we are entirely dependent on Amazon. It may take a while still. Benoit

In ISY Portal, at the top right, you can click on "My Profile". It's just beside "Logout". When My profile is open, just click on "Link this profile to an Amazon account" Benoit

If you previously had the ISY Smart Home V1, and just swith to V2, some users have reported having an issue where devices were duplicated. It is the result of Alexa discovering the V2 devices, but somehow, also requesting the V1 discovery. After a "Forget All" and a fresh discovery, do you seem to have such an issue? Are they doubled? Are you missing devices? Benoit

The account linking works differently with the echo. In ISY Portal, under "My Profile", you need to link with an Amazon ID. Then, when enabling the ISY Smart Home skill V2, you will get an Amazon login page; you need to enter the same Amazon ID as above. Note that the upcoming ISY Smart Home V3 linking will be just like Google Home. When enabling the skill, all you will have to do is enter your ISY Portal credentials. Benoit.

Hello, There's unfortunately no plans to implement an import functions at this time. It's a lot more complex to do an import, than a simple export like this. Benoit

Yes, you should disable the ISY skill. There is no real need for it anymore. All you need is the ISY Optimized for Smart Home V2. (Or soon V3) However, this is not the source of your problem. Can you control your devices from the admin console? What do you have in the echo app? Do you see devices offline? You may want to click on "Forget all devices", and redo a discovery ("Alexa, discover my devices") Benoit

Hello everyone, We will have a maintenance this Sunday 10-22-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

Unfortunately, no.

Anytime Benoit

>One last thing, when you update the portal and refresh, then refresh within gh app, how long does it take for gh to update its responses? It's immediate. >I only ask because I’ve replaced the work lamp with lights and gh still responds “turning off living room lamps” but the word lamps is no where to be found. Not in spoken or device names. You do have a "living room lamps". This is one of your alternate spokens for the scene 50565. In ISY Portal, use the search. Type "living room lamp", and edit the entry. Benoit

> QUESTION: Within UD in GH app, are the devices my spoken words? In Google Home, all you will see is the spoken. > Also, I do use the assign room feature. Would this cause an issue? It depends on your chosen device and room names. If you have a room named "Living room" you can turn all the lights in that room by asking "Alexa, turn on the living room lights". Now, what if you have a device named "living room lights"? I'm not sure what GH would do, but I'm guessing one would have precedence over the other.

The name of the ISY scene that you see in ISY Portal is the one sent to GH. The ISY scene name is the one that you had for that scene when you added the spoken. It is not refreshed unless you delete the spoken and re-add it. Now, I would try to change the spoken and see if GH understands it. The issue is that if you have a room named 'living room' enabled, then asking 'Alexa, turn on the living room lights' would be used to turn on all the lights in that room. I would bet that the room is enabled, with no devices in it. Either way, please try a different spoken. Thanks, Benoit Sent from my iPhone using Tapatalk

Currently, in ISY Portal, I'm seeing the following spoken "living room lights" with alternate spoken "living room", which is currently mapped to scene 50565. I can see that this ISY scene was once named "All LR Lamps" but is now named "All Livingroom Lamps". That name does not really matter though. What matters is that the spoken "living room lights" is mapped to scene 50565. In the device SYNC, I'm seeing that this is what is sent to Google Home. Now, are you saying that "living room lights" in Google Home is not controlling scene 50565? What scene is it controlling? Benoit

Hi, I looked at your ISY Portal spokens. I do see your "living room lights" under "ALL LR Lamps" ISY Scene, Could it be that you deleted the scene, but left the spoken in ISY Portal? I don't see your "all living room lights" (Although there is one close, "living room lights") There may be some devices with a room name GH may not like, if you are using rooms in GH. It may confuse a device with a room. I don't think you need to reset everything. But I think it would help troubleshooting if you had less devices configured in ISY Portal. Benoit

Do you know what resolved your duplicate device issue? Benoit

After investigation, it appears that the device SYNC are working correctly. The device "living room" is not returned by the device SYNC. I suspect that there may be 2 Google accounts involved, one for the initial SYNC, and a different one now. I would recommend a factory reset of the Google Home. A more detailed response should follow on the ticket. Benoit

@JSP0155, please open a ticket referencing this thread, and let us know your UUID. I will investigate and see what we can find in the ISY Portal logs. Thanks, Benoit.

I did not notice the announcement, but I can tell you that at the API level, there is nothing related to rooms or grouping. Grouping can be done, but it will result in multiple independent API calls, just like it is now. This means that every lights will turn on or off in sequence, and it can take a while if there are many. The only difference with V3 regarding groups is that in V2, this triggered alerts as the response to each API calls were taking too long. This is why it was not recommended. In V3, there is a concept of deferred responses which helps handle such use case. There will be no more errors. On the end-user side, the experience will be almost identical, in other words, it will still work. Benoit

Other than using the new Smart Home V3 API, the main features are: 1 - Proactive state update; this will allow to see the state of your devices on the echo mobile app, in real-time. This requires the live update to be active. 2 - A/V Support 3 - Color bulb support (Aeotec, Fibaro) 4 - Thermostat an be turned on (to the previous heat/cool/auto mode) 5 - Slow devices like lock will no longer return an error, unless it's very long. 6 - Locks will tell you if the lock is Jammed, or if the battery is low. Benoit Sent from my iPad using Tapatalk

It will support any A/V device that you can control from ISY. If you look in ISY Portal, Select tool, Amazon Echo, add A/V, you can see how the mapping works. For every Alexa A/V commands, you can map to a network resource, state var, or program. Benoit Sent from my iPad using Tapatalk

The infrastructure is in place to receive subscriptions and dispatch this to push services, but other that proactive state update for smart home skills in V3, there is nothing else in the roadmap for now. Benoit

Thanks for the update. I'm glad to see the problem is resolved!

Exactly. This is developed and we are currently getting into the certification process. If you look carefully, you will also see a new "A/V" Button. This is also a V3 feature. This can give you a good idea of this upcoming feature. Benoit

Ok I found it. I did not realize you were trying to add it for Google Home. I was testing it for Amazon Echo, where it worked. This is now fixed. Benoit