bmercier

Thanks for the detailed explanation. With this I was able to track the your request in the logs and found out that the authorization header is not passed to the API. Therefore the API returns http error 401 Unauthorized. This is a condition that should never happen, as the web client always sends the authorization header as part of the request. Furthermore, you mentionned that the authorization header was indeed sent with the request. I believe that some mobile browser may simply not send the auth header under some circumstances. On the other side, the web client did not correctly handle a 401. I made a fix which is likely to solve the problem. Can someone try again and see if the problem is still present or not? Thanks, Benoit.

Try "front door" instead. It should work, this is what alexa passes to the skill. Recognition for "front door" is far from perfect, but it works (when she don't hear "from door") But other than that, be patient, a new version of the skill is under certification review. It should help significantly. There is still a bug where values not listed in the samples are not being passes to the skill. But in the mean time, 3-slot device names have been implemented, and the words in the samples have been enhanced also. Benoit.

You are correct about turn on/off running the then/else clauses. However, unfortunately, connected home does not support commands like "run <spokenname>". This is not something we can implement ourselves, it has to come from Amazon, and I'm not aware of any plans in this regard. Thanks, Benoit.

1) On=Then, Off=Else. Note taken for the flexibility of a URL. However, today, you could use an interface program where then does your "On" stuff, and else handles the "Off". 2) This is coming. 3) Connected-Home can only handle Turn On/Off, and set a brightness to a percentage. All you can do for Fanlinc is use the Turn On/Off in combination with a program for each levels. Benoit.

It works very differently. In the case of connected home, the Amazon engine has knowledge of your devices. When you click "discover devices", this effectively brings your list of devices from the spoken table to their systems. So, it is able to make a very accurate guess of what device you are trying to refer to. In the case of a skill, what was understood is passed to a portal API, and the API tries to make a match with one of your devices in the spoken table. However, in order to help, the skill configuration has a list of sample devices. So, naturally, those devices will be easier to understand as Alaxa first tries to match with one of those, and if it cannot, it uses plain english words from a dictionnary. BUT, there is currently a bug which prevents alexa from going outside the list of samples. The device 'bar' is not on the list of samples, so no matter how well you pronounce it, it is never passed to the API. This bug is currently being investigated by Amazon. Thanks, Benoit.

That's good to know, I was not aware of that. Thanks, Benoit.

Michael, I tested with an Android 5.x (I don't have it with me at the moment, I believe it was 5.3.1). I have seen report of problems with version 5.0.1 up to 6.0.1) in this thread. Benoit.

This message indicates that the skill received "living room" as the device name. I looked up in the database for your spokens, and I found "living room ceiling", but not "living room". This is why you are getting this message. If whenever you speak "living room ceiling" alexa passes "living room", you may want to change your spoken to just "living room". If it worked before, it may be that it was previously understanding and passing "ceiling". That we don't have control over it. The skill configuration, like utterances and device samples, have not changed since skill went live. That's about to change though, a new version is coming. About your locks, I looked up you spoken, and I couldn't find any device of type 'lock'. Please go to your list of spoken, search for 'lock'. Make sure you have devices of type 'lock'. If you see a lock that is not properl of type 'lock', then that would be a bug. Benoit.

Hi Stusview, What error message do you get exactly? Can you type the exact message you get, or copy-paste from the echo app? (You can use echo.amazon.com instead of the mobile app) Benoit

Hold on, this is coming A new version of the skill is currently submitted for certification. That will work when it gets live. Benoit.

Hello, I'm trying to reproduce the problem, without much success. I'm trying on Android native browser, chrome on android, chrome on ios, safari on iOS. All worked. I need help reproducing the problem. I think there must be a javascript error on the browser console. Can someone with the problem try the following: - Connect a mobile device to the PC using a USB cable - Start chrome on the mobile device - On the PC, start chrome as well, and go to: chrome://inspect (this will start the remote debugger) - Still on the PC, when connected to the mobile device, go to the console tab. - On the mobile device, go to my.isy.login, and login - Assuming you still have the problem, please look at console (on the PC), and please PM me a screen shot of the error(s). Thanks, Benoit

Unfortunately this is not possible. The ability to say "run <program>" would need to be implement by Amazon. We don't have control over that. Benoit Sent from my iPad using Tapatalk

Is your ISY connected to portal and working? Try using UDAjax. If this works, this means your ISY is connected, authorized, and communicates successfully with portal. Benoit.

The ISY can only connect to Mobilinc portal, or UDI portal. Not both. UDI portal supports both the Amazon Echo and Mobilinc. To configure Mobilinc: - Set the Host type to: ISY - Set your secure host to: my.isy.io - Secure port: 443 - Use your portal User name and password. - On portal, go to "My Profile", make sure your Preferred ISY is set to the ISY you want to control. Benoit.

If anyone sees this white screen when linking with his Amazon account, please PM me the URL of that page, and which browser was used. I personally have not seen this error occur. Thanks, Benoit

Are you using the skill? or connected home? If you are saying, "Alexa, ask izzy to run program garage door", this is the skill. With the skill, yes, some words will be much easier to be recognized than others. Words being skipped is a common symptom that we can observe with the skill. The skill will be enhanced soon, and a list of sample devices will be published on the wiki and forum. Connected home has a much better facility at recognizing any device that you set, provided this is a common english word. This could be number as well, but I believe it has to be textual (2 -> two). I have not tested that though with connected home. The reason for the connected home working better than the skill is that the spoken that you define are known to Alexa. When you do your device discovery, this brings this list somewhere where Alexa can look it up and find the right one. Benoit.

Well it's mostly a matter of UI. Alternatively, an easy change could be to stick to 1 field, and use a delimiter like a comma. This way, the number of aliases could be almost unlimited. But that would not be as intuitive a let's say 3 fields under the other. Benoit.

Whenever a device is rename in the admin console, it is not reflected in the spoken table. It is carried there only to facilitate the recognition of the device by the end user. However, this description will be refreshed if you simply edit and save the entry. Benoit.

No. You can use different email addresses for your portal account vs your amazon account. The message says 2 things: - Your Connected Home is not linked -> You have to go to My Profile, and click "link this profile with an amazon account" - Your ISY skill is not linked -> You have to go on the echo app, enable the skill and follow the link process there. The connected home and the skill, although they share similarities in terms of functionality, are 2 totally different things. The portal makes it like it's a single thing (for example the spoken table is the same for both). But the way the linking works is different. Benoit.

Connected home does not allow to set a level like that. You can only turn on, turn off, dim/brighten and set an absolute brightness value. I would suggest to have 3 program with a spoken like: "living room fan to high", "living room fan to medium", "living room fan to low". So you could say, "Alexa, turn on living room fan to medium" You could turn it off by saying "Alexa, turn off living room fan" Benoit.

How many spoken would you see appropriate for a given device? Would 3 be enough? Benoit

1. Not really. 2. Try this: Alexa, dim <device> Alexa, brighten <device> Or for an absolute value: Alexa, turn on <device> to <number> percent Alexa, set brightness of <device> to <number> percent Alexa, dim <device> to <number> percent Benoit

The empty description is just cosmetic. In the early implementation of the spoken table, when it was populated with the command "refresh devices", it did not carry the ISY name. The spoken table only carries the ISY name since spoken are managed on portal. So, I believe that those devices were created using "refresh devices". Could it be that living room is a scene? Benoit

No need to try. light is passed to the skill, whereas fan is not. Wait a bit more for the next version of the skill, both will work. Benoit.

You can do both. First of all, in both cases, you need to add your program to your list of spoken. Then you can say: tell izzy to turn on <program>: This Runs the then statement of the program tell izzy to turn off <program>: This Runs the else statement of the program tell izzy to run <program>: This Runs the program, considering the conditions of the program (runIf) Benoit.