Yes. See first post 
You can’t, those items are stored in a jsondb, not in text files. Editing is not recommended.
Haven’t you found the docs yet? No problem:
http://docs.openhab.org/configuration/items.html#groups
To be honest: never tried PaperUI for that, I don’t know, sorry.
Question, will the official app ever support our own deployments of the cloud connector - without having to create a self-signed environment with Alexa? Or will it only ever officially work for myopenhab.org?
im happy to use in india
Thank you,
now it works fine.
The command “light on” or “light off” has recently been started to switch the light on or off in a room.
The devices that are to be switched must be shown in the Alexa app with the lamp symbol, otherwise it will not work.
Now, when the echo associated with the group is said to be “light on” or “light off,” it switches the lights of the group associated with it on/off. are in group other devices (sockets, etc.) These are not switched.
I use all the lights with the [“lighting”] in OpenHab, in the Alexa app they are known but with the Tpy switch displayed, so the “light on” or “light off” does not work.
Do you have any idea how I can display the devices in the Alexa app correctly.
I’m not sure I fully understand the problem from what you have written but if you want a switch to appear in the Alexa app have you tried the [“switchable”] tag?
all devices are identified as TYP- switch - as you can see in my screenshots.
I want to have them of the typ light to use the new “light on” and “light off” command for a group
my Items look like this example, both are shown as switch
Switch Alexa_EG_Kueche_Decke_D “Kueche Decke” [ “Lighting” ] {knx=“x/x/x”}
Dimmer Alexa_EG_wohnzimmer_Decke “Wohnzimmer Decke” [ “Lighting” ] {knx=“x/x/x”}
I have a group “Light” (configured via Alexa app) which contains four lights, three of them are connected through the HUE skill (so they are shown as typ “light”), one of them is connected via openHAB Alexa skill (so that one is shown as typ “switch”): all of them are switching properly when called via “Alexa, turn on/off light”.
My openHAB switch is configured via ["Switchable"]
Hi sihui,
yes thats working, but i want to use the “new” feature.- than you can use the same command in each room you habe a echo
make a Group eg “Wohnzimmer” - put all lights of the room into it + the echo in the room
than you can say “lights on” and Alexa turns all devices with the type “light” in her Group on
Stefan
Ahh, okay, did not catch that, only have one Alexa 
It looks like the code was changed late May to support the appliancetype so [“Lighting”] should register as a “Light”, before that it would register a light as “Switch” like [“Switchable”] which is what you’re seeing and mine does the same (core OH 2.1 release).
But I guess maybe the openHAB Cloud Connector service is using an earlier version as I think the code has to live in the cloud layer to provide the glue, so one for the maintainers to answer.
One small question:
I recently bought a amazon fireTV Stick 2nd gen for about 25 € on Black Friday. It has a Alexa button on the remote and i can control the fireTV-Stick with voice commands.
Can i use this to control openhab too? Or is this only working with real amazon alexa-devices, like amazon echo and dot?
The new fire-Tablets from last month have alexa, too. Is this also working with them?
You can control openhab in the same way as with Echo devices from your FireTV Stick remote. I use the remote in parallel to my Echos.
When is the skill going to available in Canada
I have just verified that Alexa openHAB skill works in Japanese.
I put the item label in Japanese (utf8). Thats all.
Actually, the skill is not listed in the skill list on Japanese alexa portal. I cloned the skill, and run it on my AWS with a dev account.
Please add Japanese language (region) into the official skill’s supported language (region) list. No need to tuch the code.
A big thank you for all openHAB contributors!
Please file an issue for that in the corresponding GitHub repo.
Maintainers will take care about it.
I am using Vera Plus to control Zigbee light switches, and OpenHAB 2 to automate these light switches. This allows me to keep local control of my home automation and not depend on the cloud for basic control. The wish for home automation control that is cloud independent is why I don’t want Alexa Echo Plus to be my Zigbee controller for devices.
For the additional luxury of voice command, I am willing to cede control to the Amazon Cloud. Thank you for this Alexa OpenHAB 2 skill, and of course, OpenHAB! Everything is working very well.
I’ve added my Vera Plus devices to OpenHAB 2 as items, then add these items using: [ “Lighting” ] flag to Alexa Smart Home.
Alexa has a new ESP feature, where you can group an Alexa Echo in the same room as your devices under Alexa Smart Home, and say “Alexa, turn off lights” to turn off all the lights in only that room. As expected, smart appliance switches, even when connected to lights, are not affected by this command.
Smart light switches connected to Alexa Echo Plus (Zigbee hub) will be seen a lights, and can be controlled as above. However, the same light switches controlled by Vera Plus hub, exported to OpenHAB 2 and added to Alexa Smart Home are not seen as lights, and thus not listen to “Alexa turn off lights” commands.
Is this an extra attribute that must be set by the Alexa OpenHAB 2 skill on the devices it exposes to Alexa so that she sees them as lights?
Think the reason is 6 posts or so up:
But still need someone a little closer to the deployment to confirm and comment.
Thanks. Hopefully this is the case, and that it’s a simple update for OpenHAB Alexa skill to use the new API for lights to work as “real” lights, and perhaps even differentiation between lights and appliances. As of right now, Alexa does partially think the OpenHAB controlled lights are lights, because “Alexa, turn off kitchen lights” will work (regardless of whether item is light or appliance switch, which is bothersome), but ESP “Alexa, turn off lights” in the same room as an Alexa doesn’t.
