Geddy

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

UnifiPresence is also on PG3, and also free. Documentation from the PG3: https://github.com/UniversalDevicesInc-PG3/udi-presenceUnifi-nodeserver/blob/main/README.md Although, based on this comment from @Michel Kohanim I'm not sure if the Node Server will work or if the developer is active any longer. What are you running node servers on currently? rpi or Polisy?

Just looked up Autoremote on the Google Play Store. Seems like it's using IFTTT and that will probably be the cause. Of course not knowing exactly what route it's taking if it's something being pushed to IFTTT you're at the mercy of the time it takes to hop through all the different services before reaching the phone. I know in the early days of ISY for me I tried Ring + IFTTT + ISY to make a light "flash" when the doorbell was rung. It never worked timely and often would flash the light so much later that it was quickly removed from my system. Not knowing how Tasker works either I'm not sure why you can't just use pushover to generate a pop-up on your phone. I know on the iOS side many use Pushover to be able to get timely notifications and even time sensitive alerts and different sounds to get their attention. I'm not quite sure why/how the other apps play into the Android system that you are attempting to get quicker notifications. I would expect that Pushover would do everything you need. Ultimately, you could also consider a node server to push to UD Mobile as I think one of the notification node servers has a method to attempt multiple sends in case there is an error on initial send. That's helpful in some cases. Good luck getting it sorted out. I doubt it's network resources that is your bottle neck though.

@BlackbirdNot sure I can help, but maybe you can help some. I'm confused by how you explain this. Can you confirm a few things? Are both method of notifications using Network Resources? How are you sending a notification to Pushover? (then to tasker? I guess an Android process) I'm an iOS user and all network resources that are pushing notifications (currently to UD Mobile) are instant. If you've got something sending to Autoremote (I assume another Android app) then perhaps there's something on their process slowing things down. Have you used UD Mobile Notifications to test this? Are any Node Servers involved in your process? Network Resources are only a single attempt process. If it errors no notification would be sent minutes later. So if you're getting the notification then it's being sent right away, but whatever is processing that alert is then taking time to deliver to you. Perhaps you can describe the process differently. Or other Android users might be able to help out.

@isy99user quick word of caution if you happen to look back in here... In your first post you say you're using Firmware Version: 3.1.3. Then in your "solution" you said you opened with 4.9 Admin Console. You could be creating issues if you are indeed using a later admin console to work on an old firmware. Just need to confirm you've got a very old ISY99i and what Firmware/User Interface you are using. In Admin Console go to Help -> About and make sure Firmware and UI match EXACTLY (to the date code also!) Typically for older firmware the best method would be to download from the device itself: http://10.168.24.245/admin.jnlp (using the IP address of your device...as you show above) The link you provided above actually downloads the admin.jnlp file for an ISY994i (http://isy.universal-devices.com/994i/admin.jnlp). That might cause you some issues if you go editing a lot in the Admin Console. Last word of caution is that ISY Launcher sometimes does not act right for MAC users (not to mention I'm not sure if it's designed to work on old equipment running old firmware). There have been some that it works just fine, and others that have a lot of issues. I forget all the steps, but there are some posts found around here suggesting to look in security settings and making changes, but have to be made close to when the errors pop up. I think @Bumbershoot, @Dub, and others have been helpful with the changes to make for MAC users. Either way! Good luck making your edits and accessing the device going forward. Glad you seemed to get it worked out.

@MrBill usually is accurate with his additional information on the link count info. It's crucial to understand what it is exactly that you're trying to accomplish with a "link count". And it's interesting...what's considered "low"? It's all relative to the size of your system. And as you mention it can change from moment to moment if there's traffic. Here are some of the instructions that @MrBill references in the wiki (maybe not entirely accurate, but is the first place seen to mention link count in troubleshooting capacity). @someguy Even though you might not have been using the PLM for long it probably isn't exactly new. Sure, that shouldn't explain your issues, but it's also a false assumption to make that simply because it hasn't been in use long that it shouldn't be failing. When you get home take a look at the sticker on the back of the PLM and make note of the date code. I'd doubt there were many PLM produced/sold in 2019-2021 timeframe. So I'd say most PLM in the market are probably from mid 2010-2019 timeframe. I think the answer here is sadly, no. If you have any friends/neighbors near you that would let you borrow their computer to try to access admin console on that for a temporary fix that might be the best thing to do. I don't think UD Mobile is yet able to perform link counts. I know @Javi has said the hope is that UD Mobile would be able to do everything Admin Console cane, but I don't think checking link counts is something it can do yet.

@tlightne did you follow the directions in the wiki?

@Bob Chase I agree with @lilyoyo1 it's probably better to fix the issue than try to go back to such a different system. Of course if you have a solid 4.9 backup you could try to roll back, but you run a risk of things still not working correctly after that process. Can you be more specific as to what your issues are and perhaps the forums can help work through the issues. Do you have a 300 Series Z-wave board (will have a blue light on the back of the ISY). Is that why you went to 5.0.16c? If you don't have the blue light then you have a 500 series board and can go up to 5.3.4. That might overcome a lot of your z-wave issues. The programs and scenes issue are probably the problem of going from 4.x to 5.x and needing to review all programs. Paying specific attention to any programs that had "adjust scene" in them. Also, I remember when I went from 4.9 to 5.x that all my "disabled" programs became enabled. So it was extra effort to go back through and disable the ones that needed to be set that way. Thankfully, they were in a folder for disabled programs so it was simple to find them. All 5.x updates stated that there might be significant work following the update. Seems that you've just got to work through it.