bmercier

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.

FYI, this has been there for months. It's just that I had temporarily reduced the delay significantly to test something.

Hi Teken, The auto logout fires after 14 minutes of inactivity, offers a 1 minute grace period to stay logged in, and if there is no response, it logs you off. It is a security measure that is not configurable. Benoit.

Please reload the page. Benoit

My apologies. This is fixed now. Benoit.

Hi Teken, I checked the logs, and the error was caused by a timeout. This means that from portal's perspective, the ISY was still online (the ISY socket was not closed), but still it did not respond. I will PM you an error log for your IP. Benoit.

No it's not. I quickly checked the logs, and I saw that you ISY disconnected from portal for about 6 minutes. Benoit

One possibility is that Alexa understands "on" instead of "off". On some occasions, I asked to turn off something, but it stayed on. But what really happened is that it had understood on, it sent a on to the device, but because it was already on, no change was seen. So it looked like it did nothing. So make sure you pronounce "off". Benoit.

Would you know when you had these 500, I just need the date and approximate time, so I can search for these errors in the logs. FYI, when you open up the spoken table, in the background, it's requesting /rest/nodes and /rest/programs?subfolder=true from your ISY. Then, if you press one of the add button quickly, and those requests are not completed yet, you will have a delay until they are. Benoit.