HomeBridge listenerPort is re-assigned after reboot

[mkormendy]

HomeBridge randomly assigns a listenerPort. This is fine, except this port number is not persisted anywhere and doesn't survive reboots.

The impact is that if a Konnected device is provisioned with a randomly assigned listenerPort, then after reboot the device would not be able to contact HomeBridge at the new port until it is re-provisioned.

[mkormendy]

Upon each reboot the plugin re-provisions all Konnected panels it finds on the network, therefor assigning a new port number in the process based on availability by the system hosting Homebridge and the Konnected plugin. In case there were any problems with this (router assignments unknown to the hosting system) then the configuration option listenerPort could be used to force a static port to be used.

Workaround:
Set listenerPort to any available HTTP port number in the advanced section of the config.json. See the Wiki for an example to persist the listenerPort in the config so that it survives Homebridge reboots.

In a future release, the first provision of the panels will select a port to be used and then store it in the config to persist across reboots - however this could cause first-time setup frustrations for users if the port chosen is blocked by a user's router, and further effort may need to be made on the preliminary installation guidance for this plugin.