Alexa cannot discover devices which used to work.

[shawn-lindberg]

I apologize if this should have been a reply to another issue, but I have been reading quite a few threads on discovery issues and none of them seem to explain what is happening.

I had been using HA Bridge for quite a few years, most recently version 5.3, with a couple of devices on a Raspberry Pi 3 B. The day before yesterday, Alexa on my Echo Dot started reporting that the devices were not responding. I started digging into this, and confirmed that the devices still responded through the HA Bridge web interface. So, I deleted the devices from the Alexa app and tried to rediscover them. Initially, it looked like this wasn't working because because of a warning about the UPNP IP address about matching a known address on the host, but I was able to fix that by removing a Wi-Fi dongle from the Pi that I didn't need anyway, and resetting the hostname. I also upgraded the bridge to version 5.4. However, the discovery will still not work.

I believe I have tried everything in the troubleshooting page at least once. In particular, I have verified that my Netgear Nighthawk X6 router has UPNP enabled, and the bridge is using a static IP. The logs are interesting. In this case, the Pi running the bridge is IP address 192.168.1.110, the Echo is .14, and my Synology NAS is .12. You can see that the Echo does request a list of the lights, but I don't see a response.
habridgelog.txt

EDIT: One other little tidbit that I forgot to add. My friend was over trying to help me with this issue yesterday and he tried to see if we could discover the devices with the Anymote app on his cell phone connected to my network. He was able to, but I wasn't able to do that later.

Any help would be most appreciated.

[shawn-lindberg]

I just tried the Anymote app again, and it was able to discover devices and turn them on and off. Here is the relevant portion of the log:
habridgeanymotelog.txt

[bwssytems]

So, if the Alexa asked for the list of lights, this will be an issue of IDs cached by amazon. Did you renumber your devices with a different seed?

[shawn-lindberg]

Yes, I re-numbered the devices using seeds of 200, 300, 400, and 500 (originally the seed was 100). I also went into my Alexa device history and deleted the device history.

[Shadow27374]

I probably have the same problem.

A few days ago I had to install HA-Bridge 5.4.0 and reallocate the IDs (100,200,etc.).
After that I still had duplicate and triplicate entries. I had to remove each device individually in Alexa. Removing them all at once does not delete them from Alexa and they would be found again.

Finally, again assign new IDs and Alexa had all my devices once.

About two days later, Alexa independently searched for new devices at night. I saw that because I had seen in the morning a notification under Android the found devices.
But since I was asleep, this is not possible...

In the AlexaApp were then again all possible devices double and triple.

From now on I can do what I want it will only Hue lamps that are integrated via the HA bridge found. All other devices via HA-Bridge are no longer found even with new IDs.

[mjrgh]

Same thing happened to me a few days ago. I didn't make any changes in my local setup at all, so my guess is that Amazon pushed an Alexa update that broke compatibility. In the morning this happened, I had a big pile of notifications from the Alexa App on my iPad saying that it had discovered many of my devices again, and as others experienced, I had duplicates of most devices in my device list in the app. The last time this happened a few months ago, the solution was to forget all the devices on the Alexa side, renumber them in ha-bridge, and go through Alexa discovery again. No luck with that approach this time. Alexa is discovering a random subset of the devices on each attempt (and it's really irritating because it keeps adding duplicates each time it does), but none of them work. In some cases, Alexa just won't find them, and in other cases, it'll find them, but it can't reach them with commands: on commands, it'll spin for about 30 seconds and finally time out with "X is not responding, please check its network connection and power supply". Nothing I've tried so far makes any difference.

[Shadow27374]

Alexa is discovering a random subset of the devices on each attempt (and it's really irritating because it keeps adding duplicates each time it does), but none of them work.

Unfortunately, you have to delete the devices in Alexa individually. The button to delete all does not work properly, then they come back again and again.

And yes, something must have happened at Amazon last night.
Now all my scripts don't work anymore. -.-

[Shadow27374]

One more small note. If I include real Hue lamps from Philips via the HA-Bridge and do not use the Hue Skill, they are still found by Alexa.

The current problem seems to affect only simulated Hues.

[shawn-lindberg]

Interesting that other people have experienced this problem or something like it as well. It does make me wonder if it is related to an update Amazon pushed out. But all of my other real physical devices to work, only to fake devices seem to be having problems.

[mjrgh]

It does make me wonder if it is related to an update Amazon pushed out.

There's nothing to wonder about - that's all but certain, based on my setup. Everything else I run is local and manually configured, and I haven't changed anything in a long time. (In fact, the last time I changed anything was the last time this happened, which was also caused by an Alexa update that Amazon pushed out.) The only thing in my system that can be screwed up by remote control is Alexa. The problem spontaneously appeared one morning, coinciding with a bunch of Alexa App notifications about newly discovering all of my devices. The most plausible explanation by far is an Alexa update.

[shawn-lindberg]

Yeah, I am agreeing with you. The fact that real physical devices are still working maybe exposes a weakness in the emulation, though?

[beandi]

I faced the same problem yesterday - after some searching i found another thread, where a solution was described:
The last digits of the unique-IDs have to be the same, so if your device has an unique id of 00:27:18:5E:E3:0D-7E, you have to change it to 00:27:18:5E:E3:0D-0D.
This change has to be done directly in the device.db-file. After that, every device was found without any problem.

[Shadow27374]

I faced the same problem yesterday - after some searching i found another thread, where a solution was described:
The last digits of the unique-IDs have to be the same, so if your device has an unique id of 00:27:18:5E:E3:0D-7E, you have to change it to 00:27:18:5E:E3:0D-0D.
This change has to be done directly in the device.db-file. After that, every device was found without any problem.

I just tried that now and it does not work.

All My devices now have these 2 values identical after the MAC address.

[beandi]

I just tried that now and it does not work.

Strange - I also removed the "copy"-text from mapid AND enabled the link-button, but the one change which definitely led to success was the edit of the unique IDs. I stopped the service during the edit, have you re-initialized the bridge?

[Shadow27374]

Yes, I have reinitialized. I turned off the HA bridge with systemctl, edited the devices.db via nano and restarted the HA bridge.

I still have a defective Fibaro switch where the relay is defective and only the ZWave part works. Thus, I can find and address my defective switch from Alexa via the official Fibaro Skill.

The switch only triggers a LUA script which sends an HTTP request to switch my fake device (air conditioner).

This is total overkill (50€ each) but at least I can now switch myA/C on and off. :D

[Epik77]

I can confirm that the same problem happened to me last week.
Echo dot3 scanned the devices notifying me of new devices creating duplicates.
I removed everything and since then it hasn't detected any devices on my habridge anymore.
Surely there must have been a firmware update on the device.

[kristofvanwoensel]

Same problem here.... I removed all cache from my echo device, reinitiated the echo, reinstalled ha-bridge, renumbered and renamed my devices...nothing seems to make Alexa discover my devices.

[castellorafa]

Same here, one 'curious' thing is that along with the missed hue , Alexa has detected my HP printer as a new device, the printer has been there for years and Alexa never said nothing about it (also tried deleting on alexa devices, renumbering on ha-bridge and other things that did work on my last discovery issue, but not working this time...)

[Shadow27374]

I hope bwssystems finds out what Amazon has done. Would be a pity for the actually good software and especially my devices.

At the moment I use my fingers like stone age people.

[Quiphainyr]

Same issue here. I guess it's due to an update of the Echo devices. I tried several solutions like deleting everything and adding them one at a time, downgrade ha-bridge to 3.x, 4.x and 5.x, change the unique-ID's, renumber devices with different seeds, but none of the solutions worked for me. Eventually I ended up with using Controlicz as a workaround. I really would like to have ha-bridge working again, but I guess for now it's waiting on a solution that works.

[dbrucep]

For me as well. Started last weekend when notifications on my phone says it discovered new devices where were old instances. Worked to remove and disconnected all echo's. Started with just one but it won't discover devices anymore even by renumber or editing the device ID's. Trace shows the handshake between my Echo and the RPi but it the Echo doesn't seem to do anything with the responce. Like someone said, it did now find my HP Printer (no big deal to me).
Could be there deploying/updating software for the new Echo Gen 4 that includes a HUB. Hopefully not the end of the line for us. I suspect that there is $$ motivating this maybe since those vendors that provide Skill's might pay a fee and Phillips took some action.

Hope I'm wrong and this is just a short lived breakage.

[mjrgh]

I suspect that there is $$ motivating this maybe since those vendors that
provide Skill's might pay a fee and Phillips took some action.

That seems unlikely given that everyone so far has reported that the real Hue devices are still working with Alexa. If Amazon were intentionally trying to disable Hue devices to extract a payment from Philips, it would have been pretty incompetent to leave the real Philips devices working and only break an emulator that they've probably never heard of and probably don't test against. My guess is that it's just that they don't test their changes against HA-Bridge, and they made some change that works with the original Philips hubs but exposes some new compatibility defect in the emulator.

[SelmaUrban]

Hi, can someone check this out:

00:17:88:XX:XX:XX-XX = this is what my uids from ha-bridge look like
00:17:88:XX:XX:XX:XX:XX-XX = this is the hue id style
you see hue ids are longer.

so i stop the bridge and extend some uid in the device.id
and after restart my echo found the bridge-device

by the way, the last digits are not the same in my test!

coincidence or can you do that too?

[Shadow27374]

It just worked for me on one device! I'm just deleting all skill devices again and test it now again completely via the HA-Bridge.

Let's see.

[the4jaggz2]

Just to add some further confusion/insights, my experience has been as exactly described by mjrgh et al with one exception. I moved my bridge from a RPI running HA Bridge 5.1 (connected to my Vera controllers) to HA Bridge 5.4 on Synology (running a virtual LAN to implement port 80 versus 8080 which Alexa can't find). I needed to move to 5.4 to incorporate Home Assistant which 5.1 does not support. Alexa discovered all the applicable devices but then started doubling up (on my Vera ones only, not my HA devices) and of course, the rest of the story has already been documented in the above posts. In desperation though, I shut down the service on my Synology and turned the PI back on, ran the discovery and everything came back with no issues and has been running very well for the last 3 days. Initially, I was going to suggest it was 5.4 related or UID or seed number etc, but it seems everyone has test those solutions and nothing has worked. So net, net, I have no idea why my original service work (has the shorter uids) but hopefully SelmaUrban is onto
something.

[Shadow27374]

coincidence or can you do that too?

Thank you it works with all my devices!

[mjrgh]

Hi, can someone check this out:

00:17:88:XX:XX:XX-XX = this is what my uids from ha-bridge look like
00:17:88:XX:XX:XX:XX:XX-XX = this is the hue id style
you see hue ids are longer.

so i stop the bridge and extend some uid in the device.id
and after restart my echo found the bridge-device

by the way, the last digits are not the same in my test!

I'll give that a try and see what happens. Interestingly, check out this old post on issue #1243 from bwssystems, Dec 1 2020, #1243 (comment):

RC3 is now out in the releases section. Updated upnp handling and device unique ids to be more specific. Also it seems the unique ids have been too long since inception and that may be the root cause. Delete all your devices in alexa and use renumber before you discover.

So it was too LONG, and now it's too SHORT... Makes me wonder if Amazon is making us run around in circles here by repeatedly changing the UID format Alexa recognizes.

[SelmaUrban]

I'm runing a Conbee II stick on a rpi and all ids (Ikea,...) are like the hue ids. All devices found by my echos.

[kristofvanwoensel]

It's not working here. I changed
"f8:99:13:9d:f5:e1:05-93"
to
"f8:99:13:9d:f5:e1:a2:e4:05-93"

Is there anything else I need to change?

[npaisnel]

I had too been wondering why I had data being ‘saved’ even after deleting habridge.config and device.db.... I had persistent data that survived the deletion.
#1311 (comment)

As you too have found... the basic concept of remembering to stop the service running is vital !

probably obvious to many, and obvious once you know.... but not obvious until pointed out !

[jayjupdhig]

OK thx

[arnieSkyNet]

Does this home bridge work with Heyu and X-10 devices do you know ? So Alexa discovers the X10 devices as Philips Hue in the same way HABridge does it ?

Yes I have all my X10 stuff controlled by heyu and these are executed on habridge (commands put in via habridge web gui).

Alexa discover and they appear.

I’m having new discovery issues but existing X10 devices are all still working

[npaisnel]

You could just try creating new devices AND NOT doing a discovery
I had a ‘device’ called ‘EVERYTHING’ So at night ‘Alexa Turn Everything off’ shut all home down. That has worked for a few years.

Earlier this month I created ‘Everything in Bedroom’ and ‘Everything in livingroom ‘ devices

Alexa would not discover them, I gave up trying... but I did not delete them from HA-Bridge GUI

About 3 days ago Alexa Turn Everything off’ stopped working with Alexa giving the ‘There is more than one device named Everything’ , which one do you want.

Seems there is some auto unannounced discovery going on.

[arnieSkyNet]

The discovery issue is fixed now by setting the Oct 9 thing in settings to true and then doing renumber in devices.

Habridge version 5.4.1RC1

everything is working perfectly now after doing that

[npaisnel]

Seems to work for some, and not others
It worked once for me, not worked again.

[phatsion]

Im not having any luck with it here.

Have tried fresh install using RC1 on a different pc.
Setting the Oct9 true.
nothing is discovered.

Running on widows 10. have allowed java through the firewall etc.. and even tried with the firewall off - still nothing.

am i supposed to have the hue skill installed on alexa? i dont remember having to do this before.
Also, people are talking about a "link button". i cant see this anywhere - only the link timeout setting?

THanks,.

[npaisnel]

You need to enable the Link button
Got to Bridge Control
Then Update Security Settings. there is a check box there to enable the Link button.
but it does not seem to make any difference,

Worth trying to delete all the two files config and db file.
om my RPi they are stored in /home/pi/habridge/data

I use the GUI to backup my devices.
then delete the files in the data folder..except the backup obviously..

Then stop ha-bridge
Not sure how you start your HA-bridge system..but on my raspberry pi I did it using a service file in etc/system/system

if you do it like that .
Stop the service
using sudo systemctl stop name-of-your-service.service

then delete those files.

If you do not stop the service first..data 'carries over'

Shut it all down
Go to Alexa Home page / device

Delete all your devices..ONE AT A TIME :(

Leave it for 24 hours or more if you can.

Restart the Pi after 24 hours and restore your device database

using the HA-bridge Bridge Control page..scroll to the bottom and change your seed number to some thing much higher.
like 1000

Renumber you devices From Bridge Devices page.

Now either Ask Alexa to discover devices...OR >>JUST leave it for another period of time .

i have had some luck with Alexa seeming to Auto discover devices..

Leave it another 24 hours..

It might work..it might not

it did for me ..but only because I had given up and I had just left it uconfigured for the weekend..I came home and it was working again ???

[skiller200]

Hello guys,

I am struggeling with the issue more then a week.

Was trying a lot of things and read on different pages.

What I did, I reset and logged out my three Alexas. Put the power off for 3 days. After three days I was using a new Amazon account.

First I used my Echo Dot 2nd generation. I made a backup from my HA Bridge.

• Deleted all devices in HB created a test device in HB.
• Loged in, into the new Amazon Account, device search and found my test device and I was able to switch it.
• Delete the test device in the amazon account and searched again and again it was found again.
• I took a break for 2 days
• After 2 days I restored my current config in HB and wanted to add in my new amazon account all devicees from HB, nothing was found. I logged out from my Echo Dot 2nd Gen. and logged in again.
• After all devices were found and I was able to control it with my Echo Dot. This Moment I felt very happy.
• Started with the Echo 3rd. Gen. Added it to my new Amazon account.
• All the devices are in my new Amazon account.
• I can switch every device through HB with the Echo dot 2nd Gen., but not with the Echo 3rd Gen.

Maybe this is helpful for the developers.

This log from the Echo 3rd Gen.

The Echo 3rd. Gen. is sending the Request to my Phillips HUE bridge with the IP 192.168.1.98 and NOT to my PI

SSDP packet from 192.168.1.98:1900, body: NOTIFY * HTTP/1.1 HOST: 239.255.255.250:1900 CACHE-CONTROL: max-age=100 LOCATION: http:https://192.168.1.98:80/description.xml SERVER: Hue/1.0 UPnP/1.0 3.14.0/IpBridge NTS: ssdp:alive hue-bridgeid: 001788FFFEA236AC NT: uuid:2f402f80-da50-11e1-9b23-001788a236ac USN: uuid:2f402f80-da50-11e1-9b23-001788a236ac

This log was from my Echo Dot 2nd. Generration

The Echo Dot 2nd Gen. is sending the request to my PI where the IP is 192.168.1.99 And again I can control all my devices through HB

sendUpnpResponse to address: 192.168.1.110:50000 with discovery responseTemplate1 is <<<HTTP/1.1 200 OK HOST: 239.255.255.250:1900 CACHE-CONTROL: max-age=100 EXT: LOCATION: http:https://192.168.1.99:8080/description.xml SERVER: FreeRTOS/6.0.5, UPnP/1.0, IpBridge/1.17.0 hue-bridgeid: B827EBFFFEF3D452 ST: urn:schemas-upnp-org:device:basic:1 USN: uuid:2f402f80-da50-11e1-9b23-b827ebf3d452 >>>

Sending response string: <<<HTTP/1.1 200 OK HOST: 239.255.255.250:1900 CACHE-CONTROL: max-age=100 EXT: LOCATION: http:https://192.168.1.99:8080/description.xml SERVER: FreeRTOS/6.0.5, UPnP/1.0, IpBridge/1.17.0 hue-bridgeid: B827EBFFFEF3D452 ST: urn:schemas-upnp-org:device:basic:1 USN: uuid:2f402f80-da50-11e1-9b23-b827ebf3d452 >>>

HB Version 5.4.1RC1
Bridge Control Unique ID to use 9 Octets (Renumber after saving this setting) True

Edit: Just added a new device in HB and Alexa found it.

Cheers

[BuxtonCalvin]

I was able to add additional devices by changing the unique ID of the device to a 9 octet number. You do this by directly editing the device.db file, saving the file, and then re-intializing the HA-bridge. xx:xx:xx:xx:xx:xx:xx:xx:xx

All colons with no hyphens, all letters in lowercase. What a hassle though to get to that point.

[mrschwarz50]

I update to V5.4.1RC1. I delete the 'device.db' file and added a couple of devices and tested them. I performed a factory reset of the Amazon Show and linked it to an Amazon account that has never had an Echo device connected to it. I set security to allow links and pressed the link button. I then searched for a new device and found nothing.

[HalRum]

I'm not sure if this has anything to do with your issue, or for that matter anyone else that is still manually updating their device.db file to set to the 9 octet number, but recently I realized that I had not actually turned on the setting in V5.4.1RC1. This setting, the way it is listed in the application and the way other settings are listed can be interpreted(at least by me!) as being in the "on" state by default, and if you touch the "false" setting you would be turning it OFF! But I realized after reinstalling everything and Alexa being unable to find any of my X10 modules, that the setting actually has to be changed to "true".

Unique ID to use 9 Octets (Renumber after saving this setting) | true

I incorrectly "assumed" the new version V5.4.1RC1 would have the setting already enabled since it was released specifically to correct the issue with creating 9 octet numbers in the first place. However, this is NOT on by default so you MUST turn it to "true" and renumber again using the application. Once this is done, Alexa will be able to find the devices! Good luck!

[mrschwarz50]

Thanks for the latest comment! I changed the setting and renumbered the devices. I turned discovery on. It went through the motions and told me it didn't find anything. Then a few seconds later, they showed up one at a time.

Being the glutton for punishment that I am, I reset the Echo Show and connected it to my original account. The Echo discovered everything again.

[HalRum]

I am so glad I was able to offer someone advice that helps! I figured I am not the only one to make this bad assumption. The settings seem intuitive, but apparently not to all of us!

[FadingDreams]

Thank you @HalRum - I enabled this setting (without any cleanup on Amazon or so) and Alexa find new devices again.

[npaisnel]

Think you just got lucky
I confirmed that mine does say ‘True’
But it never did make a difference

[HalRum]

npaisnel, did you also do the renumbering as advised within the application? If yours was set to 'true' at some point but never renumbered, it would not have regenerated the 9 octet numbers and Alexa would never find them.

[npaisnel]

I have gone back to a fresh instal, deleting all in the data folder (device.db and the other... I forget its name)
Removing the Echo Dot devices, leaving it for three days before re installing the Echo Dots, adding back the devices, Ensuring 9 Octet True renumbering with a new seed start number

Just seems random if it finds them or not.

[steviehs]

That is so frustrating... I want to add new devices but nothing is discovered any more. 5.4.1RC1 with 9 octet numbers enabled, but not renumbered, as I do not want to lose the existing devices - which still work...
This new device now has 9 octets, but still nothing is discovered... I have gen 2 dots and gen 3 dots and gen 3 echos. No success at all...

Any idea what else to try? TBH, deleting existing devices from Alexa is not an option before I do not have a serious idea to get them back.

[steviehs]

While looking for alternatives, I found, that Homeassistant also has a hue emulation feature... which I tried and it works. Maybe somebody with more skills than me could compare what is the difference :-)

[arnieSkyNet]

Steviehs, In the end I was so frustrated and started losing already connected devices so I took the risk of doing the re-number and then everything worked.

did make a backup first as much as I could but didn’t need to use any of these.

[HalRum]

Just recently in the last week Alexa stopped working properly. It seems that she started seeing my devices with the wrong address so if I said turn on den light she would turn on a living room. Everything seemed to be renumbered incorrectly. Nothing had changed on my HG/HA setup.

What I did a few days earlier was ask Alexa to discover new devices because she wasn't able to see my PLEX server properly. The discovery process did not fix the PLEX issue and I eventually discovered my NAS had an update that needed to be applied. So, my feeling is that the "discover devices" request somehow loaded up old settings. On my Alexa phone app I found a few entries duplicated that hadn't been there the last time I got everything working earlier.

My solution was the following and it has repaired everything to normal again.

1. Log into Alexa on a computer and delete all the devices by scrolling to the bottom of the screen and deleting them all at once.
2. DeRegister each listening device I have (Studio, Dot2, Dot3).
3. Reboot each listening device so it gets a fresh install.
4. Reregister each listening device. (Easy with a phone connection through the Alexa App)
5. Then I told my Dot3 to go ahead and "discover devices" again and this time it found all the correct devices.
   Now everything works when I say Alexa, turn off the den light, she only turns off the den light!

I stress that this did not involve ANY settings/changes to the HG/HA on my PI system. In fact I did not even touch them or restart them. Alexa broke due to either the discover devices request I made to originally fix a PLEX issue or something was changed by Amazon since the last time I got everything working months ago. This is some kind of Amazon bug where they might have restored old settings somewhere along the line.

[LenPC]

The solution described above worked fine for me as well! My setup had 1 echo and 4 dots and after updating one of my devices on HA Bridge and running discovery, the number of bridge devices doubled, and Alexa couldn't control anything (insisting that I "use unique names"). This persisted despite renumbering. I'm running v5.4.1RC1.

Some additional observations on the above steps:

1. I received an error message after hitting the remove all button, but after refreshing the list of devices, found they were all removed anyway.
2. Step 2 (DeRegister) can be accomplished on the Computer or the Alexa App. If you have multiple devices, After DeRegistering, I suggest unplugging the echo to avoid confusion when re-registering them (step 4).
3. Do step 3 (reboot), then step 4 (ReRegister thru setup), for each device before moving to the next device.
4. I performed Step 5 (Discover) after ReRegistering one of my five echoes, tested a couple of devices, and then ReRegistered the remaining echoes.

Just wanted to send big THANK-YOU to HalRum for this discovering and posting this solution.

[avrcode]

Alexa cannot (as of today, january 2023) recognize any devices. Considering all the hints here.
Does Ha-bridge still work???

[MarcoPolet]

Hi, I'm using HA-bridge on a daily basis with my Alexa echo dot (2nd gen I think). It's working fine, although I don't add or remove devices that often. It can be a bit of a hassle to get it working (there are a lot of hints in this thread), but it should still work .

[AndreasGaus]

Alexa cannot (as of today, January 2023) recognize any devices. Considering all the hints here. Does Ha-bridge still work???

I can agree that HA-Bridge devices which are created recently are not discovered any more these days - even with the long unique IDs. In the past, the duplicated devices have been annoying. This seems now to be solved by Amazon. But now new HA-Bridge devices are not found any more. Original Hue Bridge devices work fine with Alexa.

[OrbitTheSun]

Thank you SelmaUrban, the long ids fixed my problems when searching for new devices!
It's working now (Jan 2023) after a year of trouble finding new devices.

[der-robert]

I just tested this workaround and it indeed seems to work! Only adding "00:" to the beginning of every unique ID seems to be enough and the Link-button has to be pressed while discovering.

Full list of steps the way it works for me:

* sudo systemctl stop ha-bridge

* cd _ha-bridge folder_

* cd data

* sudo nano device.db

* use CTRL+W and search "unique" to find the unique ID's

* add "00:" at te beginning of every unique ID

* save the file

* sudo systemctl start ha-bridge

* press "Discover" within the Alexa app/site

* while Alexa is discovering, press the Link-button under "Bridge Devices" within HA-bridge (make sure "Use Link Button" is checked under Bridge Control -> Update Security Settings)

* the devices should show up within de Alexa app/site

Thanks @SelmaUrban for this workaround!

THX this works for me

[dimi-m]

I just tested this workaround and it indeed seems to work! Only adding "00:" to the beginning of every unique ID seems to be enough and the Link-button has to be pressed while discovering.

Full list of steps the way it works for me:

* sudo systemctl stop ha-bridge

* cd _ha-bridge folder_

* cd data

* sudo nano device.db

* use CTRL+W and search "unique" to find the unique ID's

* add "00:" at te beginning of every unique ID

* save the file

* sudo systemctl start ha-bridge

* press "Discover" within the Alexa app/site

* while Alexa is discovering, press the Link-button under "Bridge Devices" within HA-bridge (make sure "Use Link Button" is checked under Bridge Control -> Update Security Settings)

* the devices should show up within de Alexa app/site

Thanks @SelmaUrban for this workaround!

Thank you so much, finally it made my day. @Quiphainyr @SelmaUrban

[der-robert]

Had found a small, easier way. When you inspect the uniqueID field in the gui, you can remove the "readonly"-attribute then change the uniqueID in the field, press "Update Bridge Device". that's it.

Followed by the 4 last steps!!!