Geddy

Take a look at this recent post...doubt the ultimate issue will resolve your issue (was GFCI outlet), but perhaps the information from @Brian H might help.

@Illusion I'm not sure what you're doing (or not doing) at this point. But I might suggest you read the Polisy User Guide to help in some ways: https://wiki.universal-devices.com/index.php?title=Polisy:User_Guide Any node servers you install with PG2 can only be managed by PG2 and will show up as "unmanaged" in PG3. And vise-versa. PG2 can only point to one ISY. PG3 (I believe) can point to multiple ISY. So, are you working with a Polisy and trying to send node servers to an (external) ISY994? Or are you on a Polisy and trying to send node servers to ISY on Polisy? If you want to delete Node Servers you need to access the dashboard that installed them and uninstall and delete from there. PG2 is a two step process. PG3, I think, is a more simple solutions, but haven't gone through the process in a while to give you step-by-step. If your Polisy is "old" and you're waiting for a new drive then I wouldn't do anything with it now until you get the new drive. You're going to cause more problems than good at this point by randomly trying to flip between two entirely different systems.

@Illusion sounds like @bpwwer would need to step in to answer your questions. Or others that use this node server. Not sure what would cause it not to work through switches unless they changed subdomains somewhere along the route.

@CPrince "Find/Replace" is only found on the Programs tab when you right click on a program. You can search for devices from that screen.

@Illusion Have you installed any other PG3 node servers? Do they show up in the ISY? Sounds like you might not have the PG3 pointing to the ISY process correctly. Are you running ISY994 or ISY on Polisy? Make sure you've added the ISY to the PG3 dashboard - https://wiki.universal-devices.com/index.php?title=Polisy:User_Guide#ISYs If you do have other NS installed and appearing in ISY then perhaps PG3 needs to restart. Make sure you've also closed admin console and re-opened for new NS to be loaded to the admin console.

@Blackbird There have been lots of questions/comments on this subject through the years. Either searching the forums with the search bar at the top of the page might find the posts or using Google Site Search will find you several comments. What @kzboray states is the typical answer for the issue. Surge protectors or UPS devices tend to filter the traffic for larger system installs. While it "might" work sometimes it could be problematic. Best practice has always been to suggest plugging directly into the wall. I had a whole home surge protector installed (about the time I started installing Insteon), but also use point of service surge protection for high value equipment. However, the PLM is plugged directly to the wall outlet. Think of it like a Powerline Wi-Fi extender. Those have to be plugged directly into the outlet to propagate the network signal to other parts of the house.

It's more than likely Java related. How long have you been an ISY user? It's likely a very old cache still in the system somehow, but Java 6 would have been very old (2006~2011). But I searched for macOS and Java 6 and it seems that it's more recent (stupid macOS+java!). So it seems to be a Java related cache. You should remove the old cache. See if there's anything else in that directory. Also, reading some of these tips from Java might be helpful: https://www.java.com/en/download/help/java_mac.html You might also want to look at this for removing cache after Java was removed: https://www.java.com/en/download/help/deployment_cache.html But again, you appear to have multiple installs of Java. Maybe you need them for something. If not, I'd remove them and just use the standard release. If you need them...it might be advisable to setup another account on the Mac that doesn't have all those java versions installed and only use THAT account to run basic Java and access admin console. I guess this brings me back to your first post...are you having issues now? Your last statement really is a loaded statement... If it's working now...why wouldn't it work "down the road"? I mean, sure, macOS sucks for some people and makes things unbearable...but I think if it's working for you now, and you've got that much "junk" (java installs) working against you...what makes you think it wouldn't work in the future? Do you have that little faith in Apple that their macOS will go funky? I mean...it's Apple. It's just supposed to work, right? (Sorry...a tiny anti-macOS rant there...it's silly how users have such different experiences and abilities with macOS+java+ISY. Don't get me wrong...I am 100% in the iOS/iPadOS world, but macOS (issues) baffle my mind.)

Always the best. That sucks. Hope support will get back to you soon and it's an "easy" fix. What do you mean by this? How does the portal display readings of the thermostat? Do you mean through Web Access or something? I don't run any Insteon thermostats so don't know how you're seeing a reading on the ISY Portal site (my.isy.io). Strange to just "stop working", but Amazon/Echo is known to update stuff that might break connected items. Glad you can operate locally. Chalk another one up for local control!

Do you, by chance have any strange characters in your Polisy name? Any punctuation or characters that might make a file name invalid? Something seems to be triggering the backup to fail because of an invalid character. I wonder if might be in the Polisy name since it doesn't seem to even get to the node server level to backup. Just ran a backup in Chrome and this is in my log: 10/22/2022, 16:00:16 [pg3] info: Starting Backup Creation 10/22/2022, 16:00:16 [pg3] debug: Creating DB Backup... 10/22/2022, 16:00:16 [pg3] debug: Creating DB Backup: Done 10/22/2022, 16:00:16 [pg3] debug: Backing up node servers 10/22/2022, 16:00:16 [pg3] debug: All node servers added to backup -- finalizing 10/22/2022, 16:00:16 [pg3] debug: Removing Backup Archive from filesystem after download 10/22/2022, 16:00:16 [pg3] info: Backup Successful Please post back once you get help from support to tell us what resolved the issue.

@webminster what is the brand/model of thermostat? Log in on https://alexa.amazon.com/ click on "Smart Home" then "Devices" and confirm you see the Thermostat in that list. If it's controlled by a different Skill in Echo (depending on the brand you have) you might need to disable/enable the skill. If it's an Insteon thermostat then I'd remove it from the site/app, check the setup in ISY Portal, then run device discovery again.

@Lore Also - split your post out to get more attention. The thread you posted to originally had basically been resolved or was dead.

Not that I can help, as I don't use a mac, but what version macOS are you running currently? ISY Launcher works best with the default Java that you download directly from https://www.java.com/en/download/ (currently Version 8 Update 351). All your other Java installs could cause issues with ISY Launcher, especially using macOS. macOS users seem to have hit or miss problems with Java and ISY Launcher/Admin Console due to some safety settings in macOS. There are a few posts regarding macOS and getting into admin console that you should be able to find on the forums if you're having other issues. You should clear the java cache for your current 8.x install (be sure you select/check ALL THREE boxes in the "Delete Files and Applications" screen). You should delete any downloaded copies of admin.jnlp or start.jnlp and download a fresh copy from the UDI site. I'm not sure if there's actually anything in the cache directory you mention above, but if it's 6.0 you should probably delete anything in there also.

Do you have the Hue Hub with an IP reservation in your router? Take a look at this thread for setting up bridge/hub IP address: If this doesn’t help look at the log for the Hue node server and post any errors you might have.

It seems to come and go. Some (like @Techman above) say it works well, but just as many (or more) have come here to complain about not getting mission critical texts for hours, days, weeks later. There have been news reports of email to text messages taking months to deliver. (Not just ISY notifications) So, while is HAS worked well it’s a risky option that most would not suggest people use…especially alerts you might deem “mission critical”. Glad you got UD mobile alerts working, and yes…they are very quick! One thing people like about using Pushover is if you’re on iOS you can have different alerts and urgent delivery types that will come in through Focus times if necessary and setup that way, Just some different options for new ways to get alerts.

Also note that email to text/SMS is extremely unreliable and not suggested as a method to be used for quite some time. Many carriers are delaying such messages or bouncing them all together. If you're only relying on email to text for notifications you should consider alternate options. Many have been discussed through the forums so won't rehash what they are or how to set them up, but you should be able to find them easily. But both above suggestions of updating to 5.3.4 are correct for the initial steps to resolve sending email with Comcast. I know others that do it without issue.

@Chris McKean If you're running IoP to update: log into the IoP Admin Console click "Configuration tab" click "Upgrade Packages" wait for several beeps from the Polisy. (If you cannot hear beeps from your location wait a long time!) Please review these posts:

Can't help on the Habitat or Harmony side...don't use either of those. Did the light come in as a different icon in the past? I use Hue and it comes into ISY994 this way: The Hue bridge is as you describe as the domino, but the lights come in with bulbs, but groups of lights have the domino behind the light bulb. I wouldn't worry too much about that...it's just an icon. But, again I don't know if that matters to the system or not. As @MrBill says why start all over and put it into the ISY994? I'd just build out PG3 and move directly into ISY on Polisy if you're doing something from scratch. Why not just move the devices over to IoP before starting node servers? But, I haven't moved over to IoP either...mostly because I don't use many node servers and things work now...plus, it's all "family approved". Don't want to rock the boat.

At this point I'd say don't worry about Polisy. Take a look at the next gen eisy. But if you want to learn more about Polisy: https://www.universal-devices.com/product/polisy-pro/ https://wiki.universal-devices.com/index.php?title=Polisy:User_Guide Polisy and Polisy Pro are out of stock. So can't get them currently.

@Venicenerd Thanks for the hijack notice...I'm going to lock this since OP seems to have handled issue. If you'd like to ask your question in the Home Assistant area perhaps you'd get more assistance. https://forum.universal-devices.com/forum/128-home-assistant/

That's a bummer. I remember having that happen to me a loooong time ago. I don't remember what caused it. I didn't have to rebuild it though. Did you try hitting the "Refresh" button on the portal page you showed? Doing that re-syncs the device list from the ISY. Typically this should pull things back into the view, but you might also need to refresh the browser window. Having gone through that once, be sure you download the spoken (the download button next to the refresh). Not really anything you can do with that file, but it will at least give you what you had setup as of the time you downloaded the file. Additionally, you could go to https://alexa.amazon.com then clicked "Smart Home" -> Devices to see if things were indeed still stored in Alexa's memory. Ultimately, the question becomes - what did you do about an hour before this happened?

@eyost question has been asked a lot (especially since ~April 2022). Please review other areas of the forums for answers to your question.

Not using email notifications on IoP yet, but I remember this post from @Michel Kohanim suggesting to use 10,000 for timeout. I mean it's "only" 10 seconds. You're using 3 seconds. Does it make a huge difference? Sounds like a setup issue. I've been using gmail with notifications for ever and haven't had any problems. Must be they don't like emailing Canada. This has also been covered that it's a carrier issue. It's not handling the envelope for the email to text correctly and showing up as different random number. I tried this recently and it came through just fine from same accounts from UDI. I don't get why so many still use email to text...it's so outdated and unreliable. Use the UD Mobile notifications and network resources or a node server. All alerts are INSTANT or darn near! Also note that Google Voice no longer directly texts your phone, so @apostolakisl method above is forcing the email to text route. Google Voice stopped forwarding SMS messages earlier this year because many carriers were starting to block them more due to the amount of spam texts that go through email to text route. Google Voice will still accept text, but it only notifies you through their app. This is another reason not to rely on email to text notifications!

@dex Did you setup the IoP in PG3 correctly? It does seem that there's authentication issue talking to the IoP. In the PG3 web access look for "ISYs" and "Edit Current ISY" Make sure you followed the steps in the Polisy User Guide in the Wiki to set up correctly. I think once you get this setup correctly you'll be good to go. I know in the past I also had issue with sending a reboot to the IoP, but I think that's been corrected in a recent update. I don't usually try to do it that way so haven't tried recently. (And don't really like to randomly reboot the IoP so didn't want to test now.) I think the best way to reboot the IoP process is in Admin Console. Configuration Tab -> "Restart IoP"

No, I'm saying to go to 5.3.4 you either need a-wave 500 or no z-wave. So go to 5.3.4.

Can you PM me some of the links you were using? Were they from the Wiki or somewhere else? All current release information can be found in this area: https://forum.universal-devices.com/forum/339-current-release-announcements/ Specific release for 5.3.4 is here. (Make sure your system meets the standards for this version…specifically if you have a z-wave board.) The process of being able to update automatically ended with the release of 5.x because of so much effort to update.