Awesome…that’s what I wanted to hear! I am reading your FAQ’s for the echo and virtual switches right now, thanks alot!
Are you talk about my, “work in progess”, Setpoint smart app or successfully get the dimmer to change via Alexa?
@DarcRanger,
Interested in controlling my thermostats setpoint.
This would greatly increase the WAF in my house 
Thanks,
Scott
So far so good…but there is one device that isn’t showing up in the device list. My Z-Wave Lock from Yale. Anyone have any luck getting that to show up. Or maybe there is something I am missing since it is a lock.
You will have to use a Virtual Switch for your lock. At the moment the Echo will on do On/Off/Dim items so no locks but from what I read, its seems easy to add it with a virtual switch.
It should b done tonight. Just finalize the ability of the virtual switch and the thermostat to match updates both ways.
I’m sure this answer but I’m not home to test anything so I will ask. With the new ST and Echo intergration only on/off/dim is supported? Or can low/med/high commands be used to send to a fan switch? I’m guessing the answer is no so my only solution right now is to set low=30, med=60, high=100 dim to that level, which I set up already, just can’t test it. Ha
Correct on all counts. You cannot use “low/medium/high” but you can use a numeric setting.
Gerri, I’ll have to wait until Monday to test if my dimable virt fan switch is working correctly.
Ok, thx. I just read that on ST. How long has it been broken?
It’s the name of one of our news reporters reportersh here in Sacramento. I’ve had to change the channel more than once… Lol
How are you controlling HH using Alexa without using virtual switches?
I have this working using IFTTT as a “man in the middle” protocol. It’s working really well.
I can turn on the TV to Netflix on Roku, I can shift from Roku to cable or the DVD player, I can turn off the whole entertainment system.
It works because one IFTTT trigger can trigger multiple events.
So I have one virtual switch which represents the TV coming on. When it is turned off it triggers my harmony power off activity, and it also turns off all my other entertainment system virtual switches using one IFTTT recipe for each off.
Then I have one virtual switch to turn on each harmony activity. And additional recipes so that as each entertainment device comes on, I turn off the virtual switches for the other entertainment devices.
So if I say “Alexa, turn Roku on,” The virtual switch for power comes on, the virtual switch for Roku comes on, the harmony activity for watch Roku is triggered, the virtual switch for cable goes off, and the virtual switch for DVD goes off.
Then while I’m watching Roku, if I decide I want to switch to cable, I say “Alexa, turn cable on.” The virtual switch for power gets the on request but it’s already on so nothing happens there. Virtual switch for cable comes on, the harmony activity to watch cable is triggered, virtual switch for Roku goes off, and the virtual switch for DVD gets the offer quest, but it’s already off, so again nothing happens there.
Ultimately, I say “Alexa, turn tv off.” And the virtual switch for power is turned off, the virtual switch for cable is turned off, the virtual switch for Roku is turned off, The virtual switch for DVD is turned off, and the harmony activity to turn power off is triggered.
So three harmony-controlled devices (TV with cable, Roku, and DVD), four virtual switches because there is one additional switch for the power on/power off condition, and a bunch of IFTTT recipes.
Everything happens in one or two seconds, I can use natural language, and it works great. I’m really happy with it. 
I can confirm that at some point in adding the new echo integration, the IP address for a hue bridge that was previously connected is zeroed out in both the smartthings mobile app and in the echo official app causing Any bulbs that are connected to that bridge to then be uncontrollable from either smartthings or echo, although they will still be controllable from the native Hue app.
It’s an easy fix, you basically just have to re-discover the Hue bridge from both the smartthings side and the echo side. After that everything works OK again.
I have added instructions for this fix as step 11 in the community FAQ:
I did so many different things with echo today that I’m not sure at what point in the process this happened but it definitely happened.
I am am only using it for HH actions that do not require a mode change. I am just turning a group of lights/switches off and on as needed.
I experienced this exact problem… thanks for describing it so thoroughly.
I “prefer” to have my Hue bulbs on the Echo directly through the Hue Bridge, since it isolates them from SmartThings (pros, cons, … probably balance out).
At the moment, though, since I was unable to get my Echo to “rediscover” the Hue Bulbs after adding SmartThings access to various devices (with some overlap to the Hue Bulbs by accident…), I currently have Echo talking to the Hue Bulbs via SmartThings.
I will try to separate them again sometime. I suppose it isn’t critical, but SmartThings’s control of Hue is still rather shaky in various ways, so that’s why it is nice to isolate the Echo-Hue communication to be direct, instead of adding SmartThings in the middle unnecessarily.
I moved my app post to here to not crowd this topic with a smart app…
I didn’t have any trouble getting the echo to rediscover the hue bridge.
I have the Hue bridge available to both smartthings and directly to echo. I did not try to authorize any of the bridge-controlled bulbs for echo via smartthings, so from Echo’s point of view they only exist as part of the bridge.
I don’t know if the fix-it sequence makes any difference, as it happens, I rediscovered it from the smartthings side first, and then did a “discover my devices” for Echo. I did press the button on the hue bridge once for smartthings, and then again for echo.
You can see my list has active devices from SmartThings, wink (which is really a link lighting bridge, not a wink hub), and a hue bridge.
Yes great idea and I knew this was an option but i kept holding out hope that ST and Harmony would get their act together and it’s been what seems like a year now. All of the integration I use to this point is from Harmony to ST via virtual switches and it works flawless. When I power off my tv every night, it turns off my virtual switch which puts the house into sleep mode. I never had a driving need to trigger something from ST to Harmony until yesterday 
I did figure out how to fix it eventually. Funny the SmartThings team laughed off the connection to the echo rollout when it was obvious computer science 101.