No meethue.com connectivity but no error message about homebridge-hue HOT 4 CLOSED

Homebridge-hue does report an error message when the communication with meethue.com fails. I suspect in your case homebridge-hue did actually get a valid response from meethue.com, albeit an empty response, as your bridge was no longer registered with meethue.com. I'll add a check for this in v0.1.16.

Please note that that's still a workaround. I fear you had to redo your HomeKit configuration (re-assigning homebridge-hue provided services to HomeKit rooms, scenes, rules, etc). I need to move to dynamic platform accessories (issue #4) to prevent that. Also implementing local UPnP discovery of bridges (issue #6) would create less of a dependency on meethue.com.

from homebridge-hue.

Ah of course, https://www.meethue.com/api/nupnp gave me a [] when I went to it so it was indeed an empty response.

And yes, I did have to re-do the HomeKit config although I had thought this was because I set the host entry in my config to the hub's IP address before then undoing it after the router reboot.

from homebridge-hue.

No, unfortunately, HomeKit deletes the accessories from it's database when homebridge no longer provides them.
With dynamic platform accessories, homebridge persists accessories between restarts in ~/.homebridge/accessories/cachedAccessories. On startup, homebridge would provide the saved accessories to HomeKit and show them as unreachable, until homebridge-hue re-discovers the bridge. This would also be the structural solution to startup timing issues when using multiple plugins, see issue #26.

from homebridge-hue.

Implemented check in v0.1.6.

from homebridge-hue.