DennisC

If you went up to v5.3.3, you should upgrade all the way to the latest v5.3.4. You will find the link to the correct Launcher on the upgrade page. Best to download it from there.

Use the ISY Launcher and if it doesn't find your Polisy, add the following: https://ip_address:8080

Do you have the check box for zwave checked on the configuration page?

Right click on the program name and select "copy to clipboard", then past the program here. Also go to About page and see what version of firmware and UI you are running.

A couple of suggestions for you to try: 1. Reboot both the computer and Polisy. Then make sure to clear the browser cache and try again. 2. Try using incognito in Chrome and see if that works.

Jim, FYI, the link for Readme under the Elk Nodeservers announcement points to the Harmony Nodeservers instead of the Elk.

Not to second guess Michel, but you might look at the info in this post: You would need to use Putty to ssh in to Polisy and try the commands in post 3.

I'm not clear from your reply, have you tried a new (known working) power supply? There have been some reports of power supplies failing.

I agree with the previous poster that you should upgrade to the latest version,5.3.4. You should also try rebooting your ISY and see if that clears up your saving issue. Don't understand why you are having issues controlling from sunset to sunrise for on/off control. I have numerous programs written that way. Are you sure you have checked the box for sunrise that says next day? Do a search for ISY Cookbook, there are examples in there on writing programs. Good luck.

Once again, UD's customer service and attitude to its customers is outstanding! After emailing Michel per his instructions, he restated that 2 years portal access is included and corrected the issue. Thank you UD for continuing your outstanding commitment and ideals.

Why use two programs? On and off is easily accomplished with one program. Use the time option from - to. Don't forget to use the next day option for sunrise.

I don't disagree, I have subscriptions for my 2 production ISY's. I am just confused by the original statement that indicate things would work after the trial expired.

When I connect from my desktop I do. Access via UD Mobile, which uses the Portal to connect gave me the first error that it couldn't connect. I then went in to the Portal to check access.

My 30 day free trial for ISY Portal expired today and I lost access to ISY on Polisy. I thought from @Michel Kohanimexplanation above, we would not loose access to ISY on Polisy once the free trail was over? Did I do something wrong?

@Michel Kohanim with some PG2 nodeservers not yet available on PG3, what is the plan if a nodeservers is missing from PG3 when the backup is migrated over from PG2?

Bob, What about upgrading PG3 from a previous version? Will there be an announcement somewhere within PG3 that an upgrade is available? Would you use sudo pkg update PG3?

Have you checked the error log?

Bob, Out of curiosity, if PG3 is able to manage more than 1 ISY, would one of them be able to be at a remote location and connect using ddns address?

After getting PG3 installed on Polisy and connecting it to ISY on Polisy, I installed a Nodeserver. Apparently, the Admin Console on Polisy is missing the ability to scroll down the page. If the Nodeserver is displaying more information than will fit in the window, you can not see the remaining items without making the Admin Console window larger.

I upgraded to v5.2.0 by using the automatic upgrade from within ISY on Polisy. After waiting and trying the Launcher, my Polisy was not found automatically and when adding the IP manually, using the correct port. I ssh in and ran sudo pkg update && sudo pkg upgrade followed by sudo service isy restart. I waited and tried the launcher and it found Polisy, but my UUID was all 0. I tried a reboot which had no impact. I tried sudo service isy restart again and this time my Polisy (and ISY) were found. Even though the version was listed as 5.2.0, when I logged in by selecting LAN, I received the following error: I tried both a reboot and sudo service isy restart, but still get the above message and after clicking ok, ISY on Polisy closes. I tried sudo service isy restart one more time and now I get two instances of Polisy in the Launcher window. Only one will allow me to log in through LAN, both will allow me to login by CLOUD. I tried deleting the entry that is not completely working, but Delete is greyed out. After going in via LAN on the working entry a few times, I find both entries are now working, but I still can not delete one.

Looks like you're also having dns issues. Have you verified your dns settings?

Have you checked the error log to see if there are any errors shown?

Are you saying that adding nodeservers to ISY on Polisy is not possible while the ISY 994 is still in production and using nodeservers?

Yes, I can access ISY on Polisy, that is not the issue. I am trying to add ISY on Polisy to Polyglot to associate nodeservers with ISY on Polisy. Michel's post above indicated to use the ISY address in a browser. That isn't working for me. As you indicated above, I tried using the Launcher (cleared Java cache), but still can not associate Polyglot for the new instance of ISY on Polisy. There is still something I am not understanding.

If I use the IP address of Polisy, I connect to Polyglot nodeserver associated with my ISY 994, not ISY on Polisy. I see no way to associate the two.