Geddy

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/

Did you "ADD" the node server after installing? In PG2 it was a two step process. You go through the "Install" from the node server store, but then you have to ADD it from the PG2 interface under "NodeServers". Then you should select the slot to add it to and then you should configure then restart the node server.

@EricK If you do end up figuring out you have a failing PLM here is the repair service and cap kits others have used: https://www.ebay.com/sch/nilachidatasystems/m.html Most seem to have good reports following sending the devices in for service. @kclenden makes a good point about any traffic can alter the link count so perform it several times. Best to perform it when nobody is home or awake so you know that no switches or sensors will be triggered during the count. Also, a tip would be to open the Admin Console and Event Viewer in Level 3 and watch for traffic. I don't have any battery sensors to test to give you an idea of what you would/should see, but that should show what the ISY is receiving when devices are triggered.

It basically just checks the status of all devices and reports that to the ISY. From the ISY Cookbook: Not specific to the 3am default program that was on the ISY994. It's not in the ISY on Polisy by default, but many are adding it for personal reasons. My suggestion would be to disable the program as well. Certainly if it still happens. With the program disabled it isn't going to mess up anything and you would know then if something else was indeed triggering the device(s) at 3am (or 3 minutes past). Also check your program summary tab to see if any random programs ran around that time. You can click on "Last Run Time" or "Last Finish Time" to sort by when the programs run.

Before you do that try running the update process again from Admin Console (Photo credit to @MrBill) I had a similar situation where PG2 node servers were showing stopped in PG2 after the initial 3.1.6 was released. I think it was either something in a later release that fixed up some of that or the process didn't complete as expected on the initial run. Just also make sure there's nothing in PG3 also trying to write to slots 1 & 2 since PG2 is using those slots. Finally...aren't these also available in PG3, why not just use the PG3 version of these two?

I don't know this process. Probably best to check with UDI support through a support ticket. I'm not as inclined to have to monitor each step of the process like others do.

Glad you got it to work. Just know though that opening ports is usually considered a security issue. I'm sure it's probably low, but it's still worth mentioning and knowing. There are bots that just like to port search and spam any open ports they find. Especially well known or documented ports. Make sure any associated passwords (router and Rachio) are strong!

WOW! There's 97 node servers in the production store and "21" in the non-production store (didn't look to see if there's overlap), but you need more? Were there PG2 node servers for the specific ones you're asking about? You can run both PG2 and PG3. I'm just not sure if PG2 can push to IoP, but don't see why it can't. I just haven't moved over to that yet. Glad the transition went well. The Portal migration is covered in the Wiki.

@Dean It's not an "internal" port forward. It's actually suggesting that you port forward on your router/firewall to be able to receive external connection from the Rachio server. https://github.com/UniversalDevicesInc-PG3/udi-rachio-poly/blob/master/README.md Under the heading "Polyglot Custom Configuration Parameters" Also note in the install instructions this comment: My guess is that's so the DDNS would update if your external IP should ever change you won't have to fix the node server settings. I'm not a user of this node server. Just happened to see these parts in the readme files and wanted to point them out.

May I assume that you're using PG2 and running an update that way under System -> "Check for Polisy Updates"? Are you running PG3 yet and/or are you running ISY on Polisy (IoP)? If you have been running PG3 and IoP then you need to read this for how to update: https://forum.universal-devices.com/topic/37257-polisy-update-process-use-admin-console-upgrade-packages-button/ If your Polisy is not updated to have PG3/IoP on it then please open a support ticket to get information of how to update your system without these issues. Under PG3 there are no options to "update" the Polisy as it has been moved to IoP and using the ISY Admin Console to run the update process scripts. Good luck. To open a ticket follow one of these steps: Submit a Ticket: https://www.universal-devices.com/my-tickets Email: support@universal-devices.com

@CopyRon If having issues with Alexa, I often find it helpful to also use https://alexa.amazon.com/ and follow the links to Smart Home -> Devices. You can easily find what it's recognized and can delete from there then fix in portal and rediscover devices and update the list.

Sorry...I'm at a loss. Never had the 99i product so can't help specifics. I figure with the version of macOS that you're on that it's not letting you progress due to a certificate issue. Since the 99i is long discontinued doubtful there's much to do specifically for that.