bmercier

Thanks for the detailed write-up. I think what may have fixed your problem is what you disabled on Login With Amazon. For others who may have the issue, here's how in more details: Login to www.amazon.com Go to "Your account" Under Other Accounts, click on "Login with Amaxon" Disable anything related to ISY Portal. If anyone has this problem, please try this to see if it helps. It must be that you were using the Smart home skill "ISY Optimized for Smart Home", commonly called V1. The ISY Custom skill is something else, and it does require "Tell ISY to..." This is the root cause of the duplication problem. Even without a skill enabled, doing a discovery still makes a discovery call to ISY Portal, in the V1 format. It's like there's a shadow skill still enabled. Those with the (device) are the good ones, coming from the V2 skill. Hopefully this will help others. Benoit

A room is simply a group of devices. I would suggest to simply not assign those devices to the room. ISY Portal does not know which ones are lights or not. A user let's say with an IO linc may want it to turn on and off like the other devices in the room. Same goes for scenes, programs and state variables. Benoit

Sub-accounts will still be required. ISY portal user profile in those sub-accounts will still be required. However, the ISY portal user profile will no longer need to be tied to an amazon account in "My Profile". The Echo relationship will only be from the Echo smart home skill to ISY portal user profile directly. Benoit

Here's the mapping: Echo <-> Echo is tied to an account <-> ISY Smart Home skill is linked with same or another Amazon account <-> ISY portal user profile is tied to the amazon account of the smarthome skill <-> ISY portal profile is in an account/sub-account <-> Spokens are tied to an account/subaccount Now if you want to support multiple echo, all of the above need to be unique for each echo, except for the amazon user profile the echo is tied to (second item in the list) The next version of the Smart Home skill (V3) will be simpler, as this will be: Echo <-> Echo is tied to an account <-> ISY Smart Home skill is linked with an ISY Portal user profile <-> ISY portal profile is in an account/sub-account <-> Spokens are tied to an account/subaccount So in V3, you will no longer need multiple Amazon accounts. Benoit

Yes you can do that with ISY Portal. However, with the current smart home skill version (V2), you need to have as many Amazon accounts as you have echo. All of your echos can use the same Amazon account, but when you enable and link the skill, you need to provide and Amazon account which needs to be different for each echo. On ISY Portal, you need sub-accounts with a user profile which is mapped to the corresponding amazon account. In V3, this will be simpler. Each echo, when enabling the ISY smart home skill, you will be able to map it directly to a corresponding ISY user profile (each in their own sub-account). Benoit

Thanks for the details. Re-adding the ISY will not help. I looked again at the logs this morning, and it clearly shows that there are multiple calls to the API for each device discoveries. I also see traces of the Smart home V1 skill. This is why devices are doubled (V1 and V2 deviceIDs are different, so they are treated as different devices by Alexa). We will need to report this to Amazon for further investigation.

This is really really strange. Looking at the logs, I can see pairs of requests that are very close together, less than a second. It's for your ISY, for your account. It's a different messageId generated by Amazon. Is it possible that the skill V1 is still enabled? Please disable all smart home skills, then enable "ISY Optimized for Smart Home V2"

With the help of your UUID, I was able to trace the logs. The discovery does return 6 devices. Are you sure that you did a Forget all devices? Do you still have the issue? Benoit

IFTTT events are ISY specific. They are not sub-account specific like the echo is. So what you are seeing on ISY portal is by design. Now, are you trying to trigger the same event name from different echo to trigger different things? If so, I believe you will need an IFTTT account per echo. You can create all of your IFTTT events on ISY Portal all in the same place. Then, in IFTTT, each of your events in every accounts will need to map to an ISY Portal IFTTT event. Benoit.

These problems are now fixed and will be part of the maintenance release tomorrow morning. Thanks for reporting them! Benoit

This is in our roadmap. Sent from my iPad using Tapatalk

Thanks for the detailed description. Which browser were you using? Benoit

Hello everyone, We will have a maintenance on Sunday 07-16-2017 at 5:00 AM PDT which will last 2 hours. During this period, the ISY Portal node server is expected to be down for a few minutes which will be affecting those using the Node Server Occupancy module. Enhancements - Node server security enhancement: ISY to ISY Portal Node server will now use a new Node Server key instead of the ISY Portal user credentials. Fixes - Other ISY Portal servers operating systems will be patched, but no downtime is planned. The change to the node server is backward compatible. If you are already using the node server, it will continue to work as is. In order to increase security, after the change, you can use Select Tool/Node Server/Configuration and click on "Configure connection". This will enable the new communication method. You will not lose your occupancy configurations. With kind regards, Benoit

ISY Scenes are shown as devices in the Alexa App, this is normal. Also, each spoken variations you entered will result in an individual device in the Alexa app. This would explain why you have 28 devices instead of 8. If you want to reduce it to 8, keep only one spoken per scenes. Benoit

Good question. I looked at the logs, searching specifically for device discovery requests. Those are sent every hour or so for every ISY. I can see erratic request for about 5 hours, and definitely 2 major drops in that period. I don't see spikes after it recovered. It may be that device discoveries were blocked before hitting our lambda function. Benoit

Are you using your ISY Portal username and password?

It's not possible. A smart home skill has a finite set of utterances which only Google can control. You need another scene or a program with a "tricky" name.

My apologies, you're right, we can't set a value to a scene. Benoit

Alexa does not have something like fast on utterances. However, you could ask to turn on to 100%. That should work. Alternatively, you could also create additional scenes, or even programs that would do a fast on on your scene. If the scene is complex, you may want a program instead of duplicating the scene. Benoit

Find the program ID in the admin console, then type it in the search box in ISY Portal. I think that you may once had a program with that same ID entered in the spokens. If you delete that program from the admin console, and later on create another one which would reuses the same ID, you would observe this behavior. Benoit

I don't know much iRule, but you seem to be doing it right. I think the issue is that it is trying to do straight HTTP over port 443. You need to use HTTPS. This is an excerpt from the support page: If your IP address or URL require Secure socket connection, you simply put HTTP:// in front of the IP address or URL (https://192.168.0.69) Benoit.

You can do the following; Boomark https://my.isy.io On the login: Click "Remember me", so you don't have to login anymore Instead of clicking on "Portal Login", click the down arrow and select "Go to my ISY". This will bring you directly to the UDAjax page. This preference will be saved for the next time. NOTE: You need to set your preferred ISY under My Profile for this to work. Benoit

Unfortunately, it's not possible to brighten/dim scenes with Google Home. The Google Home API only allows to set an absolute brightness, which cannot work with a scene. You may notice that you can brighten or dim a regular light, but under the cover, GH determines what the absolute level should be and sends that command. Benoit

Yes, but they will use the same spokens, just like if you have 2 echos. You will probably want to use sub-accounts to have different sets of spokens. Sent from my iPad using Tapatalk

Hello Dave, This should be working. We can investigate the logs in order to see what's happening. Could you open a ticket with the following information: UUID Program ID (You can see it in the programs lisy, in the far right column) ISY Portal User profile Date and time of your test, and please specify time zone. Thanks, Benoit.