bmercier

Hello Teken, Thanks for reporting the problem, this is very weird. I will investigate that. Especially the "MicrowaveMicrowave / 2330423304". If you recall the sequence of events to get this, please let me know. Thanks, Benoit.

There's a fix coming this week to address the setpoint being doubled. Benoit.

I'm not sure if your intent is to use the ISY skill or ISY connected home. Connected home cannot return the status of a device, so you have to use the skill. The correct syntax for a skill has to be: Alexa, tell izzy to... Alexa, ask izzy to... Alexa, ask izzy about... To get the status of a door, you can say: Alexa, tell izzy to get the status of <door> A variation for locks that you can use is: Alexa ask izzy if <door> is locked I encourage you to use "door" instead of front door. For some reason, front should be accepted, but alexa has trouble with it, it is not always passed to the skill. Benoit

I have also learned it that way. However, I was not fully sure when I did this, so I checked online. Apparently, both are acceptable. Then, I made tests with Alexa, and testing shows that 's is always added, like in "chris's bedroom" The list was built that way so it can match what alexa is sendint to the skill. Benoit.

The Amazon ISY Skill version 2 is now live since this afternoon. This change applies only to the skill (There is no change to ISY Connected Home) The biggest change in the skill is a better support for spoken device names. There is still a bug where you cannot have a spoken name outside of the samples provided below. However, there is now much more spoken names you can use. In addition of the device name, you can choose to add one of the predefined prefix, and also a suffix. Those are optional. Here's some valid examples: upper hallway lights left bedroom lamp second floor kitchen overhead bar Prefix you can use: upper lower front side right left rear main master first second third forth fifth small large outdoor exterior interior back upstairs downstairs basement under over all backyard south east west North top down middle all first all second all third all fourth all basement all upper all lower all exterior all interior all front all rear Suffix you can use: light lights lighting lamp lamps track light track lights neon neons spot spots flood floods fan fanlight accent area overhead fans curtains drapes Devices names you can use (They have to be after prefix, and before suffix, if they are used) activate active air compressor air conditioner arriving art art niche attic awning bar barbecue barn bathroom bathroom ceiling bed bedroom beer blanket block heater bonus bonus hall bonus room bonus room hall bookcase box room breakfast breakfast table breezeway butler butler's pantry cabinet cabinets can car port ceiling cellar center chandelier chime chime mode china hutch chrismas tree christmas cinema closet clothes computer computer room conservatory cooler couch deactivate deck decor default de-icer de-icing cable den desk desk room device dining dining room disable dog door door door chime downstairs drive driveway dryer dungeon dvr electric emergency enable engage entertainment entertainment room entrance entry evening exercise room family room fire fireplace fish tank flood floor floor bathroom floor thermostat fountain foyer fridge game room games garage garage door garage front garden generator globe great room grill groove guest hall hallway heat heater high hats holiday hot water tank hutch island island sink kitchen kitchen cabinet kitchen cabinets kitchen counter kitchen desk kitchen island kitchen sink kitchen table kitchen window kitchenette lanai landing landscape laundry laundry room library living living room living room hall locker machine make it so man cave man door mantel master media media room mister motion music room niche nook nursery office orangery outlet panic pantry parlour path patio pendant piano pinball plant shelf playroom pool pool table porch power projector pvr rec room receiver red refrigerator reset restore room rotate sconce screen secure security server shade down shade up shed shop skylight sofa solar spa spare bedroom spare room sprinkler stairs steps stereo studio study study room sump sun room swimming swimming pool table task test theater thermostat toe kick toe kitchen toilet tower tree turn tv upstairs utility utility room vanity video walkway wall wall sconce washer washroom waterfall wine work workshop yard zone one zone two zone three zone four zone five zone six zone seven zone eight zone nine zone ten zone eleven zone twelve guest room guest's room guest bedroom guest's bedroom boy's bedroom girls's bedroom kid's bedroom children's bedroom mom's bedroom dad's bedroom In addition, there is about 2000 bedroom names using the most common first names, in the following syntax: aaron's bedroom abbey's bedroom abbie's bedroom ... Benoit.

Unfortunately Connected Home does not support thermostats. yet. Benoit.

Unfortunately this is not possible. The connected home API does not allow to return custom feedback messages. I also had a chance to see a draft version of the V2 API, and there still is not any way to return custom feedback. Benoit.

Create a program, and in the else clause, turn on your scene. When you turn off "basement lights", it will turn on your scene. Benoit.

Locks are not supported on Connected Home. There are no verbs available like lock or unlock that we could use. We perhaps we could have mapped it to the Turn on and Turn Off, but I would find it confusing. Should "Turn on front door" Lock? or Unlock? That would be error prone IMHO. Benoit.

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.