After jar 5.3.0 and Physical Harmony Hub Alexa no longer discovers devices

I have seen a few threads on this, but still nothing that has helped me get discovering working again.

I did read about multiple upnp devices, but not sure how or where to look to see if I do have multiple

Tried re numbering devices and too did get devices responding to different commands from other device ID’s

Have tried enabling the ‘Link’ button before discovery, but no, that does not work to help, with dicovery. It does though work to link the Harmony Hub.

These are the small `echo dot ‘flat Alexa devices Model RS03QR with device software 641575220. I see references to Gen 1 or Gen 2 Dot’s, not sure which these will be, though suspect Gen 1

What is my next step to get discovery working again, it only seemed to stop after updating the jar to get the Link button to allow Harmony Hub discovery

[evilmumi]

Hi,

i had some reboots on my raspberry and echo and now it is only working when i ran it on port 80 - perhaps the same topic? log seems identical. before i had never problem running on 8888. 80 is blocked by nginx so i have now a problem. Can you help?

[npaisnel]

Just to update this in case other find this

Even now with ha-bridge 5.4.0

The issue with Alexa not finding devices still occurs.

A fix appeared to be deleting the Data File from habridge and allowing habridge to re create the habridge config file and then re importing the devices.db file .

But second time I tried that…it did not work.

Doing that in conjunction with De Registering the Amazon Echo Devices, deletion all Devices form Amazon Alexa WebGUI, and then leaving it overnight ,… Then adding back the Alexa devices the next day, WITH NO devices added to HA bridge.

Once Alexa Devices added. go back to HABridge…ideally via a terminal and copy back a “device.db” file to the 'new habrridge/data/ folder.

That worked on…at least this time…