Ok, thank you all for your help. As I’ve run more tests on myself in the meantime I can answer some of your questions and hopefully reveal more details which help solving this mysterious case:
@gs4711 I’m assuming that you’re referring to the configuration of Hue Emulation itself, not thing configuration or something like that. If so: yes, I’ve used PaperUI for conf. Anyway, I’ve performed several reboots without any success. – But I think the problem is not coming from openHAB, although it is somehow related to it, please see my detailed test description below.
@mstormi The file you are referring to stores information on the devices I can see in PaperUI → Inbox. My problem is that the Amazon Echo detects devices which were exposed via the Hue Emulation service, but now are not longer exposed since the addon has been uninstalled. – Please have a look at the description of what I’ve tested. I think it will help narrowing down the cause.
@5iver It was misc-hueemulation-2.4.0. Regarding to the OH Alexa skill: what are you referring to? A binding within openHAB or a real Alexa skill on Amazon Skill Store side? The latter i’ve done – the openHAB skill is installed and connected to myopenhab.org. But that’s a second problem for which I will open a new issue here since this is not working for me neither. Within this issue I’d like to focus on getting rid of the old items coming from Hue Emulation to avoid any conflicts when working with cloud connector.
So here’s what I’ve tested and found out so far:
-
Preparation: I’ve uninstalled the Hue Emulation service, followed by a reboot of openHAB.
-
I’ve opened open alexa.amazon.com and deleted all discovered Smart Home devices via Smart Home → Devices → Remove all. I triggered a re-discover with the other button on that site. Besides the devices which are actually configured in the hue app on my smartphone all the devices coming from openHAB via Hue Emulation re-appeared. Such devices carry the subtitle “Royal Philips Electronics Smart Device” in the Alexa app – the name comes from the Hue Emulation service (https://github.com/openhab/openhab2-addons/blob/master/bundles/org.openhab.io.hueemulation/src/main/resources/discovery.xml)
-
I’ve uninstalled the Hue skill via alexa.amazon.com, performed another reboot of openHAB and repeated the steps in 1. Now only all the devices coming from openHAB via Hue Emulation re-appeared.
-
I’ve shut down the openHAB raspi and repeated step 2. Still all the devices coming from openHAB via Hue Emulation re-appeared.
-
I’ve used the clean-up function in the Hue app on my smartphone to re-init the Hue bridge in such way that only devices configured from the Hue app remain on the bridge. I did this to make sure the re-discovered items somehow came from the Hue bridge. I’ve repeated step 3, but the result did not change.
-
I’ve registered as Hue developer to verify that the clean-up job of the Hue app was successful. I could then enumerate the devices stored on the Hue bridge. This confirmed, that only the devices from the Hue app were stored on the bridge.
-
I’ve contacted Amazon first level support on this. They recommended a factory reset of the Echo device since the discovered items might be stored on the Echo device. As expected, the assumption was wrong since another execution of test 3 led to the same result. Anyway, the support officer filed a ticket for the Alexa engineers to prune these devices – I don’t know if or when this will happen.
What I’ve concluded from the tests:
- Test 3 shows that the issue is not directly related to openHAB, since it could not give any items to the Echo item discovery routine.
- Test 4 and 5 excluded the Hue Bridge from causing these problems.
- The discovered items can only come from some kind of cache or database on Amazon side, thus I let the support file a ticket.
Do you agree with my conclusion or have I missed something?
Best regards,
ceedee