Geddy

As @Javi says they are there...just very faint with the colors you're viewing them with. It could be a mac system color option, but the colors are limited in the admin console and can be set using themes (File Menu -> Theme -> Theme Color) (from your PDF screenshot - tried to adjust colors to show the chevrons a little better) Interesting difference in the macOS world...while in Windows 10 folders have the + next to them. In Mac if you click or double click (or mac equivalent of a double click) does the folder open? It does in Windows so assume if you double click the folder it should expand or have similar operations in Mac. Looks like the "Incoming Water Rm" is the only folder that doesn't have anything in it so it doesn't have a chevron to expand the folder.

It must be a deep and dark secret. I mean there's nothing pointing out where it would be...right? If the unit isn't supporting z-wave then the module can be removed and the devices can be upgraded all the way to the current (most recent) version of 5.3.4. However, as @MrBill points out if you have the 300 series z-wave (and using it) then you can go as far as 5.0.16C. All are clearly marked in the current release area. Good luck! Happy hunting!

@EJones01 could have been an Amazon cloud outage. I had a couple of issues earlier of "not available" replies and then some slow event progressions (i.e. asked Alexa to turn a light on and took a few seconds for it to happen...longer than usual). It happens. Life with the cloud!

@Illusion MAC has been an anomaly for most of us that are windows based to try to help understand why the ISY Launcher does or doesn't work for different macOS users. It seems to be a hit and miss issue. Have you followed the steps in the Wiki? Found here - https://wiki.universal-devices.com/index.php?title=Main_Page#MAC_Users The launcher link should download "start.jnlp". Run that and it should add the ISY Launcher to the desktop. Then, when you activate the launcher it should open a window for ISY Finder (seen below). Then you can click on the ISY process you want to access and run admin console (as you say from the lan or cloud version). I would suggest the "cloud" option if you're connecting to an ISY994i because the lan method is using encryption and the ISY994i is slow to deliver the AC that way. The cloud is usually a little quicker. But, this still brings us back to the warning you say that launcher isn't compatible with your version of macOS. That's a new one (for me). PS: Split out from the post you tagged onto as your issue wasn't directly related (other than also being macOS). This way you might get other assistance with a new topic.

Ahhh...I had everything collapsed in the main tree and just saw the folder blue colors. I see what it is now. I guess the high contrast theme might be the best option for a white background against the pink/fuchsia. This drives me batty more than anything else. It seems so random.

@MKaye I'm not sure where you see pink. I just ran through all the themes and didn't see pink text anywhere. My "default" theme appears like this: (blue text w/ blue & white rows) You can change the theme colors from File -> Themes Perhaps you have something in the windows (or mac) settings changing how some of this shows up. I don't recall anybody posting screen shots that appeared to have pink text. There is red in the default theme, but it's fairly easy to read. Post what you're seeing. But, agree...sometimes small text can be difficult to read...even in the best color combination. I find I need to enlarge the text to 15 point to see on a 4k monitor. Sadly, even then the font size resets fairly often.

More than likely you don't yet have PG3 running. How old is your Polisy? Please see the Polisy User Guide in the UD Wiki for further information of getting PG3 installed/running. As @MrBill suggests if you're just using the IP address with no port (:3000) given then you're accessing the PG2 interface. If your Polisy is "older" or hasn't been updated you need to follow the steps in the Polisy User Guide to get get PG3 (if you're not version 13). You'll need to connect to the Polisy via SSH. Details are all in the wiki. PG2 display when accessing the Polisy via basic IP address: PG3 display when accessing the Polisy via ip_address:3000: Once you have PG3 installed you should see this when you run the ISY Launcher:

While I can see that you look at the possible noise issue being related to something new many reports lately have found that old devices fail and suddenly cause noise in the powerline system. So even though you say nothing's been added it doesn't have to be something new introduced to the system. Any old appliances, chargers, "wall-warts", or anything can go bad and cause the noise issue. Another thing to check is the program summary tab. Do those programs show up a different color (I believe it's yellow)? Do the programs show last run time or next scheduled runtime? There were some strange program issues in the upgrade from 4.x to 5.x that some programs need to be edited or simply just saved again for them to work right.

@remotesanitizer Thanks for the post. It's been fixed.

Tried setting this node server up and keep getting "discovery failed" errors. It seems to discover a device, but then throws out the discovery failed error. "Found device LTE-xxxx in location XXXXXX" udi_interface ERROR totalconnect-poly:discover: Discovery failed with error 'bool' object has no attribute 'lower' I have the Honeywell LYNX L5210 with just an LTE modem. It's not on my local network at all.

I use the same as @MrBill, Philips Warm Glow. But those are mostly just in lamps and fan kits for me. I don't currently have dimming bulbs in recessed light kits.

You shouldn't be doing anything in the Groups to send to both of you. That needs to be done in the program. Just set a condition to email both of you when triggered. SMTP should be just one account. (Many that use Gmail will set up a "spare" account for only sending ISY notifications. Just be sure you actively log in on that account now and then so Google doesn't disable it for being dormant.) Then "Groups" add one for your email and one for her email. (Should have 2 lines under "Groups") In the program you will have two "send notification" lines. Example program: Email-FD-OFF - If 'FD' Status is Off Then Send Notification to 'My Email' content 'FD Off' Send Notification to 'Wife's Email' content 'FD Off' Else - No Actions - (To add one, press 'Action')

Not that it would instantly fix this issue, but your UI/FW don't match. It's a small difference, but still a difference that could impact. Again, if you have the 300 series z-wave then 5.0.16C is the last update you should do. If you have the 500 series z-wave controller then upgrade to 5.3.4 and make sure your UI is updated as well. Currently I'd suggesting clearing the Java Cache and getting the ISY Launcher and making sure UI/FW match to whatever you have and try again. Since there were apparently a few versions of 5.0.16 it's possible your UI might have some issues working with the 5.0.16C firmware. Lastly, since this is fully z-wave system are all your devices within reasonable distance from others? I don't use z-wave, but always see the comments about having a good mesh of powered devices to relay the signal to further away devices. Since you say "all devices" have this issue then something else is going on.

No, that's certainly not the norm and shouldn't be the case "every time". It's possible something isn't setup correctly with your network and the ISY Finder isn't getting a reply from the ISY service when it is loaded. Are you on Windows or Mac OS? Typically the most work to "reset" things will be to clear java cache (be sure to select all three boxes in this process) and then download and run "start.jnlp (ISY Launcher) [See "Installing the Admin Console Icon on your desktop" in the Wiki]. You mentioned running ISY Launcher. Make sure you've downloaded this from Universal Devices' site (direct link). This will download "start.jnlp". If you are on Windows and you end up with a start (1).jnlp (or other number) then you have multiple copies of this file in your download folder. Remove old downloads and only use the most current. There shouldn't be a difference, but always make sure you are using the most current downloads for anything ISY related. [Since 2018 the ISY Launcher has been the recommended method to gain access to Admin Console. This process assures that User Interface (UI) and Firmware (FW) match. That's always the most important part of any further troubleshooting with the ISY system.] Once you have the start.jnlp downloaded run it once; it will add the ISY Launcher icon to your desktop (again, assuming Windows machine) It looks like this: When running the ISY Launcher you should now have a window labeled ISY Finder as seen in the UD Wiki documentation. Be sure to review the troubleshooting for "Can't find Polisy" in the wiki. If you've gone through those steps and the ISY or Polisy are still not seen then there are further issues and you should open a ticket with Universal Devices for them to help with more detailed assistance to insure this doesn't happen "every time". Submit a Ticket: https://www.universal-devices.com/my-tickets Email: support@universal-devices.com If this does happen again and you go the ticket route please post back here what the solution is so you can help others that might have this issue. It's all part of users helping users learn.

I only have 1 Kasa device currently (bulb). It's more cloud than z-wave or Insteon. From my experience if the phone isn't on wifi it's using cell data to talk to the Kasa cloud to figure out the device status. So I figure the device is always telling the Kasa cloud what its status is. Either way, I try to stay away from wi-fi based systems. Personal choice. 2nd thing...I've had countless issues with Kasa quality. More than anything Insteon based. So just another reason there's only one in use in my house. If I had the money to buy one hue bulb I'd get rid of the Kasa device completely, but it's currently working and I don't want to spend the money for a single hue bulb to replace a working device. If Kasa doesn't replace it should it fail then it will be replaced with a Hue bulb. Again, this is just personal experience with limited devices from Kasa. Quickly found this though: https://www.tp-link.com/us/support/faq/2707/ ("How to make Kasa smart devices controlled local only") My initial word of caution still holds true even if you're not going to "use" the cloud "feature". It relies on local wifi, and sometimes routers cannot handle the larger device count. So you run the risk of other devices holding the fate of your automation process in its hands.

@jkraus There have been limited debates in the past with which is better. It comes down to personal preference and personal ability to support which route you take. z-wave = talk to each other for local relay kaza = wifi connections Basically, any wifi connected devices can ultimately overpower your home router. Many consumer grade routers aren't designed to handle ip routing for a large number of devices. Sure, they can operate well at 10-20 devices, but some people are pushing 50+ or 100+ devices and if all that went to an underpowered router it will ultimately cause more issues. It also puts you back into a "cloud based" system. z-wave (as I understand it...I don't personally use any) is independent and communicates directly with the controller and then each powered device acts as a signal relay. So as long as you build out your network your coverage should be acceptable. If you don't have many devices and you have only limited devices at far ends of your house then you will need repeaters to build a stronger z-wave mesh communication network. Z-wave is local based and, thus, would operate without internet dependency. no, don't have any experience with that.

I case you're not aware there was a huge change in the IoT market recently when Insteon turned off their cloud servers. Many users scrambled to look for other options. Some rushed to buy the Polisy that were available. I'm sure it's just a run on stock and as soon as UD can get some more devices assembled they will be made available through the UD store. You could contact them directly via email at: sales@universal-devices.com What kind of system have you been running? The ISY994 and Polisy both require a PLM (an Insteon device). Those are very difficult to get at the moment, so if you don't already have one you will want to subscribe to the UD Product News & Announcements email list by making an account and selecting that email newsletter.

@jkraus It will certainly be a learning curve, but that's where the forums are here to help. Also consider UD Wiki, specifically the Polisy User Guide to help with some questions you might have along the way... https://wiki.universal-devices.com/index.php?title=Polisy:User_Guide And would be a good idea to review some of the information found in this thread (by @dbwarner5) for migrating efforts...

@kyderr I'd say that you're trying to get notified about an issue rather than fixing the issue. If the ISY is going "offline" then it is probably a network issue that you're having. Otherwise, ISY isn't known to just go into an "offline" state. I would suggest opening a support ticket to see if there is something in the logs as if there are indeed errors with the ISY causing problems. Otherwise, it's a network related issue and should be troubleshot with the router manufacturer or your ISP. What model device are you using, and what is your Firmware and User Interface (in Admin Console menu Help -> About). Create a ticket with support one of these ways: Submit a Ticket: https://www.universal-devices.com/my-tickets Email: support@universal-devices.com

If it's in a folder with conditions like that even running then "THEN" won't do anything. The whole folder is being limited by the folder conditions. Typically the root (My Programs) folder should NOT have any "Folder Conditions". Click on the time and you should have a option/button to remove and then "save changes" Note - none of the programs in "My Programs" probably work correctly because of the folder conditions. Will you confirm if they are working? (What happens if you right click and "Run Then" on those programs while the folder conditions are on the root folder?) Do you have folder conditions set for your irrigation folder? If you do you shouldn't have any conditions on the root folder so all programs will run when triggered. Also as info - you can copy/paste programs from admin console to the forums easily by right clicking on the program and selecting "Copy to Clipboard" (last option on pop up menu). Then pate the text into the forum message. That way you don't have to take screen shots or pictures of the monitor and try to paste into your posts. Same can be done for the event viewer...click the clipboard button and it will copy the text and can then be pasted into the message (and thus be searchable in the future).

@kyderr If/when you get support from UD and they get you sorted out please post back what resolved this issue to possibly help others that might have this problem down the road.

@Wes Westhaver make sure if they get you sorted out that you post back here what helped in case this issue comes up again. I too am not familiar with those errors.

@macjeff just checked...seems to be PG3 option now indeed - https://github.com/UniversalDevicesInc-PG3/holidays-google-poly/blob/master/README.md

@macjeff Not sure of holiday ones on PG3 (not currently able to access that store), but know there's one that worked on PG2 - https://github.com/firstone/holidays-google-poly I know @asbril uses it quite a bit.

@oper8 since we couldn't help you here you should open a support ticket with Universal Devices and ask them directly if this is an ISY issue, a Z-wave issue, or product developer issue. They would know best. I think the replies here have all pointed to the product and manufacturer of such product not sending the full information to the ISY. Submit a Ticket: https://www.universal-devices.com/my-tickets Email: support@universal-devices.com Either way...report back with what you find out! Would be good to get a real resolution to the question to possibly help others that might have the similar issue.