Geddy

For Gmail you should setup this way: I just set this up on my Polisy and it worked perfectly. Take a screen shot of what you have setup and post it (blur/remove any personal identifying information) The biggest issue is the "From" needs to be in the format (if you use a name) to have the colon (:) between the name and email address. I also use Gmail and 2FA and have ISY app specific password setup and this works. I just changed from the default for Polisy to this and it sent a test message without issue. What does this mean? Are you using the ISY "Use Default" settings and you got an error? Make sure you have entries in the "Groups" to send the test to. If that's blank it might give you errors because there's no outbound recipient. That would give you a different error though so doubt this is the problem.

@GTench While it's been said that 170001 errors are informational only you are getting a lot of them so perhaps something isn't right. Are you still getting them all the time or were they simply limited to the time you showed of 11/20? If ongoing you might want to open a support ticket just to make sure everything else is connecting correctly. I think assuming 170001 errors can be ignored might have been valid for ISY994, but with Polisy and the connection of various dependencies the question needs to be asked and explored a little more as to what is causing the information log hits in the first place.

@GTench -10103 AUTHENTICATION USER ID DOES NOT EXIST https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Errors_And_Error_Messages Not sure what "LEN" means. What device are you using? What is your firmware? Did you do anything on Sunday to the system that might have started causing this error or is this just the portion that you posted?

@adam48 The 60006 and 140000 errors mean the device is not able to connect to the internet. Either you didn't put the network cable into the correct port or it's not being assigned an IP by your router. What is the light pattern on the front when you boot it up? I looked further down your log and see the 110022 and 110012 errors. Those indicate SD card issues. Either the SD card is corrupt or just needs to be reseated after you opened the ISY to remove the z-wave card. Also, you don't have to clear java cache each time you try to connect. As long as you're using the ISY (IoX) Launcher method to connect to the admin console. You should only have to clear java cache if you're having other issues or have upgraded firmware. Often times when Java updates though the icon on the desktop will go away and you would need to clear the Java cache then and download a new start.jnlp to get the IoX Launcher icon again. Wiki links for your issues: Error codes - https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Errors_And_Error_Messages Light patterns - https://wiki.universal-devices.com/index.php?title=Main_Page#Front_Panel_LEDs/Lights It's possible that your time issue was because the ISY didn't have internet connection. You probably could have left the z-wave card in there first. I might put it back in, reseat the SD card. Plug everything back up. Plug the PLM in first. Wait a few seconds. Power up the ISY, and watch the lights on the front. Once you have internet restored to the ISY everything should work correctly again. Strange that this worked. Perhaps it wasn't long time of internet outage, but you clearly were getting errors relating to lack of internet connectivity.

@asbril actually @MWareman alluded to it above. It's a chip for security on code on a device. I believe Win11 started using this too in order to verify updates. From some Microsoft documentation:

You've got some strange comments in there and the "Factory Query Program" isn't commented out. I'd remove those lines and if you want/need comments in there add them back. My query program is just like yours, but no comments: 00-KEEP-ISY_Query - If Time is 3:00:15AM Then Set 'Polisy' Query Else - No Actions - (To add one, press 'Action')

This Polisy (is) Mine!

Have you by chance deleted any devices or have devices fail that are no longer reachable by IoP? Look through some of the programs impacted for any errors that might look like this: Warning: Unrecognized Condition (program may not run) If you see this in any programs fix it and SAVE the program tab again. Also, while unlikely because there haven't been posts about it with IoP, make sure your User Interface (UI) and Firmware (FW) match. In Admin Console go to HELP -> About and make sure these both have 5.4.5 and the timecode matches. IoX Launcher helps prevent the mismatch, but this was an issue back with the ISY994 4.x to 5.x migration and beta updates. One other option is to set the java runtime memory higher.

I have successful backups (like @asbril), but don't have TPM enabled. I've been running 5.4.5 several weeks. (soon after others reported it updated...whenever that was).

@CMortimer I'm not 100% sure on z-wave side as I don't have any to test/help/review. But make sure you look at this from the wiki for variable information: https://wiki.universal-devices.com/index.php?title=ISY-994i_Series:EMail_and_Networking_Substitution_Variables I think I've seen some mention that the temp should have a node address assigned to it. You can then use the information in the link above to reference that in a notification. Hope that helps. Perhaps others with more variable experience can chime in.

Not sure, not an Android user. Moved your post out from a dead thread to see if others can help set something up. I know there have been posts about setting geofence somehow in Android.

@MWareman UDI Mobile was a different app than UD Mobile. UDI Mobile is no longer available.

While I agree that 2FA is a PITA it's become the necessary evil for many accounts. I find it helpful and turned on for every account I can have it. I'm the opposite of what you're doing. I avoid accounts that don't offer 2FA or handle it only through email (that is indeed easy to hack). Now that the new iPhones don't have physical sim cards hopefully sim swapping is a little more difficult. The point about 2FA is that it should be sent to another device. Yes, I'd say most of us are logging in on multiple devices and ultimately it probably is one log in and secure process getting sent to same device, but again...I see it as a deterrent rather than real PITA. I don't really know what you're saying here...must be Canadian for something. But my guess is once you turn 2FA on you can't turn it off? I don't think so, but haven't tried. The issue is that Google finally turned off being able to log into other applications with only user name and password. They (Google) require accounts to have additional security turned on and thus make an app specific password. The good thing is that on my iPhone once the mail app setup my Gmail account it doesn't ask the password/2FA each time it checks the mail. It's making a secure connection though so that's trusted by Apple and Google. The problem is that the ISY is making a fairly unsecure connection so by using the app specific password Google thinks that it's more secure than your basic user/pass combination. Again, just setup an ISY specific google/gmail account. Turn on 2FA set an app specific password and forget about it. It's fairly simple (IMO). But again, I've had it on for ages and accustomed to it.

There had been some discussion earlier this spring or Summer that Outlook was having more problems than people using Gmail. Even at one point a user said their Outlook.com account was causing the ISY service to crash. I might suggest getting an ISY Specific Gmail account and attempting to setup following the wiki setup that was updated after Gmail changed to require 2 step authentication for the account. Follow the setup here: https://wiki.universal-devices.com/index.php?title=ISY994:Configure_Mail_Server_Settings For testing though (with my IoP that's not in normal service) I was able to get Outlook to send a test message. It seemed to take a little while to think about it, but it worked. My setup is as shown here: NOTE: I do have 2FA turned on for my Microsoft account so I had to go to the account security and create an app specific password for this to work. Read more about that here: https://support.microsoft.com/en-us/account-billing/using-app-passwords-with-apps-that-don-t-support-two-step-verification-5896ed9b-4263-e681-128a-a6f2979a7944 Also, make sure you have at least one entry in the "groups" for recipients for the test message to go to. It can't send a test message to nowhere! I used my ISY specific gmail account and it showed up in the "inbox" for the gmail account. Sometimes the TEST message is treated as Spam and might end up in the spam folder. But this time it did go to inbox as expected. Personally, I've had better success with Gmail than Outlook for these types of alerts. I did have some errors/lines in the error log, but they seemed to be mostly informational lines (-17001 error IDs). I did not check on my primary ISY994 if I get the same lines when sending from Gmail.

@jlegault That's an issue you'd have better luck with asking in a Java forum. Perhaps this will help: https://blogs.oracle.com/javamagazine/post/java-on-arm-processors-understanding-aarch64-vs-x86 Or this - https://macperformanceguide.com/blog/2021/20211216_1200-Java-for-M1-Macs.html The issue might be that admin console is developed for standard Java that is available just by going to www.java.com and clicking download. I'm assuming that macOS still does this like Windows computers do. Users have reported errors when using multiple versions of Java or versions that are intended for different applications. If getting Java from java.com is not "native" then I'd say the answer is no.

Did you resolve your issue? If you did...then you don't need support. If still having the issue or another issue for this then yes, open a ticket.

@RPaquet be sure that you set a DHCP reservation for the ISY994 in your Xfinity gateway. Don't use Static IP setup within Admin Console (just in case you change routers down the road you want the ISY994 to use automatic DHCP, but allow the gateway/router to handle reserving the IP address so it's always constant. According to the wiki this meant the ISY was not on your network - https://wiki.universal-devices.com/index.php?title=Main_Page#Front_Panel_LEDs/Lights Even though you said the Xfinity Gateway identified it, I can tell from my past experience with an Xfinity Gateway that their information is not always current/accurate for online and offline devices. They seem to have a long memory for when things are actually not connected to the network. So it's possible the device wasn't back online yet, but your Gateway only thought it was when you looked at it. The flashing lights indicated that it was not correctly on the network. I think it might add it automatically now, but if you run into the issue in the future add "/desc" behind the IP address. See step 4 in the Wiki for "ISY not found: https://wiki.universal-devices.com/index.php?title=Main_Page#ISY_Not_Found

@Illusion did you make sure you followed the steps for the process? https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:INSTEON_Device#Replace...with https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Replacing_a_Device Key points to remember: Both devices have to be the same type of device in order for the new device to be displayed in the replace menu. The device being replaced must not be inside a folder You posted this in the support thread for the last IoP firmware update. Since this hasn't been reported by others and the release happened a while back thought it should be its own post for more attention. If you've already attempted as far as it appears you have then there might not be anything that can help it. If you had a backup from before this process started perhaps you could restore that, re-add the new keypad link then go through the steps again.

@dbuss interesting that yours works with only "ISY" in the "FROM" line. I haven't taken out the email address portion of that line, but thought that might have been an issue in the past so just left it as it was in my initial setup. Mine is actually "Home-ISY:<bogusaccount>@gmail.com". One thing I have noticed is that I need to actually log into that account on a somewhat regular basis to keep it active. I don't keep up with when I do it, but I have Spark running on my phone for a different account and it checks the bogus account when it's active so I think that counts as me logging into it. I know Google had gotten a lot more aggressive with idle accounts sending messages, but not other activity over the recent years. So best to keep it active to avoid flagging or removal from Gmail services. @larryllix like I said...this setup has been my setup since I started with ISY, about 6 or 7 years ago. I turned 2FA on for Gmail as soon as it became available; long before I had the ISY.

Here's the settings I have: Often times the error I recall seeing most is that people don't catch/notice the colon (:) between First-Name Last-Name in the setup and will error out because the "From" is not formatted correctly. Beyond that the key is usually the Google/Gmail settings for 2FA. In the Google Account Settings look at Security (seen below), make sure 2-Step Verification is "ON" then setup App Password. Once you have this it will show you what you have App Passwords for, when they were created, and when they were last used. My last notification was apparently emailed at 8:02 this morning. The WIKI was updated to link to this information for such setup (following the changes Gmail made earlier this year): https://support.google.com/accounts/answer/185833?hl=en My custom notification uses variables in the body so it's not always the same text so spam/robo checks from Gmail or receiving account shouldn't auto flag it. I was concerned that if it was a static message that got sent regularly that it would be flagged as robo sending even though it doesn't send very often (daily most of the time) so it's simple and works for me. Hope that helps. Let me know if you've got other questions.

@EricBarish another thing to look at is on a computer go to alexa.amazon.com then Smart Home then Devices to make sure it’s still seeing your devices. Should be able to see you skills in that area too (I cannot access it from an iPad to check and not near a computer for a while).

What skill version are you using? Make sure you are using “ISY Optimized for Smart Home v3”. It could have been a temp issue with some server issues between you and Amazon. Just tried several lights and no issues with Echo and ISY994. And I’m also able to control devices from ISY Web Access through Portal.

@fbelg210 follow the instructions here:

Make sure you follow the wiki setup information for Gmail. Some slight adjustments were made earlier this year. https://wiki.universal-devices.com/index.php?title=ISY994:Configure_Mail_Server_Settings#Configuring_gmail_Account If you’re getting errors post them here. I use Gmail without any problems sending to another email address. If you’re trying to use Gmail to send to text you might still have delivery problems. Pushover is good. Another good option (often suggested by @MrBill) is using a 3rd party email app (like Spark) so alerts that only that app checks the email for are ISY alerts so you know when ISY alerts are received. I think he uses a spare ISP email to send to that same account and uses Spark to check that email only.

Are you sending texts from an email? This has been asked/answered in many posts on here. The "old" method of sending texts to a #@vzw<whatever-email> is very low priority for most carriers these days. The suggested route is to use network resources, node server, and/or UD Mobile alerts. Run a Google Site Search for slow texts and see what has been said. It's not just you, and it's not UDI. It's the cell carriers.