EddieRock

so... let's say, it's not worth the time to investigate why the garage door opener is faulty and let's not get into the security war/discussion at this time What ZWave door opener is the best (for security and reliability) and works with the ISY ZWave module? So then I gotta ask, is the ISY ZWave module reliable and secure? It sounds like ELK is the way to go but I don't want to go there now. Actually, as I write this, Really, I don't use anything to open/close my GDO. I really only use it for the notifications. If I disconnect the wires to the GDO, I should simply get the open/close alerts. Right? All relevant and productive replies are welcome

No clues in the logs. I have a secure (https) rdp session that I can log into my computer (Sophos UTM9) and then run HAD (The Home Automation Dashboard) to close the door. In one case, the HAD would send commands to the IOLinc and it wouldn't respond. Later, it did. I have a hunch that the IOLinc is starting to fail and this is a side effect. Thoughts? Any way to test or get logs? I feel that these events could be phantom noise that is causing it to open...

MWareman said: "It's neither secure or reliable" Can you be more specific? mine has been almost 100% reliable. Why do you say it's not secure? I'm looking at Elk but I have to do some renovation of my house before I put it in so I don't have to do it twice. I think this has happened once before but for some reason, it's happened 3 or 4 times this week so something went wrong. I'm trying to figure out what it is. I don't like to not know why...

I already have notifications setup. Yes, the do tell me via pushover. I was using email to txt and that was simply unreliable. I checked the time from the messages, I also checked my video (I use Milestone Systems if anyone is interested) of my garage to get the exact time. Nobody around, it just opens.

I can check. This has been installed for a few years and I've strung my wires with care Did you're actually open if the door traveled away from the sensor? I was thinking that part would be just "sensing" and the relay was simply acting like it was pressing the button.

For the last 3 days, my garage door has opened on it's own (4 times total). I've checked the logs around the time and I don't see any logs indicating that it was triggered by the ISY. The second time, I tried to shut the door with the HAD and it wasn't responding. I had unplugged the garage door relay for about 10 minutes and plugged it in. The door didn't respond after but is now working fine. The only change I've made is that I've switched over to Pushover for my notifications which is working fine so I don't think it's related. Could this be a failing relay or could there be something else going on that I can troubleshoot. I would like to sniff the network if possible to see if there is any other noise or things that could be causing this. is there a way to do this and log to a file for review later? ISY 994i ISY Firmware Version 4.6.2 ISY UI Version 4.6.2 Any help would be appreciated. EddieRock

Actually, they already replied with a better answer... Not sure how they can direct device discovery to another ISY from my Echo but that's scarry.... Hi Ed, I am so very sorry for the inconvenience. Here's what happened : To test performance, we directed device discovery to a test ISY. I.e from Echo to Portal to ISY (not the other way around). We cannot control anything in your ISY without a token from your Echo which is only created by Echo. Again, this was a test for device discovery form Echo to a low bandwidth ISY and not the reverse. Ed

So, how is the NOT a security issue? So, how I understand it... UDI can inject devices that weren't discovered into my system through the ISY Skill OR ?? Please explain how this vulnerability will be addressed. There were around 15-20 devices on my echo from 12/8. The email I just received: ISY Portal / Amazon Echo Discovery Error Dear ISY Portal Subscriber, With sincere apologies, during our last performance tune up for ISY Portal / Amazon Echo on 12/08/2016, we introduced a bug which was fixed within an hour. This said - and unfortunately so - during that one hour your Echo performed its automated discovery and discovered devices that belonged to a performance test system. Although you will not experience any service interruptions and/or performance issues, we do recommend that you follow the instructions below in order to have those test devices removed from your Echo Smart Home profile: 1. Login to https://echo.amazon.com 2. On the left navigation bar, click on Smart Home menu item. On the Right pane: Method 1 - Remove Everything and Rediscover 3. If you have defined any Groups, please make note of them as you might have to recreate them 4. Scroll all the way down 5. Click on Forget all devices and groups link at the bottom 6. Once that's done, scroll up a little and then click on Discover devices 7. If your Groups are missing, please recreate them Method 2 - Selectively Remove Erroneous Devices 3. Slowly scroll through the list of devices 4. If you don't recognize the device name, click on the Forget link at the right end Again, sincere apologies for the inconvenience. With kind regards, UDI Sales ~WOW!!!

Can you send me a link to the z-wave device you use?

Well, at least my system tells me when the door opens. Both times this happened, I had a low battery in a Insteon motion sensor. @larryllix the IOLink was new in the box and I do not have any X-10. My neighbors do not either.

Paul, Yes, I've set most of my multi then statements with 2 seconds between set lines. Must have missed this one. Interesting is that I haven't changed anything with my ISY since March (I think) and the kitchen motion sensor triggers this program 2-3 times a day without any side effects. I'll add the 2 second wait times.

Yes. I have a motion sensor in my kitchen. If there is no motion, it turns off all my scenes and lights in that room. That occurred 4 seconds before my garage door opened. Unsure if it's related. Also, that motion sensor is NOT the one that had the low battery. Ed

I have ISY v4.4.6 and it's been running flawlessly! Love it. I've had no issues or questions since March. For the second time, I've been at home and I receive a text that my garage door has opened. I rewind my security camera and lone behold, it opened on it's own. This is the second time this has happened so i now need to know what I should check. I remember reading a while back that someone mentioned that if you have an Insteon motion sensor that is low on battery, it may cause strange things on the network. I have one of those and the batt was low. Garage Door Opener is an Insteon (2450) IOLink v.41 Anyone have any ideas? here are the last logs I have. Between 6:40:22 and 6:40:26 something caused the Garage Door to open. I do not have any programs to open or close the door. Just notification programs. Kitchen Level / Kitchen Motion - Sensor Status 0% Mon 2016/09/12 06:40:21 PM System Log Scene:Kitchen Level / Kitchen Evening Mode Scene A Fast Off Mon 2016/09/12 06:40:21 PM Program Log Kitchen Level / Kitchen Can Lights Fast Off Mon 2016/09/12 06:40:22 PM Program Log Scene:Kitchen Level / Fireplace Lights Scene Fast Off Mon 2016/09/12 06:40:22 PM Program Log Kitchen Level / Kitchen Sconces Fast Off Mon 2016/09/12 06:40:22 PM Program Log Kitchen Level / Kitchen Under Cabinet Lights Fast Off Mon 2016/09/12 06:40:22 PM Program Log Scene:Kitchen Level / All Kitchen Lights Scene Fast Off Mon 2016/09/12 06:40:22 PM Program Log Kitchen Level / Kitchen Can Lights Status 0% Mon 2016/09/12 06:40:22 PM System Log Scene:Kitchen Level / Under Cabinet Lights C Scene Fast Off Mon 2016/09/12 06:40:22 PM Program Log Doors, Garage and Outdoor / Garage Door - Sensor Status 0% Mon 2016/09/12 06:40:26 PM System Log Bedroom Level / Bedroom Thermostat - Main Humidity 52% Mon 2016/09/12 06:43:38 PM System Log

I believe there can be security built into it via a "Skill" that UDI can program. In other words, the ISY and the Echo get linked and there is an option for a program or insteon device to "Send" the word or words to the Echo on the same network. Similar to linking an insteon device to the ISY. We would "Link" the Echo to the ISY (or vice versa) and then send words to it that it can speak. Similar to sending out an email or notification via SMTP. We could have a secure link between the ISY and the LOCALLY connected Echo. Currently, My echo only does what we tell it that it can "hear" from the microphone. I'd like it to "hear" from the network if the following is ture: secure connected app/skill/appliance manually approved (and configured) commands/words/phrases from ISY securely developed communication On/Off configuration from both the Echo and ISY Obviously, UDI/ISY would ensure that it is secure

Please...!!! let there be the ability for UDI to push voice/speech to my Echo! If this is possible, please look into it. I would LOVE to have my echo's say "Front Door Open", "Garage Door Open". Even if the time is between 6:00 and 9:00 AM, and my motion sensor detects movement, I'd like my echo to say "Hi Ed, The forecast for today is...." and much more. Pushing commands to the echo is absolutely a must to complete my system. If this is already available, please let me know how to do it. I'm currently in pain Thoughts?? EddieRock

My Amazon Echo is at version 3202. I DID NOT order any other echos. I did unplug it overnight and plugged it in this morning. Maybe it updated then. I never checked it's version before reading this thread. Mine is also a recent purchase (1 month old). EddieRock

Thank you @MWareman for the response. After some troubleshooting last night and this morning, I had a network switch that had gone bad and was flapping some ports. Once I remove that, all the problems had gone away. During my troubleshooting, I had realized that the ISY and PLM were working correctly as everything seemed to work fine from an automation standpoint. So, after putting those puzzle pieces together, I concentrated on my network. Systematically turning things off and/or unplugging them to reduce complexity steered me in the right direction. Time to go to MicroCenter to pick up a new switch (with a price match on Amazon ) Ed

I attempted to log in again and the system does seem to be acting normal now. I made another backup. I could restore from Sunday but I would like to know what the problem may have been. It wouldn't even respond to a ping earlier. It's all back up, responds to pings and is accessible via my.isy.io. Let me now if anyone needs more info to help me troubleshoot. Regards, Ed UPDATE: It's happening again after 10 minutes or so. here is a latest ping of the device: Request timed out. Reply from 192.168.0.230: bytes=32 time=3ms TTL=60 Reply from 192.168.0.230: bytes=32 time<1ms TTL=60 Request timed out. Request timed out. Reply from 192.168.0.230: bytes=32 time<1ms TTL=60 Request timed out. Request timed out. Reply from 192.168.0.230: bytes=32 time=2ms TTL=60 Reply from 192.168.0.230: bytes=32 time<1ms TTL=60 Reply from 192.168.0.230: bytes=32 time<1ms TTL=60 Request timed out. Reply from 192.168.0.230: bytes=32 time<1ms TTL=60 Reply from 192.168.0.230: bytes=32 time=4ms TTL=60 Reply from 192.168.0.230: bytes=32 time<1ms TTL=60 Request timed out. Reply from 192.168.0.230: bytes=32 time<1ms TTL=60 Reply from 192.168.0.230: bytes=32 time<1ms TTL=60 Request timed out. Reply from 192.168.0.230: bytes=32 time<1ms TTL=60 Reply from 192.168.0.230: bytes=32 time<1ms TTL=60 Reply from 192.168.0.230: bytes=32 time<1ms TTL=60 Reply from 192.168.0.230: bytes=32 time<1ms TTL=60 Reply from 192.168.0.230: bytes=32 time<1ms TTL=60 Reply from 192.168.0.230: bytes=32 time<1ms TTL=60 Reply from 192.168.0.230: bytes=32 time<1ms TTL=60 Reply from 192.168.0.230: bytes=32 time<1ms TTL=60 Request timed out. Reply from 192.168.0.230: bytes=32 time<1ms TTL=60

I noticed that my ISY was not available online (my.isy.io Portal and via my PC using Java) and I could not log into it. I rebooted my ISY and PLM. it would respond but extremely slow. Once I finally got logged in, none of my programs were available, and the logs were empty. I was thinking that I had a run-away program but there were none there. I decided to try and click on "Undo Changes" under program details and all my programs came back or appeared. I clicked on Save changes after that. I then tried to do a backup and then I noticed that all my icons were blank and there the backup/restore options are unavailable. On the main page, there is a red ! on the ISY. After I clicked in the "Undo Changes" the system does seem like it's responding now and I can turn on/off devices from the Main tab. The front of the ISY only has the blue light on. Before and after the restart (unplugging power). Any idea of what's going on? I could do a restore (backup after every change) but I'm afraid to move forward until I get some understanding of what's going on. Also, all the programs do seem to run fine. Any help would be appreciated EddieRock ISY Version: 4.4.3 EDIT: I Got into my logs and attached the error log ISY Error Log.v4.4.3__Thu 2016.03.24 09.53.21 PM.txt

*** UPDATE *** I have done some testing (which I'm not done with yet) and simply disabled my query program to see how the tstats reported. They all stay on heat mode and they all report back to the ISY without issues (so far). My test for the tstats not being on heat mode still is running but... there isn't a "trigger" to set them off. If someone manually turns them off heat, I get a txt. I'm going to setup a program test on 1 tstat to set a low threshold and alert on it and then set the heat mode "setpoint" to be below that to ensure I get a text if it breaches the program test temperature. Suggestions and input are welcome Ed

Michael, I was just replying that I figured it out. I have egress filtering enabled on my router for security purposes. For testing, I enabled my ISY to talk to the internet on all ports to all IP's. This is OUTBOUND only and has nothing to do with port forwarding So, for the ISY to talk out to the portal, does it only need 443 and 8001? If so, I can just enable those ports but would like to ensure I have the necessary info before I restrict via port. thanks for the quick reply EddieRock

I've followed the instructions for setting up the portal and i can't get it approved. What I've done so far: I upgraded my ISY to 4.4.3 and UI (Verified by going to Help > About) Also cleared my Java Cache I created a portal account and added my UUID to it (Verified that it's correct as well) I purchased the portal and added it to the ISY In UI under Portal Status/Configuration I have: Portal Integration - UDI: Offline and Not Registered Requested Services: Pending with the +Approve button. I click on that and then refresh. The pending request never goes away AND in the portal, the ISY says it's not online I've read that I DO NOT need to do any port forwarding which is preferred I've rebooted the ISY and logged out/in on the portal What am I missing here? My ISY is using port 8443 for HTTPS and the HTTPS says it's TLS 1.2 and I'm using HIGH strength EddieRock

Maybe I fully don't understand how the triggers work relating to an Insteon thermostat then. It sure seemed that what I had programmed worked and that's why I'm throwing this out for help. So, are you saying that the below statement DOES NOT ask the thermostat the mode it's in? Does it simply look at the ISY's last report received from the thermostat query. That's what the queries are for? I may be totally confused how this works...: If Status 'Bedroom Thermostat - Main' is not Mode Heat ELI5 then? Ed

I'll try this! Thanks Stu Ed Sent from my Android device

So, I'll lay it out below. The "If Status" programs check for state changes. I have three types of programs and also a query program. I'll list them below and explain them best I can. I searched for a "Best Practice" for Insteon thermostats and ISY. I found this and followed it: http://homeautomationguru.com/programming-your-insteon-thermostat-with-the-isy-994i/ I have States, Events and Actions. If you read the page at the above link, he can explain it. My programs for ONE thermostat are below and my main Query program. Main Query Program (this queries the tstats every 15 minutes. It was recommended that I do this. If it's a bad idea, let me know why. Please don't just say it's bad...) If Time is 12:00AM Then Repeat Every 15 minutes Set 'Bedroom Thermostat' Query Set 'Apt Thermostat' Query Set 'Green Room Thermostat' Query Set 'Kitchen Thermostat' Query Else - No Action Action: Bedroom Thermostat Too Cold Program (This is a fail backup program. If something happens to the furnace or boiler and the tstat can still talk to the ISY, I will be notified every hour. If Status 'Bedroom Thermostat - Main' < 45 (Temperature) Then Set 'Bedroom Thermostat - Main' 50 (Heat Setpoint) Repeat Every 1 hour Send Notification to 'Ed' content 'Bedroom Temp Too Cold' Else -No Action Action: Test Thermostat Heat Mode Off Bedrooms If Status 'Bedroom Thermostat - Main' is not Mode Heat Then Send Notification to 'Ed' content 'Heat Off Bedrooms' Set 'Bedroom Thermostat - Main' Mode Heat Else -No Action Action: Test Thermostat Heat Mode On Bedrooms (this sends me a text when the tstat is changed to Heat. I get this text after the above "Heat Off" program fires. Basically, is a status check that the above program ran correctly. If Status 'Bedroom Thermostat - Main' is Mode Heat Then Send Notification to 'Ed' content 'Heat On Bedrooms' Else -No Action Thermostat Daily Notify of Temps (Gets the temp twice a day and ensure they are all on heat mode also, send me a text with the temps) If Time is 8:00AM Or Time is 5:30 PM Then Set 'Bedroom Thermostat - Main' Mode Heat Set 'Apt Thermostat - Main' Mode Heat Set 'Kitchen Thermostat - Main' Mode Heat Set 'Green Room Thermostat - Main' Mode Heat Send Notification to 'Ed' Content 'All Thermostat Temp Status' Else -No Action There are also a handful of "Event", "State", and "Action" programs that shouldn't make a difference so I won't list them. They just adjust the temp twice a day. The odd "Off" messages I receive do not correlate to the times of these programs. So... With the above programs, I can keep an eye on my on my systems and have enough notification to get something fixed.