Geddy

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.

Not entirely. But certainly update that, if possible. The underlying updates are complicated (at this point); that's why I suggested opening a support ticket to get the help and steps to properly update without causing too many issues (if possible).

@upstatemike WOW! If we had known you were trying to access "old school" PG2 we probably could have resolved it long ago. Everybody was helping you reach PG3 login. All the other information should have sent you into the PG3 log in. If you're not seeing that then it seems that the Polisy isn't up to date. Have you updated the Polisy to even be running PG3 and IoP? You probably need to file a ticket with UDI to get the process of updating the Polisy if it is an older device. You don't have to run anything in PG3/IoP, but should probably at least update it to have it available.

AH! The 3000 is for PG3. I've been trying to get you there. PG2 should just be straight up https://192.168.0.10

@upstatemike Are you physically near the Polisy? Make sure the lights on the front have just a solid light on the left. Are you able to ping the IP? I don't ever try to access Polisy through the ISY Launcher, but it can be done as you're attempting. I just use Firefox or Chrome with the IP address. Sometimes routers do not correctly route "Polisy" locally. And even though you say you have a reservation for that port have you confirmed by logging into the router that the Polisy is indeed at that IP? Showing in the "Attached Devices" or however your router shows it?

@tome I'm not sure of what the version numbers are for the different products, but as @MrBill mentioned there was a comment. not long ago, about different versions of these devices...here's a post from @Teken that describes their behavior: And just so it's linked for reference @Teken also posted a good thread about repairing Leak Sensors if that's ever needed. It's been archived so found it through a Google Site Search, but you should be able to see at this link:

If it's relaying through IFTTT there's probably a choke point through either the IFTTT servers or the Autoremote servers. Again, why not just have the network resources send to pushover? https://wiki.universal-devices.com/index.php?title=ISY-99i_Series_INSTEON:Networking:Mobile_Notification#Pushover I'm sure the setup hasn't changed all that much through the years. And if you're comfortable in NR setup then it should be "easy". Would seemingly remove a dependency on a 3rd party relay step.

If on a browser try: https://polisy:3000/ If that doesn't work then sub the IP address (https://192.168.0.10:3000) First time you will probably get this warning (or something similiar) Take a look at the Polisy User Guide in the Wiki for when you can't find the Polisy https://wiki.universal-devices.com/index.php?title=Polisy:User_Guide#Can't_Find_Polisy