DennisC

Did you try power cycling Polisy? The way mine is working, is just the https://ipaddress in a browser brings up pg2 Polyglot. When port 3000 is added in browser it brings up pg3 Polyglot. Using https://ipaddress:8443 in ISY Launcher let's you click on Polisy to open admin console of IoP. If it doesn't work like that for you after a power reboot, open a ticket with UD.

If you are trying to access the admin console of ISY on Polisy, using your example from above, try: https://172.16.1.226:8443 in the ISY Launcher (but I think your missing a block of number(s) - should be https://xxx.xxx.x.xxx:8443). If it doesn't work the first time, power cycle the Polisy and give it a chance to come fully on line before trying again.

Hi Michel, I am casting a vote for getting WOL working on IoP. I use it twice a night to wake a Win10 machine from hibernation to insure certain processes run when they should. I had a problem last night with them not working and was forced to enable the WOL programs on the ISY994. Right now, I am fully on IoP except for this program. I never experienced an issue with authentication with the WIN 10 machine.

Hi Michel, I didn't extensively test to see how far it extended. However, I after I posted my initial problem I also had a problem with updating a Network Resource. I was able to both disable and enable a program.

I experienced something strange so I thought I would post it here to see if anyone else can reproduce it. I am also tagging @Michel Kohanimjust in case it is confirmed as a bug. Last weekend, I was at the remote location of my 2nd Polisy and decided to migrate ISY994 to ISY on Polisy, I wanted to attempt this one first since it was a smaller site. The migration went well and it has been running all week without issues, except I realized I wasn't getting a specific notification. Now that I am back at my main residence, I wanted to remote in and correct the typo I made it the notification address. I signed into the ISY Portal and obtained the admin console URL to allow me to directly remote in to the admin console via the ISY Launcher without opening a port. So far so good. I signed into the remote IoP and went to Configuration - Emails/Notifications - Settings/Groups page and proceeded to correct the typo in recipients address. I hit OK on the popup page after making the change and then clicked on Save. All looked good so far, however, I wanted to send the notification to make sure the change was successful and changed to the Programs tab. The page never loaded and I received the following error: [LIB_ERRORS-503] After logging out and back in, I found the change was not saved and had reverted back to the original text. I tried this several times with no success, receiving the same error when ever I changed pages. I then rebooted Polisy and tried again with the same result. I have tried to make this change several times over the last 3 days and have received the same error each time with multiply reboots in between. Being curious, I tried again this morning and that attempt failed. I remoted in to my offsite router and "temporarily" opened a port to IoP (the port is now closed). I made my change and tested it without issue. As I said at the beginning, I am not sure what this issue was but something was amiss, possibly a bug in(?), well not sure in specifically what.

I would agree that use of the UD Portal simplifies reaching your ISY or IoP by computer or with UD Mobile. The cost for two years is minimal and once you have the key you can enter it right in the ISY Launcher if you are using your computer away from home to access the admin console.

I'm fine with waiting, I know you are busy. Let me know if when you have something for me to test. BTW, I ported over my main system today and this didn't happen on this system.

What are you suggesting to delete - the Elk Nodeserver? I am not necessarily in a hurry, just want to know its being looked at. I would much prefer having the issue corrected so it can't happen again.

@Jimbo @bpwwer Any thoughts on how I can correct this?

I'm not sure if this will help, but every time I go from running admin console on my notebook and then go back to plugging my notebook into dual monitors I have to delete the files listed below. You might give it a try. Admin Console Minimized/Invisible and Cannot be Restored This is usually related Admin Console state files not being updated properly and especially in case of multi monitors. All you need to do is to find the following files in Java temp directory (on Windows: c:\Users\[Username]\AppData\Local\Temp) and delete them. Or, you can simply search the computer for udi_*.* file patterns: udi_tree.state udi_frame.state udi_pgm.state udi_finder.state udi_launcher.state

You can disable any program you are not ready to use if you port it over early.

Also, when you click on the name of most nodeservers in the store it takes you to GitHub and you can read info on the nodeserver. This one takes you a private website with no info on the nodeserver.

Try updating your version of PG3 by SSH.

Yes, for Tempest. Thank you.

I'm confused, I don't think I understand what you are saying. BATLVL is shown as a node in the Nodeserver on PG3. You can read the value there, but it's not in the admin console.

Log package sent and thank you!

On PG2 I have both the Weatherflow and Elk Nodeserver's stopped. I opened the ISY on Polisy admin console with no change. I closed the admin console and restarted Polyglot for PG3, opened admin console for ISY on Polisy with no change. Next, with Weatherflow and Elk Nodeservers on PG2 stopped, I rebooted Polisy and opened the admin console for ISY on Polisy. I am still showing "Sky Battery". I am out of things to try to correct this.

I just tried closing the admin console, opening PG2 and stopping the Elk Nodeserver for ISY. I restarted the admin console for ISY on Polisy and was still showing "Sky Battery". I closed the admin console, and with PG2 nodeserver still shutdown, restarted PG3 Elk Nodeserver. I followed this by opening the admin console for ISY on Polisy and it still shows "Sky Battery".

I built the Elk Nodeserver out yesterday and started the cutting over from ISY to ISY on Polisy today. While both admin consoles might have been opened together at various times, there were times when only ISY on Polisy was opened after a reboot of Polisy. As of right now, I am still showing "Sky Battery". I just started and stopped PG3 Elk Nodeserver and it updated to v3.1.2. I restarted the ISY on Polisy admin console and here is the result:

Yes, several times. I installed the nodeserver yesterday.

Bob, I am still experiencing the following missing items from the Weatherflow Nodeserver: Sensor Status Battery reading (however, battery reading shows up in UD Mobile RSSI Value Thanks

Jim, Elk NS 3.1.1 on ISY on Polisy shows some strange verbiage on the Elk Controller page. It shows Nodeserver Online - Connected and Sky Battery - False?

No, I have never owned this Nodeserver. Earlier today, I purchased both Weatherflow and Elk Nodeservers and neither of them showed a trial offer. Here is a screenshot from the Notification Nodeserver as an example.

Thanks for confirming it works fine. I don't get the Trial License under purchase license, only Perpetual License option shows for me.

Starting to add Nodeservers to ISY on Polisy and wanted to checkout TimeData. Clicking the name on the latest PG3 Nodeserver Store results in the following error: {"error":"Authentication Error"} Searching the UD repository on Github doesn't show TimeData either. I wanted to read a little about configuration and capabilities before purchasing. Is there a working link for information? Can you also confirm if TimeData is fully functional for PG3? Thanks.