Xathros

I found I needed to first Dissociate the portal from my Amazon account via the portal (I had previously linked them before the connected home aspect was released), then Follow the link at the top of this thread to connect my Amazon account to the portal, then return to the portal and relink the portal to my Amazon account before the ISY showed up under connected home in my iOS Alexa app. Basically, just dissociate all of the accounts then reconnect them again. Then after the ISY was listed, before it would discover any devices, I also had to "Alexa, tell Izzy to select ISY" and select my "Home" ISY even though my home ISY was listed as my preferred ISY on the portal. She wouldn't discover devices from either of my ISY's prior to that. I'm not sure the preferred selection on the portal has anything to do with the Alexa/Amazon interface. Hope that helps. -Xathros

You would use the App or ISY network resource to Turn On/Off/Brighten/Dim/Change color etc. I cannot speak for the bulbs as I don't have any of those yet (Larry might) but the LED strips remember their last color and brightness when turned On or if power is lost then restored. Also, if off when power is lost, they stay off when power is restored unlike the damn Hue bulbs. The API is a bit clunky but very workable from the ISY and I've been quite happy with the reliability so far. -Xathros

I realize this is a reply to an old post but for the benefit of others finding this: Have a look at MiLight strips/bulbs for ISY controllable RGBW/RGBWW. Strip Controllers: http://www.ebay.com/itm/WiFi-Wireless-IOS-Android-Phone-MiLight-Controller-for-5050-RGBW-led-strip-light-/351384115618?var=&hash=item51d02019a2:m:mZYVEjmVrjn7rsBs5oS7WMw Strip LED's: http://www.ebay.com/itm/SUPERNIGHT-5050-SMD-300Leds-RGBW-RGBWW-LED-Strip-Lights-RGB-Cool-Warm-White-/321899907765?var=&hash=item4af2bacab5:m:mqKzAnMYXhgjY2k5MxlQ9-A LED Bulb Kit: http://www.ebay.com/itm/Milight-2-4G-Wireless-RGBW-W-WW-E27-9W-LED-Light-Dimmable-Bulb-Lamp-wifi-Remote-/231430824884? var=&hash=item35e25a23b4:m:mEwAwd7gFjbsVJzvFjVLhnQ Open API for controlling the above: http://www.limitlessled.com/dev/ Hope this proves helpful to somebody. Credit for this find goes to @larryllix -Xathros

Just be be clear, You can connect to the ISY from Mobilinc using the UDI portal just as you can with MLConnect however, MLConnect offers some additional value added features that you won't get if you switch to using the UDI portal. I believe the custom push notifications are one of features you would lose along with Today view widgets (though the widgets seem to work fine for me without MLConnect) Using the UDI Portal opens up access to Alexa and somewhere down the road IFTTT support/integration is said to be planned. Choices are good! -Xathros

I can see my connected home requests logged under Settings / History in my Alexa app. Is this not there for you? -Xathros

Hmmm. I won't be able to test for that until my second echo arrives. Quite interested to see what you find. I would hope and expect that the selection of ISY is local to the echo and not the Amazon cloud. -Xathros

It's a bit odd. Select the first ISY, discover devices, test. Select second ISY, discover devices, test. All good so far. Now, when I look at the Alexa app, I see devices and programs listed from both ISYs but the deselected ISY's devices and programs show as offline. Telling Alexa to turn On/Off an item from the selected ISY works as expected. Telling Alexa to turn On/Off an item from the deselected ISY results in an "Ok" but the device/program on the deselected ISY does not respond to the request. I think we should receive an error like "This device does not exist on the selected ISY" or something similar in this case. -Xathros

There should be a link below that box to link to your amazon account. Click that link and provide the requested details, the box will get filled in with your Amazon id. -Xathros

Via the UDI Portal and Amazon cloud. Intra-cloud communication. I have tested both pointing the local echo at the local ISY as well as at the remote ISY and both work equally as well. -Xathros

Awesome! Just tested this and it works perfectly. Thank you! -Xathros

I too am interested in this. I have an ISY at the office and one at home. While both ISYs do communicate for some things, I'd rather have the Echos linked only to the local ISY. I kmow I can tell the skill which ISY to address but I don't believe that affects the connected home aspect. Is there or will there be a way to address certain spoken entries in the portal to a specific ISY? Thanks. -Xathros

Working fine for me as well. -Xathros

Hi Teken- I feel your frustration and that of others still suffering from these events. My thoughts and comments in Blue above. -Xathros

That won't work. Control events are only generated when devices are manually actuated at their paddles. When commanded on by a remote linked scene/device, status changes but no control event is generated. Since devices don't transmit their status changes unless queried, the ISY is unaware of the All-On, thus the need to periodically query a device for an unexpected state change. -Xathros

While I haven't had anymore All-On events, I did build a program to watch for them, notify me and shut things down in the event of another All-On. I used a spare Lamplinc module and plugged it in alongside my phase bridge at the main panel. No load connected and I keep this module Off. I have a program that queries the module once every minute. I have another program that triggers if that module's status changes to "On" and sends a notification and turns off my "Almost Everything" scene with the assumption that if that module turned on, an All-On event has occurred. Hope this helps. -Xathros

If Alexa is recognizing your commands accurately then the vocabulary is the problem as Jon alluded to above. I suspect that once the Connected Home portion of the ISY goes live, these problems will disappear. -Xathros

Not sure how this differs from Ubi other than being funded on Indie go go instead of Kickstarter. Looks to be based on Google's voice processing just like the Ubi. -Xathros

What names are not working for you? Izzy CAN address scenes. Just set the spoken name for the scene in the same way you do for a device. Make sure there are no duplicate names (Don't use same spoken name for a scene and a device). Check the Alexa app to see if Alexa is understanding your requests. In my testing I have found that Alexa can misunderstand "...tell Izzy to...' as "...tell it to...". When that happens, the commands fail as they don't get passed to the Izzy skill. Hope this helps. -Xathros

And refrain from calling devices Lights or Lamps. Alexa is having a problem with things named lights & lamps at the moment. So, for example, instead of "Kitchen Lights" in the spoken field, use just "Kitchen". -Xathros

Your UI is out of date. UI should match the firmware version. Clear your java cache and then download the JNLP for the console from the 4.3.26 release post. -Xathros

Have you logged into the portal and connected it to your Amazon account? -Xathros

Hello and welcome to the forums. How are you accessing the console? Via web browser or have you downloaded the JNLP application and have an icon on the desktop? Do you know what firmware version you have on the 994 and do you know if the admin console is the same version? -Xathros

Not exactly but you can just create another scene with all of the above as responders. -Xathros

man cave

You can right click your programs and use the find replace to search for the name of your stat. Also, sort the program summary by last run time and look at the most recently run program(s) -Xathros