Geddy

@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.

@TriLife first on the ISY994 upgrade to 5.3.4…there were minor updates through the steps, but probably nothing major and since you seem to be running fine it might be okay to stay where you are. Read the release post for 5.3.4 and maybe prior releases to see if any issues you might have might be fixed. While I would typically say yes, it’s more difficult given your location as to if you would notice any difference. I assume you have the 500 series controller since you’re up to 5.3.0. Read the release posts and see what you think might help your setup. There is a recent post from @Michel Kohanim that UD is developing hardware for the Polisy for Z-wave and Matter. It will be released later this year. If might be worth waiting for that board to be relegated for your use (as you say given location and difficulty to get z-wave 700 dongle.

@TriLife - I split your post out of where you had it for hopes of getting some individual attention. You bring up a lot of questions and ideas that are more specific to your system rather then general migration path topics. My only suggestion is don't try to migrate to Polisy or IoP with a deadline in mind. It will never fail that something will cause you strife and perhaps delay your enjoyment. As for the z-wave specific question I think others with more experience of the process will be better able to answer your question. Perhaps others have their own take on #2 and 3 questions as well, but my thoughts... I don't know "the point of no return", but YES, IoP and current 994 can operate at the same time. HOWEVER, controlling the same devices from two devices will be an issue (i.e. don't do it). I have 100% Insteon and still have it on ISY994i, but have IoP running just for testing and review of PG3 node servers. I'm waiting for family to take a vacation for me to make the switch to IoP where I have several days to make sure any kinks are worked out. (that and my system works as is...I'm a little worried about breaking it, but it might finally be time soon) The only "what if" on this...if you're currently using the Polisy with PG2 (polyglot v2) node servers and you try to update the Polisy to get PG3 and IoP running. You could run into issues...see below... There were reports of a chip issue in some very early versions of the Polisy. I don't specifically know if there's a batch that @Michel Kohanim could identify as having a problem for sure or not, but it might be worth either opening a support ticket with UDI just to check if your unit has the chip in question. Otherwise, keeping everything off the Polisy and just setting it up and getting it updated and current you'll know if/when it has issues. Make sure you're checking the ISY Wiki for the Polisy User Guide and watch for the 3rd light problem. Hope that helps. Perhaps others can now see this better and chime in with additional assistance.

@Panda88 Thanks. Just changed.

@jkraus Unsure how to help, but tagging @Panda88 as the Node Server author to see if they might be able to assist.

The issue is marked solved because it solved the issue OP had. Op had multiple issues that were resolved by simply rebooting the ISY. While rare, it does happen that, communication can become flummoxed and a simple reboot will sort things out. This is indeed what "SOLVED" the issue for @paulw (topic OP). The others that have posted that they are having issues are, in fact having DIFFERENT issues than the OP. For those issues to be handled with different resolution there needs to be more to consider. If you have a Mobilinc Connect issue then I would suggest you post in the Mobilinc forum and tag @InsteonNut to hopefully get their attention and support. Meanwhile, other users will attempt to help the best we can. If the typical troubleshooting steps have been performed, there might be bigger issues that the developer (and owner) of the servers will be the only one that can help resolve the matter. It appears that there might be issues with Mobilinc Connect. If multiple users have sent a message to @InsteonNut and Mobilinc Support then hopefully a resolution for those issues can be handled soon. And it's all possible that Wes is on vacation and therefore unable to respond immediately. Just an assumption given that it's that time of year that most people do try to take a vacation break. Finally, as @MrBill stated (as a Mobilinc Pro user - through ISY Portal) the app worked fine for him. I too can confirm that Mobilinc Pro/HD works just fine through UD ISY Portal.

So you changed the actual content in the custom notification? If you go to the Configuration -> Emails/Notifications -> Customizations tab then click on the area for "Customized Content" it should open up the actual message that it is sending. Make sure you fixed the typo in there. Either the notification didn't change if you had it specific to a device rather than a node variable. It appears that your typo is in the email account setup itself. It's showing a from "Spriniler System". That is more than likely an email system issue. What is shown in your "SMTP Settings" area?

It's there now! https://forum.universal-devices.com/forum/377-wake-on-lan/

In putty you just need the Polisy IP address. Port is 22, type is SSH. This is my putty session info: Read the Polisy User Guide from the wiki for further assistance with migration steps and making sure the OS version is up to date so PG will install.

Make sure you've manually refreshed the webpage. Sometimes it also takes logging out of the dashboard, closing the browser, and coming back and still refreshing. More than likely it's just a web cache glitch. If not, restart the ISY service again. What process did you use to update the system? In the PG3 dashboard look under System and "Reboot ISY". You might hear a beep if you're close to the Polisy. If this method doesn't happen to work then try to reboot the IoP from the admin console configuration tab. Post back either way to let us know if it worked (or not).