zorax2

Down in MN. Maybe somewhere around 10 PM Central time.

Down in MN. I have the same error. I also can’t use the UD mobile app.

Issue solved - my router not the portal. Thank you Michael for determining that outbound traffic for the eisy was blocked. In case anyone runs into a similar issue, here is the rundown: I use a VPN on my ASUS router along with its built-in VPN director (with the eisy’s address specifically assigned to the WAN which had been working correctly with that configuration). At some point yesterday, I had to change my personal computer connection for its IP address from the VPN to the WAN for a financial transaction with a dropdown box to switch the connection type and applied the new setting for that specific device. It appears that even though I made no changes to the eisy’s WAN assignment in the VPN Director, something must have went awry when the change was applied. I turned off the VPN entirely and the eisy is now back online with the portal. I never would have expected the change I made on the VPN for my personal computer’s IP address shouldn’t have affected the eisy and I would have never thought to check that setting as there seemed to be no reason the change I made would have affected another device on the network.

My Alexa integration on my EISY stopped working. My EISY is hardwired ethernet on battery backup. I did a full power-off reset. Logged in to administrative console and "Portal Integration - UDI" showed offline. Any ideas? Local issue on my side or with the portal?

@Javi Any recommendations or should I turn in a support ticket?

@DennisC I'm on eisy running the current firmware version 5.8.0 I am on the latest UD Mobile I have rebooted the eisy via Configuration / eisy System Settings / Reboot

I recently added notifications to the mobile app and PG3 and it seems to have corrupted the notification system. I’ve put this in the PG3 Notification section of the forum – hopefully this is the right place. Prior to making this update, my notifications did work properly. Once I made the update, all of my existing notification content (Burglar Alarm, Fire Alarm, etc.) were replaced by “Response Type2”. If I go to If/Then, I am not able to use the “Remove Line” button to delete “Response Type2” and make changes. If I go to “Customizations” to add new content, I am unable to add new content as clicking the box does not do anything. I’ve attached a copy of the error message that shows within the Mobile app if I try to add a notification there. I’ve also attached a screenshot of the PG3 notification installation. Is there a way to fix this? Or, will I need to go back to a backup to start over with this?

@dbwarner5 Does the program operate something like this in terms of logic? 1. Tracking variable or armed status from Elk module indicates that system is armed. 2. Your random light program runs the "Then" part of the program (within the hours shown - I assume with the option to run it daily checked to keep the program running until you return). 3 Tracking variable or disarmed status from Elk Module indicates that system is disarmed. 4. Your random light program runs the "Else" part of the program and turns everything off.

Thank you both @RPerrault and @dbwarner5 for the great suggestions!

@Jimbo.Automates Time for your laugh of the day... As you wrote, my first example should have worked perfectly yet didn't. Your example showed a similar syntax to what I was using so I was puzzled. My next step was to go through every single program folder to check for anything related to arming / disarming. Here's the shocker and reason things weren't working, the top hierarchal folder "My Programs" had an IF: "Home Armed Staus is Disarmed" which only allowed any of my programs to run when disarmed. Oh my! I have no idea as to when that If statement was added. If the system was in "Armed Away" status, it meant I was gone away from home and therefore had no idea that my programs weren't running as intended. Somewhat obvious to me now is that we rarely armed our alarm system over the years since our kids were growing up and someone was always home. Now that we'll soon be empty nesters, we'll be arming our system regularly and it's good to know all my programs will run properly. Thank you very much for your reply as it prompted me to dig further!

My simple goal is that while I’m on vacation or away from home, I’d like to have some lights turn on (in my case I’m trying to set lights to turn on at specified times each day while I’m gone). I thought this would be very easy to accomplish but having tried every approach I can think of, I can’t get anything to happen when the Elk’s Armed Status is “Armed Away”. Can anyone provide a way to accomplish this goal? None of these methods worked with screenshots below as I don't know how to insert them within the message: 1. My first try was what I thought would be the easiest simply using armed status as a trigger. 2. My second try was to set a rule within Elk to turn on output 80 to use to start a program. 3. My third try was trying to use a state variable to activate a program. I use the Elk to trigger a lot of activities such as turning on a light on/off when a door is opened/closed. I’m able to arm and disarm within the Elk Module using the ISY Admin Console to “Set Armed Status”. From my perspective, everything with the Elk Module is working properly. I've also attached a screenshot of my Elk status in armed mode: Thank you in advance for any help you can provide!

PM Sent with log package attached. Thank you.

I’m having the same issue. I thought I was perhaps losing my connection with the Internet provider but it’s always one minute at random times.

Thank you! I'll go ahead with your recommended solution.

I recently started receiving notifications on my UDI Mobile App showing "ELK (1): Failed from PG3" followed (usually within a minute) by "ELK (1): Connected from PG3". These notifications are at least daily and sometimes multiple times per day. I turned off the sound for notifications due to the frequency of the notifications. I don't recall this happening in the past and it seems to have started within the past month I'm guessing. I just thought it was an aberration and would go away on its own. In terms of troubleshooting, I'm stumped. I have my cable modem, router and ISY on an uninterruptible power supply. There is no evidence of a bad internet connection at the failure times on either my cable modem or router logs. My Elk alarm panel gave a system battery error last week but I replaced the system 12V 8AH battery within a few days and continued to recieve these notifications both before and after the battery replacement. There are no other causal factors I can tie to this other than the notification behavior seems completely random. Any ideas?

Thank you @glarsen! For some reason, I didn't see that option previously - either I overlooked it or it initially wasnt there. Nevertheless, I was able to install it and appreciate your help!

I purchased this (didn't realize there was a trial option as it didn't show initially) and can't figure out how to install it. It shows as purchased in the Polyglot 3x server store. The available purchase / install options shows Install Type is ZIP package. I can't find or haven't been sent a link to the Zip package to install the package. Does anyone know how / where to install this nodeserver? I'm hoping this well allow me to easily set a program to run one day a month. It's too bad you can't easily do this within the EISY's time function if / then statements.

I wish I documented my steps better but I think I had to reload the devices within Alexa app to get new "spokens" to work. I think it was Add Devices, all the way to bottom to choose other (House with wifi symbol in it), Device doesn't have matching logo, Device needs to be setup using device manufacturer's app, Discover Devices. I had to fumble around a bit to get everything working but it is pretty solid once it works though we do occassionally find that Alexa doesn't "understand" commands at times even though they work 99+% of the time otherwise.

I have a similar setup with more devices, no Schlage locks, Portal, connection with Alexa and hadn't used the UD Mobile app. In the end, I'm thrilled I upgraded to eisy and am now enjoying the UD Mobile app. If you update your ISY994, print a topology report and document things well, I'd expect you'll have a smooth transition / migration to the eisy. I wouldn't go back to factory clean unless you have a real need to do that or something goes horribly wrong in the process. The greatest challenge I had was finding everything hunting between wikis, the forum and elsewhere as to how to configure things as my system was rock-solid and I hadn't done much other than use the 994 to add devices over the years. Transferring the portal goes well if you follow the instructions. The PG3 version of Elk was new to me as I had the Elk Portal. It was a bit of a struggle to initially configure so I put a step by step approach in the PG3 Elk thread to help others. I initially had trouble having started with ethernet and then trying WiFi as there was a bug that was since corrected. I really appreciate the increased speed / snappiness of the eisy's interface coming from the 994. I wish there was IR but someone is trying to figure out how to add that via PG3. I invested more time than I would have liked and do hope for documentation / steps to improve over time. I'm pleased to have shown UDI continued support by purchasing the eisy (as I really had no need given my system was rock solid). The new eisy does however provide me with newly developed updates and the ability to do things as technology changes so I'm happy I upgraded. Give yourself a bit of time to do the upgrade and I'm sure you'll be thrilled with the new eisy platform.

IR thread for eisy - see later posts in this thread.

Easiest way I know is via IR. Here's how I used it with my URC remote (MX-990). The remote is both IR and wireless (not WiFi in my case) RF capable. We have a large home and have 3 IR/ RF receivers /transmitters (MRF-350s with RFX-250 remote sensors) to ensure full coverage throughout our home. I have at least ten MX-990s scattered throughout our house. I have one IR output from the MRF-350 that was placed in front of the IR reciever for the ISY 994. I'm sure you could do it this way with any of the high-end remotes. You just have to teach the eisy some IR codes - the instructions are in the forum. My preference for high-end remotes is the Crestron but it gets very spendy as you know or will find out. I prefer the Complete Control line so I can DIY and program my own devices since I'm always changing equipment. However, URC locked out home users from their software a couple of years ago but made exceptions for some long term home users who paid for licenses. I have at least 50 Insteon devices. I setup on/off and dim commands for many of those devices and it worked flawlessly for me with the ISY 990 Pro IR and ISY 99. The problem is the eisy isn't IR capable. However, I think someone is developing an IR compatible receiver for the eisy. I sure hope so - IR works perfectly for many things. I imagine any of those companies could write a driver for the Universal Devices eisy and you could port it for whatever commands you need. There are several companies that can do this if I remember correctly.

I am at this point up and running with everything on my eisy (All Insteon working, PG3 and Elk Node Server working, UD Mobile working). I have my eisy in wired mode and decided not try to change it to wireless mode. I had everything working last night with eisy but could not get UD Mobile to integrate with eisy no matter what I tried on the app. I tried to get UD Mobile working this morning and "Bingo" everything worked. I have no idea as to what may have changed given all the permutations I previously tried. I'm just thrilled everything is working!

Change specified (do not do step #14) made to the original post. Thank you for reviewing the steps.

I'm using a ASUS RT-AX86U WiFi mesh. Rock solid, new firmware, mesh configuration in large home. I've been trying to connect via the wired (rather than wireless) process on the UD Mobile app from my iPhone on my regular (non-guest) network with no luck either. I am able to connect and setup the portal. No matter what permutation of settings I try, I'm having no luck connecting to my eisy. It can see it and gives the correct MAC address under the system name but can't connect remotely via the ISY portal or with local network connection settings. I'm stuck.

This morning I decided to factory reset the eisy and started over by migrating my backed up 994 file. Everything transferred easily and worked correctly. The ISY portal and Alexa integration were easier to connect as the license had been transferred already. Voice commands worked right away. I then installed the PG3 Elk Node Server to replace the Elk Module. All went well and everything seems to be working fine. No lights on and off, dimming, system busy or weird behaviors. For me the only change was that I did not use the UD Mobile app at any time during the migration process and did everything via hardwired ethernet.