webminster

Have you checked Ebay? I see a few there if you search. I bought a few a while back off EBay because of this same reason...

You can do that, either with a scene (setting on-level for device in that scene) or direct device control. You don't mention the Insteon device type - you're sure it's a dimmable type of device?

1. The leak sensors send a heartbeat status about every 24 hours, give or take. Why you often see a "wait 25h" is to allow for a little fudge on that. 2. Yes, they should stay running. They are started at ISY boot, and they wait for a heartbeat trigger. Then they wait for about 24 hours for a program retrigger. If it arrives, the ISY restarts the program, for a new 24 hour cycle. If the heartbeat doesn't arrive, the wait falls through, and the notifications start (until the heartbeats start arriving again). 3. There's no "exit" on these programs, at least explicitly. Are you aware that, if a condition in a program IF changes while a "wait" command is waiting, that the wait is aborted and the program restarts with the condition getting re-evaluated? If not, that may be an important clue to understanding how much of it works.

Is this the deal where you have to mark the scenes as type "lights" or some such (e.g. "Alexa Category"), instead of "scene", in the ISY Portal, to make them show up as usable for Routines?

Alternatively, go to https://alexa.amazon.com/spa/index.html and find Forget All under Smart Home / Devices.

Yeah, that's what I tried too... create a group with an Echo and a device, then said "Alexa, lights on" (according to the documentation). Just replies, "can't find lights." Maybe the feature's not baked yet.

From their documentation, I'm not sure how this is supposed to be helpful. They say create a group, and add the echo to the group... great. They also say, "Give each group a different name if you have multiple groups. " How does this help me create 2 groups with Echos in different rooms, and say "turn on the lights?" Must be missing something.

For some of us, this isn't true (point of the thread). "close" doesn't work for us anymore on a garage door program. And programs that control lights /do/ work. Hence the confusion. I'm /assuming/ Michel's statement is biased more toward "it's unreliable," versus "your house will explode..." I hope.

For fun I deleted the program from the ISY portal Echo device list, and forgot it from Alexa. Added the program back in the portal and Alexa as "garage door". Same behavior for "close," "garage door doesn't support that." Spent a while trying different utterances as well... nothing worked. Got everything from "having trouble understanding you" to "doesn't support that." EDIT: PS. But, "close all kitchen lights", also a program, returns "OK." Fascinating.

Quick look at my app shows my echos (dots) at 588443520. The app itself as client version 1.24.2573.0, bridge version 2.1.297.0.

So the information is inconsistent, Michel saying they're now reserved in Amazon's V3 changes, stusviews saying not. I do see the same as DaveStLou, they worked fine, then suddenly, not. My program is essentially the same, except I don't populate the Then path, only the Else. But as I understood, a program to the SH integration is a program - should be no difference in what it does or to what devices. So still at a loss why it works for some now and not others, unless Amazon is doing a staged rollout of new stuff that's only affecting some people yet.

I got a support response back from Michel K, he tells me that "open" and "close" are now reserved and restricted by Amazon for door locks. Not sure why stus' would work then, or why anyone would say "close the door" to lock it...

Then I don't understand how my (and others) no longer work, and just respond "garage door doesn't support that." I know I have made no changes on the ISY, the portal, or on the Alexa side. Something had to have changed, and outside of my view. I can run the Else on the program from the portal, works fine still. Don't know your implementation, my "garage door" spoken is on a program that mostly triggers an i/o linc, standard stuff. But now, Alexa doesn't think the program is a valid target for a "close." So not sure how yours works and ours no longer does.

Be nice to know where the change happened, on the Amazon side or the UDI side.

I just noticed this today too. I told it to "close the garage door," which is linked to a program. Program only responds to the Else (turn off, close) if the door is open (doesn't allow open/on). It now only responds "garage door doesn't support that." Used to work just fine like that. What changed? Did the ISY skill get updated (part of that release recently to get ready for the V3 smart home support)? Did this "close program" == "turn off program" get removed? Like you, I think "turn off garage door" is pretty counterintuitive (e.g., sounds really dumb). But I don't see an alternative way to implement it. -Alan

Portal yes, but other threads suggested the Google Home thermostat integration to the portal was missing. Trying to find out if that's still true, can you control the thermostat through Google Home? The wiki page for Google Home doesn't mention thermostats.

Am getting kind of sick of my Echo Dot, but need thermostat support on Home to dump it. Do thermostats work yet on the Google Home / ISY Portal integration?

To me, Echo has become rather useless. Any more, it often spins lights and otherwise doesn't respond (say anything, let alone do anything). When it does, the "a few things share that name" happens. It's becoming a lot faster to just pick up my phone and use Mobilinc, like the good old days. I did get an answer to one of my feedbacks from Amazon. They suggested I do a factory reset and reconfigure my Dot from scratch.

Has circumstances changed yet? I see GH advertises thermostat support on the web site now. UDI wiki does not yet mention thermostats in the GH page.

I'll +1 this, and I've sent a few feedback forms to Amazon to this effect. The number of "clarifications" it asks for has gone up dramatically, and it acts more hard-of-hearing for other things as well.

AWS is reporting a lot of service problems at least in N. Virginia area, and the Web page for Alexa says "we are experiencing technical difficulties." So it's the Echo that's sick. Mine is erratic, only works occasionally. https://status.aws.amazon.com/

Thanks. That'll do what I need.

Are there commands to ask for and set thermostat modes (heat, cool)? I thought I read the older skill could do it, but i can't hit upon any phrase that seems to work in the SM optimized one. Some "ask isy" phrase? Alexa misheard me last night and turned off the thermostat. Wish there was a way to get it to turn it back on.

I've read a thread or two about scenes and understand. Is there possibility for an enhancement to allow a fast on/off command? Or is that not possible with the Alexa side, and it'd have to be a program with a tricky name?

Thanks for the reply. I just tried "turn on x to 100%", it replied "that command doesn't work on device x".