toflaherty

I can't get the groups to work properly either but it sounds like v3 will improve that situation. Sent from my LG-H915 using Tapatalk

I guess I'm just waiting for a more user friendly method then. Sent from my LG-H915 using Tapatalk

This is incredible. I only have 2 routines set up so far; "Alexa, good morning," and "Alexa, good night." Good night simply runs my "turn everything off" program, but good morning turns on a light scene, gives me the weather, news briefs, and traffic. This is such a large stride towards more natural language where you don't have to say "turn on" or "turn off" for something to happen. The next major natural language breakthrough is going to be when it is possible to speak to an echo in any given room and just say "turn the lights on." It's weird when I'm in the kitchen and have to say "turn on the kitchen lights," or similar in any other room. I think this will be coming soon as well.

please let me know if in "auto" mode, if you ask to increase or decrease the temperature, both heat and cool change by a degree, but in "program auto" mode, it says the command doesn't work

what an excellent observation, i never pay attention to the lights on top so wouldn't have noticed this

thank you

whoa, how do you identify which microphone is responding?

easily doable by turning a program on, then putting a wait in the then portion of that program you could set up a bunch of programs with different waits for the most common delay times you use

the biggest issue i have with any of my devices is recognizing the wake word... it's been nearly perfect as long as it wakes up in the first place

yep exactly, i bet auto works, but program auto does not work i got my first echo (dot) monday, ordered the second one tuesday...

change your thermostat from "cool" mode to "program cool" if you have it also, having temperature as a spoken word for your thermostat might hurt the alexa functionality of asking it what the temperature is, i'd suggest sticking with air conditioning/thermostat

Yes, get in the habit of forgetting everything and adding everything, because discovering devices only adds, it doesn't check what is no longer there and remove it, just adds... this is an amazon/alexa app problem. Happy to help. I'm curious if you have the same problems as me, if you could please check, where any "program" mode doesn't work.

yep, thanks for your understanding, now let's hope we can help the OP get his echo working with ISY/insteon tstat.

larryllix, I couldn't agree with you more, your setup is significantly more advanced/awesome than mine, I just wanted to see if I could get it to work and probably never use it again... i'm more than happy with the programs I have directly in the thermostat itself my comments were directed towards the OP, I'm 90% certain that his problem is that he's asking alexa to control the wrong node of the thermostat... *edit, I shouldn't have quoted you on that previous reply, my apologies as that definitely made it look directed towards you

I have this skill working with a different thermostat. Please try what I suggested. The skill can't control the heating or cooling nodes, you have to set it up with only the "main" node. This is what works for me. I just got it going about 2 hours ago.

excellent screenshot, mine is working only with the "main" node delete the spoken words from your cool node and put them onto the main node, hopefully that fixes it!

Is it set to "cool" or "program cool"? Maybe your interface/modes are different as I only have the venstar adapter and not an insteon thermostat. Hopefully my previous reply helps someone else with the venstar adapter at least. If the mode is "off," then you say "alexa, set (device name) to xx degrees," does it turn on to the setpoint? *edit, your first screenshot wasn't there originally, which now answers my question. I think your problem is that you are trying to control the cool node, but you need to control the main node.

I just figured this out today with my venstar t1800 thermostat with insteon adapter 2441V. I really hope this helps you! I have discovered that ISY (through the admin console) is unable to change the heat/cool temperature when in program auto, program heat, or program cool mode. Somehow, mobilinc changes the temperature properly while in program auto mode, but the admin console isn't capable of this. I guess that's a lucky side-effect of mobilinc doing something unexpected, maybe, but I got used to it and hoped that alexa could do the same thing... oh well, the good news is that it is still possible to make the thermostat and alexa work together. The workaround is setting the thermostat to auto (not program auto) (or set it to heat or cool). If I'm in any of the "program" modes, I have to say "alexa turn thermostat off," then "alexa set thermostat to xx degrees." In Off, Heat, Cool, or Auto mode, everything is working great! Auto mode adjusts both heat and cool temps equally when you ask it to increase or decrease the setpoint, which I like. As I see the echo as more of a novelty right now, this isn't a big deal for me at the moment, but I would really like it if the isy was capable of adjusting the thermostat temp when in any of the "program" modes, as I like to change the temp sometimes knowing that at the next time that is programmed into the thermostat itself, everything will get set back to what it would normally be at that time.

Yes sir. I feel a little silly for posting this in the echo forum now after learning what I have learned for troubleshooting, but I don't know what else I can do other than how I immediately asked for it to be moved... I factory reset it, moved it to another circuit, tried powerline only, rf only, etc... everything resulted in the bottom outlet working less than 10% of the time and the top outlet working about 90% of the time. Michel agreed that I did everything possible to prove that it was an isolated device issue and not a signal/wiring issue. The key point here being that the bottom outlet was significantly more problematic than the top. I have now actuated the plug-in wall wart on/off module on a regular outlet that replaced the on/off outlet about 100 times through the admin console and a KPL, and about 20 times through the echo. Even through the echo it responds instantly, every time. I'm quite disappointed in the on/off outlet, especially hearing that others are having the same trouble with it, as it's the newest device I have, built just a couple months ago... I didn't think it was really worth mentioning, but after the 2nd or 3rd factory reset (which sucks with this module, you have to remove power), it took MANY tries to get it added back to the ISY. Kept failing with communication errors.

Although it may be possible that some people experience a similar issue due to the cloud service taking some time to respond or a poor quality home network, this is an isolated device issue with the insteon on/off outlet. In this case, the ISY/PLM responded immediately every time to the echo/cloud service, it was just the insteon device not responding. The exact same behavior occurred when commanding the device on/off through the admin console of ISY. The on/off outlet has been replaced with a traditional outlet and a plug-in on/off module. Everything is working flawlessly now. Smarthome has been contacted, hopefully I can get the outlet warrantied (although I heard from UDI that other people are having the exact same problem with the bottom outlet taking a very long time to respond).

To follow-up, UDI support was very helpful in confirming that this appears to be a device issue. The PLM is sending the command, but not hearing anything back sometimes for a long time. The bottom outlet is much more problematic than the top outlet. It turns out that someone else is having the exact same issue as I am with this device (more trouble with bottom outlet than top, and only trouble with this device). I have contacted smarthome support to see what they say...

yeah, I may have to contact support. It appears to be random now. Sometimes it's immediate, sometimes it's 10-20s as reflected in the log. Doesn't matter if I command it on/off with Echo or straight from the admin console.

OK thanks again for your reply and for confirming that it's purely the "hops left" that identifies communication problems. I just wasn't completely sure as I'm not very familiar with what the rest of the messaging means. Maybe this is a hardware problem with the outlet.

stusviews, I appreciate the reply, thank you. I would like to point out that the echo heard my request correctly though, and immediately the ISY responded. The first few lines in the log above was me simply clicking "on" in the admin console. It took 19 seconds after clicking the button for the outlet to actually turn on. This is why I think I was incorrect in thinking it was an echo problem at first.

Well I grabbed a level 3 log file, and as much as I don't really know what I'm looking at, I think I can confirm that I posted in the wrong forum, so I apologize. If a moderator could please move this to where a communication problem is more appropriate, I would appreciate it. It seems to be that when I request the outlet to turn on or off, nothing really happens for 10-20 seconds. At first I was only noticing the "hops left = 2," which I thought meant good communication. What does it mean when it takes multiple INST-TX-I2CS/INST-ACK before getting the INST-SRX and then the outlet actually turning on or off? In the log below, I used the admin console to turn it on, then off, then I used alexa to turn it on, then off. Turning it on, Alexa responded with "ok" and it was instant, but turning it off I got what appears to be an alexa time-out of some sort, saying "that command doesn't work on device kitchen plug in," but it did actually turn off afterwards. The on command was ~1 second, almost instant it seemed, but the off took ~19 seconds. Please help me understand this, as I thought poor communication would be reflected in the "hops left" being <2. My issue appears to be that it takes a really long time to even attempt the hops. Thanks in advance. Tue 11/29/2016 08:02:47 PM : [INST-TX-I2CS] 02 62 42 00 88 1F 11 FF 02 00 00 00 00 00 00 00 00 00 00 00 00 EE Tue 11/29/2016 08:02:47 PM : [INST-ACK ] 02 62 42.00.88 1F 11 FF 02 00 00 00 00 00 00 00 00 00 00 00 00 EE 06 LTONRR (FF) Tue 11/29/2016 08:02:56 PM : [INST-TX-I2CS] 02 62 42 00 88 1F 11 FF 02 00 00 00 00 00 00 00 00 00 00 00 00 EE Tue 11/29/2016 08:02:56 PM : [INST-ACK ] 02 62 42.00.88 1F 11 FF 02 00 00 00 00 00 00 00 00 00 00 00 00 EE 06 LTONRR (FF) Tue 11/29/2016 08:03:05 PM : [INST-TX-I2CS] 02 62 42 00 88 1F 11 FF 02 00 00 00 00 00 00 00 00 00 00 00 00 EE Tue 11/29/2016 08:03:05 PM : [INST-ACK ] 02 62 42.00.88 1F 11 FF 02 00 00 00 00 00 00 00 00 00 00 00 00 EE 06 LTONRR (FF) Tue 11/29/2016 08:03:06 PM : [INST-SRX ] 02 50 42.00.88 40.D3.C1 2B 11 FF LTONRR (FF) Tue 11/29/2016 08:03:06 PM : [Std-Direct Ack] 42.00.88-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Tue 11/29/2016 08:03:06 PM : [D2D EVENT ] Event [42 0 88 2] [ST] [255] uom=0 prec=-1 Tue 11/29/2016 08:03:06 PM : [ 42 0 88 2] ST 255 Tue 11/29/2016 08:03:17 PM : [INST-TX-I2CS] 02 62 42 00 88 1F 13 00 02 00 00 00 00 00 00 00 00 00 00 00 00 EB Tue 11/29/2016 08:03:17 PM : [INST-ACK ] 02 62 42.00.88 1F 13 00 02 00 00 00 00 00 00 00 00 00 00 00 00 EB 06 LTOFFRR(00) Tue 11/29/2016 08:03:26 PM : [INST-TX-I2CS] 02 62 42 00 88 1F 13 00 02 00 00 00 00 00 00 00 00 00 00 00 00 EB Tue 11/29/2016 08:03:26 PM : [INST-ACK ] 02 62 42.00.88 1F 13 00 02 00 00 00 00 00 00 00 00 00 00 00 00 EB 06 LTOFFRR(00) Tue 11/29/2016 08:03:28 PM : [INST-SRX ] 02 50 42.00.88 40.D3.C1 2B 13 00 LTOFFRR(00) Tue 11/29/2016 08:03:28 PM : [Std-Direct Ack] 42.00.88-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Tue 11/29/2016 08:03:28 PM : [D2D EVENT ] Event [42 0 88 2] [ST] [0] uom=0 prec=-1 Tue 11/29/2016 08:03:28 PM : [ 42 0 88 2] ST 0 Tue 11/29/2016 08:03:42 PM : [INST-TX-I2CS] 02 62 42 00 88 1F 11 FF 02 00 00 00 00 00 00 00 00 00 00 00 00 EE Tue 11/29/2016 08:03:42 PM : [INST-ACK ] 02 62 42.00.88 1F 11 FF 02 00 00 00 00 00 00 00 00 00 00 00 00 EE 06 LTONRR (FF) Tue 11/29/2016 08:03:43 PM : [INST-SRX ] 02 50 42.00.88 40.D3.C1 2B 11 FF LTONRR (FF) Tue 11/29/2016 08:03:43 PM : [Std-Direct Ack] 42.00.88-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Tue 11/29/2016 08:03:43 PM : [D2D EVENT ] Event [42 0 88 2] [ST] [255] uom=0 prec=-1 Tue 11/29/2016 08:03:43 PM : [ 42 0 88 2] ST 255 Tue 11/29/2016 08:03:54 PM : [INST-TX-I2CS] 02 62 42 00 88 1F 13 00 02 00 00 00 00 00 00 00 00 00 00 00 00 EB Tue 11/29/2016 08:03:54 PM : [INST-ACK ] 02 62 42.00.88 1F 13 00 02 00 00 00 00 00 00 00 00 00 00 00 00 EB 06 LTOFFRR(00) Tue 11/29/2016 08:04:03 PM : [INST-TX-I2CS] 02 62 42 00 88 1F 13 00 02 00 00 00 00 00 00 00 00 00 00 00 00 EB Tue 11/29/2016 08:04:03 PM : [INST-ACK ] 02 62 42.00.88 1F 13 00 02 00 00 00 00 00 00 00 00 00 00 00 00 EB 06 LTOFFRR(00) Tue 11/29/2016 08:04:12 PM : [INST-TX-I2CS] 02 62 42 00 88 1F 13 00 02 00 00 00 00 00 00 00 00 00 00 00 00 EB Tue 11/29/2016 08:04:12 PM : [INST-ACK ] 02 62 42.00.88 1F 13 00 02 00 00 00 00 00 00 00 00 00 00 00 00 EB 06 LTOFFRR(00) Tue 11/29/2016 08:04:13 PM : [INST-SRX ] 02 50 42.00.88 40.D3.C1 2B 13 00 LTOFFRR(00) Tue 11/29/2016 08:04:13 PM : [Std-Direct Ack] 42.00.88-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Tue 11/29/2016 08:04:13 PM : [D2D EVENT ] Event [42 0 88 2] [ST] [0] uom=0 prec=-1 Tue 11/29/2016 08:04:13 PM : [ 42 0 88 2] ST 0