Geddy

There was an email blast from UD a few weeks ago and the announcement posted on their website. You might need to sign up for email alerts from UD. I believe the host (OpenADR) is posting the recording. You might want to check their site for this and past events. Indeed they have released the recording and slides - https://www.openadr.org/webinar-series - "OpenADR 3 Price Signals and Local AI to Automate any Building or Device" Happy watching! I signed up for it and signed in at the start, but had work happen so couldn't listen to the whole thing. Glad the recording is up so quick so can watch it this weekend while snowed in. ❄️

@aguden take a look here - https://wiki.universal-devices.com/ISY-99i/ISY-26_INSTEON:Linking_a_KeypadLinc However, if some of the buttons are there you might be able to right click the main node for the keypad and select "restore device". When you say you lost connection with all the switches what happened? Did you remove the PLM or replace the PLM? There's a process to restore the PLM that might have brought things back, but if you have everything working except for this one device not sure what you had happen.

@Ray95xxx review this post: https://forum.universal-devices.com/topic/44943-admin-console-not-working-on-mac/ Does this resolve the issue? I'm not sure about Java on macOS, but if you can clear the cache on it like on Windows machines I would clear the cache first then run start.jnlp again after changing the security settings mentioned in post linked above.

Trying to avoid making a snide comment is difficult. I really dislike the Alexa+ and turned it off as soon as it was forced update on my devices. Aside from the voice being unpleasing the constant follow up being enabled was not appreciated. The fact that I still had to go into the app and find where to turn off follow up made the entire forced "upgrade" even less likable.

@m6bigdog this sounds like could be a browser issue. If you're able to log into the eisy just using "eisy.local", but you're unable to browse to the settings/portal page or it's blank I would think it is browser related. Have you tried a different browser? Or depending on what you're using try a private or incognito browser session to see if plugins or cache might be blocking/hiding the information. Since this is a new setup and you've not been able to get it registered with the portal I would suggest opening a support ticket with UD so they can explore the issue and make sure this isn't a system issue with eisy-ui and hopefully get you up and running quickly if they find the problem. Support tickets can be opened here: https://www.universal-devices.com/my-tickets Either way, please post back what steps they go through to get this resolved so it might be able to help others should they face a similar issue.

Best way to ask UD directly would be through a support ticket - https://www.universal-devices.com/my-tickets While they somewhat monitor the forums they aren't as active as they once were (a lot of development going on). For reference I just changed mine to use the default server and sent to a comcast address and the test and a standard notification (by running the "then" line of a program that generates a notification) were received. So, no, does not appear to be Comcast blocking the messages, but this doesn't mean it isn't blocked on your side if you have a lot of alerts going to that address it could be considered inbound spam and it could be filtered at your user level. I changed the SMTP back to gmail and it still worked for me. I might suggest you setup a different SMTP if you are relying on emails for notifications. Otherwise, if you're using Polisy or eisy you should look at getting and using the notifications plugin for notifications.

In the link I provided above looks like ISY994 could use either FAT 16 or 32. Also there is this comment: Later on it seems there is the ability to go up to 32GB card. I think can use a larger, but ISY994 would only recognize/use 32GB. I’m not sure as I never tried bigger cards. Only replaced my card once (I think for testing purposes) ages ago.

It could be that Comcast/xfinity is blocking the messages. If going through to another server then it’s a receiving server issue. Either blocking UDI server or a relay between the two is broken/blocking. I would suggest setting up to send using a 3rd party SMTP (perhaps Gmail) and testing send to Comcast.

Unsure. And since nobody answered the first time you asked either they didn't see the question or don't know either. Try it and let us know. Strange that formatting in the ISY is causing the telnet to hang. Do you happen to have a different computer to test with? Wondering if a Windows connection would be different. Doubtful, but could be a bad SD card. Do you have a "spare" that can be wiped and tested to see if the PNY card is bad? Probably not likely to have many 32GB micro SD cards laying around. Since this is a "spare"/backup ISY994 do you know if this ever worked? Did you recently buy this device or is it one you've had and just haven't been using?

Just tested a program and a "test" email. No issues for me. I'm using gmail as my SMTP server and going to outlook.com domain. I also setup to send to gmail and yahoo and the "test" email all went to those domains. What SMTP are you using? If "Use Default" is checked try using a gmail account. The directions in the wiki seem to still be accurate since those are the settings I currently use. If you're already using Gmail to send the message make sure you've logged into that account within the last 6-12 months (Google will make an account inactive or not allow sending email if not logged into over a period of time). What domain are you sending TO? You might want to change the TO address and run a test message (be sure to select where to send the test message by selecting it in the "Groups" area (if none are selected it will not send the "test" message).

UD has been updating the wiki here and there with eisy ui information: https://wiki.universal-devices.com/Eisy:User_Guide#eisy-ui It's very much a work in progress. I have a few folders and find the main list very lack luster and difficult to migrate. It had a period of time that folders would automatically expand and they don't seem to keep their memory from one use to another. Because it's not very useful (to me) I haven't used it very much up to this point.

@j.rieff glad you found it. For future reference: Go to Universal Devices site (https://www.universal-devices.com/) and it's available via the "My ISY" near the top right of the site. Or you can direct link to it here: https://isy.universal-devices.com/start.jnlp

@matapan I'm assuming by "per documentation available" you were following the instructions found in the wiki: https://wiki.universal-devices.com/ISY-99i/ISY-26_INSTEON:Replacing/Formatting_an_SD_Card It says if it was a new SD card you wouldn't need to format it. I'm not sure if formatting it has any impact on the NEW card or not, but perhaps some artifacts from macOS formatting it might happen (not familiar with macOS to know if even doing FAT32 doesn't add some "mac cooties" to the sd card. According to these directions there should be a "Goodbye" message after the formatting in the telnet session and then the ISY should reboot. I think at that point you have a very basic way to access the ISY994 via the admin console and that's why/where you would then need to update firmware to the latest for that specific device. NOTE: do you have a PLM connected to this "backup" ISY994? If not, you should only download/install the non-Insteon firmware. Otherwise, without a PLM connected you will always launch into admin console in "safe mode". I wonder if you could disk copy the working SD card to the new SD card and try that to see if it would boot up. I've never attempted it, so just a swag suggestion. Otherwise, try the telnet formatting again. Is there a way you can wipe the new card of any information and put it in an unformatted state?

Try these directions: https://wiki.universal-devices.com/ISY_Portal_MobiLinc_Configuration Remember, I don't think you can add the ISY Portal to ISY994 any more, but certainly works if/when you get the eisy on the portal. I just checked it out and my setup is exactly as described in the wiki. Online line I think it left out was "Connect Method" and I have it to Auto Detect and it shows as "Auto (HTTPS)". I also have it set to auto sync over wifi and cellular. Oddly enough it does show my plugin folder and the YoLink plugin does show temps of all my temperature devices (that's nice). Other plugins are there and report some info, but I don't typically refer to them in the app and don't use many plugins in automation settings. A couple of my Zigbee smart plugs/outlets do work. I don't have any z-wave currently connected so not sure if they respond or not. They do show up in the list of items, but they are not currently in use (come to think of it I don't even know where they're being "stored").

Did Michel get things cleared up for you through the support ticket?

Mobilinc HD still works just fine with Insteon devices and the eisy. I use it (rarely). I have it on the iphone and know exactly what you mean by being able to sort by name or on/off status. I've set mine up to use through the portal access just as I always had it with the ISY994. The only things I miss by using Moblinc are devices added by plugins. To me Moblinc HD/Pro has/had much better UI for layout. However, UD Mobile has been good the newer things being added with z-wave, zigbee, and plugins. I just don't have much use for those so haven't spend the time learning/transfreing to UD Mobile like others have. I'm using Mobilinc v4.17 on iphone iOS26.2 without issue. The "old" Moblinc Connect option is what broke when UD came out with the Polisy/eisy lines.

If you clear your java cache or look in the windows (I assume you're on Windows) temp folder for UD*.state files and clear one that might say finder or list or something (I forget the actual name and not local to my device currently) it might change the name the next time IoX Launcher is run. I think the name of the device is a cached value. If it didn't change on the following launch. Best to use the ticket option. My guess is something didn't update correctly and UD will look through the logs and probably give you a few commands to run. Since you ran the update packages again in admin console that would be the first suggestion to try an update process again. Odd that the web didn't give you anything on the sysconfig page. That could be a web issue. I would suggest trying a different browser. Also, you mentioned you use the Unifi edgerouterX. Do you run vlans? Are you running any antivirus, firewall clients, or VPNs on your computer? If so make sure you are on the SAME vlan as the eisy. Turn off antivirus, firewalls, and VPN clients.

This would be simple if you had an on/off outlet for the modem. I might wait a little longer than 60 seconds for the modem to be fully offline and the cable provider to "know" the device was offline. Make sure the program isn't set to run at startup in case you have a power outage and it shuts things down just as things are trying to boot up. I would probably go the route that @Ross did and get an inexpensive "smart plug" and just have an automation within that app to turn the plug off for 3-5 minutes (maybe middle of the night). It's tricky though do those power back on if the network is down when the scheduled time to turn back on happens? I don't use them so can't test (haven't tested). But ultimately, it comes down to what are you really fixing? You might still have underlying internet issues somewhere that would be better fixed with the provider. You're just making a work around situation rather than getting them to fix their problems (or finding out that it's something on your side that needs fixing). It's kind of like when router manufacturers added the ability to self reboot on a schedule. Why did they do this? Because they wrote bad code that would cause the router to lock up over time and people felt it was easier to make a reboot schedule than to buy a better quality router. You're just rebooting a problem rather than having the cable provider "fix" or at the very least troubleshoot if they have potential issues.

@stillwater Since the IoX finder window seems to indicate the device is updated to 6.0.4 it's possible you need to perform another reboot/power cycle to the device to bring things up again. Are you able to get information if you browse to this page: https://eisy.local:8443/WEB/sysconfig.txt (If you get a security message click advanced and click continue to site - it's local so it's fine to access) If after a power cycle you're still unable to get eisy UI to come up at https://eisy.local/ then I would suggest opening a support ticket before you go any further. Certainly don't get into SSH and run any random commands. During this time of development it helps UD more if users file support tickets before random attempts of repair that might make things worse. It helps them learn what happened to a system, but is also easier for them to correct what has happened to this point. Open a support ticket here: https://www.universal-devices.com/my-tickets Where will it show as "ISY"? On mine the "Name" is my personalized name given to the top item in the node tree and "Type" shows as "eisy". What's the result when you got to https://eisy.local/?

@matapan the underlying question is simply, why? Why do you need to try to capture an extended event log? Perhaps you could explain any issues you are having or are trying to find and get help with those rather than just a random time of event viewer? Also, as @IndyMike points out I don't recall there being any timeouts on the admin console. Certainly not on the ISY994 (that's where you posted this question so I assume you're using the ISY994). What firmware are you currently running? I know it's not advised to leave admin console open, but it's been known that many do. It's more likely a computer issue is killing the Java connection after a period of time. If you're going to leave it open for an extended period of time I might suggest you do so on a computer that can be hard wired to the network rather than a laptop or other device that is relying on wifi network access. Even with sleep and hibernate turned off sometimes a small blip of the wireless network signal can cause issues (perhaps causing the admin console to disconnect/reset).

@bwbeisne not that it would be the entire answer to your issue since it's "worked" this long, but you're on an outdated firmware. It's a small update from 5.3.3 to 5.3.4. I would suggest you make a backup of your system and update to 5.3.4 to see if there are any fixes in that update that might resovle other underlying issues. The release information for 5.3.4 and the download links can be found here: https://forum.universal-devices.com/topic/33287-534-isy994-last-release-for-isy994/ The errors of "System -170001 [UDSockets] PSub:41 error:6" are infomrational in sorts for the ISY. According to Michel in another post (from 2019) this indicates that a socket isn't closing properly. Do you leave admin console open for long periods of time? And you also mentioned something about the web ui (is this through the portal?). Neither options are designed to be left open/connected for long periods of time. I woudl suggest you log out of everything if changes are not actively being made. See here: https://forum.universal-devices.com/topic/28034-help-with-repetitive-errors/ Other items that would tend to slowdown admin console: Memory usage of Java on your system. Look up how to set min/max memory settings in the Java console (configure java). Looping programs - make sure in the program / summary tab that no programs are looping. Usually this would make admin console unusable, but just watch for any out of control programs. Look in the summary tab for any programs that are set to run at boot. Turn those off or disable the programs for now and reboot the system again. Lastly, are you using any 3rd party apps to access the ISY994? I would make sure those are closed and/or disconnected from the ISY994 then power cycle the ISY994. This could be a drastic last step that I would suggest. If you do this make sure you have a current backup and perhaps even a backup from before these issues began. If the PLM is failing (again) making a backup now could include issues from the failing PLM. This is why you would want to be sure you have a (recent) backup from before the issue was noticed. According to the PLM quick start guide - to factory reset the PLM - What's strange is after the reboot you're having something logging into the device that's failing (-10104). Then you have some files that are failing to open (-110022) (you can see more about the error codes in the wiki). It might be a problem with the SD card and that gets a lot more involved with fixing. Look in the wiki for replacing the SD card. Again, try running a backup now and see if you have any recent backups that you could try to restore depending on your next steps.

@theitprofessor I learned recently that there's been a few "bugs" under the surface that UD is suggesting you only access PG3 through the eisy_ui connection rather than the "old" port 3000 method. Now that you're on 6.0.4 make sure you get in the habit of connecting to PG3 through eisy.local (web ui) moving forward and not through the "old" method of directly accessing PG3. The bugs seem to cause some connection issues with plugins when using local or eisy.local credentials. I'm not sure what plugins were/are impacted, but just out of precaution use the eisy_ui method moving forward. (Thanks @DennisC for pointing this out to me!)

Maybe describe some of your issues you're having and people here can help identify if this is an Insteon issue or an ISY994 issue. As @apostolakisl mentioned above there's a new "eisy_ui" in the works that is browser based. So far it's still being worked on and developed. For the time being the tried and true java admin console access remains available and works just like it has for the ISY994. However, I might expect that "replace device" might be a late addition to the web interface. There's no ability there currently, but I too hope that it would become available before completely shelving the Java access. This one ability alone has helped so many through the years as old Insteon devices fail and are replaced. Sadly, if you are replacing old devices with "new" i3 devices from Insteon the only way to fully support those would be with the current eisy r2 (and eisy or Polisy, but these devices are not currently being offered and Polisy has changed to end of life - basically - with no further os updates). This is in the eyes of the beholder. Many others have relied on the Java interface for ages (many more that don't post here because they don't have issues and thus don't need to post here). My only hope is the new web ui has the same abilities as the tried and true java admin console. It's certainly been growing pains while it's being developed.

@HTTRC I never recall trying to add/change user names. As far as I recall from comments on the forums I don't think the ISY994 ever implemented the multi-user ability. I think it was limited to one account that acted as admin. It's been so long since I used the ISY994 and not a feature I needed so just going off long time ago memory of random comments on the forums.

If the password didn't reset then it's possible you didn't hold the button long enough. Sadly, on the ISY994 if you hold the button too long you can end up factory resetting the device. The instructions you linked to indicate that it will be about 4 seconds for the lights to blink in unison then hold an additional 7 seconds. It's an awkward process and timing is everything, but if you went an additional 10 seconds after the lights started blinking it might be enough to trigger the password reset. If you're able to log in why not just change the admin password back to the default? What are you attempting? Typically the password reset function is to use when you cannot get logged in and need to reset the user/pass to default rather than fully resetting the device. Since you are able to log in then I would just reset the admin user account and possibly the User 1 account (if that's what you're saying you're using to log in). https://wiki.universal-devices.com/ISY-99i/ISY-26_INSTEON:File_Menu#Set_Userid.2FPassword It's been quite a while since I used the ISY994 and remember having to reset the password once or twice and didn't have issue with the button process. I'm not sure what firmware you're using, but don't think that process ever changed since the wiki is written for the older ISY26/99 devices, but continued to work for the ISY994 (and even Polisy and eisy) device(s) using the Java Admin Console access method. PS: @DennisC this is in the ISY994 area so I assumed they're using ISY994 device.