DNewkirk
Members-
Posts
10 -
Joined
-
Last visited
Profile Information
-
Location
: New Jersey
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
DNewkirk's Achievements
-
The old AJAX and Home Automation Dashboard local interfaces which were built into IoX on the ISY 994 are still present on the EISY (at least in version 5.7.1). They have been deprecated and may be removed with any future updates, and some options are not functional (for example, the admin console doesn't seem to open from the UD AJAX interface). Basic control of devices, scenes, programs and variables seems to work, at least for Insteon devices. On the EISY, http and https ports have been moved from default 80 and 443 to 8080 and 8443 respectively. In addition, the mapping of a default web page has been eliminated, so the exact URL to the desired page has to be specified. They can be accessed at the ip address of the EISY, or alternatively at eisy.local if the EISY is properly registering its name. EISY Local URLS include: UD AJAX interface: http://xxx.xxx.xxx.xxx:8080/WEB/udajax.htm or https://xxx.xxx.xxx.xxx:8443/WEB/udajax.htm Home Automation Dashboard interface: http://xxx.xxx.xxx.xxx:8080/WEB/HAD.htm or https://xxx.xxx.xxx.xxx:8443/WEB/HAD.htm You can also download the appropriate admin console for your version from the EISY at: https://xxx.xxx.xxx.xxx:8443/WEB/admin.jnlp or access your local Polyglot server at: https://xxx.xxx.xxx.xxx:3000
-
After trying a number of different wiring combinations, it turned out to be that I had a Netgear router configured as an access point in the barn that must have been blocking some protocols. It wouldn't let the EISY connect to NTP, and I couldn't SSH into it. The funny thing is that I wired it to the network exactly as the 994 had been wired, and the 994 never had an issue with it. The EISY didn't like it, though. Go figure. In the end I just had to switch one patch cable to resolve the issue, but it took me three days to figure that out, with Michel's help.
-
Michel resolved this issue through a support ticket. TLDR: It was a network issue My 994i was always located out in my (heated) barn, since that is where the majority of my Insteon devices are. I originally started using Insteon to control the various lights and doors in the barn so that I wouldn't have to run a bunch of switch legs back to the house. The barn has a CAT5 run (about 100 feet) from my house network with a 8 port switch on it, and various other network connected gear. The 994 worked fine on it, as do my other items out there (Roku, laptop, etc.) The EISY must be more particular about its network connection, or there is some kind of issue with that network run or switch. Including the barn switch, the EISY was two hops from my main router, which is another two hops from the internet. The EISY couldn't communicate through that many hops, or at least through that particular connection. When I brought the EISY into the house and plugged it directly into the router, everything works fine. FYI for anyone else who is suffering from this, the symptoms were that the EISY would not synchronize its time, my Polyglot Dashboard wouldn't launch, and I couldn't SSH into the system. I could talk to it fine through Admin Console and UDMobile could connect and sync. IoX launcher found it without a problem, and the EISY got a reserved IP address through DHCP and reliably registered eisy.local with the router. Since the EISY responded on the network in many ways, and it was literally a plug and play installation of where I had the 994 installed, I didn't think that it could be a network issue. Relocating the EISY proved that this was the problem.
-
I can change the timezone (including putting in a custom Lat/Long), but it is already correct. EISY isn't updating its time, and I have no way of manually setting the time or forcing a time update. It thinks it is February, 2021, so that doesn't seem like a timezone issue. In the 994 admin console system configuration page, the clock area had options to synchronize with the computer time, to manually adjust the clock, or to enable an NTP server, including specifying the server and sync interval and forcing an immediate synchronization. None of those settings appear in my EISY admin console. If this is by design, then the EISY must automatically just go to a time server, but mine is obviously not doing that. Making NTP the only option would make the EISY useless on any installation that isn't connected to the internet, so I wouldn't think that that would be a design choice by UD. Internet isolated systems might be rare, but not unheard of. Anyway, thanks for your help @Geddy. Hopefully, I can get this straightened out through the ticket.
-
After the EISY cooects to the portal, you have to authorize the connection from the EISY. Go into the admin console, and on the Configuration>Portal tab, authorize the connection. Once you authorize the EISY to connect to the portal, the migration can continue The migration process on UD Mobile/portal only moves the portal license over to the new system and migrates your Google or Alexa spokens. It will not migrate your devices in ISY. Restoring your ISY backup to EISY will populate your network with all of your Insteon devices
-
I recently installed one of these (albeit on an ISY 994i 5.3.4) and only changed a few of the parameters. Looking at the options on mine now, this is what they show: Program Lock: not checked LED, Key Beep, Send Cleanup Messages and Send Cleanup Errors: all checked LED Brightness: 0 Off Button Timeout: I changed this to 300 minutes, but I think the default was around 1545 if I remember correctly. I believe that this is how long the detector waits to turn motion back on if you manually turn if off with the button on top of the unit. Motion Nodes: One Condition: Always Report: On & Off Sensitivity: I changed this to 255, but I think it started at around 35. It doesn't actually seem to make a difference what it is as far as I can tell. Timeout: 120 Seconds Light Polling Interval: 15420 Hysteresis: 5 Day Threshold: 80 (31%) Night Threshold: 64 (25%) Hot Not Hot: 74.4 F (69.0 F battery) Hot: 86.1 F (80.5 F battery) Cold Not Cold: 67.1 F (61.8 F battery) Cold: 69.3 F (64.0 F battery) Battery Nodes: None Low Threshold: 133 Misc. Nodes Motion Enabled: One Tamper: One I don't think it makes a difference, but my motion detector is not on battery as I power it with a 5V USB power supply. I only have experience with the one, but my motion detector seems to be a bit flaky. The sensitivity varies significantly from one day to another. Also, I have a program that when I turn on the garage lights from the switch, it sets the Motion Enabled node to off, and when I turn the lights off again, it sets the Motion Enabled node back to on. This is just to keep the motion light from going on and off while I am working in the garage. However, I have noticed that it takes quite awhile, maybe 5-10 minutes, before the motion detector will again function to turn on and off its light after I have toggled the enabled mode. Hope this helps.
-
This link worked to bring up the UD Ajax dashboard. The link to load admin console doesn't work. It brings up the Java splash screen that tells you to keep the window open, but never launches the console. That's what I thought, but that is not what my admin console shows, whether I launch it from the EISY or from the cloud. See the attached screen grab. My time section just allows me to change the timezone, but the other time items are missing from this section of the tab. Thanks! I've lurked here for awhile when I needed some information, but never posted before. I don't consider myself enough of an expert in this to give any credence to any answer I might provide.
-
Thanks for your response, Dennis. I have updated packages and rebooted multiple times (both by clicking Reboot on the configuration tab and by unplugging and replugging the power supply). If I update packages now, it just tells me that I am up to date (IoX 5.7.1 and PG3x 3.2.16). I can get to the EISY from the IoX Launcher to launch the admin console, but with the ISY, I also used the Ajax interface from the local webserver to control devices when I am home. I assumed that this was still available on the EISY, although maybe I am mistaken. I have tried the access from several different browsers, so I don't believe the browser cache is the issue. I know the webserver is working (can download the admin console via eisy.local:8080/admin.jnlp), but it seems to be missing many of its files, including its home page. Regardless of how I access Polyglot (either from xxx.xxx.xxx.xxx:3000, eisy.local:3000, from Iox Launcher, or from Node Servers>Launch Polyglot in the admin console, the result is the same. I log in (to Polyglot and then the portal) and get to a page that just says PortalAuth (see attached). Although these are all concerns, my biggest issue is the fact that the EISY won't update its date and time, and there are no controls for date and time in the Configuration>System tab, so I can't even provide the date and time manually. This means none of my automations will run (or more accurately, they won't run at the right time which is even worse). I was considering a Force Upgrade from UD Mobile Admin>Firmware under the assumption that that would force write all update files even though the system is reporting it is up to date, but I was hesitant to do that unless someone advises me that it might help. As I mentioned, I do have a ticket open, so I may have to wait until I get a response from the support team.
-
Another data point: I went into Help>About in the admin console, and the last line says: Internet Access: disabled. So, this whole thing could just be a misconfiguration on my part, but I can't find where to change this setting. In configuration>portals, my portal connection is active and registered.
-
I have been an Insteon/ISY user for about 7 years and have about 80 devices and a couple dozen programs, although my experience is limited to basic Insteon control and programs. I migrated my ISY 994i 5.3.4 to EISY 5.7.1 yesterday. It was a bit more of a process than the wiki migrate process seams to indicate, but in the end I was able to get the EISY connected to my Insteon network and load my ISY backup to get the Insteon side of things working, with some caveats: My EISY's date and time won't update. I am stuck in February, 2021. Obviously, this wreaks havoc with my scheduled items. In the admin console, on the configuration>system tab, it shows the time and allows me to set the time zone, but there are no controls for the time sync, i.e. time server, poll interval, manual set time, etc. as there was in 5.3.4. I don't know if this is by design, or if there is something keeping these items from loading. In any case, I can't update the time, and it isn't updating itself. The EISY web server seems to be missing some htm files. If I go to eisy.local:8080 or https://eisy.local:8443, I get a 404 error. If I go to eisy.local:8080/desc, the xml file loads, and I can get to the admin console from the LAN through IoX finder, so it seems that the EISY web server is serving pages, it just doesn't have its home page (and possibly others). If I go to eisy.local:8080/admin, the Keep this web page open page loads, but the admin console never loads. Eisy.local:8080/index.htm gives a page not found error. I tried going into configuration>networking>web server and clicking on Use Default then rebooting, but it didn't help. My Polyglot dashboard won't load. If I choose Polyglot V3 from IoX Launcher, it takes me to the Polyglot login page (as does eisy.local:3000). After I login, it brings me to the Portal to login. I login to the portal, and it brings me back to Polyglot with a page that just says PortalAuth at the top with two links: Home and Login, both of which just bring me back to the Polyglot login page, and the process repeats. I have successfully migrated my portal account, connected to the EISY and sync'd my network to UD Mobile, so the portal connection and UD Mobile seem to be working. I have cycled power on the EISY and reset my router multiple times (my EISY is connected via ethernet, so Wi-Fi is not in the equation. I have also updated Java, cleared my cache, downloaded the latest start.jnlp, etc. I have also opened a ticket on this item, but am hoping someone can provide some input on what the issue might be. Thanks in advance for any advice from more experienced users on the forum.