If after changing item definitions I then get unexpected behaviour, especially with groups, then normality can sometimes be restored by stopping openHAB, clearing the the cache, and then running a forget and discover in Alexa.
I also noticed that running discovery a few times recovered missing devices.
SO it takes “Switch” instead of “Küchenlicht”. I can change the name “Switch” but in V2 the name was pulled by default from the skill. Asking Alexa for Küchenlicht, I receive the information, that Küchenlicht does not exist. Am I doing sth. wrong?
I had the same yesterday, Alexa seemed to discover a new item I had created but it don’t appear anywhere for me to use.
I started poking around to no avail, I then walked away in a hump as I couldn’t get it to work only to come back to it a couple of hours later to see it there.
I had a discovery issue as well. Tried many delete/rediscover/clear cache but couldn’t solve. I also tried using v2 and v3 definition of items as the 2 are supported by the v3, but didn’t solve: I couldn’t get new items discovered.
I had mixed v2 and v3 item definitoon in my .items files so I decided to only use v3 and it worked.
Is it possible that whilst the v3 tolerates both v2 and v3, it doesn’t tolerate mixed use of v2 and v3?
Don’t know but if you wanna give a try…
It sounds like you weren’t triggering manual discovery whenever you made configuration changes and that the daily automated discovery triggered on the Alexa side fixed your issue.
Because of security concerns I would like to disable Alexas access to OH when I am not at home (when I am away it does not make sense anyway.
Is there any option to activate / deactivate Alexa’s access to my system?
Like:
Block Alexa’s Internet connection temporarily?
Disconnect openhabCloud to my system?
Change UUID of OH, so that openhabcloud does not have access anymore?
something else?
I am confused. I actually recall answering this question before and then I noticed you were the person I replied to in the first place. Did you end up implementing the solution I recommended?
Damn it - you are right.
That slipped through my notes somehow.
Sorry for that.
I will try to play around with your recommendation!
Thanks for pointing this out to me (again)
I guess I have another issue.
After activating the OH Skill in my Alexa app and tagging the items, I can discover them.
But I guess this interfers with my previous Hue emulation setup, because all items are discovered as Royal Philips Device.
Of course I deleted all Devices before the new discovery (and removed the hue emulation binding), but they seem to be buffered somewhere.
Where can I look for this?
EDIT:
I guess deleting the cache will help!? (as always)
Thanks for pointing this out.
Yes, I read that and have the same issues.
The only difference is, that I don’t have a physical hue bridge, but this does not make it any better.
Alexa discovers my “Orange” device, displays the “Démarre” and “Stop” buttons in the Alexa Android app which send the right Play/Pause commands to OH and then MQTT.
However I cannot found the right vocal orders to activate these commands. I always get (in French) “the device Orange does not take into account this command”.
Can you please provide the exact utterances in French you tried?
Also, it seems that the PlaybackController capability may be more appropriate for the functionality you are trying to expose. Although, it will probably require the use of Player proxy item and some rules to integrate.
I have tried the following utterances :
"alexa démarre orange”
"alexa arrête orange”
"alexa ouvre orange”
And I have got always that response from Alea :
“L’appareil orange ne prend pas en charge cette commande.”
For the utterance “Alexa met le mode démarre pour Orange” i’ve got “Je ne sais pas comment régler l’appareil orange sur ce paramètre.”
I have also tried
"Alexa mode démarre pour orange”
"Alexa mets orange en mode démarre”
with only a beep feedback from Alexa