Loaded question of late. Amazon has been making changes with Alexa, pushes out code updates with no notice and no way to confirm and we’re often left to discover on their own. I have a couple of location where I noticed the same behavior recently, ha-bridge stopped working and I was unable to immediately get Alexa to discover all devices.
There was a fix recently on ha-bridge where the id in the device.db file needed to be set to 9 hex digits instead of 6 or 7. I haven’t seen any updates from ha-bridge for the issue, if you haven’t already tried that approach suggest a quick search for ha-bridge and device.db. Advanced skill, requires editing data file on the device (for me raspberry pi) running ha-bridge. Symptoms present as you note, no issues connecting between vera and ha-bridge, its another issue with ha-bridge Hue emulation and Amazon code.