PG3 on Polisy

[bpwwer]

5 hours ago, macjeff said:

I noticed yesterday after the upgrades all of my node servers showed the modification date of 3/24 at the same time.  I thought it was due to the upgrades

But today I noticed they all changed to 3/25 and all the same time

So I did a REFRESH store and the time changes.  So this is showing the CURRENT refresh time NOT the modification time.

Plus the time there is 4 hours ahead of my time.   log times in PG3 are correct so its just the modification time inside PG3 store that is showing both the current time (After refresh) and the wrong time zone.

 

** Showing the correct time of modification, and only on those modified, is important because thats how I know one of my node servers was updated!!!

Yes, I noticed this too and it'a a bug (sort of).  Every 8 hours it refreshes the contents of the store and updates it's internal cache of that info.  So what is being reported is the last time that cache was refreshed, not the last time it was modified in the store.  So yes, that needs to be fixed.

 

[macjeff]

3.0.54 seems to fix all the issues including wireless tags

[macjeff]

On 3/25/2022 at 1:14 PM, bpwwer said:

Yes, I noticed this too and it'a a bug (sort of).  Every 8 hours it refreshes the contents of the store and updates it's internal cache of that info.  So what is being reported is the last time that cache was refreshed, not the last time it was modified in the store.  So yes, that needs to be fixed.

 

This seems fixed also in 3.0.54.  Only issue left for me is the Harmony Hub 3.07 wont upgrade.  Jimbo confirmed issue and reported to you.

[Jimbo.Automates]

This seems fixed also in 3.0.54.  Only issue left for me is the Harmony Hub 3.07 wont upgrade.  Jimbo confirmed issue and reported to you.

As I said, HarmonyHub does upgrade, it's just an issue that it doesn't actually see the new version and tries to upgrade on each restart, and UI shows old version.

Sent from my Pixel 6 Pro using Tapatalk

[macjeff]

On 3/27/2022 at 12:11 PM, JimboAutomates said:

As I said, HarmonyHub does upgrade, it's just an issue that it doesn't actually see the new version and tries to upgrade on each restart, and UI shows old version.

Sent from my Pixel 6 Pro using Tapatalk
 

Even with 3.08 it still said 3.06.   This is a VERY easy Node server to setup.  No API keys or anything so I went ahead and deleted and added back.  Now it says 3.08.

[DaveStLou]

On 4/1/2022 at 10:13 AM, macjeff said:

... so I went ahead and deleted and added back.  Now it says 3.08.

Same thing I did to get from 3.06 to 3.08. All is well.

[apostolakisl]

I just installed and ran PG3 on polisy.  It appears to have connected to my ISY, it says "connected" and it lists the uuid of my ISY in the settings.  However, on the dashboard, it lists no nodes, unmanaged or otherwise.  When I try to add a node , it asks me what slot and the drop down makes any number I want available.  Should it not see that I already have nodes (from PG3 and IoGuy) occupying many of those slots?

[bpwwer]

Depends. By default, PG3 will try to connect to an IoP ISY running on the Polisy.  

If you both that and a standalone 994 ISY, you'll have to add the configuration for the 994 under the ISY menu.

It is also possible that it found the ISY, but doesn't have permissions yet to actually log into it and get the existing node information.  In this case, you'll need to edit the ISY entry and add the ISY username/password.

[apostolakisl]

2 minutes ago, bpwwer said:

Depends. By default, PG3 will try to connect to an IoP ISY running on the Polisy.  

If you both that and a standalone 994 ISY, you'll have to add the configuration for the 994 under the ISY menu.

It is also possible that it found the ISY, but doesn't have permissions yet to actually log into it and get the existing node information.  In this case, you'll need to edit the ISY entry and add the ISY username/password.

I did put the isy info, ip, username, password, and it says "connected", since I don't know what else it would connect to, I assume this means ISY.  It also lists ISY as 5.3.3 which is correct along with the correct UUID, neither of which were entered by me but rather discovered.

[apostolakisl]

Never mind.  I deleted it and re-added and now it shows the nodes.

[wrj0]

Never mind.  I deleted it and re-added and now it shows the nodes.

@apostolakisl I have a similar problem with installation of a NS on PG3, that I can't get to show up on my ISY (PG2 node servers are running fine). May I ask what you deleted and reinstalled? (the node server, the ISY entry on PG3?, something else?)

[apostolakisl]

47 minutes ago, wrj0 said:

@apostolakisl I have a similar problem with installation of a NS on PG3, that I can't get to show up on my ISY (PG2 node servers are running fine). May I ask what you deleted and reinstalled? (the node server, the ISY entry on PG3?, something else?)

Deleted ISY from PG3 and re-added.  This was my very first installation of PG3, so I had no nodes installed to screw up by doing that.

[wrj0]

@apostolakisl Thanks. My first NS install on PG3 as well. I’ll try deleting/re-installing the ISY from PG3 as you suggested, once the local thunderstorms have subsided.

[asbril]

I just did a 'Check for Polisy Updates', noticed 100 available, then did 'Update Polisy', and now I can no longer access PG3. I tried 'Reboot Polisy' but no success.   I can access Isy on Polisy and control its devices, but the PG3 node servers are not working on either  ISY or on ISY on Polisy.

Any suggestion ?

Edited April 7, 2022 by asbril

[Javi]

I've noticed during an update yesterday the update duration was close 10 minutes, so if rebooted before the updates complete ssh may be needed.  

[asbril]

4 minutes ago, Javi said:

I've noticed during an update yesterday the update duration was close 10 minutes, so if rebooted before the updates complete ssh may be needed.  

what SSH command should is use ?

[Javi]

I'm not at my machine now, but it should be the same documented upgrade checks and install.

[asbril]

5 minutes ago, Javi said:

I'm not at my machine now, but it should be the same documented upgrade checks and install.

Thanks. Yes I used the "usual"  SSH update Sudo commands and PG3 is back !!!!!!!

My mistake may indeed have been to do a Reboot Polisy before the updates had been completed. When there are 100 updates, it is better to wait quite a bit before a reboot.

Edited April 7, 2022 by asbril

[brians]

I just updated mine from ssh and was 121 updates.

Process took about 5 min. then I reboot.

Only 4 or so look specific to Polisy (ie. pg3 3.0.56) and rest are regular FreeBSD updates.

pg3 3.0.56 has more noticeable blue showing store production. What is difference between production and non production store (is latter for testing?)

 

 

 

Edited April 8, 2022 by brians

[wrj0]

@apostolakisl Thanks. My first NS install on PG3 as well. I’ll try deleting/re-installing the ISY from PG3 as you suggested, once the local thunderstorms have subsided.

Once the storms passed, I spent a couple of hours looking at the configs of ISY, Polisy, and PG3, and restarting them a few times, trying to get my first Notification NS to show up in PG3.
Finally realized that after purchasing the NS (trial version), I still had to go to back to the store and select Install. After doing that the NS showed up fine in PG3 Dashboard and populates properly in my ISY994. Got too lost in the configuration details to see what was likely clearly obvious to others. To borrow an expression from another knucklehead: Doh!

[bpwwer]

16 hours ago, brians said:

pg3 3.0.56 has more noticeable blue showing store production. What is difference between production and non production store (is latter for testing?)

Node servers in the "Production" store have been vetted and approved.

Node servers in the "Beta/Non-Production" store don't have that requirement.  The primary purpose is a place for developers to release pre-release or bug fix versions for testing by a limited audience before moving them to the Production store.  In general, you should only install a node server from this store if the developer recommends you do so.

[jlamb]

I have pg3 up and running but it is not showing my isy portal (unmanaged) node server.  The portal node server does show up under my pg2 dashboard and in my isy node server configuration (slot1).  Any suggestions to get this node server to show up under pg3?

[bpwwer]

The portal node server entry isn't managed by PG3 so PG3 has nothing to do with it.

[MrBill]

15 hours ago, jlamb said:

I have pg3 up and running but it is not showing my isy portal (unmanaged) node server.  The portal node server does show up under my pg2 dashboard and in my isy node server configuration (slot1).  Any suggestions to get this node server to show up under pg3?

Did you just complete migration? IS PG3 pointing to IoP or back to your 994.   is this the Occupancy or Occupancy V2 node server that you're referring to as the portal node server or something else?  I susupect that you're using one of the Occupancy node servers and it's still pointed to a 994, I don't think the migration tool migrates that from reading the list of checkboxes on the migration tool.    If this is the case you just need to re-add the occupancy node server to your new IoP installation.

14 hours ago, bpwwer said:

The portal node server entry isn't managed by PG3 so PG3 has nothing to do with it.

It still should show the slot occupied and "unmanaged".  I believe @jlamb is trying to say that the slot is not showing unmanaged.   I suspect his problem tho is detailed above... he's using one of the Occupancy node servers and it wasn't migrated by the portal migration tool.

[jlamb]

18 minutes ago, MrBill said:

Did you just complete migration? IS PG3 pointing to IoP or back to your 994.   is this the Occupancy or Occupancy V2 node server that you're referring to as the portal node server or something else?  I susupect that you're using one of the Occupancy node servers and it's still pointed to a 994, I don't think the migration tool migrates that from reading the list of checkboxes on the migration tool.    If this is the case you just need to re-add the occupancy node server to your new IoP installation.

It still should show the slot occupied and "unmanaged".  I believe @jlamb is trying to say that the slot is not showing unmanaged.   I suspect his problem tho is detailed above... he's using one of the Occupancy node servers and it wasn't migrated by the portal migration tool.

I have had things working with the unamanaged slot showing up in PG3 previously.  It now seems I have some config files that are corrupted or causing issues.  I've tried uninstalling PG3, PG2, etc. to no avail.  I've factory reset Polisy.  The root of the issue is around a Hue hub NS in PG2.    The Hue hub was factory reset and when trying to add it back, it keeps pulling up old username of hub and wont add nodes like normal.  It's like it has settings saved in an old config file on Polisy.  I've been trying to find a way to completely delete all config files from PG2, PG3, general Polisy, etc.  so I can start over.  I have been unable to do this.  At this point I am wanted to just completely delete all polisy settings and start over.  When I did a facory reset, it still had some of my saved settings that showed back up.  I'm at a loss.

Jasson