Geddy

@webminster since your other post "sent" you here and this thread is inactive for over a month, I would suggest you open a support ticket to get specific help. As @Michel Kohanim posted above there was some sort of bug, but the forums aren't a place to track bug progression. I would suggest opening a ticket and describe what your issue is and submit your log there (I think it needs to be in .zip form though and not .txt). If it is "still" a bug then having a ticket in the system may allow UD to track the resolution better. Submit a Ticket: https://www.universal-devices.com/my-tickets Email: support@universal-devices.com Good luck! Please post back to your original thread when you get this resolved (what helped resolve the issue). Since it would be specific to your issue.

@MJsan excellent! Indeed lots of great help around here! That's exactly what I've been doing. Checking out a few little things with PG3 and node servers and small non-Insteon things I have. Good luck when you make the migration. Let us know how it goes or certainly post back with any issues you might have.

@ccclapp I know you said "PC", but are you actually on Windows PC or are you a macOS user? Reason I ask is the biggest issue I've seen are users with macOS...those baffle me as they either work as expect or don't, and take a lot of interaction to make work. Otherwise, it sounds like a system/network issue for you as there aren't tons of others having same issues...or else they too are sitting quiet on the sidelines. Please note that "admin.jnlp" and the ISY Launcher (using start.jnlp) are different methods. The new process only involved "start.jnlp" to put the ISY Launcher on the desktop. The only time I would suggest using the admin.jnlp is when macOS users have issues with ISY Launcher. Using the ISY Launcher always assures the UI and Firmware match. When you download the admin.jnlp directly from the ISY you must do that every time you update the ISY and is also known to have more issues when Java updates to that removes the links to access admin console (I feel that's what happens to you if you don't use it very often). Two important questions: 1) What is your Router/Network gear that you are running? Are you using ISP provided router/modem combo? Or your own modem with a router handling DHCP? (make sure you have DHCP reservation for the ISY handled by the router rather than setting static IP on the ISY994 itself) 2) On your computer are you running any Anti-Virus (other than Windows Defender) or Firewall (other than Windows Firewall)? If you are...TURN THEM OFF BEFORE PROCEEDING AND KEEP THEM OFF THROUGH SETTING UP THE STEPS BELOW. My suggestion would be to start from scratch with the computer. My directions are from the Windows PC approach: In your "downloads" folder - REMOVE any existing copies of "start.jnlp" or "admin.jnlp" (or any other *.jnlp files). Remove any such files you might have downloaded and stored elsewhere. Don't want to run the risk of using an old file in following steps! Clear Java Cache https://www.java.com/en/download/help/plugin_cache.html BE SURE YOU SELECT ALL THREE BOXES!!! Remove all Java installs - either through control panel (Programs and Features) or using the Java Uninstall tool found here - https://www.java.com/en/download/uninstalltool.jsp REBOOT computer Install Java - https://www.java.com/en/ ONLY use the current Java for Windows (currently showing: Version 8 Update 333) Don't use any "fancy" version or any versions downloaded from "strange" places. Download ISY Launcher from UD Site - https://isy.universal-devices.com/start.jnlp Find the file you just downloaded and run it (usually double clicking, but don't want to assume in case you have single click enabled) This step should put the ISY Launcher icon on your desktop that should look like this: BEFORE YOU RUN ISY LAUNCHER --- log into your router CONFIRM your ISY is connected to your network (find the IP # for the ISY - Look for the mac address that should match the UUID if you don't see something that specifically says ISY994). Once you confirm that the ISY is connected to your network then proceed... RUN ISY Launcher You should get a window that looks somewhat like this: Note: this window has Polisy lines showing, but if you just have an ISY994 it should populate If the window does auto populate the ISY (as you indicate) then you need to add it manually. Click "ADD" You should get this window Type: http://<ip of ISY>/desc the "ip of ISY" is what you wrote down a few steps ago This should add it to your ISY Finder window. Click anywhere in the row of the added ISY and it should pop up the "admin console (lan)", "admin console (cloud)", and "dashboard" options. Click on "Admin Console (Cloud)" option should load into Admin console FIRST STEP - make sure you go to Help -> About and make note of the user interface and firmware you're using. They should match identically (down to the date code and time stamp). Latest firmware for the ISY994 is: 5.3.4 (from July 2021) If you're using a PLM it should have about as seen below If, you go through these steps and still have issues please consider opening a ticket with UD support to try to get further guidance for why you cannot get this to work as expected. Again, since it works flawlessly for so many it's some system issue you're facing. Good luck! Submit a Ticket: https://www.universal-devices.com/my-tickets Email: support@universal-devices.com PS: Thanks @Techman...posted while I was typing to steal my thunder of clearing java cache, but you said you did that. I think starting by completely removing Java gets you to the spot of really a "fresh start".

Yeah, I think it's just used this this case to indicate that it won't get further update/development. However, as @larryllix points out there are some database dependencies in play that will eventually be removed.

Yes, you would be nuts! This should not be something you attempt. As @stillwater points out you cannot run 2 PLM for only Insteon devices. Now, if you wanted to run two different systems you could, but Insteon can only be controlled by one (1) PLM at a time. Others here have had Insteon on the existing ISY+PLM and run different systems on Polisy and IoP. I don't entirely know the setup for if you get into node servers of how to point some at the ISY and some at IoP. So, really, you'll end up making it harder on yourself. If you attempt to have some items moved over to IoP you run a big risk of having 2 PLM sending powerline signals and creating noise and disrupting the path from one controller to device. So I wouldn't even suggest having a sub-set for testing. Make sure you follow the steps in the Polisy User Guide in the wiki for migrating from ISY994 to IoP (ISY on Polisy). Many have completed the migration over the last several months. While some processes might have altered slightly you should read through this thread to know about any "gotcha" moments that might get you. Remember...lots of user-to-user help here if you run into issues. Good luck!

@mmb Is this the post you're talking about? You got lots of responses there, and as you say you went the Gmail route. I think the biggest issue is that nobody has had/posted successful use of outlook.com settings so since Gmail is shown in the Wiki and it's known to work it's often the path of least resistance. You said outlook.com settings worked fine on Polisy. Do you still run those settings on Polisy? I think Outlook might need some of the same setup steps that Gmail needs (or once needed) by allowing pop (even though using SMTP isn't the same), but yes, the Outlook setup for SMTP suggest STARTTLS, but you seemed to indicate that just TLS was working. The other option might be to use IMAP settings: Server name: outlook.office365.com Port: 993 Encryption method: TLS But, I have not tested these settings. I just see them in the Outlook.com setup for synching email. One thing for @LarryCRetired (and others) to remember is that Outlook also now has 2FA settings that might be enabled and an app specific password would need to be added to the account rather than using the standard User/Pass that you have setup. So if you have 2FA (two factor authentication) active on the account you need to find out how to add an app specific password for Outlook.com. Honestly, I wouldn't have any free email accounts without having 2FA setup. But that's just personal security preference. PS: @LarryCRetired just noticed on the Outlook site that the SMTP settings are different than what you're using... Server name: smtp.office365.com Port: 587 Encryption method: STARTTLS

@LarryCRetired I can't help you with outlook.com settings, but if you read through this thread you'll learn how to reset (or setup) your Google account so that it will work. It's quite simple (if you follow the steps that Google outlines). I've always used Gmail for my notifications and haven't had any issues...even with the latest changes to their systems.

@195901, “way back” in 2018 Universal Devices released a new way to launch the Admin Console using what they termed “ISY Launcher”. Mostly this was to abandon the “old” way of accessing the Admin Console because most current day browsers dropped the process you are (were) still using. The old way of having IE start a Java applet and said “keep this window open…blah, blah, blah”. During the process of updating ISY994 firmware into the 5.x levels the ISY Launcher made it easy to assure users were using the proper User Interface to access the version Firmware they had installed on the ISY994. So, if you’ve been using the “old” method then you’ll have a little bit of a learning curve, but it’s super easy and you’ll probably be kicking yourself for not knowing about this method sooner. Take a look at the link above for ISY Launcher. If you need more info look for the UD Wiki for ISY and look at the Launcher information found there. Some steps to do: make sure you have Java installed directly from www.Java.com (current Java is 8.x, ISY Launcher is geared forward standard Java release…not a special/different version) clear Java cache (make sure you select all 3 boxes in this process) download ISY Launcher from Link above run “start.jnlp” once (will add ISY Launcher shortcut to desktop) ISY Finder window will probably load (or may have to double click/activate the shortcut), finder should find local ISY instance. If not hit refresh. If still doesn’t then add manually (see wiki information) click in the line for the ISY994 it found and launch admin console (note, “cloud” option is sometimes quicker so it’s fine to use that option) Clean-up: delete “start.jnlp” from your download files. If you need again in the future always download a fresh version! Once you have that you should be able to open your admin console just by double clicking the ISY Launcher icon on your desktop. No web browser is needed in this process of accessing admin console. Note: sometimes when Java updates it can mess up the ISY Launcher shortcut and you just need to clear Java cache and download new “start.jnlp” and run it to get the ISY launcher shortcut again. You should be up and running again within minutes!

@EJones01 and @Adam Ant I think PG2 is still needing to at least exist on the Polisy for now. It will probably change in the future. If you’re just wanting to remove node servers, they can be deleted and uninstalled through the web access for PG2.

@JAvnaim very interesting to hear that something in Firefox was blocking the process. But good to know it was a "simple" fix. Thanks for letting us know.

@cyberk As @Bumbershoot points out nothing you ran should mess it up. But it could be that if it's in a very early production run there could be a chip issue when attempting the OS update. Also, I don't think any of what you ran would have reset the password to default. But it sounds like your device isn't even on the network. Make sure you have checked out the troubleshooting steps in the WIKI for the Polisy User Guide. During some of the upgrades it can take a while (several minutes) to process. Make sure you are allowing a lot of time before removing power to the device (even then power cycle isn't usually necessary). It's possible it you ran the "shutdown -r now" command and pulled the power too soon interrupting the process it was in. If you're not getting web pages and cannot get to the device via SSH then it's not booted properly. Can you tell if the device has reconnected to the network? It could be at a different IP address if you didn't have IP Reservation at the router level. It's preferred to assign the IP at the router DHCP level rather than the device setting in case you change routers in the future the device will auto join and pull an IP address from the new router. 1 - Make sure you see the device connected to the network from your router. 2 - if IP changed try new IP to connect 3 - What is the light pattern on the Polisy? If you've opened a ticket with UD they'll get back to you soon. It might take a little longer during the weekend, but you'll get help soon.

@CManson it looks like you have a different version than @tazman. Your screen shot is showing version 0.0.0. To update the node server you need to go to the Node Server Store and hit "Refresh Store". The version showing on the production store currently is 0.1.9 Once you have the new version showing in the store on the right might be an option to "upgrade". Otherwise you can restart the node server and it should pull down and install the new production version automatically. But the first step is to run the "Refresh Store" process. I don't know if that will make much difference as @tazman is having issues that the developer might need to work out.

Not sure if this would be an issue that the node server developer (@Goose66) could help with or if you might need to start a support ticket to have them check the portal setup. I'm not entirely sure you can conclude that if UD Mobile sees it then Portal is aware of it. That might be an answer @Javi could provide. I don't think that UD Mobile is seeing the devices through portal, but just using the portal access to contact the ISY directly so don't think that assumption is a straight correlation for UD Mobile = Portal awareness.

I know you got it updated, but just so you (and others that might read this) know you can find the directions in the release notes in the "Current Release Announcement" threads. Specific the most recent for PG3 is found here: Make sure you follow the main forum area of Current Release Announcements to get notifications for any Universal Device release announcement made so all systems can be kept up to date. Update directions can also be found in the Wiki in the Polisy User Guide section.

@JAvnaim Since you've tried the normal process it might be time to open a support ticket to see if they have any specific steps or methods to attempt to be able to change the pass. It's odd that it would function like I experienced, but not trigger the new pass when you tried logging in again. Submit a Ticket: https://www.universal-devices.com/my-tickets Email: support@universal-devices.com When they get you working please post back the steps taken to get it fixed to possibly help others if this comes up again. No, currently there's no sync between the passwords. You do need to make sure you setup the password in the ISY settings, but that's in a different area. The steps your going through to change PG3 password appear to be correct, and your description of it making you log into the portal again matches what happened when I changed the pass yesterday so I think you're doing the steps right. Something just isn't actually storing it in the device.

Not that I think it would make a difference, but current PG3 version is 3.0.63. If you're familiar with SSH commands (through Putty or even Windows built-in) I might suggest going that route to force the PG3 restart. (Update instructions given in link for 3.0.63 release thread.) When you click on Profile -> Settings does it give you this window: When I type a new password in there it logs me out and asks for my Portal login then allows me to log into PG3 again. Even though you said above you are going through Profile -> Settings something doesn't appear to be going to the correct place.

The Node Server is licensed per Polisy. It can support both ISY994 and IoP options. So no, you would not need to buy the node server again just to convert from ISY994 to IoP. It's just simply changing the setup in the PG3 to point to the IoP. Above @bpwwer mentioned the license being tide to the hardware. His warning is to your initial comment of having 2 Polisy. You wouldn't be able to sub in the backup/spare device and restore backup of purchased node servers. That's when you would need to buy them again.

@dpierre Are you sure you changed the port numbers? Did you change in PG3 or PG2? Are you running a ISY994 or are you running ISY on Polisy? Or do you have other devices on your network that might be listening to port 80 and blocking the Polisy? It's strange because it shouldn't really matter, but some routers might only allow 80 to be used by one device. So might need to unplug any other devices. I think somewhere I read people having issues with Hue listening on the same port that something else was using and it would conflict. Either way, if you can't figure out how to get back into it and don't want to perform a factory reset (instructions in the Wiki and linked in @MrBill's reply above). I would suggest opening a support ticket request and seeing if there is some magic process they can help identify. Either way...please post back how you get this resolved in case somebody else needs help down the road! Good luck! Submit a Ticket: https://www.universal-devices.com/my-tickets Email: support@universal-devices.com

Not completely, you should remove the device from the scene first then delete the scene. I don't think ISY can delete the scene if devices are in it. Haven't tried that recently. Somebody else can confirm. If you've always been ISY for the controller and you reset links when first connecting the device to the ISY then you should be decently okay. However, if you've come to ISY from Insteon Hub (or even some other hub/controller for Insteon) then it's possible devices had links from the prior setup if they were not factory reset and then linked to the ISY. That's strange. Shouldn't usually need to reset them more than once. You probably had line noise causing issues with connectivity to the ISY. Glad it went away though. If this happens again (for these or others) you should check for line noise in the system. Reviewing the Event Viewer (level 3) can help you troubleshoot commands from the ISY to the device and vice versa. I think the main answer to your question is that factory reset is a manual process. It is NOT something that can be triggered from the ISY. You should be able to Google Search by item number to find the user manual if you don't have any. Last checked the links to Smarthome were not working, but some cache sites will have links to the old manuals. Once reset then perform a "restore device" in the ISY and it should find the device in the system and apply what the ISY knows for links and settings. You can read more about this in the ISY Cookbook (found in the Wiki)

@CPrince why not include a link to the topic you reference in the title for a little background? What is it you're asking and trying to achieve? Factory reset for any Insteon device can be found in the user manual. If it's not on the Smarthome site it's still usually able to be found in Google search for item number. I think @larryllix and many others, myself included, will typically suggest a factory reset for any device that might have been included in a previous system to clear out any prior programming. Some also think it is necessary for any "new" device as there is a chance some factory testing links could still remain in device memory. That's hit an miss, but always a good suggestion to follow...especially for many that might just be starting out. Linking from Admin Console has always been an option. It should still exist. I think with more background about what you're really asking and what context you expect a result will determine what kind of replies you get to your post.

@srm just wondering if you got this resolved. If so, what did support do to get this corrected? Just would be nice to get the resolution to this situation to possibly help others in the future.

Yes, you should open a support ticket. If Portal isn't showing a request on ISY on Polisy then support might need to reset the request. I also didn't think that the IoP was able to change the DHCP setting. It shoudln't be set to static on the device (as you're showing) because that needed to be managed by the Polisy. You will need to have Support review that as well. Is there a reason you're trying to setup PG2? Since you are starting fresh with the Polisy I would suggest not setting anything up in PG2 and only use PG3 and IoP settings. To setup the IoP in PG3 follow the steps in the Wiki portion found here - https://wiki.universal-devices.com/index.php?title=Polisy:User_Guide#Polisy_.28PG3.29_Dashboard But, wait until you have a support ticket to confirm the steps based on what you're showing above.

The app specific password is not like the standard 2FA as you say needing to refresh if IP changes (or other factors change). I've had a spare Gmail account setup with the security settings since they were available (probably before 2016) so I've always used the more secure method. I've never had to change/update my Gmail settings. However, I do just because I think it's smart to change/update passwords (even system generated long (16 digit) passwords). But, if you didn't change it yourself then there's no need to change it. It just works. That is until Google changes their methods again. It's possible that you have advanced security on already, but the old way still worked until the end of May. I simply picked the Elk post because I remember it recently. There's also an area in the Wiki that has always described the "optional" method for setting up Gmail. That's just the required method at this point. This can be found in the wiki- https://wiki.universal-devices.com/index.php?title=ISY994:Configure_Mail_Server_Settings#Configuring_gmail_Account Yeah, I know Yahoo! changed their process a while back as well so I guess it would be only a matter of time before Outlook does the same thing.

No. No issues using Gmail here. But I planned ahead and heeded the warnings that have been posted here a half dozen times. The most recent was in this thread: You can STILL use Gmail. Just have to use the more secure access to the account and thus an app specific password for sending email via the ISY. I've always had more secure on the account I use for the ISY so didn't have to edit anything when this started becoming an issue. Surprised more people didn't take the 5 minutes to do this when Google started warning everybody of this many moons ago. Gmail works just fine...like it always has...for me. Oh, and just so you won't be surprised...if you try to text yourself through the email server most phone systems will often delay the relay of email to text speed so if you're doing mission critical notifications of any type I would suggest using one of the node servers that can push notifications to your phone rather than relying on email and/or email to text options for notifications.

@TriLife z-wave 700 has much better range. I don’t know about getting through such construction, but from the board it should be better.