mbking

@bpwwer, I had a notice for the Ambient Weather NS to update to 2.0.7. I'm on 2.0.6. After restarting the NS, the version remains 2.0.6(at least according to the NS info). I've tried this several times with the same results. The PG3 log for that event is attached. I'm running PG3 3.1.15. Can't say if this is limited to this NS. Ambient Weather Update(25Nov22).rtf

@Michel Kohanim, since using IoX Launcher, I too could not launch the Admin Console via the Cloud. But just a few minutes ago, I tried it again and it worked. Maybe it was the website issues. Java Console did not show any errors. Mark

I tried adding this URL, but nothing was added. Now, that URL is how my Polisy is setup in Launcher, so maybe nothing was added because it's already there. Admin Console Cloud doesn't work for me, Admin Console LAN does. Note: I deleted and reinstalled using Start.jnlp Mark

@asbril, I have the same issue with Launcher; I can access Polisy through the LAN connection but selecting Cloud does nothing. There was a change to launcher recently; it is now called IoX Launcher. I suppose this is in preparation for the launch of eisy. There's been no official word on IoX Launcher though. There may be more back end work required before Cloud works again. Also, if I save my launcher configuration and look at it with a text editor, it's junk, no configuration data. The Reboot ISY menu selection was removed in the recent PG3 3.1.14 update. Looks like the Admin Console is the preferred location to reboot ISY.

I'm curious the see what others who updated PG3 are seeing with IoX Launcher. (PG3 updated to 3.1.14 normally) I'm on macOS Ventura 13.0. Launching IoX Launcher, my Polisy is detected automatically. I can load the Admin Console using Admin Console (LAN), but selecting Admin Console (Cloud) does nothing. This used to work. I'm also able to launch PG3 via IoX Launcher. I selected Save to save my configuration, but when I look at the file with a text editor, I see this (was expecting to see Polisy info):

@macjeff, how did you reinstall IoXLauncher. I cleared my Java cache and now I don't have the app. Not sure where it is. Mark

@bpwwer, Do you know anything about IoX Launcher? I was going to run the PG3 update and noticed my dock icon for ISY Launcher no longer worked. I have a desktop icon labeled IoX Launcher now instead of ISY Launcher. I assumed this is a more generic version of launcher since it launches more than ISY now, but I can't find anything in the forum about it. Also, while I can see my Polisy, I can only launch it with the Lan version and not the Cloud version. Just curious if you know anything about it.

@bpwwer, I ran update packages to update to PG3 3.1.14, but I'm still showing 3.1.13 and the Reboot ISY menu item is still there. Doesn't look like it updated. It appears to be running OK and I got all the normal lights and beeps I expected from Polisy. I could run Update Packages again, but thought I'd wait to see what you think before doing that.

Version 3.1.12 installed without issue. Thanks for all the work you put into this, @bpwwer.

@Jimbo.Automates, I personally use ELK for security and fire alarm only. I will generally prefer a direct connect to other devices, so I'm unlikely to use thermostats connected directly to ELK.

@bpwwer, I rebooted Polisy, but had to also restart each node server. After the reboot, all but the RainMachine NS showed Disconnected. The RainMachine NS showed Connected, but wasn't running. After restarting all of the NS's, operation appears normal. Not sure why each had to be restarted, but the reboot and restart did the trick. Thanks for your help!

@glarsen, I noticed recently I wasn't getting any updates in UD Mobile for RainMachine, so I restarted the node server. It appeared to restart and then immediately stopped. Attached is the log package showing the errors. I'm running IoP 5.4.4 and the PG3 3.1.11. RainMachine_10-17-2022_80819_PM.zip

@bpwwer, Has UDI resolved the update issues you're referring to here? I'm ready to update to the latest version of PG3, but was waiting for some indication is was good to go.

I was able to update and reconnect to my node servers on PG3 and PG2(still have one waiting of the PG3 version) using the commands Michel provided, but I notice that when I log into PG2 and check for Polisy updates, I don't get the reply I usually get. Any one else seeing this?

Thanks @bpwwer and @slimypizza, My network is an Apple Extreme setup which is about the be replaced with a Unifi system. This may improve name resolution. Bob, thanks for dissecting the log file for the root cause. A battery backup for Polisy is definitely on the list of To Do's.

@bpwwer, This has happened a few times before and happened again tonight. I quick power off/power on from a lightning strike caused Polisy to reboot. Everything came back up except for the Ambient Weather node server. A restart gets it working again, but thought you'd want to know that manual intervention is needed. I'm attaching the log package. The Polisy reboot occurs around 17:50. AmbientWeather_6-27-2022_93008_PM.zip

Confirmed. They are working. Appreciate it, @Javi!

@Javi, I added a network resource for UD Mobile notifications and was able to get a test notification on my iPhone, but there is no sound with the notification. My notification settings for UD Mobile show Sound is on. Not sure what I'm missing. Notifications are a welcome addition. Thanks to you and the team!

@Michel Kohanim, I upgraded to IoP 5.4.3 and found it was necessary to reboot Polisy to get IoP to communicate with my Insteon devices. I initially did an Update, Upgrade, and Restart of ISY. After waiting several minutes(maybe 3 or 4), I looked at UD Mobile and did not have any statuses on the Insteon devices. Went into the Admin Console and had Failed Communication error messages for all Insteon devices. That's when I did a sudo shutdown -r now to reboot Polisy and everything is working fine now. It's possible I didn't wait long enough before checking. It seems IoP takes the longest to reboot. Not sure if this is an issue, but wanted others to know that a restart of IoP may not get them working again. Thought on this one?

@Michel Kohanim, Thanks for the information on PG2. I wasn't aware of some of the resource consumption issues. I only have one more "must-have" node server that I need ported over to PG3 and the developer has indicated it's on their list. Once that happens, i'll be ready to shut down PG2. I'm assuming the PG3 interface will get all the settings and maintenance functions for Polisy in the near future. This gives me an idea of what's coming. Thanks!

IoP and PG3 are now in Beta (I think this is true) and we have a Polisy Version 2 interface for Polisy and PG2 related functions and a PG3 interface for PG3. Will these two interfaces be merged into one with access to PG2, PG3, and Polisy? I still have one node server on PG2 because it is not yet available on PG3, but will move it over as soon as it's available. Other than this node server, all of my production devices and node servers are on IoP and PG3. Just curious what the next big step will be.

@JimboAutomates, Sending messages to keypads now. Thanks for getting this figured out and working. I'm still showing version 3.1.4 even after the update to 3.2.0. I restarted the node server to do the update. Looks like a bug in PG3 3.0.55 @bpwwer.

I’ve upgraded to IoP 5.4.2 and I’m excited to see the ELK node server get the ability to send messages to the keypads. Thanks for adding the feature @jimboautomates. Sent from my iPhone using Tapatalk

bpwwer just pushed PG3 3.0.52 and ELK is now working.

@JimboAutomates, bpwwer pushed PG3 3.0.51 which fixed Hue Emulator and some other node servers, but ELK still fails. My RainMachine node server gives the same errors. I passed this on to bpwwer.