bmercier

Could it be a valid error this time, where there is really a spoken of that name? Please use the search to see if that spoken is already used or not. If it is not used, and it still does not work, please PM me your UUID along the spoken you are trying to use. Thanks, Benoit.

Hello All, There was a bug introduced yesterday which affected programs only, as rehills pointed out. This is now fixed. Benoit.

Multiple echo with different spoken for the same device is now supported. This is achieved by having 2 echos linked to 2 different Amazon accounts linked to 2 different portal user profiles in 2 different portal accounts (or sub-accounts), which each their own set of spokens. As of today, the same ISY can have a different set of spokens when it is registered in different accounts (or sub-accounts). In details, you need to: 1. Have your echos tied to 2 different amazon accounts. 2. In portal: - Create a sub-account - Add you ISY to this sub-account, and approve access to it in the admin console. - Create a user profile in this sub-account for the second echo - Link this user profile with your second echo's amazon account. - To edit spokens for your second echo, switch to your sub-account first - To edit spokens for your first echo, switch to your root account first Of course, you can have as many echo as you want, with each their own sub-account, user profile and set of spokens. Also, it is not required to have a primary echo in the primary account. All echos could be managed in sub-accounts only. For those of you who already had sub-accounts, you will start with the same spokens in each accounts/sub-accounts for all of your echos. When you add/edit/delete your spokens, the change will be applicable to that account only. Including the Delete all. NOTE: If your account selector is set to [All], you will see all of your ISYs, no matter which account/sub-account they belong to. When an ISY is in several account/sub-accounts, you will see it only once. When you edit your spokens, without explicitly choosing the account, you can't be sure of the context of which account you are working on. You should switch to the intended account first. Benoit.

No no, just this time. The only case where you may want to "forget devices" is if you remove spokens. Either if you remove a complete device with it's spokens, or if you remove some spokens on a device. In this case, they will be left in the list of devices. You may forget them individually, or forget all devices before doing a discovery. If you simply let's say change an alternate spoken to something else, it will keep the sequence number and it will be updated in the CoHo device list.

Devices imported through the discovery process gets assigned a device ID. Previously, the device ID was simply the address of the device/scene/program. Device IDs needs to be unique. Thefefore, with the introduction of the 5 spokens per devices feature, each devices IDs now have to have a sequence number. Bottom line, yes, there will be duplicates if they are not forgotten before.

Exactly. Sent from my iPad using Tapatalk

Looking at the logs, I see that some are trying to set an absolute level on a scene. That is not supported. You can Dim, you can brighten, but you can't set to a specific percentage. You cannot say: Alexa, turn on <scene> to <percent> Alexa, brighten <scene> to <percent> Alexa, dim <scene> to <percent> You can say: Alexa, brighten <scene> Alexa, dim <scene> Furthermore, with Alexa, you can say: Alexa, brighten <scene> by <percent> Alexa, dim <scene> by <percent> That will work for devices, it will increase the percentage by the percent you said. However, in the case of scenes, it will brighten or dim, but it is fixed to 3 x DIM and 3 x BRT. (+/- 9%). The percentage spoken is ignored. Benoit.

I looked up in the logs. For some reason, I see it dropping off and trying to reconnect around 12:35 EST. But then, on the /rest/whoami request (portal requests that to know who is connecting), there is a timeout. ISY does not respond. It has not tried to connect. Could you reboot the ISY? Benoit.

Yes, that's the only way.

https://my.isy.io Benoit.

Do you see it online on portal? Benoit.

Is this with the skill, or connected home? Is this with an insteon device, or zwave? My hypothesis was that this was an insteon device. At the rest API level, insteon devices work on a scale from 0-255. Therefore, I though this could be a rounding error. However, I tested both connected home and the skill with a request for 70%, and both showed correctly in the admin console at 70% after the command. You may want to try this rest command on your ISY: http://<your isy ip>/rest/nodes/<your device address>/cmd/DON/178 178 is the value that alexa will use for both connected home and skill, when you want to set an insteon device to 70%. See if this reports to 70% in the admin console. Benoit. Absolutely. Just trying to be concise.

Exactly Benoit.

Amazon Connected Home simply does not have the capabilities to do that. All that we could do today is map "Turn on" to increasing temperature or "Turn off" to do the opposite, but that would not be intuitive. Benoit.

Let me clarify this one. The skill works with the spoken entered on portal. Only those, and all of those. The connected home discovery process (The discover devices button) will import all of the spokens from portal, except those not supported (thermostat and locks). Benoit.

Yes. A fixed quantity of 5. Update: I misunderstood what the question was referring to. The answer is "Gone". The list of devices, or programs, will contain only those that have not been used yet. Benoit

Hi Stu, Then, I really have no clue why. I found your last discovery in the logs: 2016-02-02, 22:11:59 - info: Lighting API: <your IP> DiscoverAppliancesRequest uuid <your uuid> <your portal login> 2016-02-02, 22:11:59 - info: Lighting API: <your IP> 148 devices discovered 2016-02-02, 22:11:59 - info: <your IP> POST /api/voice/lighting/event processed successfully Portal returns to Alexa without errors. It must be that there is something in the data that Alexa does not like, if it's not the quantity. Benoit. Can you confirm that your 148 devices are getting "discovered" correctly? All of them? Benoit.

Hi Michael, After discussing it with Michel, we are adding this to the development queue. Thanks for the suggestion. Benoit.

Hello Keith, Your suggestion has been added to the development queue. Benoit.

Hello Stu, I checked the logs. I could not find any error, the discovery seems to complete correctly. However, I notice that you have a lot of devices, close to 300. It may be that there is just too much for Alexa to digest, and it may timeout somewhere. If you are not using all of those devices, I would suggest to do a cleanup and reduce the number of devices exposed to echo. Benoit.

Bob, please PM your uuid, I will investigate. Benoit.

Hello Bob, We want the portal to be as secure as possible, so that would go against the purpose. However, browsers like chrome will allow to cache the user and password, and fill it for you if you wish to do so. Benoit.

Hello Stusview, Do you still have the problem? Looking at the logs, I see a successful device discovery around 8pm, eastern time. Benoit.

Please double-check the following: - In the Echo App, under settings/connected home, is ISY still there and enabled? - In portal, in My Profile, is your account still linked? I would try to unlink and relink. FYI, in the spoken window, pressing "refresh" does nothing other than refreshing the screen with data from the portal server. Benoit.

Did anyone notice if device control was faster now? This afternoon, I pushed an update that speeds up connected home response time. It's now about 350-400ms faster than it was. Benoit.