Jump to content

Minor PG3 issue with ISY5.3


sjenkins

Recommended Posts

Minor issue for feedback.

Updated my ISY on Polisy & PG3.

the PG3 is showing the new PG3 but old ISY:

Frontend Version: 3.0.36
ISY Version: 5.2.0

Also one other item.  I changed the IP address which my Polisy is on my network, all is working fine and really is moved except the Polyglot Settings in PG3 show the current IP as the old IP and cannot be changed.

I have PG2 concurrently running but it does not have a field for this in settings.

again minor cleanup issues, Happy new year!

 

Link to comment

The ISY version issue is a know issue.  Restarting everything will probably correct that as I think PG3 only checks that on startup. 

Changing the Polisy's IP address is not a trivial process.  When a  node server is installed on the ISY, it includes the IP address of the node server (PG3/Polisy) so that it can send status/commands to the node server.   PG3 will also compare the value the ISY has with its own IP to see if it "owns" the node server.  

If you change the IP on the Polisy without changing the IP for each node server installed on the ISY, PG3 will assume it no longer owns those node servers and will delete them from it's database.  Once deleted from the database, the only way to restore would be from a backup or by re-installing the node server after manually removing it from the ISY.

Because of this, PG3 isn't designed adapt to it's IP address changing.  It checks the IP address when it is first time it is run and saves that IP address in its database.  The assumption is is that if you're changing the IP address you are starting over with a new install.

Basically, changing the IP address isn't really supported on PG3 and while it may appear to be working fine now, things may fail later that will be hard to debug.

Link to comment

@bpwwer,

appreciate the response,

even after a number of reboots it still shows the old ISY but no worries for now.

on the PG3, I am glad I have only played with it for now, I will start my nodes from scratch.

was able to get my PG2 over from my 994 to the poly after restoring my 994-ISY to the polyISY.

have lost my portal connection to the polyISY with the restore ; can I still do the ISYportal migration?  that is my next step here.

I don't have but four z-wave's so that is no issue really.

onward and upward!

 

Link to comment

@sjenkins Is it the PG3 ip address that's showing wrong or the ISY address?  Those are two different things in two different menus on PG3.

The PG3 IP address is set when PG3 is run for the very first time and there is no mechanism to change it later. The only way is to uninstall PG3 and remove the database so that when it is re-installed it starts with the new/correct IP address.

The ISY IP address is configurable using the Edit ISY menu option.

Completely unrelated, but we used to go boating on Lake Fenton when I was a kid.  I grew up in Grand Blanc. Small world sometimes.

Link to comment

@bpwwerits the PG3 as its associated with the port address of 3000.

If that is how it works I may just uninstall and reinstall PG3; as I said before I have only played with it so far.  I will move what I can to it from PG2 as I get things stable first.  I was able to change the ISY address to localhost ; it is working well.

on the unrelated note, we are very lucky to be on lake Fenton, I didn't grow up here but was able to buy at the last downturn.  It has meant a really wonderful place for my kids to spend their time growing up.  Not a bad place for mum & dad to float around on as well.  I have lived in about eight countries, I agree the world is very small.  The more people realize that and that we are all the same in the end means a better planet.  Hope your life travels from Grand Blanc have treated you well.

 

Link to comment

I don't think just uninstalling and re-installing will solve it as I don't think the uninstall removes the database, but I could be wrong. I haven't tried uninstalling.  You can also just remove/move the existing database and restart PG3 if you're comfortable with the Polisy command line.

The database is in /var/polyglot/pg3/pg3.db  so either remove or move that file and then run

sudo services pg3 restart

that should re-create the database and populate it with the new IP address.

Link to comment

@bpwwerI deleted the database as you mentioned.  Then removed and installed PG3.  IP address still was the old POLISY one.  Looked at the logs but cannot see where it grabs the IP for the database.

I also tried stopping, then removing the whole /var/polyglot/pg3 directory, removed, installed PG3.  Same result.

So its getting the IP from somewhere else.

btw: :  I am not so bought in so far that I could not do a complete Polisy reset to factory.  I have backups of my PG2 and have only just restored my 994ISY to my PolisyISY ; both are backed up.

thoughts?

Link to comment

That's weird.  

When PG3 starts and the database doesn't exist, it looks at, in order:

  • an environment variable PG3IP (which shouldn't be set)
  • the system's current IP address
  • if those are both blank, it uses the local address 127.0.0.1 

Can you post (or pm me) a screen shot of where you're seeing the old IP address and what you get when you run 'ifconfig' on the Polisy?

Link to comment
  • 2 weeks later...

@bpwwer,

This could be a big deal in the future.  I'm planning to replace my aging network equipment soon and had been planning to organize my IP's a little differently than what I have now.  That was going to mean changing the IP for Polisy.  I've used DHCP reservations to reserve IP's on my current network without setting a static IP on my devices and will do the same on the new network.  It sounds like I need to set a static address on Polisy, but I've avoided that because of issues I remember people having early on getting that to work.  Is that the best approach to avoid the problem you're describing here?  Also, I use an ethernet connection and I don't see a way to set that to static.  The WiFi settings seem to be there.  Maybe I'm just looking at the configuration screen wrong.

Edited by mbking
Link to comment
Guest
This topic is now closed to further replies.

×
×
  • Create New...