This feature/enhancement seems to be the most exciting to me.
How would this be implemented in a Rule? Would the “command location” need to be passed in? Or created specific dummy items for each location? Seems like it would need to enhance the rule engine.
There’s a few different ways to do it. You shouldn’t need a rule. The way I understand it, you put an Echo into a group (in the Alexa app) with the devices in the same location, the kitchen for example. Then instead of saying “turn on the kitchen lights” you can just say “turn on the lights” and it will know based on the group membership that you are talking about the kitchen lights.
So you can either put all of the particular devices in the Alexa group, or if you have your items grouped in OH you could create a proxy item that acts on the group and put that one item in the Alexa group.
I tried that, but I have not found any setting that lets you put a specific echo device into a group in the Alexa settings.
Has anyone figured this out?
The feature hasn’t been released yet. It’s supposed to drop this month, but we will see.
Can’t get Alexa skill to find a simple zwave switch created in .items. Homekit is able to find it so the tags are working fine. Any suggestions?
I think, as someone else has suggested earlier, the ability to identify which binding is permitted to use (eg: is discoverable) the tags , would be a great addition, since many of us seem to run both hue emulation and echo binding. Eg: [“switchable:hue”] or [“switchable:echo”] or perhaps for multiple discovery [“switchable:hue,echo”] or a similar format.
For the most part, I want to use hue emulation and have Alexa discover the hue emulated devices too, but with some items I’d prefer Alexa binding native support only, like the temperature control tags.
The skill is not available in the app store for india. When checking online, it says “
You are not eligible to enable this skill due to geographical restrictions.”
Is there any other way for me to get it?
Thanks!
even im facing the same issue,fix it soon
Should be available soon, I guess:
OK using the new Routines option I can finally say “Alexa Goodnight” and then based on that command I can then set a switch (or group or multiple switches) on or off. I think this gives ultimate flexibility as I can still use OH interfaces to “turn off the house” as the proxy I use is called “the house”, or even voice command this the same as before.
Only thing I think is missing is the voice response from Alexa - I say " Alexa - Goodnight" and she replies “OK” - a bit of a cold response from her I think - would be great if the Routine supported a voice response - then you could have some fun with that:
I say - "Alexa - Goodnight"
She Replies - “Goodnight you sexy beast”
Its a pity that English(India) language is not supported due to which it is not possible to access the openHab skill in India yet. Hope we get to use the skill with our projects soon!
@Matt77 @Kanusel I’m have the same problem. I’ve just added my Thermostat as described. Alexa found the device after I asked her to find smart home devices. When I ask “Alexa, set the Lounge Thermostat to 21 degrees” she says “I’m not sure what went wrong”.
Interestingly this does not happen if I ask Alexa to increase or decrease the temperature rather than setting a specific temperature.
This is my configuration:
Group gLoungeThermostat "Lounge Thermostat" [ "Thermostat", "Centigrade" ]
Number thermostat_lounge_temperature "Lounge temperature [%.1f °C]" <temperature> (gPersistChange, gLoungeThermostat) [ "CurrentTemperature" ] {channel="zwave:device:15a8680e20e:node7:sensor_temperature"}
Number thermostat_lounge_setpoint "Lounge setpoint [%.1f °C]" <temperature> (gPersistChange, gLoungeThermostat) [ "TargetTemperature" ] {channel="zwave:device:15a8680e20e:node7:thermostat_setpoint_heating"}
Number thermostat_lounge_battery "Lounge battery [%f]" <temperature> (gPersistChange) {channel="zwave:device:15a8680e20e:node7:battery-level"}
String thermostat_lounge_cooling_mode "Lounge Thermostat Heating/Cooling Mode" (gLoungeThermostat) [ "homekit:HeatingCoolingMode" ]
The heating / cooling mode is a bit of a fudge, I don’t have any such thing. Could that be the issue?
Is it worth starting a thread for just this issue?
Hi Simon,
might be worth it. Maybe someone has a solution for this issue. I would really like to get this fixed.
Hi!
Anyone made experiences with Alexa Routines and setting a Thermostat?
When i select a thermostat in the app i get the notification:" device not supported"
Best regards
Hello,
I have the same problem my Alexa set the right temperature but says "something went wrong"
could some one fix it?
Best reguards
Waiting eagerly for Openhab Alexa skill to support English(India). Eager to use it in India since echo devices have launched here. The openhab alexa skill is not available here yet.
I had this for a longer time as well. It was actually becuase my heating mode was undefined instead of somethign like: off, auto, heat or cool
Hey guys,
at first - thanks for the skill - great work.
I’ve some troubles with the Humidity and alexa.
I am using Homematic CCU2 with several Homematic IP devices. One of these devices is one Wall mounted thermostat which is collecting the current temp, set point temp and humidity and much more.
CurrentTemperature and TargetTemperature are working fine. I’ve configured them as a part of a group which is tagged with “Thermostat”.
I’ve added another Thing with the Tag “CurrentHumidity” and exposed it via openhab cloud connector.
The “Thermostat” Group is shown at alexa - the “CurrentHumidity” Number not - Any clue?
Thanks in advance