Geddy

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

Based on @CactusJ post and picture (in another thread) and a couple of tweets and maybe a couple of posts on reddit it does appear the hub is connecting and back to life.

Glad you've got the experience to work on the devices yourself. Having a working PLM and a spare is helpful. I think you'll be able to use your system for a long time to come. Sadly, I don't think the pandemic directly played into the loss of Insteon, as many have speculated the writing was on the wall a while before Covid happened. It's just the nature of some businesses that fail for various reasons. But, that's been a topic beaten far too long in other places to be brought back up here. Currently, my system is working. Like you, I have a few spare devices and a spare PLM. I'm not looking for anything to change to at the moment, but have certainly started that extra "rainy day fund" for if/when an automation change is needed. I'd rather save up the funds now and then explore the options available at the time something is required to change. Ultimately, going back to the "dark ages" of manually turning lights on and off is a simple stop-gap measure if it ever comes to that. However, I suspect that I'll be in a different house before my current system fails.

@eduardo_garcia Yeah, it's been hard news to handle with the loss of Insteon devices. But, it's been a topic of discussion for a while. As for replacements there's been a lot of discussions in this area (since the official shutting down of Insteon) as well as in the Coffee Shop area of the forums. Since you're international the best bet would be to find a local automation professional and discuss options. The overall feeling is that nothing has had the success and reliability that Insteon has over the years (for most people). There's no one fix solution for what to attempt next (without going a more professional/high cost route...at least for US/Canada based options). Depending on how old existing devices are their longevity seems to work for most people, but everybody is different.

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

@EVENALAINEN First and foremost make sure that you have a network cable connected from the ISY to your router (or network hub). The device must be able to access the internet for Portal access. Then make sure you've followed the directions on setting up the portal account. Are you on ISY994 or a new Polisy that you're setting up ISY on Polisy (IoP)? If on ISY994 - https://wiki.universal-devices.com/index.php?title=ISY_Portal_Installation_Instructions If on Polisy - https://wiki.universal-devices.com/index.php?title=Polisy:User_Guide#Setup_ISY_Portal_for_Remote_Access.2FAlexa.2FGoogleHome.2FIFTTT Also, please let us know the firmware of the ISY that you are using. From the admin console use the "Help" menu then About and take a screen shot (image) of the Firmware and User Interface (UI) that you are using. These MUST match exactly. If they do not then follow the steps in the wiki for installing and using the ISY Launcher.

Sounds good. Good luck! Perhaps start a new post if you have more issues with those unresponsive devices since this thread has a post marked as the solution any further updates here might not get noticed. Have fun finishing up the desk and hot tub!

@andrew77 It's been several days. Wanted to check in to see if you were able to get everything working again. Hope all is well and you're off and running!

@JTsao google told me about this site - https://ttsmp3.com/ Not sure if it's good or not. I'm sure there are others you can find.

@andrew77 seems like you've got more issues than user to user help on the forums can provide. You should open a new ticket with UD Support for this behavior and describe as best you can. Submit a Ticket: https://www.universal-devices.com/my-tickets Email: support@universal-devices.com The reason I suggest trying to get support help is because your issues seem to be changing often. It's quite possible you have some power supply issues within the house. You say you had a storm come through and knock the power out for 8 hours the other day. Are power outages normal in your region? Do you have any other power supply issues? Nothing with Insteon will just be 1 line in the event viewer. That causes me to consider that you have line noise somewhere in the house. That's a whole different issue and is very difficult to locate. You can't just consider anything "new" you've added to the house as it's been commmented on by others that old wall warts have even triggered line noise that blocks the powerline traffic for Insteon devices. Take a look here: https://wiki.universal-devices.com/index.php?title=INSTEON_Signal_/_Noise_Troubleshooting Also see what @MrBill has commented on in the past for testing for noise: https://forum.universal-devices.com/topic/35216-programs-not-working/#comment-330289

Does this mean you created an account at my.isy.io and setup the portal from there? When you login does the UUID show and is there a red dot next to the UUID? If you haven't gone to the Portal site you need to go there. Sign up for a 30 day trial. Add the UUID and it should send a signal to the ISY on Polisy that will need to be approved. The IoP needs to reboot. In the PG3 interface you should have an option under "System" to "Reboot ISY". This will reboot that system. Give it a few minutes to complete (I believe PG3 gives you alerts to the process). Make sure you are not actively in Admin Console when you reboot the IoP service. Once it reboots you should now have a tab for portal approval. If after reboot you still do not have a portal tab please open a support ticket to get assistance with the proper steps to achieve this. Submit a Ticket: https://www.universal-devices.com/my-tickets Email: support@universal-devices.com You lose me on the discussion you're having about DHCP and Static. Currently ISY on Polisy does not allow to edit the IP for the IoP service. This is because there are some relationships between IoP and PG2/PG3 that require the ISY service to be at a known IP address (basically). Make sure that you have read the Wiki for the Polisy User Guide for more information and setup guidance.

Do you make notes on devices? Right click "Notes"? Seems that I see comments that *.prp files are just notes files. You might have empty notes and thus making zero file sizes that can't be closed or opened properly and topology is having issue with them. I've seen comments to remove them via telnet, but I can't tell you how. I would suggest opening at ticket with support to get assistance with the removal process. They can also help you evaluate if it might be a sd card going bad. (Please note that the ISY994 takes a Micro SD and can accept up to 32GB. Make sure that it is a newer brand name with A1 rating. Only if you end up needing to replace the card, but I don't think that's the case just yet.) Submit a Ticket: https://www.universal-devices.com/my-tickets Email: support@universal-devices.com

@andrew77 I'm glad it's seemingly working! That's great to hear. Are they wired or battery devices? What are you attempting to do with them? Just turn them on/off in admin console? Before you remove/re-link/restore them try this: In admin console: open the event viewer (found under Tools -> Diagnostics -> Event Viewer). Set the level to 3 "Devices communications events". Select any device (that you think it's working correctly) and try to turn on/off and watch the event viewer. In the event viewer you should see something similar to this: (I just chose a random on/off switch I have and turned it on then off from the admin console) [INST-TX-I1 ] 02 62 46 0D F9 0F 11 FF [INST-ACK ] 02 62 46.0D.F9 0F 11 FF 06 LTONRR (FF) [INST-SRX ] 02 50 46.0D.F9 44.D1.80 2F 11 FF LTONRR (FF) [Std-Direct Ack] 46.0D.F9-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 [D2D EVENT ] Event [46 D F9 1] [ST] [255] uom=100 prec=0 [ 46 D F9 1] ST 255 (uom=100 prec=0) [INST-TX-I1 ] 02 62 46 0D F9 0F 13 00 [INST-ACK ] 02 62 46.0D.F9 0F 13 00 06 LTOFFRR(00) [INST-SRX ] 02 50 46.0D.F9 44.D1.80 2F 13 00 LTOFFRR(00) [Std-Direct Ack] 46.0D.F9-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 [D2D EVENT ] Event [46 D F9 1] [ST] [0] uom=100 prec=0 [ 46 D F9 1] ST 0 (uom=100 prec=0) Now, physically go to the device and turn it on then off. Go back to the admin console and see what the event viewer is showing you. I don't have any battery devices so I cannot show you what that might look like. But you shoudl see the TX and the ACK lines for sure. If not then there are communication issues and removing and re-linking then right-click "restore device" might be best attempt. At least the ISY is functioning again.

Why are you trying to telnet? Also, if you're on macOS what version? Apple removed Telnet from recent versions of MacOS so you would need to find way to add telnet in to be able to use it. But, why are you trying to telnet to anything? If you start at step 3 (with a blank/new microSD card) then telnet isn't needed. @Michel Kohanim brings up the network issue. You mentioned your on Orbi (mesh?) system. Do you use any switches/hubs that you can hard wire your computer into the same device that the ISY is connected to? It's quite possible that your network is causing issues talking between wired and wireless devices.

If you know the address of the ISY then just setup a low reservation for it and the device should attach to that as intended. You're just adding an extra step of trying to force the ISY to join at the low IP then reserving that in the router. If it's already connected to the router you know the MAC address and can just setup a lower number in the reservation. Then power cycle the ISY and it should connect at the new IP. But your way should work...especially if just a quick change. It's just an extra step.

@kzboray - the only issue with the button pressing option was that I think it was only implemented in 13+ to work that way. It worked somewhat okay in 12, but when I got my Polisy it was v12 (something) and I remember having to go through the SSH commands to be able to have the button presses register as the way to upgrade the system.

How are you trying to paste in command prompt SSH? Just right click and it should paste what you've copied. Otherwise, I would suggest Putty SSH for a slightly different approach. Sometimes it's a little more user friendly than what's built into Windows. Although, it's all in what you're used to, and right now you're not used to any SSH processes. If you follow @kzboray directions above they are the same commands found in the wiki. This should still work for what you've got. It appears you're logged into SSH okay in the window above. I don't have the old version anymore so I see a slightly different script after logging in via cmd ssh. But you're in there. If you're typing "admin" at that point it does respond "-bash:..." as you have. So you're logged in. Open the wiki link in another window so you can see the commands and copy from the browser then paste in the CMD SSH window just by right clicking. Then hit enter. Once you type the "shutdown" command...seriously wait a long time! Some people have reported it taking as long as 20 minutes, but I seem to remember at least 5-10 minutes. Final thing to ask...do you know when you ordered/received you Polisy? If after you go through this process look at the lights on the front of your Polisy. If the left is steady you should be good. Otherwise, check the wiki for possible issues. But, let's at least get you through running these SSH commands first.

@andrew77, how do you know the zip file isn't empty? And since you're trying to restore the ISY does that mean you were successful in accessing via admin console? You mention telnet and formatting the card above. If this is a new card you can skip that step. Are you 100% sure that your Safari is setup to NOT unzip the file on download? Apparently this is a known MAC issue with Safari and must be changed in the Safari settings. Make sure you follow the steps here - https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Replacing/Formatting_an_SD_Card Start at step 3. Also, what did you do with the original SD card you removed? Since it might have been a power supply issue perhaps the old SD card was indeed still good and still has the original setup on it. Perhaps put that back in and see if the device starts normally. Final note - if you have a PLM make sure that it always powered on before you power the ISY994 and do anything with the firmware so it will not start in safe mode.