If a listenerPort is not specified in the config.json, 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 (it's unclear if this happens automatically).
Workaround: set listenerPort to any available HTTP port number in the advanced section of the config.json. See README for example.
to Fix: persist the listenerPort in the config so that it survives Homebridge reboots.
If a
listenerPortis not specified in the config.json, HomeBridge randomly assigns alistenerPort. 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 assignedlistenerPort, then after reboot the device would not be able to contact HomeBridge at the new port until it is re-provisioned (it's unclear if this happens automatically).Workaround: set
listenerPortto any available HTTP port number in theadvancedsection of the config.json. See README for example.to Fix: persist the
listenerPortin the config so that it survives Homebridge reboots.