Geddy

I would say this is an AT&T issue and not a UDI problem. While I don't see a huge uproar about this searching Google for AT&T issues there is this one post that was easy to find: https://forums.att.com/conversations/att-mail-features/att-email-to-text-feature-is-not-working/62e57d87e232bb632089fdd0 Perhaps search if other AT&T users are having issues.

@Prana electric what wireless carrier do you use? @raymondjiii just posted similar issue and mentioned on AT&T. If you are too can you send a simple email to text from a different domain? Does it get through?

Another user is having issues as well… https://forum.universal-devices.com/topic/37705-not-receiving-text-notifications/ if you email/text yourself from another domain does it get through?

@mjrush, honestly...you DON'T have the same problem. So now we're troubleshooting your problem in a thread that OP (@Prana electric) stated they weren't getting TEXT MESSAGS. Next time, please start your own thread. It's quite possible that your host might be blocking messages coming from the UDI Default email server. Depending upon how many messages you might have been sending if they never change some servers can consider that bot attack or spam of some sort and block it for a period of time. I just tested the default mail server going to gmail and it worked exactly as expected sending 5 test message. Side note: The messages pass normal spam/spoofing (SPF and DMARC) filters so that's a bonus, and a little surprising the Comcast puts them into spam. The easiest solution would be to suggest setting up an ISY only Gmail account. Following the Wiki setup steps and testing from that way. This way it does two things...it gets the burden off the UDI servers for sending timely alerts. But also assures that you've setup and received messages as expected. If once you're using a different sending server you still have issues then you need to check your receiving server for bounced/delayed/undeliverable messages. If you have your own domain for receiving the alerts are you hosting the mail server or is your webhost handling the mail server? It's possible they've blacklisted UDI's server for some reason.

@Prana electricand @mjrush, What mobile provider are you on? As @MrBill asked if you're using the default mail server? What Firmware are you on? It's been covered here many times that the texting process is unreliable. Mostly because of cell providers blocking mail to text or making them very low priority that they come in hours (or days) later or might not arrive at all (as you're describing). If you're using UD Mobile I would suggest you look up how to setup alerts using network resources. Read how to set them up here: https://wiki.universal-devices.com/index.php?title=UD_Mobile#Notifications_Tab Also, if you're not using the default email option you might want to check the settings for the server you are using. If you're using Gmail there is also a thread on here about setting up the additional security options. There are several options available to move away from the "old" way of pushing an email to text alert that are more reliable. Yes, it takes a little effort to set them up, but doesn't reliability outweigh the setup?

Thanks for the light pattern...seems that it is up and running normally. You get the log in page as expected. But you say... Have you tried on a different browser? What browser are you using? It's possible a cache issue has developed in the current browser and the page needs to be hard page reload (ctrl + shift + r, or ctrl + F5) Are you trying to access PG2 (https://polisy) or PG3 (https://polisy:3000)? It sounds like a browser issue if you're not getting any reaction from the "login" button after you enter credentials. Are there any error icons/notices in the URL from the site you're going to? Like hidden popups or not running scripts? I know the PG3 process changed a few versions back that it pushes you to the ISY Portal login before you actually log into PG3. If you're going to PG3 are you getting the request to log into ISY Portal before you enter Polisy credentials? If you open ISY Launcher you do you get a window similar to this: Click on the Polisy line and then select "Polyglot V3 (PG3)" option. What does your browser do when you get there? If you get a warning that it's not safe click advanced and proceed to the site. Hope you're able to get in with a different browser. Once you're logged in please post a screen shot of what version Polyglot you're running. Mine currently shows: (for PG3) For PG2: (Note, I'm like you in still using ISY994 on PG2 settings...thus the difference in ISY versions)

@CopyRon with 4 portals do you just use one account to log in and see all of them? Make sure you have the right “preferred ISY” selected in your profile. You might be sending things to the wrong ISY. I haven’t done a sub account, but perhaps when you made the sub account that is set with the preferred ISY you were working on. When logged into the portal click on “profile” in the top right to choose preferred ISY.

Since you can't work on it until tomorrow a ticket is probably your best bet. You'll probably hear back from them tomorrow as they tend to take Saturday off, but it is the weekend so don't be expecting too much back and forth. Simple troubleshooting: Step 1 - power cycle the Polisy cleanly once. Just pull the power, wait a few seconds, and power it back up. Listen for the beeps then check the lights on the FRONT of the device. https://wiki.universal-devices.com/index.php?title=Polisy:User_Guide#Troubleshooting What are the lights on the FRONT doing? If the left is on solid then the Polisy seems to have come up and working normally. The lights on the back are probably just network and PLM traffic. Can you log into your router and see that the Polisy has connected to your network? I'd say so since you mention that you can get to your ISY admin console (unless you're talking the ISY994 admin console and not IoP). You also mention you can get to the login screen, but it doesn't progress. Did you get the Portal login screen when you first attempt to login? If you don't know how to SSH to the device there's not really much to do unless support suggests you attempt some SSH commands. Then you should get a program like Putty to make it simple. Some like to use the Windows SSH shell, but I find it a little clunky (personally). It's just all in how you learn it for personal preference. Submit a Ticket: https://www.universal-devices.com/my-tickets Email: support@universal-devices.com

Had you moved the portal account to the Polisy (IoP)? If so then the old ISY might not have had a Portal account. But you said you got it to work with a "sub account". Where did you make a "sub account"? It could have been that something was down when you tried adding the main account, but worked by the time you created a new account. Have you attempted to use the primary account again? I don't have Google Home devices so can't help too much with the setup, but if it had been connected why did you disconnect it? Either way...sounds like you're back in business the way you wanted, but still kind of strange.

@Bumbershoot guess that answers your question...it's not thoroughly tested and thus you've shown it doesn't fully work (at least not for your attempt). From memory there's been several questions about that function in the past (like @MrBill's above). I've seen @Michel Kohanim say specifically in the past not to use it, but I forget what it was for...I want to say it was more geared toward ISY994 updating to 5.x, but that's just going from memory. @Bumbershoot Do you know if it messed anything up on the device you were trying to update? I know you said it was for a vacation home so maybe you're there now and can attempt updates locally.

Submit a Ticket: https://www.universal-devices.com/my-tickets Email: support@universal-devices.com Be sure to include UUID of your device.

@TVC15 Glad you were able to fix the issue. This issue is a known part of upgrading from 4.x to 5.x and part of why "Step 6" is written into the upgrade process in the release notes for 5.3.4 (probably appears in all 5.x update release notes). Even in the "NOTES" section at the top of the release post references the manual intervention needed when going from 4.x to 5.x. While you said you're all set, it is still important if you had any "Adjust Scene" programs that you check each of those individually (and update if/as needed).

@RJ K did your Hue Hub change IP addresses recently? That's what sparked most of this thread. Either a router change or not using DHCP reservation with the Hue Hub after you got it online. If so then you need to add the following for Custom Parameter: Key = bridges Value = ["#.#.#.#"] (MUST have the square bracket AND the quotes) As soon as I added that (in PG2) it found the hub right away. If you're still having issues then look at the lot (put it in debug mode) and restart the node server. Allow it some time to start up and then review the log. See if it is giving any idea as to the IP it's looking at for the bridge. When I attempted to add PG3 version (after having the PG2 at the old IP) it still looked for the hub at the old IP address. I do not think there is a way to remove the current configuration. Just a custom parameter to overwrite it. I think I attempted to remove the custom parameter and it still looked at the old IP.

Excellent! Glad it worked out! Yes, Kaspersky can be a doozy sometimes. I quit using their products about 15 years ago for similar reasons (long before I was using ISY). I'm sure there's probably a way to approve the app to run in Kaspersky, but couldn't help with that without some Google searches so I'll let you check on that. My only other suggestion would be to remove it from your system and get something like ESET anti-virus. As long as you're not specifically going to sketchy places Windows 10 (and I think Win11) do a fairly good job of blocking attacks and scanning for viruses.

That's an interesting difference. I just downloaded start.jnlp from my link above and moved it to the desktop. My icon appears like this: If you right click on your icon and select "open with" what program is the default for you? I show the following for mine: The icon you're looking for is the ISY Launcher. That's only added to the desktop once the start.jnlp successfully runs. It appears that's still the issue you're facing. I've not seen an issue of having to specifically have the 64 or 32 bit versions of Java. Either seem to run the .jnlp just fine. I just tested on a computer that I've never used to access admin console. I removed Java as outlined above (man, my son is going to hate me if his Minecraft won't load right after this). I then went to java.com and downloaded what was offered up as default when I clicked on "download java". Installed it. Downloaded ISY Launcher. And it ran without issue. I don't have any Antivirus, Firewall (other than Windows Firewall) or VPN running on that computer. So I suspect even though Kaspersky is "disabled" and your VPN (being off) are still blocking the necessary traffic for Java to communicate with the resources needed to properly add the ISY Launcher to the desktop.

This was going to be my next question. If Virus and Firewalls are turned off. If your VPN is off are you still able to access websites? This error appears to be a Java issue that cannot reach the external source to complete setup of the ISY Launcher icon. The "unable to load resource" is commonly found on google searches to mean the computer cannot reach the web (due to DNS issues). If you are able to access the web with your VPN turned off and you've gone through all the steps above then I would open a support ticket as you've attempted the usual troubleshooting steps to get on the right path again. Perhaps they have other tricks to try. Either way, please update once resolved so that it might help others in the future. Submit a Ticket: https://www.universal-devices.com/my-tickets Email: support@universal-devices.com As you said this is a generic web interface/dashboard of types and isn't what you're looking for. Since the inception of the ISY Launcher process (introduced in 2018) there's no need to have a browser open to try to access admin console. @ccclapp, I understand your point. It appears the reason that thread was closed was because you never came back to update the status and others were tagging onto it with same, but different issues. So to avoid the thread issues it was closed. If you're still having issues please send me a PM and I will re-open that thread so you can update in there. Otherwise, let's try to help @cdave1252 with their issues. It's certainly a small minority of comments about not being able to get the system to work as expected. So I would have to say for a very large majority of users the system works as designed.

Moved from prior location as was new issue. Was attached to this post: https://forum.universal-devices.com/topic/37031-after-so-many-years-still-cant-connect-to-isy/ @cdave1252 where did you get that version of Java? The current general Java version is 8 update 341 (https://www.java.com/en/download/) - you mentioned you have 351 (maybe just a typo). Seems like something is not correct with the Java install. And then you're not using the ISY Launcher to correctly get the icon on the desktop. I would suggest completely removing Java (yes, again). This time be sure to remove it using Windows control panel -> programs and features -> uninstall. If you run other versions of Java then you need to download the app to remove old versions (found here: https://www.java.com/en/download/help/remove_olderversions.html). After you remove Java do a search on your computer for any *.jnlp files. REMOVE all old copies of admin.jnlp and/or start.jnlp that you might have (either in the download directory or in temporary locations). We've seen users attempt to use old files they thought worked for the current Firmware and it causes issues. Best to download a fresh copy every time you need to add the ISY Launcher icon back. Once you've removed all Java versions and deleted any old UDI files reboot the computer. Download Java (linked above). Download a fresh version of ISY Launcher Run start.jnlp (ISY Launcher file downloaded) Accept Java warnings Accept Windows firewall warnings You should now have an ISY Launcher icon on your desktop that looks like this: If your ISY does not appear in the ISY Finder window once opened then you need to confirm the ISY is online. Log into your router and confirm the ISY is connected to the same network your PC is in. Make note of the IP address seen on the router. Manually add the IP address: http://your.isy.ip/desc From there you should have what @MrBill posted above.

@alambertus checking in...it's been almost a week. Were you able to get this fixed? And if so what allowed you to regain access to the IoP? If still having issues I would suggest opening a ticket with support to try to get things back to normal. Submit a Ticket: https://www.universal-devices.com/my-tickets Email: support@universal-devices.com

@ahwman I think the best way to do this is to add a user and make them admin then you can remove the prior user account once you've logged in using the new email. This will keep all prior configuration in tact. After removing old address make sure the portal is still online and registered (admin console -> configuration tab -> portals). While logged in on my.isy.io click on "Users" tab at the top: Then click on "Add User": Then fill out the new user information and make sure to check "Account admin"

But that's fool proof....right? @Athlon I've always wanted to use some of that stuff.

Glad it worked out! That summary page does come in handy from time to time. Time to disable the program or tape a sign "do not use" to the button!

Not where it's coming from..at least not outside the ISY. If you see traffic in it then it is traffic within the ISY, but it won't tell you if it's being triggered by something outside the ISY (at least I don't think so...) I just tested by turning a light on/off via HomeAssistant and directly in the admin console. They are identical events thrown. So, there's no way to tell where it came from, but that something was sending traffic to/through the ISY. And you're 100% certain you don't have any programs in the ISY that could trigger such light status? Check the summary tab of the program area and see if any programs have run recently (or around the 9:00 time.). You can SORT the last run time by clicking on the column header. Only other thought would be to disconnect devices just before 9pm and see if it does it. Might take a couple of days if you disconnect one-by-one to figure out what's doing it.

@PBatavia01 you haven't been back since posting this message earlier this month. Do you still need assistance? The wiki information you're looking for is in the Universal Devices Wiki for Polisy: User Guide. Found here: https://wiki.universal-devices.com/index.php?title=Polisy:User_Guide Please note, that there are some late updates that can mess up the system. So currently I would suggest if you still need to update to PG3 that you open a support ticket with Universal Devices to get the specific commands to get IoP (ISY on Polisy) installed, running, and updated so that the admin console of IoP can then update the parts of PG3 in order not to corrupt other items. Ticket can be started either of these ways: Submit a Ticket: https://www.universal-devices.com/my-tickets Email: support@universal-devices.com

Great to hear! Glad it ended up being something "simple". Not sure if you're still needing help on the Elk stuff or not, but you'd be better off starting a new post in the Elk sub-forum to get help specific to those issues.

You should upgrade the ISY994 to 5.3.4 firmware. Not saying that will fix all your problems, but I would think some changes between 5.1 and 5.3.4 probably finetuned some z-wave settings since that was a big part of the 5.x upgrade. Especially since 5.3 was the first one to be an "official build" for full z-wave certification. 5.3.4 is further minor updates within the system. But you mention they're old devices and probably a generic z-wave device that might not actually meet some certification aspects that could be causing problems as ISY advanced into z-wave certification.