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.

[jayjupdhig]

"5.4.1RC1 is broke on renumbering"

Same problem here - thanks.

[glandecki]

this worked for me:

1. Enabled UPNP Advanced
2. Enabled "Unique ID to use 9 Octets"
3. Renumbered & reinitialized the bridge

Alexa was able to discover devices.

[bwssytems]

So, after I realized I did not check the use 9 octets box and saved... I went and did that, a renumber and all devices show up in the echo perfectly. I did not need to set the UPNP advanced item.

Key here before discovery is to make sure you have removed your devices on the echo before doing a discover with the new unique id.

[danigge]

Hello all, for me everything was working fine for a long time. On last Friday I received my new Shelly device, I installed the hardware and also added it to my FHEM installation. Of course I also wanted to implement it to my HA bridge and from this point everything went wrong!

So I added the switch to the HA bridge, I deleted all my devices from the alexa.amazon webside, I did a renumbering of the devices and started a new search for Alexa. She did find all my "old" devices but not the new one. Furthermore a couple of the "old" devices didn't work properly respectively I couldn't add them to my Alexa scenes. Everything was strange from now on. Maybe I did some misstakes as I update the 5.4.1RC1 revision, than I updated the device.db by adding the "00:" to all unique IDs and restartet the bridge and the search as well. Afterwards I read about the 9-octets-checkbox in RC1, I activated it and re-initialized the bridge. From that point I can't renumber the devices anyhow. Meanwhile Alexa is still finding my "old" devices. Even those I deleted from the bridge as the Harmony commands. I dont know what else I can do. I appreciate any hint I can try. Thanks a lot in advance!

Edit: Two days later my Alexa is still finding devices that have been deleted from my HA bridge days ago! I changed the configuration back to 7 octets, stopped the bridge via telnet, edited the device.db by deleting the "00:" from the unique id, restartet the bridge, confirmed that all devices have unique id changed to 7 octets and changed the setup again to 9 octets. Afterwards I started the renumbering of the devices, the id changed to 9 octets. Nervertheless no change at amazon.alexa.

Edit 2: Problem solved, the bridge is running good but Alexa isn't able to "forget" devices! After a clean factory reset everything is working fine again (despite the fact I can't inmplement my Harmony hub into the bridge)...

[jayjupdhig]

Any news from the HA-Bridge developers?

[bwssytems]

@jayjupdhig v5.4.1RC1 does work properly to change to the 9 octets on a renumber and when a new device is added. If there are any other issues, then it is not the uniqueid issue.

[dbrucep]

v5.4.1RC1 still doesn't fix it for me. I've miminize my Bridge to just one device and have renumbered. Thie one device MapId is 00:36:44:a6:84:f9:8e:a8-fe Should work but doesn't. Trace shows the Echo (US) and Bridge doing the send/recieve during discovery. My original device.db had over 50+ devices and worked for years but with it also being change to a 9 octet they longer discover.

Did the API change last month? I see lots of negative reviews (one star) on Amazon releated to Echo's no longer working with first generation HUE lights. Phillip tells customers they now need to buy there V2 Bridge.

Anyway, the 9 octet work around has yet to work for me.

[teasert]

I tried all the tricks suggested on this thread and the 2 other threads, nothing worked.

These steps finally worked for me:

1. Deregister my echo dot.
2. Delete the smart device history from the echo website. It's under Settings > History.
3. Run a fresh set up of 5.4.1RC1 (delete old data folder) and add your devices. Enable 9 octets option.
4. Since my brother has an extra echo dot (3rd gen) that he doesn't use, I took it home and registered it to my account.
5. Tell Alexa to discover devices. Voia! It discovered all my devices.

When I went back to the echo dot website, I noticed that my original echo dot was still listed under Smart Home > Devices. I wonder if this was my problem all along (not finding new devices because it still thinks devices exist in the website).

So, if you have an extra echo dot that has never been registered under your account, try the steps above. They worked for me.

If you don't have an extra echo dot, try the steps below. I didn't test these since I got mine working and didn't want to mess everything up again.

1. Deregister the echo dot.
2. Delete the smart device history.
3. On the same website, go to Smart Home > Devices and remove your echo dot device.
4. Run a fresh set up of 5.4.1RC1 (delete old data folder) and add your devices. Enable 9 octets option.
5. Change ID Seed to something different than previous.
6. Stop and Restart HA-Bridge.
7. Re-register your echo dot. Rename it to something different than what you named it originally.
8. Try to discover device.

Hope this works for those who are still struggling to get theirs working.

[npaisnel]

What / where is 9 octets option ? Can’t say I have seen that

I did all of what you mention a few months ago and it all worked. This time it does not work....but

where else does habridge store data other than habridge.config and drvice.db in the data folder ?

There must be another place... because even when I do delete the ~/habridge/data folder and reboot the server, some settings still stick from the previous config....the setting I am referring to is the Name and IP address entry line under Bridge Control tab, Harmony .

I was just thinking that if data is persistent across reboots and deleting of the data folder, then Habridge must have another data /config repository that needs deleting/flushing too ?

maybe that repository is also storing stuff that is giving us this Alexa unable to discover devices issue ?

[Neokamikaze]

Hello, Changing the unique identifier works for all Alexa versions higher than Generation 3 but no results for lower generations. Do you have a solution for older versions? Thanks

[bwssytems]

@Neokamikaze Are all your alexa devcices older or do you have a mix?

[Neokamikaze]

@bwssystems I have two houses, one with a mixture of Generation 3 and 2 and the other only with generation 2

[shawn-lindberg]

I had changed the IDs on the devices manually a while ago with no success. However, over the weekend I added some new real smart devices to my account and during the discovery process all of my old fake devices finally reappeared.

[jayjupdhig]

I had changed the IDs on the devices manually a while ago with no success. However, over the weekend I added some new real smart devices to my account and during the discovery process all of my old fake devices finally reappeared.

I known that issue... in my case, there is a device called "Bad" (which means "Bath" in German) and it's removed / disconnected since years. But it also still appears...

And Amazon can't or don't want to help...

[Shadow27374]

I known that issue... in my case, there is a device called "Bad" (which means "Bad" in germen) and it's removed / disconnected since years. But it also still appears...

Try to delete each device you want to delete individually via the web interface. For example, delete the bathroom individually.

I know this phenomenon also when I delete all devices. If I delete each device individually (must be confirmed each time) and wait 2 3 seconds per deletion, then these devices remain really deleted.

As strange as the system must act internally, but this is just a tip. Who knows what is really going on...

Ach ja, Bad mit Bad übersetzen bringt nicht viel.^^

[jayjupdhig]

´Ach ja, Bad mit Bad übersetzen bringt nicht viel.^^´

Oh, vielen Dank, ging ein wenig schnell, ist aber nun korrigiert!! ;-)

[dddfr52]

I tried all the tricks suggested on this thread and the 2 other threads, nothing worked.

These steps finally worked for me:

1. Deregister my echo dot.
2. Delete the smart device history from the echo website. It's under Settings > History.
3. Run a fresh set up of 5.4.1RC1 (delete old data folder) and add your devices. Enable 9 octets option.
4. Since my brother has an extra echo dot (3rd gen) that he doesn't use, I took it home and registered it to my account.
5. Tell Alexa to discover devices. Voia! It discovered all my devices.

When I went back to the echo dot website, I noticed that my original echo dot was still listed under Smart Home > Devices. I wonder if this was my problem all along (not finding new devices because it still thinks devices exist in the website).

So, if you have an extra echo dot that has never been registered under your account, try the steps above. They worked for me.

If you don't have an extra echo dot, try the steps below. I didn't test these since I got mine working and didn't want to mess everything up again.

1. Deregister the echo dot.
2. Delete the smart device history.
3. On the same website, go to Smart Home > Devices and remove your echo dot device.
4. Run a fresh set up of 5.4.1RC1 (delete old data folder) and add your devices. Enable 9 octets option.
5. Change ID Seed to something different than previous.
6. Stop and Restart HA-Bridge.
7. Re-register your echo dot. Rename it to something different than what you named it originally.
8. Try to discover device.

Hope this works for those who are still struggling to get theirs working.

Yes, this worked perfectly for me. Now I can add a single new device, delete it, add another one. All is great. Re-registration is the key. I have 7 devices, and it didn't take very long at all to re add them. It is certainly not a BWSystems issue, but a local caching on echo devices that is causing all this grief. Oh, I didn't re-name the echos, it just re-added them as they were.

[jayjupdhig]

"Renumber after saving this setting"

But that does not seems to work... after enabling it, there was still 8 octets... i had to empty the devices.db file (respectively to disable the voice control in our smart home software and enable it again which also restart the ha bridge service)

[jayjupdhig]

But i can also confirm that it works now - thank you very much!! :-)

[belindelu]

it works for me too thank you !!!

[npaisnel]

Most of these 'fixes' seem to work occasionally ..then the next time, they do not ...

Another way that often works is to burn photos of Bill Gates under a Super Moon, while dancing naked around an alter of used Windoze XP Installation CD's...

[jayjupdhig]

´Another way that often works is to burn photos of Bill Gates under a Super Moon, while dancing naked around an alter of used Windoze XP Installation CD's...´

LOL, ROFL...

´Most of these 'fixes' seem to work occasionally ..then the next time, they do not ...´

But that is 100% correctly...

[npaisnel]

I seem to remember someone mentioning a History of Devices..I am wonder if this is purged at a set time by Amazon...so say every midnight local time where ever the server is located....so you might get lucky and it resets soon, or you need to leave 24 hours or more if you just missed the 'deadline'

I used the delete device.db / de register / register devices in the past. and it worked fine.

This last time..I went though the whole thing a few times ...until finally it worked.

[jayjupdhig]

´I seem to remember someone mentioning a History of Devices..´

Oh yes, that seems to be 100% correctly too...!!

[Neokamikaze]

Hello, I still have a problem with Generation 2 Alexa. Has anyone found a solution ? Thanks

[npaisnel]

As discussed above...Burn photos of Bill gates under a Super Moon seems as reliable as anything !

Seriously ......you might need photo of Steve jobs too

I have Gen 2

Seems Deregister the devices from Amazon first. do this from Amazon Alexa website too..search all pages and tabs for Settings/ Device History. Ideally leave de-registered for at least 24 hours. unplug the Alexa Devices and leave unplugged for 24 hours.

Go to your habridge webgui page and create a backup of all devices...ideally then copy that device.db backup file to another computer... copy the habridge.config file too if you feel the need. I did just to make sure I could go back to original

Delete the /habridge/data folder which should have the habridge.config and devices.db files in them.

Restart the computer you are running the ha-bridge server on ... ha-bridge wil restart.

Go to the WebGUI Enable the 9 octet setting...no idea why ..but people found that has helped. Change the numbering of your devices to start at a new number.

DO NOT YET import your old devices from backup file

From here, wait the 24 hours before re-registering the Alexa Devices...the Gen2 ones are a pain to get in to get in to setup mode.

I tried all sorts of button presses to get them in to the Orange Ring setup mode...but best bet is to unplug..leave for good while..24 hours..then plug back in ...then jsut wait..dont press anything ..eventually ..like 1-2-3-4-5 minutes no idea TBH it seems to take for ever...the orange ring stats flashing..get out your phone app and re register the diabolical devices.

Once all set up, maybe create one new devices..totally different name to anytime else.

See if Alexa can find your new device. GOOD LUCK.

If it does work..be brave and try a reimport of your old devices file and do a renumber.

Try discovery again.

If that fails...do it all again. I had to do all that two or three times before it finally worked.

If that fails revert to burning the pictures of Bill Gates

[Shadow27374]

I don't want to hear about Bill Gates. The whole Corona nonsense is just fake and is supposed to establish socialism in the whole (western) world.

[npaisnel]

Ah well substitute for Steve jobs pictures...but slash them / in the opposite direction

[npaisnel]

Hello, I still have a problem with Generation 2 Alexa. Has anyone found a solution ? Thanks

Also go to the Amazon www. webpage...and your account. Not the alexa.amazon page bu but the actual web page of Amazon account.. Weirdly in to the Privacy Tab. There is a Device History tab.

Delete History too...then wait the 24 hours...

[Neokamikaze]

Comme discuté ci-dessus ... Graver des photos de Bill Gates sous une Super Lune semble aussi fiable que n'importe quoi!

Sérieusement ... vous pourriez aussi avoir besoin d'une photo de Steve Jobs

J'ai la génération 2

Semble Deregister les appareils d'Amazon en premier. faites-le également à partir du site Web d'Amazon Alexa .. recherchez toutes les pages et tous les onglets pour les paramètres / l'historique de l'appareil. Dans l'idéal, partez désinscrit pendant au moins 24 heures. débranchez les appareils Alexa et laissez-les débranchés pendant 24 heures.

Accédez à votre page Webgui habridge et créez une sauvegarde de tous les périphériques ... idéalement, copiez ce fichier de sauvegarde device.db sur un autre ordinateur ... copiez également le fichier habridge.config si vous en ressentez le besoin. Je l'ai fait juste pour m'assurer de pouvoir revenir à l'original

Supprimez le dossier / habridge / data qui devrait contenir les fichiers habridge.config et devices.db.

Redémarrez l'ordinateur sur lequel vous exécutez le serveur ha-bridge ... ha-bridge redémarrera.

Allez dans WebGUI Activez le paramètre 9 octets ... aucune idée de pourquoi .. mais les gens ont trouvé que cela a aidé. Modifiez la numérotation de vos appareils pour commencer à un nouveau numéro.

N'importez PAS ENCORE vos anciens appareils à partir du fichier de sauvegarde

À partir de là, attendez les 24 heures avant de réenregistrer les appareils Alexa ... les appareils Gen2 sont difficiles à entrer pour entrer en mode configuration.

J'ai essayé toutes sortes d'appuis sur les boutons pour les faire entrer dans le mode de configuration Orange Ring ... mais le meilleur pari est de débrancher ... de laisser pour de bon ... 24 heures ... puis de rebrancher ... puis d'attendre ... N'appuyez sur rien ... finalement .. comme 1-2-3-4-5 minutes aucune idée TBH cela semble prendre une éternité ... les stats de l'anneau orange clignotent .. sortez votre application téléphonique et enregistrez à nouveau les appareils diaboliques.

Une fois que tout est configuré, créez peut-être un nouveau périphérique .. nom totalement différent de tout autre moment.

Voyez si Alexa peut trouver votre nouvel appareil. BONNE CHANCE.

Si cela fonctionne ... soyez courageux et essayez une réimportation de votre ancien fichier de périphériques et faites un renumérotation.

Essayez de nouveau la découverte.

Si cela échoue ... recommencez. J'ai dû faire tout cela deux ou trois fois avant que cela fonctionne enfin.

Si cela échoue, revenez à la gravure des photos de Bill Gates

Thx i'm testing this.

[npaisnel]

Bonne chance ... c'est la magie noire - Sorcellerie

[jayjupdhig]

"The whole Corona nonsense is just fake and is supposed to establish socialism in the whole (western) world."

100% correctly too!!

[jayjupdhig]

And: I don't understand french, so please write english only here... thx...

[jayjupdhig]

-> That it changes automatically after enabling 9 octets in HA Bridge GUI with save and reinit is COMPLETELY WRONG...

[jayjupdhig]

"Renumber after saving this setting" -> NOT REALLY...

[npaisnel]

I cannot see where any one has said anything changes automatically ...what is the "It, " that you are referring to?

I have had no success with re numbering either..although some have suggested it as a fix. No harm in doing it I guess ?

[jayjupdhig]

Nobody said that it works. But...

So clearly a bug (may it's still unsolved because of RC1...?)

[npaisnel]

is the Unique ID 8 or 9 octet " thing " the same as the difference between these two 00:1a:fa:34:a7:f9:84:ee-ab or 00:1a:fa:34:a7:f9:84:ee:ab

I did read that changing the - dash in the first one to a colon : in the second was also a "fix"

I manually edited the device .db, changing all UID to have the :" and not the - ...still no change. still did nto discover.

and on re numbering ..the - came back ...even with 9 octet enabled.

This is RC1

[jayjupdhig]

I removed ALL entries (voice control flag) via our home automation software then added the "Voice control" flag to the button again...

[AndreasGaus]

Changed to new Unique ID 8-ab octets (9 octets) mode,, deleted device list in Amazon Web Frontend and renumbered devices with start seed 1000 (so that new numbers are generated). Now the old issues with duplicated devices and German Umlaut problem are back again on stage :-(

My configuration: > 10 Echos 2rd and 3rd generation (2 having a Zigbee hub). Additionally, Hue Bridge (new rectangle version) and HA-Bridg (5.4.1 RC1 - the most current one).

Tried nearly anything:

• Disabled Hue skill connection
• Delete and created Hue account again
• Checked without any Hue skill connection
• Shutdown any Echo (2rd and 3rd generation)
• Deleted Amazon devices in Web interface and also in iOS / Android Apps again and again
• Requested on Amazon site to delete all the Smart Home devices - see Amazon Site Settings (no feedback for 2 days until now)
• Clean up Philips Hue devices in iOS App (see Hue Hub App settings)

No way. The zombie devices (old ones) come back again and again. Instead of 150 devices I sometimes had a record with up to 500 devices! Depends on which Echos are enabled or if Hue Bridge is enabled. But even with all disabled, some zombie devices are found.

IMHO my zombie devices are stored on Amazon servers and cached on Echo devices. Amazon says, that if a device shall be permanently deleted, the original manufacturer App shall be used. Unfortunately, HA-Bridge is no offical manufacturer. Maybe an Amazon API exists to delete the device permanently and manufacturers call this, but HA-bridge does not have this feature implemented?

Would be so fine to get this working again, without solving the issues with duplicated devices #1216 I promise, there is no persistent solution for the detection issue (first fix trial in RC1 needs at least another fix regarding the duplication issue).

[Gaspode69]

@AndreasGaus I had this problem a couple of weeks ago. The Alexa Support adviced mo to to as follows:

Unplug all Echo devices
Plug in each Echo device one by one and reset it. Unplug this Echo device after the reset is complete.
Go to the Alexa App and remove each home automation device one by one (do not use "delete all")
Plug in the Alexa devices
Search for new devices in the Alexa App

This worked for me.

[npaisnel]

Works for me too...but only some times . yesterday and the day before it did not work.. I have not left all the Alexa devices unplugged over night. will leave 24 hours.

[AndreasGaus]

@Gaspode69 @npaisnel : thanks for your hints. Yes, I also tried a similar approach without reset, and I have been never waiting with all Echo devices in off state for 24 hours. However, I got it to work in the last years with patience and many hours of work.

I will accept this 24h divorce from Alexa. The first hours I missed her, but more and more I feel free without the really frustrating discussions about home automation devices with her ;-) Will give you feedback, if I managed to get it done finding the new 9 octet devices and not the old zombies...

[npaisnel]

Well I left mine 36 or more hours. Re-Registered Alexa Restored backup device.db 9 Octet option true Renumbered Restarted Alexa Found ZERO devices Tried again... with Link Button Alexa Found 21 of my 31 devices.... but then started listing them all...’You can control Living Room Lights by saying.... Going through each device it found... never done that before.

BUT... no duplicates... do not think I have ever had duplicates.

Amazon Chat... tried them... as expected .... no help.... well apart from saying it must be a hardware fault and 15% discount on new devices...

I deleted devices all at once

[AndreasGaus]

@Gaspode69 @npaisnel : my update on the Amazon support advice:

1) Unplug all Echo devices 2) Plug in each Echo device one by one and reset it. Unplug this Echo device after the reset is complete. 3) Go to the Alexa App and remove each home automation device one by one (do not use "delete all") 4) Plug in the Alexa devices 5) Search for new devices in the Alexa App

This helps a bit. I needed some hours and days to reset all Echo devices. After that, HA-Bridge founds 2/3 of my valid HA-Bridge devices. The last 1/3 of devices is nearly complete after retrying (tried with Link Button enabled and disabled). In contrast to the steps suggested by Amazon support, I enabled step 4) also one by one and search step 5) for each device added again separately.

Unfortunately, after getting 90% of my HA-Bridge device to work, another 10% of old zombie devices come up again. I found out, that my Amazon Fire Tablet (with Echo software enabled) adds the old devices! This was obvious, when I used the tablet the first time after resetting all other devices, the old device list was immediately displayed in toast pop-ups!

I disabled the tablet, but the 10% of old devices come up again and again. Even more strange: after disabling the Philips Hue skill, another 100% of old devices are listed again! In my case 500 devices listed!

You may imagine, that deleting 250 devices one by one in Amazon's web portal is very annoying, but gives me the only opportunity to distinguish the old zombie devices from the working ones (displays new devices firstly by using the very cool sort order feature).

---

So, after going to the HA-Bridge (5.4.1 RC1) and renumbering with 9 octet mode enabled, three issues are detected by me using this release candidate:

a) Because renumbering devices is needed in HA-Bridge to solve the issue with devices which cannot be found, old issues with zombie devices come up again. Even Fire Tablets and maybe also iOS or Android devices with Amazon or Philips Apps seem to cache the zombie devices which makes the complete system unusable. Workaround: delete the zombies every day after they appear again and again.

b) Some devices are found, some not. In my case, the newly created devices in HA-Bridge are not found or not working (devices added after RC update). Previous devices (not the zombie devices) are working with the 9-octed workaround again. I also managed to see one new device working for a while, but now it is dead again.

c) Even the working devices sometimes say immediately "Device is not responding. Please check the power, ...", but the device works quickly and well. If repeating this, it sometimes works without a complaining Alexa. Maybe this depends on temperature or humidity? In one case I checked the non responding tagged device directly in HA-Bridge. There also an orange toast pop-up was displayed once. The immediately executed second click results in a green pop-up and works without complaining!

To sum up: the 9 Octet trial seems to be a first workaround, but no real solution for b). a) and c) are known bugs in combination of Amazon Zigbee Bridges / Philips Hue Bridge and HA-Bridge.

A last remark: I am also using FHEM's Alexa module, which does not have any of these problems. Unfortunately, this module is not that flexible to control all my devices. So the hope dies last. Maybe the HA-Bridge developers find a solution to identify newly created and old devices in a unique way, so that the weak Amazon software works better...

Thanks in advance for your effort.

[AndreasGaus]

Additional log entries for these cases:

1) New device (after RC update and renumbering): detected, logged, but not visible in the Alexa list. 2) Zombie device which is created in Alexa list again and again (duplicated). 3) Old valid device, which is not duplicated in Alexa list after searching for devices and works fine.

Having log level 'debug' enabled (trace seems not to work for me), I cannot detect major differences, except for the user IDs (striked through here for security reasons): the user IDs are different in each case:

However, there are also old seeded IDs in the log (my new seed after RC renumbering was 1000, the old one 100):

The "found device" log entry is missing in case of old seeded IDs. Additionally, the user ID seems to be another one. For me, it looks like old seeded IDs are sent to HA-Bridge and HA-Bridge does not find them (which is OK).

The IP origins of the zombie devices are Echos of 1st generation!

If I can help with additional log files, please let me know...

[kristofvanwoensel]

I gave up, after so many months there is still no solution. I switched to homebridge instead, works like a charm. (See: https://github.com/homebridge/homebridge/wiki/Install-Homebridge-on-Raspbian)

[npaisnel]

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 ?

[kristofvanwoensel]

No idea, there are a lot of plugins for this. Personally, I just need Alexa to send udp-requests to some esp8266 devices, on which I hooked up the lights of my house. This works very well with homebridge as well. It's also very easy to write your own plugins.

[MarcoPolet]

Hi all, I can confirm everything is working after trying everything in all threads concerning this problem. What finally worked:

With the 5.4.1RC1 version, I had to stop the service, remove the device.db and habridge.config file, restart again, setup as before, and also enable the Unique ID to use 9 Octets. After that, add a new device, and found by searching through the Alexa website in a heartbeat. Note I have link button disabled.