Bruce L

Not sure if this is a problem with the ISY (running 5.0.16C) or one of my insteon devices, but I just tried to solve a problem where my remotelinc was not controlling one of three devices (an Insteon LED bulb) in four scenes (a, b, c, and d assigned to different scenes. It was setting this bulb to 100% in all scenes, though it was only 100% in a.) I tried restoring both the remotelinc and the bulb but no changes. I removed and re-added the bulb to each scene, no improvements. I factory reset the remote linc then restored it, no change. I finally removed and re-added the remotelinc as a controller for the scenes, and that finally fixed the problem. Bruce

Is there a page that summarizes all of the changes (and new features) in 5.0? I've only found individual discussions, and would be really interesting to have a list of differences. I figured out that status conditions are interpreted differently (I prefer the new implementation, I thought the 4.x implementation of status conditions was a bug) but would like to know anything I missed or if there are new features in programs I can take advantage of. The release notes have a link to the wiki and specifically the variables page. But that doesn't seem to have any updated content. Would help if the instructions mention specifically that you need to manually save the programs after the update runs. With that said, everything appears to be working fine after an hour or so of work, and the motion sensor v2 that I set up is working fine. Thanks, Bruce

Create a program where the Else clause sets your "basement lights off" scene. Link the program to the spoken "basement lights". Then "turn off basement lights" will turn them off. (presumably you might want to have some scene in the then clause so "turn on basement lights" does something as well) Bruce

You choose what scenes (or devices or programs) the echo knows about, and you give them spoken names (that don't have to be related to the scene or device name) in the control panel at http://my.isy.io. So you won't have any problems. Bruce

Ah, magic keywords it was. I renamed all of my scenes to not use "all" or "dim" and there is no more confusion---Alexa does what I ask the first time. Is there a list of bad keywords somewhere? Bruce

Thanks for the work on connected home. I just got my Echo yesterday and it was great to be able to set this up. The only real problems I had with the setup were that I hadn't enabled the admin panel to for unrestricted access in Safari, so I couldn't buy the module, and then I missed that I had to re-run discovery on the echo after setting up everything in the portal. But once I figured those out it all got connected. The only problem I have now I think is with word recognition with the echo. I have two kitchen scenes set up that I gave names for as "Kitchen All" and "Kitchen Dim". What's odd is that every time I try to use one of these I go through the same process: "Alexa, turn on kitchen dim" "I found several devices matching that name. Which one did you mean?" "kitchen dim" "ok" It's the same sequence every time. And looking in history it got it right the first time. I thought I would help by using "kitchen all" and "kitchen dim" rather than "kitchen" and "kitchen dim" but it doesn't seem to have helped. I actually sent amazon feedback that it wasn't doing what I wanted, but just got a generic reply. Any suggestions? Thanks, Bruce