Geddy

Another option would be that you could buy this adaptor and make the cable yourself if your so inclined… https://www.amazon.com/StarTech-com-Serial-adapter-DB-9-RJ-45/dp/B00006IRQA I know this product has been linked in other posts and is what @MrBill references in a post above with the link to another cable option. In the other posts there was discussion about how to wire it correctly. You would need to search the forums to find those posts.

Why not just upgrade and find out yourself? I’m not local to my Polisy so can’t for a while. You should just upgrade your device so you have access. Doesn’t cost you anything to bring the device up to current supported system level….might even be better that you do it sooner rather than later. Think of all the fun things you can “play” with and learn about!

Just part of the system that hasn’t been updated. Kind of like why does the Wiki still have the steps if it doesn’t work? Because there are just too many moving parts sometime. Getting the correct processes for new development is priority for the wiki. Just as I figure it is for portal coding.

Yep, I know what it is from prior posts about it and from the wiki. My point is that the app isn’t supported anymore, and not available to install, according to other android users posting here in the past. So, if you’re on Android it might not work. Again, I’ve not heard of it “crashing” an ISY or IoP before so that’s why I suggested downloading logs and starting a support ticket in case it did cause the crash perhaps support can find something in the logs. There are other posts around about setting up geofence with Android. I’m on the iOS side of the fence so don’t know what to suggest for other options if an old app is not compatible with the new phone. I was just suggesting that a support ticket is the only way to better trigger a review of the system or track a bug or find if you stumbled into a way that crashes Polyglot. Wasn’t sure if you posted as “info” for others or really needed help with an issue. So suggested that you go the ticket route in addition to what you posted. Hopefully you’ve got your issue sorted out. 👍

Please read the wiki for the steps you need to perform: https://wiki.universal-devices.com/index.php?title=Main_Page#Installing_the_Admin_Console_Icon_on_Your_Desktop In 2018 the process changed to use what is called ISY launcher so it is not dependent on any browser being needed to launch admin Consol. All you need is a standard version of Java that you download directly from java.com. Make sure that you clear Java cash before proceeding on any steps in the above wiki.

Is you Polisy updated an current? If so you can find this yourself by logging into the Polyglot 3 web front then looking at the store yourself. https://wiki.universal-devices.com/index.php?title=Polisy:User_Guide Since prices might adjust it’s better to find the info yourself rather than posting for you and risk it be inaccurate down the road. You don’t have to use/run node servers in PG3, but if you have been updating your Polisy and possibly running IoP then you already have access to Polyglot v3. Find out how to access it in the wiki link above.

@apostolakisl Interesting, I’d download a full Polisy log from PG3 and PG2 (since you use both). Then I’d start a support ticket with UDI including the logs. Are you sure that you are using UDI mobile app? That is a very old app that has not been updated recently. I believe it’s only available on android and has even been removed from the android store so it’s no longer available to download. But I am not sure going from memory of other posts about “UDI Mobile”. It is NOT the same as the current UD Mobile (https://wiki.universal-devices.com/index.php?title=UD_Mobile) being developed by Universal Devices. It is a known “issue” that IoP and node servers do not load simultaneously in polyglot. The note servers should try to reestablish connection to IoP over the next few minutes following a reboot. I believe it is said that it could take as long as five minutes for everything to resynchronize.

This is somewhat “normal” lately….I’ve also had this issue when using the admin download direct from the ISY994. I don’t use that method now, but when I tested a while back also had issues launching it multiple times. Since you were able to get it to work once then the ISY Launcher method should work just fine, and would work EACH time you tried to open the admin console. Let’s look at network and computer issues…do you use VLANs? (Perhaps your ISY and Win10 machine aren’t on same local domain. Does the “Cloud” option ever load admin console when you tried the ISY Launcher icon? Win10 and Java 32 bit? Have you tried to remove Java (also using the Java remove tool to be sure ALL old versions of Java are removed)? When you reinstall what browser are you using to install Java? Maybe specifically install the 64 bit version. I’ve not personally seen much difference as I know I have 32 bit installed on one machine and 64 bit on another and both can access ISY without issues, but you might just consider this change. I would suggest these steps: Clear Java cache (be sure to select all three boxes in this option dialogue) remove Java (through windows AND the Java remove all version tools) DELETE any *.jnlp file you might have been using….look EVERYWHERE! Get rid of any old copies of start.jnlp, admin.jnlp, or any other ISY related .jnlp file) Install 64bit Java (might be a download process rather than simple click of “get Java” From the Java site. Be sure it installs in the “program files” directory…NOT the “Program Files (x86) directory) Download fresh “start.jnlp” from the wiki link you have above run start.jnlp and accept any Java warnings. Make sure it adds the “ISY Launcher” icon to your desktop. run ISY Launcher from your desktop icon try LAN option first. If doesn’t work, close and try Cloud option. Report back your status after trying all above steps. Include any necessary network information (be sure you can log into your router and see the ISY is an attached device. Make sure your ISY and computer are on the same subnetwork (192.168.1.x or something that the first 3 digits match!). Icon added to desktop should look like this: (probably without the green check mark though….mine is on desktop and being backed up to OneDrive)

Correct….they were not specifically fixed in that update…they were between the version you were running and the latest release. So I suggested to go all the way to the current release for ISY994. Since you were already at 5.3.0 then it’s a simple and safe update to 5.3.4. I think the mail servers were in an update or two before the latest. I’m sure in the past some users didn’t want to run beta or test versions, but due to the z-wave certifications each minor update is showing as simply an update. And since this version hasn’t had an update in over a year it’s fairly sure to be steady….as are most prior builds for the ISY994. Hopefully @MrBill got you the info needed for z-wave info. I don’t use them so couldn’t help ID them. I know there are a lots of posts here saying what makes one a 300 or 500. My suggestion would have been to ask the vendor you bought them from. Surely there is a serial number or other identification on the chip that could be referenced with the supplier as to which model they are. But I think the answer above should head you in the right direction.

@bgrubb1 you need to update. 5.3 is an outdated version. An update resolved the default email setting issue. Please update to 5.3.4 for ISY994 found here:

@bgrubb1 what are you attempting? And what firmware (and Ui) are you actually running? You mention”latest”, but please state what version you indeed are using. Usually just checking “use default” means nothing needs to be entered. What is your error? If you’re sending tests be sure to check your spam folder for receiving account (for me nearly all test sent from default servers went to spam folder). The more details you can provide here might get you help. From what you’ve said not really sure what you’re attempting to do. Not sure what your issues are. So not sure what you need “fixed”.

It’s very possible that your backup is corrupt. If you were having SD card issues or other issues prior to failure of last ISY. And, yes, I think network settings are stored in the back up file so it might be causing you issues when you restore and try to put it on your new network. It has always been commonly suggested that the ISY be in DHCP mode and handle IP reservation at the router level. But you seem network savvy enough to do it however best fits your system.

@JMC were you by chance using PGC? That was shut off earlier this year please see this post. If you have Polisy or Polygloy availability you can run a local version if available in the node server store.

@MGustin glad you got it solved, and thanks for sharing steps to resolve! @Hoosier Daddy originally was posted to another thread. But doesn’t really matter…split it out and OP got answer from support and updated. Thx all!

What version Polyglot are you running? At the bottom of the dashboard (or almost any PG3 page) what do you have for version? I'm currently running 3.0.63 and Hue NS runs fine in PG3. Perhaps this is something the developer @xKing can help decipher or else you might need to PM them your full Hue log file for them to check. My hunch is that you might have updated PG3 with an SSH command recently (it's not advised to do that currently) and you might have corrupted some UDI files. Since this isn't being reported by many others you might be better off with a support ticket with UDI for them to review PG3 logs as well. However you get things working please post back here to update what helped resolve your issue incase others have a similar issue. And yes, as @lilyoyo1 says it wasn't anything like the thread you posted in. So moved out to its own thread for additional attention. Thanks for posting! Hope you get things working soon.

@dinostop merged your post into this issue as it referenced same issue and @Michel Kohanim has confirmed this is a known issue that is being worked on.

@Schlyguy try logging into alexa.amazon.com Click on: Smart Home -> Devices Do you see more than just the few devices you've setup from Portal? Should have all spoken listed. It sounds like you might need to open a ticket with UDI asking about the portal. Perhaps there is something they can get from your logs to figure out why Alexa might be able to trigger something that isn't specifically exposed to the skill. I think it's something @bmercier might need to review.

Regardless of the device. Scenes are what link switches within the ISY control. That is if you want the ISY to know the status of the switch at all times. If you have manual links ISY might not get updated if the switch isn't reporting to the PLM. Maybe review this video for scene making: https://youtu.be/hbkFnzBhKB4?t=436 Also read through the Wiki - https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:How-To_Guide#Scenes (Most of the wiki scene information was written prior to or during 4.x firmware and should give you help with windows you're seeing.) Your Patio/Spotlight example is something that could be done with a program for on and fast on. Scenes are handled much different now (in 5.x firmware). Most users have upgraded to 5.x so getting support in 4.x might be more difficult. I'm not suggesting to upgrade because that's a complicated process. I think you should fix/work out your issue before you consider changing firmware versions. Did you control the Insteon with a hub before going with ISY/PLM?

@landolfi moved over to IoP area since you're specifically referencing Polisy. You did not have the same error as the thread you originally posted. Perhaps @MrBill's suggestion of opening a ticket will get you the help you need. Are you trying to backup IoP (admin console) or Polyglot (web interface)? And you reference you found a link somewhere suggesting a bash command. Always good to include that link in your post so anybody trying to help you here can go read what you're talking about and not your interpretation of that issue. Good luck getting this resolved! Please post if you get help from UDI Support as to what was done to resolve this issue so that it might help others if they run into this issue as well.

This appears to be an AT&T issue. There was a comment on another thread about this...seems like AT&T is not picking up the correct "from" and just using string of numbers. I tested with ISY994 and IoP over the last week using T-Mobile and never got such strange looking messages. This still comes back to the suggestion that Email to Text is not the ideal way of processing notifications in 2022. There are Node Servers to handle pushing notifications to mobile devices either through UD Mobile or other applications (such as Pushover). Those options have many more functions and features than Email to Text. I think anybody using Email to Text should consider other options.

I don't know first hand, but there have been a few other posts about X10 working with IoP. Seems to be hit and miss. Here's one that might help:

@Sachelis well...in truth...the url you posted is "impossible" and "wrong". There was should have more to the URL. That's why I asked if you actually posted the bookmark URL or just summarized it. Looking back at some old 4.x release posts the URL had the version number behind the /994i/. I had to go back to 4.3.x release notes to find that. And yes...I remember the days of having to use IE to start the process. But even at the 4.3.x stage Chrome had removed such Java support so IE was the only way to still access it. That's why the ISY Launcher method was vital. It helped resolve two issues (reliance on IE to launch admin console and helped match UI/FW by default). I'm not at a decade yet, but just over 6 years so I remember the old process...vaguely. Thankfully, the new way is simple and easy. Let me know if you have any issues with it. Hopefully your ISY is somewhat up to date.

You're still having these problems? Didn't you post about that a year or so ago? I would have thought it had resolved. I would have scrapped Google home long ago if I couldn't make it work for something simple like that.

@TriLife Yes...well...I believe you can, it should be possible. Are you going to leave z-wave items on the ISY994? Also, since you are going to be removing the PLM from the ISY994 you should change the firmware on the ISY994 to the non-PLM version so if/when you log into the admin console it's not showing being in "safe mode" because there's no PLM connected. You can find the different firmware in the release threads. Basically, the Polisy would run PG3 and IoP. You would enable Insteon support on the IoP and then follow the migration process in the wiki (Polisy User Guide). Once you got all the Insteon devices moved over you should then reset the ISY994 with the non-plm firmware. I don't use Z-wave so can't help with the process there. I'm not sure if there's a way to backup just z-wave and then just restore that to the new firmware on the ISY994 or if you would have to set everything up again. I know @lilyoyo1 and @asbril more proficient with z-wave that they might be able to answer that specific process. There is still little known about the eisy. That's just been a few posts from UDI about that and think it's a new device that will work just like the Polisy. It seems that Polisy and eisy will maintain some similar support for the time being. PG3 is still the route that development appears to be going. It's so new that I doubt it would make a major course change at this point. (All just speculation...I don't know...I'm just a user like most of us here!) So I'd say stick with the Polisy since you have it in hand. Keep learning to develop for PG3. If you're in the UDI developer system then you have all the tools needed to keep current as Polisy and eisy are available and as PG3 continues to advance.

@Sachelis Is that URL you posted exactly what you have in your bookmark that you've used for ever? I recall "back in the day" there were links that were needed back when browsers handled Java requests and opened the admin console that way. Long ago browsers stopped supporting Java and how it launches applications such as the admin console. In 2018 UDI released the "ISY Launcher" method so a browser isn't required to access the ISY admin console. This "new" way is a cleaner, easier way to access the admin console. This process also always makes sure that the User Interface matches the Firmware of the ISY994. Since that was a large issue people were having as upgrades were being released over the last few years. There is an alternate way of getting the admin console file directly from the ISY, but it's just that the current suggested/preferred route is using the ISY Launcher process.