Geddy

Also note that email to text/SMS is extremely unreliable and not suggested as a method to be used for quite some time. Many carriers are delaying such messages or bouncing them all together. If you're only relying on email to text for notifications you should consider alternate options. Many have been discussed through the forums so won't rehash what they are or how to set them up, but you should be able to find them easily. But both above suggestions of updating to 5.3.4 are correct for the initial steps to resolve sending email with Comcast. I know others that do it without issue.

@Chris McKean If you're running IoP to update: log into the IoP Admin Console click "Configuration tab" click "Upgrade Packages" wait for several beeps from the Polisy. (If you cannot hear beeps from your location wait a long time!) Please review these posts:

Can't help on the Habitat or Harmony side...don't use either of those. Did the light come in as a different icon in the past? I use Hue and it comes into ISY994 this way: The Hue bridge is as you describe as the domino, but the lights come in with bulbs, but groups of lights have the domino behind the light bulb. I wouldn't worry too much about that...it's just an icon. But, again I don't know if that matters to the system or not. As @MrBill says why start all over and put it into the ISY994? I'd just build out PG3 and move directly into ISY on Polisy if you're doing something from scratch. Why not just move the devices over to IoP before starting node servers? But, I haven't moved over to IoP either...mostly because I don't use many node servers and things work now...plus, it's all "family approved". Don't want to rock the boat.

At this point I'd say don't worry about Polisy. Take a look at the next gen eisy. But if you want to learn more about Polisy: https://www.universal-devices.com/product/polisy-pro/ https://wiki.universal-devices.com/index.php?title=Polisy:User_Guide Polisy and Polisy Pro are out of stock. So can't get them currently.

@Venicenerd Thanks for the hijack notice...I'm going to lock this since OP seems to have handled issue. If you'd like to ask your question in the Home Assistant area perhaps you'd get more assistance. https://forum.universal-devices.com/forum/128-home-assistant/

That's a bummer. I remember having that happen to me a loooong time ago. I don't remember what caused it. I didn't have to rebuild it though. Did you try hitting the "Refresh" button on the portal page you showed? Doing that re-syncs the device list from the ISY. Typically this should pull things back into the view, but you might also need to refresh the browser window. Having gone through that once, be sure you download the spoken (the download button next to the refresh). Not really anything you can do with that file, but it will at least give you what you had setup as of the time you downloaded the file. Additionally, you could go to https://alexa.amazon.com then clicked "Smart Home" -> Devices to see if things were indeed still stored in Alexa's memory. Ultimately, the question becomes - what did you do about an hour before this happened?

@eyost question has been asked a lot (especially since ~April 2022). Please review other areas of the forums for answers to your question.

Not using email notifications on IoP yet, but I remember this post from @Michel Kohanim suggesting to use 10,000 for timeout. I mean it's "only" 10 seconds. You're using 3 seconds. Does it make a huge difference? Sounds like a setup issue. I've been using gmail with notifications for ever and haven't had any problems. Must be they don't like emailing Canada. This has also been covered that it's a carrier issue. It's not handling the envelope for the email to text correctly and showing up as different random number. I tried this recently and it came through just fine from same accounts from UDI. I don't get why so many still use email to text...it's so outdated and unreliable. Use the UD Mobile notifications and network resources or a node server. All alerts are INSTANT or darn near! Also note that Google Voice no longer directly texts your phone, so @apostolakisl method above is forcing the email to text route. Google Voice stopped forwarding SMS messages earlier this year because many carriers were starting to block them more due to the amount of spam texts that go through email to text route. Google Voice will still accept text, but it only notifies you through their app. This is another reason not to rely on email to text notifications!

@dex Did you setup the IoP in PG3 correctly? It does seem that there's authentication issue talking to the IoP. In the PG3 web access look for "ISYs" and "Edit Current ISY" Make sure you followed the steps in the Polisy User Guide in the Wiki to set up correctly. I think once you get this setup correctly you'll be good to go. I know in the past I also had issue with sending a reboot to the IoP, but I think that's been corrected in a recent update. I don't usually try to do it that way so haven't tried recently. (And don't really like to randomly reboot the IoP so didn't want to test now.) I think the best way to reboot the IoP process is in Admin Console. Configuration Tab -> "Restart IoP"

No, I'm saying to go to 5.3.4 you either need a-wave 500 or no z-wave. So go to 5.3.4.

Can you PM me some of the links you were using? Were they from the Wiki or somewhere else? All current release information can be found in this area: https://forum.universal-devices.com/forum/339-current-release-announcements/ Specific release for 5.3.4 is here. (Make sure your system meets the standards for this version…specifically if you have a z-wave board.) The process of being able to update automatically ended with the release of 5.x because of so much effort to update.

Sounds like I misunderstood the initial issue. You implied that you couldn't connect on "computer 2" so I assumed when you were home it wouldn't connect. As @MrBill says there's no current way to access PG2/PG3 web dashboard while remote. Your method of using TeamViewer to access "computer 1" is working for you so that's a good way. Otherwise, if your router can handle an inbound VPN connection that would be the only other way to access from "computer 2" while remote. Are you able to access PG2/PG3 from "computer 2" when you're on the same wifi as the Polisy? If so...it's acting as expected. If you're still having issues when you're in the same network then you've got problems. Connection to ISY994 or IoP can be made through the Portal access while remote and not having to use VPN or open/forwarding ports on the router.

@CPrince Make sure that the settings in the PG2 web area is accurately pointing to the ISY994. (Make sure you hit save at the bottom of the page!) Then try just a restart of Polyglot Then check the log after it boots up. If it isn't changing to the ISY994 then you might need to start a support ticket to figure out if something in the database is messed up and not removing the IoP address on the PG2 side. Since PG2 isn't being developed further it might be a quirk that can't be fixed. But it could also be something simple to fix it as well. If you open a ticket download the PG2 log and include it (you might need to zip the file) in your support ticket so it can be reviewed to get you the right steps to fix this. Simple check to see which ISY PG2 is talking to...check the bottom of any page for the "ISY version" running to see what it's connecting to. Mine shows 5.3.4 since PG2 is talking with my ISY994.

@CPrince PG2 is not able to send node servers to more than one ISY. That's a feature developed specifically under PG3. (I believe) And yes, PG2 would auto locate an ISY on the same network. It's typically looking for ISY994 in the same subdomain. It probably doesn't auto find the IoP, but guess it could. I haven't tested that. So I'd say things are working as expected. You're trying to operate differently.

@CPrince glad that seems to have worked for you... Are you saying you're having the same issue with PG2? Are you trying to push PG2 node servers to IoP or back to the existing ISY994 (since you said you aren't migrating yet)? In PG2 going to the ISY994 it's a little different. Go to "Polyglot Settings". There you want to setup the ISY994 IP address and port is 80. Use the ISY994 user (admin) and password (whatever you use to log into admin console) BE SURE you hit SAVE at the bottom of the page!

@Stagehand have you followed the process in the wiki - https://wiki.universal-devices.com/index.php?title=Polisy:User_Guide#Accessing_Polisy Using the ISY launcher should be able to put you into PG2 or PG3 dashboard. If you're unable to connect directly through a browser. What do you see if/when trying to connect to the PG3 dashboard from the 2nd computer? Please review this part of the wiki to see if you're seeing similar pages: https://wiki.universal-devices.com/index.php?title=Polisy:User_Guide#Polisy_.28PG3.29_Dashboard Finally, hat OS are you running? Windows (10 or 11?), Mac, Linux? What browser are you using? Have you attempted to clear browser cache? Are you using vlans on your network? Can you ping the Polisy (and get a result) from the problem computer? Is the computer that's always on wired to the network and the one you're having issues with wireless? My hunch is the issue is network related. After that it's browser related.

@CPrince I've never seen them on the portal side and I run several with PG2 and ISY994. I've never tried on PG3 or IoP. I don't know why there would be anything showing on the portal. My assumption is that might go back to the days of PGC or the Occupancy NS that was setup through the ISY Portal. It sounds like PG3 isn't setup to push the node servers to IoP. You need to check your ISY settings in PG3 dashboard. When logged into PG3 check on "ISYs" on the menu then "Edit Current ISY" You should get this screen: Just confirm that it's pointing to the UUID of the IoP. More than likely it is, but you also need to set username and password for IoP. You should check the log of the PG3 (in screen shot above). There might be errors about it not being able to find the ISY or not able to log into the ISY. This means that PG3 is not communicating with IoP to push node servers to it. If you have confirmed that your IoP is the target for PG3 and no node servers show in IoP then I would suggest opening a support ticket and trouble shoot the issue further. Submit a Ticket: https://www.universal-devices.com/my-tickets

Just where are you looking for it to show up? Are you looking on admin console or on the ISY Portal web site? I think it's only going to show on an Admin Console instance. I've never tried to look for node servers on the ISY Portal route. In Admin Console look for the "Node Servers" in the menu.

Maybe check on the KASA forums? https://community.tp-link.com/us/smart-home/forum/73?keyword=strip I'm sure lots of your questions have been asked there. If not...you could ask their community and probably have wider sampling of answers and suggestions for your apparent need.

Great to hear! Before you get too far into it make sure that if you had any programs that were disabled prior to the update are disabled. That's another quirk that has been reported (and I remember having happen) from the 4.x to 5.x update. All my disabled programs became active and it wasn't until some strange actions did I realize this. Just something to doublecheck. Also, be sure you read here and on the wiki about UD Mobile. The wiki will walk you step-by-step to make sure you have things setup correctly for best access of the ISY both while home and while remote. You'll need to make sure you have an active ISY Portal subscription!

@ktierney662 If your test message will go out then sounds like the configuration for the notification is not correct. Do you have something in the "From" on the customization? As @MrBill suggested make sure you leave that blank. That way it will use what you've setup in the general email settings tab. If you've put anything in the "from" it will try to send using that address. That could be what's giving you bad SMTP write errors.

@RLC99888 The WIKI gives you help about what the light indicates: https://wiki.universal-devices.com/index.php?title=Main_Page#Front_Panel_LEDs/Lights Do you have/use z-wave with your current ISY? If not then you should ultimately upgrade all the way to 5.3.4. The current version of Firmware for the ISY994 and steps for install are found here: https://forum.universal-devices.com/topic/33287-534-update-for-isy994-july-30-2021 As @lilyoyo1 suggests you need to read the release information for the new firmware as they do require a lot of manual intervention. The final thing is to attempt to use the ISY Launcher method to connect to admin console once your device is behaving better. (Also some of this is in the wiki: https://wiki.universal-devices.com/index.php?title=Main_Page#ISY_Launcher_cannot_find_ISY) Using the ISY Launcher will always ensure you match firmware and user interface. If you're 4.9, but your UI is 4.7.3 you need to clear java, download a new ISY Launcher and run it to get the ISY Launcher icon on your desktop (by the way are you on Windows of macOS?). Before you get too much further...delete any old admin.jnlp or start.jnlp files you have ANYWHERE on your computer. This is the icon you're looking for: The ISY994 uses a MicroSD card so if you end up replacing that get an A1 rated MicroSD.

@ktierney662 Even though you've been lurking in the shadow let me welcome you to the forums! Great first post to get you going. I'm not a professional at looking at error logs and the one you posted is kind of short, but the main thing is it's failing on the SMTP setup. If you've got a new one after you updated to 5.3.4 as @MrBill suggested then post that, but look at the wiki for what the error codes are telling you... https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Errors_And_Error_Messages#SMTP_Errors In the original post you did attach the error log with system error -50001 -20 and -5. -20 is SMTP_UNSUPPORTED_AUTH_METHOD -5 is SMTP_CONNECT_FAILED If you are using the default I could see that happening with the 5.3.0 version you were running, but an update fixed the default server. If you're using a different email system to send out then you might have some "from" or other SMTP setting incorrect. Perhaps try the default server first then if messages go through you can setup the other option if you choose to use something else. Please also note that if you're using Gmail (or other free email services) that additional security might be needed. Be sure to read the information in the wiki about setting up other email accounts for sending notifications: https://wiki.universal-devices.com/index.php?title=ISY994:Configure_Mail_Server_Settings

I think it's is case-by-case issue. Some API seem to allow things to run locally, but in a lot of cases there might be a requirement for some system to communicate to a cloud function then the Polisy/Node Server communicate to same cloud for status change. But as @Javi points out the only main dependency on internet connectivity is on the initial setup. Apparently ELK is more local centric and would work just as the module has worked for the ISY. Ultimately though, the issue is notifications. If there wasn't an internet available method to send a notification with the ISY994+Elk Module you probably won't get a notification from IoP+Elk Node Server. Perhaps it would be something that developers could include (in the future) in the notes/readme/setup information as to if their node server works with and/or without internet reliance. No. I don't think it's fare to assume they're "less" reliable. But some are still early in the tooth where small changes/issues in the system can cause them to be temperamental. Many have commented that the Elk Node Server is more robust than the module ever was. Not using either, I can't comment on that, but do recall reading such comments.

@Panda88 just setup a forum for this now that it's in the production store. https://forum.universal-devices.com/forum/391-blink/