toflaherty

Bought a few items friday and they arrived monday on the other side of the country. Thanks!

Haha, unfortunately I don't have a follow-up to what went wrong. I opened the network resource, looked around, didn't change anything because I couldn't see anything wrong, then closed it, saved it, and everything is working perfectly now.

Yes, sorry, i deleted my post but you already replied. That was the first network resource I ever made, and something was actually wrong with it. I don't know what, but when I tried the address manually in a browser, it reset the variable back to 1 and everything started working again. I'll carefully check your instructions to see where I went wrong with the network resource.

This opens up a lot of possibilities. Thanks for the idea stillwater and thanks for the solution bmercier! I have programs to notify me when the power goes out (via Elk M1) and when the power comes back on (via Elk M1 and via ISY power-up), but this will let me monitor when just the internet goes out (possible modem or router lock-up). Awesome! Attempting a power cycle via insteon outlet on the modem/router is another great idea on top of the monitoring.

I have a switchlinc dimmer that has suddenly stopped responding to my ISY. The interesting thing is that it still responds to scenes properly but ISY flags it as unable to communicate with the message: "Cannot Communicate With 38 E0 DD 1. Please check connections." I've tried restore device to no avail. Tried a factory reset as well, and ultimately ended up at the same spot. Here's the log where it failed trying to write dbAddr=0x4008. Fri 02/01/2019 09:15:05 PM : [INST-TX-I2CS] 02 62 38 E0 DD 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Fri 02/01/2019 09:15:05 PM : [INST-ACK ] 02 62 38.E0.DD 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Fri 02/01/2019 09:15:14 PM : [INST-TX-I2CS] 02 62 38 E0 DD 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Fri 02/01/2019 09:15:14 PM : [INST-ACK ] 02 62 38.E0.DD 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Fri 02/01/2019 09:15:23 PM : [INST-TX-I2CS] 02 62 38 E0 DD 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Fri 02/01/2019 09:15:23 PM : [INST-ACK ] 02 62 38.E0.DD 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Fri 02/01/2019 09:15:27 PM : [38 E0 DD 1 ] Memory : Write dbAddr=0x4008 [09] cmd1=0x20 cmd2=0x09 Fri 02/01/2019 09:15:27 PM : [INST-TX-I2CS] 02 62 38 E0 DD 1F 20 09 00 00 00 00 00 00 00 00 00 00 00 00 00 D7 Fri 02/01/2019 09:15:27 PM : [INST-ACK ] 02 62 38.E0.DD 1F 20 09 00 00 00 00 00 00 00 00 00 00 00 00 00 D7 06 (09) Fri 02/01/2019 09:15:36 PM : [INST-TX-I2CS] 02 62 38 E0 DD 1F 20 09 00 00 00 00 00 00 00 00 00 00 00 00 00 D7 Fri 02/01/2019 09:15:36 PM : [INST-ACK ] 02 62 38.E0.DD 1F 20 09 00 00 00 00 00 00 00 00 00 00 00 00 00 D7 06 (09) Fri 02/01/2019 09:15:45 PM : [INST-TX-I2CS] 02 62 38 E0 DD 1F 20 09 00 00 00 00 00 00 00 00 00 00 00 00 00 D7 Fri 02/01/2019 09:15:45 PM : [INST-ACK ] 02 62 38.E0.DD 1F 20 09 00 00 00 00 00 00 00 00 00 00 00 00 00 D7 06 (09) Fri 02/01/2019 09:15:49 PM : [38 E0 DD 1 ] Memory : Write dbAddr=0x4008 [09] cmd1=0x20 cmd2=0x09 - Failed Fri 02/01/2019 09:15:49 PM : [D2D EVENT ] Event [38 E0 DD 1] [ERR] [1] uom=0 prec=-1 Fri 02/01/2019 09:15:49 PM : [ 38 E0 DD 1] ERR 1 Has anyone else seen anything like this happen? I'm assuming warranty claim. Replacing this switch with another one in the same location shows no trouble at all. Comms have always been good.

Thank you!!!

Just picked up one of these myself. Anyone know what "Off Button Timeout" means?

and everything else too, though

Correct. At least in my case, however, the dot that is connected to external speakers via the line out jack is significantly time shifted vs. the other dots. I would love the ability to configure which echo's announce an incoming call, as the reverb is horrendous.

Benoit, I wanted to let you know that I finally got a chance to test this today. Although thanks to how extremely universal the isy is, I had a workaround, but this is now significantly more straightforward and user friendly. Instead of the requirement to have an alexa routine turn a program OFF, where the else in the program was to turn a scene ON, I can directly turn on a scene through a routine now (with isy scene exposed as a light). I set it to turn on to 100% brightness and it worked great. Thanks for the update.

Yes, it will announce the full phone number for a number that isn't in your address book. I forget the details of other options to set it up, but mine is set up with my cell phone address book, so it announces the name when someone calls the landline as if that number was calling my cell.

I have a single echo connect hooked up to my voip.ms service. One of my echo dots is connected to the whole home stereo system, so when somebody calls it announces the caller through every echo device as well as all the house speakers.

Can you please provide more information on the "fix for Alexa routines using ISY scenes exposed as devices?" I currently have an issue where I can't turn a scene exposed as a device on through a routine. I have to have the routine turn a program off, where the program turns my scene on.

This is awesome. I used this same basic idea to create a bunch of programs to monitor and control my 2 garage doors. Both doors are wired to elk zones and relays. Instead of using mobilinc to open/close, I use KPL buttons. I originally had it working using the elk module to look for "normal" or "violated," but using the variables makes it a lot easier to follow. I especially like the opening and closing status variables. Thanks!

I really don't use dimming very much. That's a good idea, thanks. While I have you engaged here, are you aware of the alexa routine problem where a routine is incapable of turning anything on? It will only turn something off, so I had to write a program where the else is to turn my scene on. Now the routine turns off the program which turns my scene on. This required exposing the program as a device/light and giving it a spoken, of which I just made the spoken some garbage to not accidentally trigger it that way. This also seems like an alexa problem, but could be the portal, i don't know. The isy event viewer sees nothing with the on command from a routine. I believe I saw a thread on the forum here somewhere about this and the program workaround was suggested. Sent from my LG-H915 using Tapatalk

That's it. Sorry I overlooked that detail. None of my devices are by themselves in alexa, so they are all scenes exposed as lights. I'm probably stuck with this alexa problem because I like to keep my kpl status buttons synced with my lights. Sent from my LG-H915 using Tapatalk

Is there anything I have to do if I'm still getting the error message in the alexa app? Sent from my LG-H915 using Tapatalk

OK, update to above post. Thanks to this amazing ISY portal update, changing my ISY program to an Alexa light instead of an Alexa scene allows me to run the ISY program within an Alexa routine. Thanks UDI for making this so flexible and useful! Unfortunately the Alexa app really complicates things when coming from an ISY background, but it's amazing that UDI is able to make everything work so well given all of Amazon's API restrictions. I really wish Amazon didn't force the thermostat functionality change, but the rest of my Alexa/ISY system is working exactly how I want it to now.

Working well! Thank you! Every ISY scene that I configure as an Alexa light now works properly in each Alexa group when I say "turn the lights on/off" in a room. One issue I am having, which seems to be on the Amazon side and not the ISY portal side, is that when I have an ISY program configured as an Alexa scene in the portal, that scene shows up properly under alexa app/smart home/scenes, but I can not control it via Routine/Smart Home/Turn on scene. For some reason in that menu, the scene doesn't show up in the list. If this is already a known issue/already reported to Amazon, then disregard. I'll continue poking around with a work-around, like maybe making my program a light in alexa instead of a scene. This is all still rather confusing, but with the help of this forum I've been able to get nearly everything working exactly how I want it to. Thanks everyone (especially Benoit for v3/portal update!)

Sure do. Maybe they're still messing with it. It was only a couple weeks ago before i could even find the app on the play store. It was a few days after the announcement that the hardware would be released dec. 5. Before that i had to download the apk. The latest apk i downloaded was older than this version that updated from the play store though. Sent from my LG-H915 using Tapatalk

I hope so. Thanks for pointing out the potential discrepancy though. Sent from my LG-H915 using Tapatalk

I updated from the canadian google play store to 1.24.3096.0. Sent from my LG-H915 using Tapatalk

Kingwr, thanks. You have communicated exactly all the same issues I am encountering when going to v3. I don't really have any lights that I would control without a scene due to kpl sync issues. For now, v2 works a lot better for me. The only thing missing in v2 is the ability to generically say turn on the lights in a room without saying the room name. V3 lost a lot of functionality for mw until there is an ability to tell alexa that a scene is a light. Sent from my LG-H915 using Tapatalk

I've had routines working for a week or two and they all suddenly broke. I noticed this morning when it said "sorry I'm having trouble please try again in a little while." Still saying the same thing this evening. Anyone else have this issue? Sent from my LG-H915 using Tapatalk

That's all I was looking for. Thanks. Surprised the spread of approval time is that large. Not good for them... Sent from my LG-H915 using Tapatalk