Geddy

Please see some troubleshooting steps in this thread and ultimate solution was network issues.

There have been a few posts about this a while back (both when Polisy came out and again earlier this year when eisy was released). Most feel since there is a lot more being processed by these more advanced systems that a proper shutdown or forced reboot is suggested so you know systems are halted/stopped and don’t risk becoming corrupt with a simple power pull. Of course if they aren’t on a UPS and the power goes out there’s nothing stopping the systems, but usually we (the users) see a power cycle as a quick/easy way to just restart everything. And usually it’s when updates have been attempted or if something is “stuck”. Often times that can be when systems become corrupt if not stopped properly.

The ticket link was in my previous post, but I see @Javi shared the link again. Technically it shouldn't be different, but many have found over the course of updates that sometimes the reboot button in admin console doesn't fully restart the eisy. For that reason a full power cycle might be necessary. I can sometimes tell if a system is hung or stuck if the muti-function button presses does not actually reboot or shutdown the system as expected. The wiki has the proper button pushes for the multi-function button (the power button) on the eisy. Hope it's a simple fix. Please try to post back what steps might have been taken to get this resolved so it might help others should they have this issue in the future.

Thanks for updating us on the issue. Are you able to keep the eisy closer to the primary router/modem or will you be moving it back to the barn? Did you resolve the network issues back out to the barn? (if moving it back out there) Wouldn't want it to become an issue again and have to keep moving it into the house to update/run stuff. Glad you got help through the ticket!

@midrar 2 nodes seems right. I have a Ring Doorbell Pro and only have the same as you. I have a program that when it dings will turn lights on. If you make a program use "Control" and your doorbell will show up and then you should get a "Ding" option. Your comment made me think about mine because I recalled that I had a ring a few days ago and events did not happen as expected. Indeed, my program was not triggering. Check on the UD Portal and see if your remote connection is active. Mine was "NO". I figured that might have been my issue and then pressed "Reconfigure" and after a moment "Refresh" and it went to "Yes". After that was yes I tested my doorbell and the "Ding" program triggered as expected. @Goose66 see if your portal is showing "No" for the active line. Just for reference the last time my "Ding" program had triggered was December 4th (based on the summary tab). I've had several dings since then so know it hasn't been working for about a week.

As @DennisC points out maybe just reboot or power cycle of the eisy will help. Otherwise, make sure the eisy and UD Mobile are completely updated. You can find the current firmware for eisy in the current release announcement area. Make sure you have the current version of UD Mobile from your mobile device store. If all this is confirmed and you're still having problems then let us know how you are connecting to the device. If through portal - maybe setup a local connection to make successful sync if locally then attempt portal connection for a successful sync Did you migrate to the eisy recently? If so, did you click on and save each network resource (that's part of the migration steps) Have you ever had a successful sync with UD Mobile? If so, what might have changed since the last successful sync? account credentials change? Network equipment change? If these fail the next best thing would be to open a support ticket with UDI and be sure to mark as UD Mobile issue. https://www.universal-devices.com/my-tickets

Try changing time zone (to not your correct zone) then power cycle. Check the wiki for button pushes to shutdown (I think it’s 6). Blue light should turn red. Then pull the power supply. Wait 30-60 seconds and power it back up. Wait about 2 min then go into admin console and change time zone back and/or put location back in. If the device is online when it boots some systems should try to sync with a time server. If still not updating and support gets you sorted out try to post the steps they give you so it helps others if they get into this situation. Good luck!

This hasn’t worked for years. At least don’t think it has. Mostly because browsers dropped support for Java. The suggested (only) way to access admin console is through IoX Launcher. All you should need to do is change timezone. Once in that screen does the bottom of the screen show custom location that you can enter latitude and longitude for your location? I’m not at a point I can get into my admin console so can’t try on mine. But should be where it is set. Helping others always helps strengthen the forums and you own comfort in the systems. Still, thanks for joining and posting. Hopefully between this and a support ticket things will sort out as expected.

Try this: http://eisy.local:8080/WEB/udajax.htm If your router isn’t allowing friendly URL replace “eisy.local” with the IP address of you’re device. Make sure you have set an IP reservation on your router so the eisy is always at the same IP address. As for the time issue, you should be able to change location in admin console on configuration tab just as you did in the ISY994. https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Configuration_Tab (I know this is “old”, but still applies for the most part) This is normal and not impacting anything. Don’t try to enable it. That’s not necessary for normal operations. PS: @DNewkirk welcome to the forums!

I agree with @Bumbershoot that I think the ticket is the best option now. Had you already run the "migrate to ZMatter Z-Wave" on the Polisy? I'm not 100% sure if that was ever an option on the eisy, but might have been in an early firmware. It might have been removed, but don't know. Reading the wiki the "migrate to ZMatter" is the only time it would give you a migration backup option (seems like anyway). Otherwise, I'd think like a normal backup if you ran the Z-Wave dongle backup first then backed up the IoX that it should restore everything on the eisy. But if you've tried it that way then I'm not sure the next steps to try. Good luck! Hope it's a simple fix. If it is...or even if it isn't...try to make some notes and post the fix here so it might help others should they run into the same issue.

@jdm5 For reference please let us know what IoX version you are running. Admin Console -> Help -> About If you've turned on Z-wave support do you now have a Z-Wave menu in admin console? If you're making a Z-Wave backup on the Polisy you have to also backup the IoX system. The Z-Wave backup is fed into IoX then your backup should include Z-wave information. I did not have Z-wave before having the eisy and it's been almost a year since I put things into service so don't remember the steps, but it's possible if you've just always had the Z-Matter dongle attached that it might not need that step. I think the migration was more for people coming from Polisy with different Z-Wave controller.

@NewTech As @Brian H says the reset button has multiple options "associated" with it. You can see on the wiki some steps in resetting: https://wiki.universal-devices.com/index.php?title=Resetting_Your_ISY

@x046866x, @Goose66, & @Whitehambone I suspect this is part of a known issue with a recent "behind the scenes" update that is causing issues. There's another post about it where @Michel Kohanim says a fix is in the works.

It’s all in one update process. I’m not sure if UDI pulled the IoX update that had an issue or if it’s still being worked on. Might be worth opening a ticket to ask directly. Otherwise, if not mission critical to have this node server running now you could wait until UDI makes a release announcement or updates on the issues.

Try here: https://eisy.local:8443/WEB/sysconfig.txt If not on eisy remove that and put "polisy". If the qualified domain doesn't work try the IP of your device in place of "device.local"

Not sure. I never recall trying the reset button on the ISY994. I would have just performed a power cycle. If you reset the router (or modem/gateway) make sure you’re using DHCP reservation for the ISY994 so it will reconnect to the same IP address. If you have the device set to static and there is an IIP conflict it’s possible it didn’t reconnect to your network correctly. The ISY994 should be set to Auto DHCP and the router/gateway should handle the DHCP reservation for the device.

You might need to hit "Refresh Store" at the top of the page. It only updates the list automatically on a schedule within PG3. Updating plugins is only performed through the Polyglot web access. It does not update them when running "Upgrade Packages" in the IoX admin console.

First you should troubleshoot the ISY994 to determine if it's salvageable because there's no real "plug-n-play replacement". Review this from the wiki as first step of troubleshooting: https://wiki.universal-devices.com/index.php?title=Main_Page#Front_Panel_LEDs/Lights Depending on what the lights do (or don't do) on boot determines next step. More than likely it's simply the power supply failed. Replacement power supply information in the wiki link above. Questions for us to help further: Is anything working (programs, scenes, Google commands)? Have you changed any home networking equipment lately? What computer OS are you using to try to connect to admin console? Do you have a "recent" backup? (i.e. from the last time you made adjustments to the ISY994) It's unlikely an ISY994 just fails. Let's try to get it running/working again before you go looking for a replacement. However, to give you an idea of a replacement - if you're going to stay in the Universal Devices system they have the eisy. You can read more about it on UDI's site and the wiki. That would be the closest you could get to a "plug-n-play replacement", but that needs a recent firmware backup from the ISY994 (4.9 or 5.x). Or you could look for a used ISY994 (see the coffee shop forum area or maybe ebay) and if you had a backup could try restoring that.

MacOS doesn't play well with *.jnlp files like the IoX Launcher. You need to allow non-app store developers to approved list. I think it's easier than that these days, but not a mac user so can't give specific directions. If working on another mac and a PC is it possible to use those regularly or is this on a primary machine you use that you want the admin console ability? What macOS are you running? As @apostolakisl I would remove Java and download again. Just get the generic Java available from java.com (currently Version 8 Update 391 - https://www.java.com/en/download/manual.jsp). Then try. It might give you a warning that it's not able to run a file from a source other than the app store. I think you can click more info and still run it. I had limited access to a very old install of macOS that took a few extra clicks (and reading the alerts) to get things to run, but it ran without much trouble. And then ran without effort each time I attempted to launch admin console while I had access to that computer. You can search the forums for other posts about this for tips/tricks to try. I know @Bumbershoot had several help posts related to this issue that helped me when I tried the process.

@JRobbins probably not because that's not a "normal" issue to experience and need to overcome. If a PLM is working correctly then there's no need/reason to randomly reboot it. I've read tons of posts about unplugging the PLM and making sure you unplug/reboot the ISY (old models 99 and 994) and power them back up after the PLM has stabilized. If you're forcing the PLM to reboot it's possible it could put the IoX system into safe mode and it wouldn't know to recover once the PLM was stable again. Your issue is probably something better suited to ask UDI directly. You can refer to their website for "contact us" and send an email to ask them directly.

@Techman since it's an unannounced update you should probably open a ticket and see if @Michel Kohanim or @Chris Jahn can troubleshoot. Have you performed a full power cycle? https://www.universal-devices.com/my-tickets

Do you make a habit of leaving admin console open? That's not what it's designed to do. I would suggest always exiting admin console after you make adjustments. What firmware are you on if you were planning to upgrade to 5.7.1? It's possible something in the x.1 update fixed an unknown issue that you might have. Otherwise, save the error log for IoX and maybe PG3 log package and open a support ticket for them to review what might have happened. More than likely it was an overnight internet outage and because the admin console was open something got hung updating and a full system power cycle might fix it. https://www.universal-devices.com/my-tickets Out of curiosity: Why do you have to open every door and window after restarting the IoX system?

Shouldn't impact it, but I've never tried a filter plugged into the same outlet as a PLM. I would unplug everything from the other part of the outlet the PLM is connected to and see if you still have issues. If still having issues it could be a failing PLM. How old is the PLM?

This is a known issue with the start.jnlp file that had some issues released a few months ago. Resolution: Clear Java Cache (checking all three boxes) Delete any start.jnlp or admin.jnlp files on your computer Download fresh copy of start.jnlp from UDI website (or wiki or forum announcement post) Run start.jnlp Should be fixed for that "Not Found" issue. As for not being able to control devices it shouldn't matter if a computer is "closer" to the ISY. What do you mean "it's behind a filter"? Erratic control of devices seems that noise has been introduced to the system. Doesn't always mean a "new" device was added as many have found that even a failing power supply or wall-wart of another device has added noise. For one that is giving you issues open admin console and start the event viewer. Set it to "Level 3". Try controlling the device through admin console and see what events happen. Then physically control the device and review the event viewer. It's probably easier to save to a text file or copy to clipboard and paste to a text file so you don't have to keep having it scroll on other activity. Review the wiki troubleshooting steps for noise: https://wiki.universal-devices.com/index.php?title=INSTEON_Signal_/_Noise_Troubleshooting Fix issue 1 ("not found") first. If still having 2nd issue look for noise issues. Report back if you can give better description of the issues or the other error messages you get popping up.

If this is for a lot of programs make sure you've updated your UI. If you went through the migration and didn't clear the Java Cache (temp files) you need to run that process (make sure you check all 3 boxes!). Download a new start.jnlp from the UDI site, UDI Wiki, or the forum post for IoX Launcher. Tip to what @Techman says above about the "Query" program, if you've renamed the Polisy (look at the folder under "Polisy" in the main device tree) to a different name look for THAT name. It's probably at the end of your device list. It might also have a different icon that looks like a monitor.