bmercier

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.

Thanks everyone for your suggestions. A new version of the skill is about to be submitted for certification. Most of the suggestions in this thread were added to the sample devices. Benoit.

Program support is now available! Benoit.

We can now enter spoken for programs on portal. Other than the ability to specify a spoken for a program, this change also allows to : - Turn on programs (runThen) - Turn off programs (runElse) The existing "run <program>" still exists, and it should be easier to use. It now uses the same sample names as a regular device. Therefore, if you have a device name that works well with devices, it should work as reliably with programs. FYI, a "run <program>" will do a runIf (not runThen). Please note that the connected home will also support programs with those same spoken names. It's implemented, but unfortunately not live yet. Benoit.

Stusview, Thanks for the screen capture, that helps understanding. From what I see, it's a conversation which is all within the skill. Connected home is not involved at all here. There are a few verbs that gets you into a skill, like: open <skill> tell <skill> to ask <skill> to In the case of tell and ask, it's the combination of the "verb + skill name + to" that routes the request to the skill. So, if Alexa does not understand the to, and clearly understands the turn on, she thinks it's for connected home. Even if you have no connected home adapter enabled. When you are within a skill, and the skill asks you a question and leaves the stream open, then you can say something else (like a device name), and this gets routed to the skill currently opened. That happends when you ask for a command, and the device is not found, then the skill will ask a question and leave the stream open. Same thing goes when you are within the help. Benoit.

Stusview, You request was indeed sent to the skill. If you hear a reply which says "Turn on which device?", or "I could not find device <xyz>. Turn on which device?", then yes, the request was directed to the skill and it could not find the device. However, if you hear "Sorry, I could not find a device or group name <device> in <user>'s profile", that's not coming from the skill. This means Alexa tried to find the device in the connected home profile. I believe this is the message that Z3phy got. One reason for this can be for Alexa not to understand "to" properly. Benoit.

Z3phyr. Whenever you hear that it can't find a device in your "profile", this is a symptom that Alexa sent your request to the connected home. It was not routed to the skill. Make sure to pronounce the "to" correctly. Alexa, tell izzy to turn on dining room. You can look at the echo to see what she understands. Benoit.

Absolutely, it still uses the lighting API. It's just that they want us to use a new method to publish the connected home adapter. So far, it's been a manual process for them. Each time I wanted to publish in test mode, I had to send an email with a few information. I assume the process will be similar to a skill, in the sense that you need to enter your informations somewhere and then submit for certification. Benoit.

Right. The reason is that Alexa often skips words which are not on the device samples. So in that cases, it only passes "kitchen", and the skill can then make a match with your spoken "kitchen". However, be aware that this is currently being enhanced, and in the next version, light will be recognized. So when this goes live, "kitchen light" will start to work, and the skill will not be able to find that spoken in your list of devices. Benoit.

Ronbo, GPG, The fix is now in production. Thanks, Benoit

Hi Barry, I'm currently using standard jQueryUI buttonset(). Would you have a screen-shot of what you suggest? That would help for inspiration to customize the buttonset. You can PM me. Thanks, Benoit.

No, not alone! Hi Junky, We had news today from the Amazon Echo Sr product manager. Amazon is about to have a new self-publishing method for connected home adapters and want us to go through it. That was supposed to be ready in late december, but the dev team is late. We are told to wait a "couple more days". Benoit.

Hi Ron, When you start typing, it should bring you a dropdown with scenes that match what you type. Or alternatively, if you the field is empty and you click on the arrow, you should see all your scenes in the dropdown. If that's now what is happening, I'm starting to think that it may be a browser specific issue. What browser are you using? Benoit

Hi Michael, Connecte home will use this same table. Now, the spoken field on ISY has no purpose related to portal. It can perhaps be used for other home automation needs, if integrated with something that speaks or can accept spoken requests, or just be ignored. About the "Spoken" not having Add... well, the idea is that there will be Programs as well. It may not be too obvious, but those two buttons form a buttonset. For esthetic & real estate reason, I opted for a button set where you have 3 places to click on to Add devices/scenes/programs. When you see "program" appear there, having "Add" in front of all 3 will look redundant. Benoit.

Hi Rombo, Please click on Add scene. There, you will be able to add scenes to your list. The refresh button does not synchronize with the ISY. It just refreshes the UI with the content on the portal server. Benoit.

Ronbo, They should all be listed, unless you type something in the field, which has the effect of filtering on the list shown. Are you sure you are missing scenes? Any one else seeing this behavior? Benoit

Hi Michael, I was suggesting to delete the devices on portal. That's how you opt out a device from the Echo. You are right, they are not synched with the ISY. It's now totally separate. We could have started with an empty table instead, but we figured it would be best to start with those from the ISY so that the move to production is not disruptive. Benoit.