When asking the machine if the lights on/off it answers “floorlight doesn’t support that!” which I take some kind of offense in because I’m quite sure Openhab does support that and the mistake is with me using it and not the software itself
I went over the documentation but the only examples coming close to what I need is tempeature - and that exposes another Alexa interface which lights, as I understand it so far, don’t have.
What I’m confused about is the fact that in the Alexa companion app, the light is shown as “off” or “on”.
I tried adding the ReportState in addition to the lighting but still no change in behaviour. The app tells me the state of the switch, Alexa, when asked, tells me “how should I know?”, exaggerated
Or does that link mean that this falls under
“Your skill should not fail if it receives additional fields in a directive or directives it does not recognize.”
And I can’t realise this with the standard Openhab Skill?
wait I think I’ve described this wrong - I don’t want to control Alexa from Openhab (with the binding the lastVoiceCommand is part of, https://www.openhab.org/addons/bindings/amazonechocontrol/ ).
I want Alexa to query OpenHab and report back the state of a lightswitch. I don’t even have that binding.
So this is a limitation on the Alexa side with the PowerController interface. Only Amazon would be able to answer the reason for it.
As you noticed, you can get the status of a PowerController modeled item via the Alexa App but you can’t get that same status when requesting via voice commands. This is because the skill only gets ReportState requests for the former but not for the latter.
I know it’s pretty frustrating but if this is a feature you must have, you could use a workaround via the toggleController interface. Keep in mind that you will need to use the component friendly name to control the device and the Alexa app integration wouldn’t have a nice bulb icon to turn on and off.
and the command “schalte Garten an” doesnt work" but “Garten off” does (without the ‘switch’/‘turn’ keyword.
In addition, when asked what the state is, it answers “Garten Garten ist OFF/ON” (yes, English phrasing, although it takes the German commands without issues.
Anyway, I can now check if I’ve forgotten my garden electricity without taking my phone out, even if the voice commands are not as smooth as I would’ve wished for.
Thanks again for your help - thought that you’d perhaps like a success-Update
The category parameter is not translatable. It needs to be one of these values. Same goes with the semantic extensions you have setup. These are only for open/close commands which doesn’t apply here and therefore aren’t needed.
Correct. This is what I meant by “Keep in mind that you will need to use the component friendly name to control the device”. You have to use device name Garten + friendly name Strom to send a command in this case. I agree it’s another unnecessary limitation on the Alexa side.