We actually need to add Portuguese translation to support that language. Until it is added to the skill, you will not be able to use the official skill unfortunately.
Have you tried to deploy your private skill? The localization in that setup may not be a factor. Also, I am curious to see which region the Lambda function should be deployed since Amazon hasn’t updated their documentation for your skill language as of yet. My guess would be with the North America endpoint (us-east-1). It would be great if you could confirm?
Just a question on Alexa groups, am I right in saying that creating the Light and the Echo into a group is an Alexa app side configuration and that nothing is needed in OH2 to make this work? I only have a need to say ‘Alexa, turn on the lights’ in a room which has an Echo and a number of lights (but I’ll only put the downlights into the group) for example
I just added a Security System, as defined in the documentation, and it shows up in Alexa as a security system, but it does not seem to be recognized by Alexa Guard. Has anyone else gotten it to work? Is there something I am missing, or is there a limitation where Amazon only allows this to work with Ring and ADT?
You are correct. Just create a group in Alexa app, add the lights that should be controlled and link the relevant echo device to that group.
You are correct. Alexa Guard is considered as a separate security system device. However, you should be able to use the latest beta version of the Amazon Echo Control binding to synchronize the arm state between the two via OH rules.
I am not using myopenhab.org, but rather my own public (via nginx) openHAB server. I did not run into any issues with the install and my devices all showed up!!! The bad news is they are all offline. Any ideas on how I can debug?
I deleted all items in the alexa app and started a new discover search. The first try was yesterday and i now tried it again. Unfortunately alexa isnt finding any new items.
What am i doing wrong?
With the recent ability added to the Alexa API, to set a given mode, range and toggle controller interface as a non-controllable property, support for the CurrentHumidity label has been added and is now available in the live skill. This is currently only available in the US since it is based of the range controller interface but should be available globally in the near future based on Amazon’s latest announcement.
rule "RolladenArbeitszimmerAlexa"
when
Item AlexaArbeitszimmerRolladen received command
then
logInfo("RolladenArbeitszimmerAlexa", "Status" + AlexaArbeitszimmerRolladen.getState())
end
Is it possible to link the “Original”-Item directly to the Alexa-Item? What i want:
i will see the current % of my Shutter. i will get the % from alexa. i will control the shutter by voice to x%
Yes as long as your original item can directly process the commands issued by the Alexa skill. Based on the description you provided, it seems to be the case.
Looking at the configuration you provided, your original item is already Alexa-enabled through the “Lighting” tag which the skill converts as metadata configuration {alexa="PercentageController.percentage" [category="LIGHT"]}.
So my recommendations here would be to remove your AlexaArbeitszimmerRolladen item, as it would be conflicting with your original item due to same label name, and update your original item to use the “Switchable” tag in place of “Lighting”, if you rather stick with tags configuration in case you are using other smart assistant integrations.
Would the V3 Skill using the MediaPlayer tag allow you to get basic stop/pause/play voice commands through to the kodi binding?
If this would work can anyone start me off with an example item?
my current kodi player item:
Player Kodi_Control "Kodi Control" {channel="kodi:kodi:56633dfc-xxx-xxx-xxx-42392bba46xx:control"}
The metadata label MediaPlayer would allow you to send requests to your Player item linked to the kodi binding. Keep in mind that the “Stop” command is not supported by a Player item on the OH side and therefore not available with the skill. You can find all the supported actions in the documentation.
You should update your item as below. For example, you can request Alexa, play on kodi or Alexa, rewind on kodi. Additional utterance examples can be found here.
Player Kodi_Control "Kodi" {alexa="MediaPlayer", channel="kodi:kodi:56633dfc-xxx-xxx-xxx-42392bba46xx:control"}
@jeshab youve made my day - one change and I am set up! all controls work - even Stop! Its not as feature rich as the kodi-alexa dev skill I set up but all I really used from that was the player contrals anyway - and this without any code to manage - awesome!!!
