Node will not let go of former IP address

[rskirch]

Just an FYI for folks who are seeing this.  I recently updated my Venstar CT's wireless network and IP address.   I then changed it in the Node configuration.  I was using the hostname: IP address custom parameter.  It was on the same network as the eISY but was subsequently moved to a different VLAN.  I then rediscovered the new IP and it appeared in the ISY, but the old IP Venstar was there as well.  I deleted the old item from the ISY, and restarted the Node server.  That did nothing. It just added it back in.  Then I restarted the PG3, and still no change.  You could see in the logs that the Node server had saved the IP address (as mentioned in the documentation), but would not let go.  I had to uninstall the Node server.  This is not desirable, as the ISY will comment out the lines in your programs referencing the Venstar and you will need to recreate them.  Maybe this can be fixed in a future version?

[Goose66]

Nodes from plugins should be deleted in the PG3 Dashboard, not from IoX Admin Console. The  node list is stored in the PG3 database and most plugins recreate all of the nodes from these database entries when they restart. If you delete a node from the IoX Admin Console, it will just get recreated when you restart the plugin. Deleting it from PG3 deletes it from IoX as well.

This is a known limitation in the PG3 system. Once PG3 is absorbed into IoX (v6?), this should be cleaned up.

Edited October 12 by Goose66