Geddy

@Michaelv I've been watching from the sidelines just to see how this progressed. Thankfully I don't have any battery devices so I couldn't help along the way, but really looks like the next steps might be to scrap the old programs you had and write new ones. Apparently something in the old programs (or notifications) broke and you're not sure how to troubleshoot them to fix what you have. @MrBill recently made a great post about this same issue for another user (look here). That really outlines some great ways to get the heartbeat to send an alert. I think what's really strange is your notifications and somehow your existing programs are triggering something that is triggering an odd notification. At least you comment that it appears to be wrong. Yet when you did the test with @MrBill things worked as expected. I know you've got it really detailed, and I've seen people post that they just copy programs (and notifications) that somebody else wrote (and posted elsewhere) many years ago. By copying other setups you might not really know what they've done. (Even though..."it used to work".) So I think the easiest thing would be to start from scratch with new programs and new notifications. Because something isn't right with what you've been using. Why not just start anew and have that working from this point forward?

@TVC15 Glad you were able to fix the issue. This issue is a known part of upgrading from 4.x to 5.x and part of why "Step 6" is written into the upgrade process in the release notes for 5.3.4 (probably appears in all 5.x update release notes). Even in the "NOTES" section at the top of the release post references the manual intervention needed when going from 4.x to 5.x. While you said you're all set, it is still important if you had any "Adjust Scene" programs that you check each of those individually (and update if/as needed).

Thank you for the information. This has been discussed at length in the Megathread in the Insteon sub-forum area. Please keep any such conversion in the below topic.

@RJ K did your Hue Hub change IP addresses recently? That's what sparked most of this thread. Either a router change or not using DHCP reservation with the Hue Hub after you got it online. If so then you need to add the following for Custom Parameter: Key = bridges Value = ["#.#.#.#"] (MUST have the square bracket AND the quotes) As soon as I added that (in PG2) it found the hub right away. If you're still having issues then look at the lot (put it in debug mode) and restart the node server. Allow it some time to start up and then review the log. See if it is giving any idea as to the IP it's looking at for the bridge. When I attempted to add PG3 version (after having the PG2 at the old IP) it still looked for the hub at the old IP address. I do not think there is a way to remove the current configuration. Just a custom parameter to overwrite it. I think I attempted to remove the custom parameter and it still looked at the old IP.

Excellent! Glad it worked out! Yes, Kaspersky can be a doozy sometimes. I quit using their products about 15 years ago for similar reasons (long before I was using ISY). I'm sure there's probably a way to approve the app to run in Kaspersky, but couldn't help with that without some Google searches so I'll let you check on that. My only other suggestion would be to remove it from your system and get something like ESET anti-virus. As long as you're not specifically going to sketchy places Windows 10 (and I think Win11) do a fairly good job of blocking attacks and scanning for viruses.

That's an interesting difference. I just downloaded start.jnlp from my link above and moved it to the desktop. My icon appears like this: If you right click on your icon and select "open with" what program is the default for you? I show the following for mine: The icon you're looking for is the ISY Launcher. That's only added to the desktop once the start.jnlp successfully runs. It appears that's still the issue you're facing. I've not seen an issue of having to specifically have the 64 or 32 bit versions of Java. Either seem to run the .jnlp just fine. I just tested on a computer that I've never used to access admin console. I removed Java as outlined above (man, my son is going to hate me if his Minecraft won't load right after this). I then went to java.com and downloaded what was offered up as default when I clicked on "download java". Installed it. Downloaded ISY Launcher. And it ran without issue. I don't have any Antivirus, Firewall (other than Windows Firewall) or VPN running on that computer. So I suspect even though Kaspersky is "disabled" and your VPN (being off) are still blocking the necessary traffic for Java to communicate with the resources needed to properly add the ISY Launcher to the desktop.

This was going to be my next question. If Virus and Firewalls are turned off. If your VPN is off are you still able to access websites? This error appears to be a Java issue that cannot reach the external source to complete setup of the ISY Launcher icon. The "unable to load resource" is commonly found on google searches to mean the computer cannot reach the web (due to DNS issues). If you are able to access the web with your VPN turned off and you've gone through all the steps above then I would open a support ticket as you've attempted the usual troubleshooting steps to get on the right path again. Perhaps they have other tricks to try. Either way, please update once resolved so that it might help others in the future. Submit a Ticket: https://www.universal-devices.com/my-tickets Email: support@universal-devices.com As you said this is a generic web interface/dashboard of types and isn't what you're looking for. Since the inception of the ISY Launcher process (introduced in 2018) there's no need to have a browser open to try to access admin console. @ccclapp, I understand your point. It appears the reason that thread was closed was because you never came back to update the status and others were tagging onto it with same, but different issues. So to avoid the thread issues it was closed. If you're still having issues please send me a PM and I will re-open that thread so you can update in there. Otherwise, let's try to help @cdave1252 with their issues. It's certainly a small minority of comments about not being able to get the system to work as expected. So I would have to say for a very large majority of users the system works as designed.

Moved from prior location as was new issue. Was attached to this post: https://forum.universal-devices.com/topic/37031-after-so-many-years-still-cant-connect-to-isy/ @cdave1252 where did you get that version of Java? The current general Java version is 8 update 341 (https://www.java.com/en/download/) - you mentioned you have 351 (maybe just a typo). Seems like something is not correct with the Java install. And then you're not using the ISY Launcher to correctly get the icon on the desktop. I would suggest completely removing Java (yes, again). This time be sure to remove it using Windows control panel -> programs and features -> uninstall. If you run other versions of Java then you need to download the app to remove old versions (found here: https://www.java.com/en/download/help/remove_olderversions.html). After you remove Java do a search on your computer for any *.jnlp files. REMOVE all old copies of admin.jnlp and/or start.jnlp that you might have (either in the download directory or in temporary locations). We've seen users attempt to use old files they thought worked for the current Firmware and it causes issues. Best to download a fresh copy every time you need to add the ISY Launcher icon back. Once you've removed all Java versions and deleted any old UDI files reboot the computer. Download Java (linked above). Download a fresh version of ISY Launcher Run start.jnlp (ISY Launcher file downloaded) Accept Java warnings Accept Windows firewall warnings You should now have an ISY Launcher icon on your desktop that looks like this: If your ISY does not appear in the ISY Finder window once opened then you need to confirm the ISY is online. Log into your router and confirm the ISY is connected to the same network your PC is in. Make note of the IP address seen on the router. Manually add the IP address: http://your.isy.ip/desc From there you should have what @MrBill posted above.

@alambertus checking in...it's been almost a week. Were you able to get this fixed? And if so what allowed you to regain access to the IoP? If still having issues I would suggest opening a ticket with support to try to get things back to normal. Submit a Ticket: https://www.universal-devices.com/my-tickets Email: support@universal-devices.com

@ahwman I think the best way to do this is to add a user and make them admin then you can remove the prior user account once you've logged in using the new email. This will keep all prior configuration in tact. After removing old address make sure the portal is still online and registered (admin console -> configuration tab -> portals). While logged in on my.isy.io click on "Users" tab at the top: Then click on "Add User": Then fill out the new user information and make sure to check "Account admin"

But that's fool proof....right? @Athlon I've always wanted to use some of that stuff.

Same here...also after some discussions with @MrBill and reading other posts here and there. Interesting to see the overall abilities that HomeAssistant supports. The latest for "Works With..." seem to be promising moving forward. I too have kept the ISY/Polisy as the backbone and plan to. I haven't gone too far down the rabbit hole of actually getting things to work with HA, but soon enough. I have it working, but getting things the way I want them before opening up the options for the wife and kid are where I'm still at. Might have to look at those custom buttons @Athlon mentions. While I like what I'm currently using some flare would be appreciated for fun.

Glad it worked out! That summary page does come in handy from time to time. Time to disable the program or tape a sign "do not use" to the button!

Not where it's coming from..at least not outside the ISY. If you see traffic in it then it is traffic within the ISY, but it won't tell you if it's being triggered by something outside the ISY (at least I don't think so...) I just tested by turning a light on/off via HomeAssistant and directly in the admin console. They are identical events thrown. So, there's no way to tell where it came from, but that something was sending traffic to/through the ISY. And you're 100% certain you don't have any programs in the ISY that could trigger such light status? Check the summary tab of the program area and see if any programs have run recently (or around the 9:00 time.). You can SORT the last run time by clicking on the column header. Only other thought would be to disconnect devices just before 9pm and see if it does it. Might take a couple of days if you disconnect one-by-one to figure out what's doing it.

@PBatavia01 you haven't been back since posting this message earlier this month. Do you still need assistance? The wiki information you're looking for is in the Universal Devices Wiki for Polisy: User Guide. Found here: https://wiki.universal-devices.com/index.php?title=Polisy:User_Guide Please note, that there are some late updates that can mess up the system. So currently I would suggest if you still need to update to PG3 that you open a support ticket with Universal Devices to get the specific commands to get IoP (ISY on Polisy) installed, running, and updated so that the admin console of IoP can then update the parts of PG3 in order not to corrupt other items. Ticket can be started either of these ways: Submit a Ticket: https://www.universal-devices.com/my-tickets Email: support@universal-devices.com

Great to hear! Glad it ended up being something "simple". Not sure if you're still needing help on the Elk stuff or not, but you'd be better off starting a new post in the Elk sub-forum to get help specific to those issues.

You should upgrade the ISY994 to 5.3.4 firmware. Not saying that will fix all your problems, but I would think some changes between 5.1 and 5.3.4 probably finetuned some z-wave settings since that was a big part of the 5.x upgrade. Especially since 5.3 was the first one to be an "official build" for full z-wave certification. 5.3.4 is further minor updates within the system. But you mention they're old devices and probably a generic z-wave device that might not actually meet some certification aspects that could be causing problems as ISY advanced into z-wave certification.

@telljcl Thanks for the reply and images. Have you clicked on "start" or "restart' on all the node servers? It's strange for them to all being showing disconnected. It's as thought they've never started up. Especially since all show 0 (zero) nodes. The configuration for the nodes needs to take place in the PG3 screens (mostly...at least I've found that's easier and more accurate for some I used previously. I don't have any devices that would use these node servers so I wouldn't be a good one to try to buy/install/setup, but I did just run the Kasa NS on PG2 and it started right away. I'm not seeing any setup that needs to be done for Kasa. So I assume in PG3 it would be the same. Have you read the Kasa README.md information found in the link from the node store? Read here: https://github.com/UniversalDevicesInc-PG3/udi-poly-kasa/blob/master/README.md Once it's starting it should find devices on your network. Since it doesn't require any log-in information. (At least not what I see on PG2 version). But in your RainMachine screen shot above click on "Configuration". That's where you should enter (probably the information you entered from the ISY side). I've always just done the configuration from the Polyglot side (either in PG2 or PG3). That then is what is fed to the ISY (in this case IoP). Then be sure to click on Start or if you find it's running click on "restart". Also, click the "LOG" button and see what is being logged. If there's a setting to change to debug set that and then "restart" the node server. Give it a few minutes then "Download Log" (this will download just that Node Server log). Here's what you want to look for: Once you've downloaded the log then read though there and see if there are errors trying to connect to the IoP or other obvious errors. I wouldn't post the log here (not yet anyway) as I don't think the developer is very active at this moment (I think they're busy moving) so you're going to be relying on others that might use this Node Server to help you from there. Perhaps this gets you going. Post back if you get some of them working or still having issues. Hopefully others with this node can help out some of the configuration settings to help you out.

@telljcl Have you added your IoP to the PG3 settings? Please read this section of the wiki: https://wiki.universal-devices.com/index.php?title=Polisy:User_Guide#ISYs As @Bumbershoot points out most of the configuration will be as you apparently have attempted, but you need to be sure the ISY on Polisy is properly added in PG3 setup. Otherwise, the information for the node server (or any node server for that fact) won't know where to send the information. Perhaps sharing some screen shots of what you see might help further, but sounds like you're on the right track.

It’s not hard to find…it’s in every ISY994 Firmware release announcement. for 5.3.4: https://forum.universal-devices.com/topic/33287-534-update-for-isy994-july-30-2021/ You’d download the one that says “if you do NOT have a PLM”. This way the ISY wouldn’t boot into safe mode if/when the PLM isn’t connected when it boots up. The help -> about section will look different too, but when you use the ISY Launcher to open the admin console FW/UI will still match. So once you do that make sure they match…looking at the part before the version numbers (if I remember correctly).

@GQuack I believe you're referencing this thread - Always a good idea to actually include the link if you're bringing up an old topic that's been closed. Perhaps @lilyoyo1 can explain the process and help you further.

Not sure about the Yolink process, but some others use Alexa routines (and I think Google Home) to make announcements. So if you already have one of those home (monitoring) speakers you could try those first. https://wiki.universal-devices.com/index.php?title=ISY_Portal_Amazon_Echo_Integration_V3#ISY_Can_Talk_To_You.21_.28Alexa_Routines.29 I just recall others mentioning it on the forums. Might try a search (or Google Site search) for the references to that.

@isyrocks! the easier/better way to share programs on the forums is to right click on the program, select the bottom option ("copy to clipboard") then paste the program to your message/post here. This captures all the important parts, and it makes it searchable and editable for anybody helping you. Result of paste: 00-Query All - KEEP - [ID 0000][Parent 0001] If Time is 3:00:10AM Then Set 'MyISY' Query Else - No Actions - (To add one, press 'Action') Also, is there any reason you're on 5.3.3 on the ISY994? The latest version is 5.3.4 and a simple update/upgrade from what you're running. Very small fixes were made, but still, suggested to go ahead and get up to the latest version since you're almost there already...and you said you have z-wave 500 so it's okay to update. I don't think it would help your issue, but wanted to ask and suggest the update. Your initial "away" program seemed long. If you had it doing a lot of things without the waits there was risk of missed signals going out. Sometimes it might be better to break processes down into smaller chunk programs and have one program trigger additional programs (with waits between those triggers). And you scrambled a large chunk of what you're trying to turn off. It might be something that you have a program simple as: If: armed away then: Run "THEN" of away program 1, wait 10+ seconds, run "THEN" of away program 2, wait 10+ seconds, run "THEN" of away program 3 The "Away Program #" would not have an "IF" value and would be disabled. Thus the only time they would run was when called on by the "armed away" program since they would specifically process the "THEN" of those programs.

@silverton38 Like others...up for me, and the downforeveryoneorjustme site shows it's up: https://downforeveryoneorjustme.com/elkproducts.com?proto=https&www=1

While that works as long as you keep your current setup. It's sometimes unavoidable when you change brands of routers. Unless you always make a mental note to change your DHCP back to what you had previously. I don't usually worry about setting DHCP reservations, but it seems to be becoming more expected that people do for situations like this. What's interesting is that another automation process found the Hue Bridge without issue. So somehow the node server is putting the IP it found the bridge at into its configuration for when it gets loaded again and ALWAYS looks at that location. Thankfully it can be changed with the custom configuration setting, but that requires a different way of indicating the IP address.