Geddy

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.

@MWareman you might be better off getting help through a support ticket. This way @Michel Kohanim and/or @bpwwer can look into the logs a little better and perhaps have a better idea of what happened and how to fix. What update process did you attempt?

@CopyRon It might be since you already have accounts for the new devices that it might be a little more tricky. Just make sure you follow the steps in the wiki for migrating from ISY994 to Polisy - https://wiki.universal-devices.com/index.php?title=Polisy:User_Guide#Migrating_from_994_to_Polisy Step 10 has specific link to migrating the Portal over - https://wiki.universal-devices.com/index.php?title=ISY_Portal_Migrate_configurations_to_a_new_ISY And I was about to add the exact same image that @MrBill just added. So you should be able to migrate without issue by doing that. Granted I haven't attempted it, but many have and seemed to have been simple. EDIT: One word of caution/question - have you been keeping the Polisy up to date so far? Or is it still in the box? If still in the box when you first get it online check the OS version. Log in with SSH and run this command: sudo uname -a If you're below 13 you should open a ticket with support to see the current suggested route to update. There's problems with original way to update to get PG3 and IoP updated and installed. If you've been updating as time went along, but not running anything in it yet then you should be good to go directly with an ISY Migration.

@tlightne your issue didn't seem to be same as where you posted it so split it out for more visibility for your issue. Will you please confirm your ISY Version (Firmware and UI) and Z-Wave controller?

If you're trying to post what the program is for you need to right click the program then COPY to Clipboard then past to the forum. I think you did "export to clipboard" to get the "xml" in the post above. Copy to Clipboard is the very last option when you right click the program. If you're physically flipping the switch and the ISY still doesn't see the device then there's communication issue. I've never gone through the replace PLM process so kind of at a loss for why it seems to work when you created a new scene, but now they programs don't work. But, now if you're physically triggering a switch and the ISY does not see the event then the PLM links are not there. You might need to factory reset the devices that it doesn't see.

"This is usually related Admin Console state files not being updated properly and especially in case of multi monitors." Does this apply? If not, sometimes Java just gets "stupid" and doesn't handle resizing the window right or just changing things up. Nothing really triggered it (IMO). But I've seen this as the option to fixing. When you said loading from admin.jnlp opened a different finder and nothing was selectable it triggered it might be a .state file issue. Glad it helped and worked!

@DJonas how old is the ISY994? Have you ever had power supply issues? What's the light pattern on the front of the ISY? And if you're willing to power cycle it again watch the light pattern when it starts up. https://wiki.universal-devices.com/index.php?title=Main_Page#Front_Panel_LEDs/Lights Since dashboard loads it seems to be getting to the device on the network. Leads me to think it's computer related or else power related and the draw on power to load the admin console might be causing the issue. Before trying anything else post a screenshot of what you see when you load admin.jnlp admin console. You say above it shows ISY information, but nothing is selectable. Feel free to blur out personal info. Also, be sure you check Firmware and UI in the Help -> About menu (is that even selectable? Next steps I would suggest are: Clear Java Cache (yes, again). Be sure you select all three boxes in the process Refer to this wiki article to remove .state files - https://wiki.universal-devices.com/index.php?title=Main_Page#Admin_Console_Minimized/Invisible_and_Cannot_be_Restored (***NEW STEP you might not have done before!***) Delete ALL start.jnlp or admin.jnlp files downloaded ANYWHERE on your computer download a fresh start.jnlp version from UDI - https://isy.universal-devices.com/start.jnlp Run start.jnlp Should put fresh ISY Launcher icon on desktop Run Launcher - Try Admin Console (Cloud) Make sure when you run ISY Launcher that it opens the "ISY Finder" window that looks similar to this: Report back with what happens.

@DJonas What version of Java are you running? ISY Launcher typically works best with the basic Java downloaded from java.com. Current version is: Version 8 Update 341 If you're not on that version or have a different version installed then please use the java removal tool to remove all java installs on the computer. Download the 64bit Java 8 update 341 directly from java.com.

@Banichi glad you got it sorted out quickly. For reference this is in the wiki for the ISY994 for the lights on the front: https://wiki.universal-devices.com/index.php?title=Main_Page#Front_Panel_LEDs/Lights Though doesn't describe what you experienced. It might have been that it was in safe mode. You might have seen that once you got into the admin console and noticed that it wasn't seeing the PLM. Also, let your client know to always plug the PLM in first then the ISY (about 30-60 seconds later).

@oskrypuch your post was hidden and off topic where you put it, so split it out as a new question for hopeful more attention. I'm sure this is all something that will be revealed as it gets closer to actual release/availability.

@SSchmidt True, you didn't ask that, but you basically got your answer then, and as @lilyoyo1 says there's several posts (certainly more over the last 9 months - so it seems). There's also Google (or other preferred search option) https://www.allhomerobotics.com/comparing-insteon-vs-z-wave-protocol-best/ https://zwaveguide.com/z-wave-vs-insteon/ (I find this one quite "funny" as it certainly has the z-wave lean as to which would be better and why). I think here you'll find a large majority prefer the reliability and function of Insteon. Those that like/love z-wave like it for different reasons and it works for them. Sadly, what works for others might not work for you or might not be what you want/need best for your situation. So you have to make that judgement yourself of what you want to achieve. Good luck! Enjoy the new house.

@SSchmidt So I guess you didn't get this answered in part of your original post about this?

@dpierre something doesn't look right there. You're able to log into the Admin Console to change the admin password, but you can't see the UI version? How are you accessing the admin console? Are you using the ISY Launcher method? This looks like you're running something that isn't setup to communicate to IoP. Maybe it's an old admin.jnlp file from an old ISY994. You need to get the ISY launcher (start.jnlp). DELETE/REMOVE any old admin.jnlp files you have in your computer....ANYWHERE! Clear Java Cache (be sure to select all 3 boxes in this process) Delete any admin.jnlp or start.jnlp files you have downloaded in the past download NEW start.jnlp Run to put "ISY Launcher" icon on desktop Follow steps in WIKI to access ISY on Polisy. Something's not looking right in the screenshot above. If you go through the above steps and still doesn't load into IoP correctly then certainly consider a new support ticket. Good luck. Report back how it goes and if you end up working with support let us know the steps to fix the issue to help others in the future.

When you're in admin console and try to change the password do you get this warning? Can you confirm your Firmware and UI match? I just tested on mine and it worked each attempt. Might want to reopen the ticket or start a new support ticket just to be sure things are installed, updated, and running as expected.

Open a support ticket with UDI. Submit a Ticket: https://www.universal-devices.com/my-tickets Email: support@universal-devices.com Should be able to help at this point.

Have you tried lower case "admin"? Or did you change your SSH admin password to something else?

@atmarosi I'd try to create a new program (identical to existing programs) and see if a new program works. Also, I assume that you're process of testing the program that you just "run then" and nothing worked. I don't use "fast on" so have you tried to just use "on", or is there a reason that it's a "fast on" trigger? Do other programs work and it's just the ones that turn scenes on/off? Do the programs that aren't working happen to be in a folder? Is there a chance there are folder settings that aren't allowing those programs to run? If they're in a folder move them to the root program level and see if they work. If they do then you have something in folder settings that aren't allowing programs to run.

No worries. It's simple issue. I actually was going more for the option of doing the restore for device specific menu when I read @lilyoyo1's post again and looked at the screen shot and saw it right away. Did that process resolve your issues? Hopefully you're running right again.

Look up one line! You can also right click on any device and "restore device" if you don't want to do them all.