Geddy

@Prana electric Congrats on getting things and good luck setting it up! I guess you didn't read through the information provided on your prior post that pretty much gave you everything you'd need to set up and running. Good luck as you learn!

Have you followed the steps through the Wiki for setting up with the portal access? https://wiki.universal-devices.com/index.php?title=UD_Mobile#Existing_Portal_Users The URL should start with "https://my.isy.io....". It should be auto generated after you log in following the steps in the Wiki. Welcome to the forums. Post back if you're still having issues. Perhaps @Javi (the app developer) might have other steps to attempt.

It saves the file with the addresses you have showing (should save a file with a "*.state" looking file name). If you have both the local and the remote address then there will be two lines. The next time you are remote your finder will probably come up empty. Just hit "load" and find that file and then you'll have the local and remote addresses and be on your way. As I said...this happens. It's not something I've ever tried to figure out how/why it happens. If you'd like to know more then I suggest opening a support ticket and asking them specifically what is happening for your situation. It's not such a big deal for me so I have my processes and keep on trucking. Exactly! That's what I've been saying. The ISY Launcher icon opens up the ISY Finder window. If you're not local then from my experience is that sometimes the Finder just wipes out whatever you've had in the past. I don't know all the details, and haven't cared to dig too deep into it. You appear to want to dig deeper. So I suggest opening a support ticket. So basically, the steps I suggest you use: When local the finder will add the local address. (Uses local credentials to login) Add remote ISY Portal URL (uses ISY Portal credentials to login) Click "Save" (save the file "ISY-Finder.(date+time).state" somewhere you can access quickly - if you save things to the desktop then fine. I prefer keeping the desktop clear so have it in a folder on root of "00-quick" so it's a typically at the top of a view.) Next time you're remote it will probably appear empty on launch. Click "Load" and find/open the file you saved above Use remote URL & ISY Portal credentials to login to IoP while remote. Is it a pain? No (IMO) Does it take < 30 second to fix? Yep! Submit a Ticket: https://www.universal-devices.com/my-tickets Email: support@universal-devices.com PS: If you get a ticket going and @Michel Kohanim tells you the super secret trick of not having the entry clear out be sure to share it with us. It's something I've faced since 4.x and all the time on 5.x. Sometimes it works...sometimes it doesn't. I haven't worried enough about it to really dig too deep.

I feel your pain. Happens to me and I'm not even on a laptop trying to access from both places. I think it's just the nature of remote access. I've never really tried to figure out the rhyme or reason to it, but I just figure that it's still trying to locate the ISY locally while you're remote. When it doesn't find it then it just wipes out what you've got. It's simple to just hit "save", then save the file locally (in an easy to access area), then hit load when it comes up empty and you're ready to rock and roll. No need to go out to the ISY Portal and copy/paste again.

@Papa C Are you only asking for how to access IoP while remote? If you are trying this while remote then no. This will not work. You will need to use the Admin Console that is available in the ISY Portal -> Select Tool -> Information -> ISY Information screen. One note about this...I've had issues with the finder keeping the URL stored (from remote computers). Sometimes it will be there and other times it's just gone. So I always save the finder addresses (as long as the computer you're working on is yours) then you can load that file and not have to go through the ISY Portal to get (copy/paste) the URL again. If you're on a laptop that you are using to access AC locally and remotely (at different times) then it will be two different entries. Perhaps you could use the one ISY Portal login for both and it might not get confused, but I've never actually tried that. You can add both and save that file then load it and both should appear if you need to load the finder file.

@tazman seems TeslaEV has moved to the production store so opened up the forums and moved your message in there. Hope somebody can help you out.

@simplextech would you see this as a different place than the current "Product Requests" forum? I mean, it is "way down" in the Site Comments area of the forums, but I'd see that as the best place to post specific requests. I know others have been posting in the PG2 node server section asking if developers are going to be releasing a PG3 version if there isn't already one. But I'm thinking the existing "Product Request" forum would be where I'd suggest posting NS requests.

There's your issue. You've got to do like @Techman and @MrBill now suggest and setup a scene. And, just so we're clear...are you migrating from an Insteon Hub to the ISY with PLM? Have you performed a factory reset on all the devices before adding to the ISY? It's possible your hub stored links in the switches that the ISY won't know about and you've made a cascading issue of failures when moving to the ISY. It's suggested to perform factory resets to the devices to clear out previous programming. At least for easy to reach devices. There is a process when adding to the ISY to clear prior links, but it's not always as final as a device factory reset.

@auger66 log into the ISY Portal and click on "My Profile" on the top right. The window comes up and should have your preferred ISY showing. Does that UUID match what you're expecting? Then, just to confirm on the main ISY Portal page it should show that same UUID with a green "light" next to it indicating the status is online. If these don't match then you've somehow mismatched something in your account. Did you migrate from an ISY994 to ISY on Polisy (IoP)? Or are you using an ISY994i with Polisy/PG3 Node Servers?

@LMcGrath I'd delay the upgrade to Firmware 5.3.4 until you get your current issues worked out. You're at 4.9 now and that is the last version in the 4.x branch. Sure, 5.x will help with other things, but your problems are fairly basic and you need to be sure you have them working right in your system as you expect them to before you bite off more than you can chew trying to upgrade to 5.3.4. As @lilyoyo1 says if the switch was working in the past then it's probably a bad bulb. It happens. Just trying to link it to the ISY isn't going to change a switch that works/worked manually. Then go back and read the post by @MrBill that shows you how to program the way you described in your original post. Don't worry about the True/False status of the programs. That isn't important. The best way to test if the program works (if before sunset) is to right click the program and select "Run Then". If the device turns on then it works. Right click the program and select "Run Else", and the device should turn off. Lastly...be sure that your User Interface (UI) matches your Firmware. When you're in the admin console check the match by going to Help (menu) -> About. You should see Firmware version and UI versions match EXACTLY. If they don't then please clear your Java Cache and download the ISY Launcher by following these steps in the wiki. Since you say you've now updated to 4.9 (probably through the manually upgrade process in 4.x) you need to be sure you've updated the UI to match 4.9). The 4.9 ISY Launcher will be a slightly different window than what's showing in the Wiki currently. That is geared toward 5.x and specifically ISY on Polisy. Just clearing Java and downloading the ISY Launcher (start.jnlp) are the key steps you need to focus on to match FW/UI.

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.