Are you sure you are not using any previous Beta skill url, instead of the official one found in the Amazon skills menu ? Have you also tried, removing the skill, and reinstalling it ?
Hello,
I’m here in the US. Same issue with that error message except for my Wemo switch (shows up multiple times in Alexa app). It looks like the “connected via Vera” for the other devices is in fact not connected. The Wemo screen says waiting for Vera and then functions as expected. Voice commands work fine. I have an email into support. Let’s see who points the finger at who. Fingers crossed
Vera Plus UI7 latest firmware and latest Vera Skill
I’m getting the same problem. Whenever I login into Alexa Web UI and click on Vera Control skill I also see a message that it couldn’t retrieve permissions. I think what’s happening is I’m somehow stuck in beta testing skill, and cannot install newer version. When I uninstall Vera Skill and install it again, I see “devUS” logo next to the skill, which means that I’m not getting public version of the skill for some reason.
I too see DevUS, but I don’t think that’s the issue. Vera support told me to contact Amazon. I think Vera should contact Amazon, because I doubt anyone with a Vera has the home control device button functioning in the Alexa app. Frustrating.
John, another thing they added is the ability to assign an Echo in a room, so that you could say turn on lights for a specific Echo in a room/area. It isn’t working with “included” in wall switches, but it does work with plug in lamp modules. It’s similar to groups, but allows the ability to say turn on lights as a phrase for each individual room. - Derek
This is still being discussed internally for an official explanation.
But to give you some insights, this is not a bug or issue. So it’s more than a “quick fix”. These are new capabilities added by Amazon to the functionality of their app, which are part of V3 skill and API.
I believe Amazon Routines feature is another capability part of this new API.
Vera Skill is based on V2 Api, and a new Skill might be required to support these features. At this moment in time I don’t have an estimate for when V3 Vera Skill will be ready.
LE: ?Amazon recently announced new capabilities for the Amazon Alexa Apps, including direct device controls and status reporting from within the application itself. We?ll be updating our Vera Control Skill in the coming weeks to add support for these useful new features and functions.?
While waiting for the Vera Control skill to be updated, I’ve been tinkering with a custom Smart Home v3 skill implementation that I can share if you’re anxious enough to set everything up yourself in AWS:
With this, the v3 features in the Alexa app have been working for my devices: The new Smart Home devices UI, Routines, Smart Groups, etc.
See the README.md in the repo for more details.
The v2 to v3 migration does not seem to be an easy thing, to me at least. There are a lot of breaking changes. Adding v3 support into a v2 codebase I expect would take a lot of testing. And then there would be the recertification process. I’ll be (pleasantly) surprised if a new version of the Skill can be turned around within the next few months.
[quote=“jnex26, post:10, topic:197525”]I do find it hard to believe that Amazon released its V3 API with no backwards support and breaking all V2 skills.
Can we get an ETA on this please ?[/quote]
Backwards compatibility is still there, ONLY new features are NOT working. Nothing is broken. Unless you have a different type of issue, that I and others misunderstood, in which case we need to look at something else, as being the culprit.
I’m here to inform, not to create confusion. Not intentional confusion, at least.
Thanks.
[quote=“Drex, post:13, topic:197525”]well, I installed the V2 skill then (the official skill) and cannot control lights.
There is an error every time. So not sure how this would be backward compatible…[/quote]
Are you trying to use voice to control your devices? Because that’s all the V2 Vera skill supports. Activating a device via the Alexa app is a V3 Amazon feature, and it not supported by the V2 Vera skill.
There is definitely something broken for me. Scenes no longer work, none of them although I only had two they aren’t new scenes. I removed the helper from my vera, forgot devices in alexa app, removed the beta skill and installed the official, was forwarded to account linking to define device names in alexa, including the scenes. After doing all this I’ve gained progress in the form of Alexa not discovering scenes when I rediscover now? I suppose that is technically an improvement over discovering the scenes and then saying they don’t respond.
I have no idea what the “new features” are but scenes worked under v2 and are now broken.
[quote=“John M., post:12, topic:197525”][quote=“jnex26, post:10, topic:197525”]I do find it hard to believe that Amazon released its V3 API with no backwards support and breaking all V2 skills.
Can we get an ETA on this please ?[/quote]
Backwards compatibility is still there, ONLY new features are NOT working. Nothing is broken. Unless you have a different type of issue, that I and others misunderstood, in which case we need to look at something else, as being the culprit.
I’m here to inform, not to create confusion. Not intentional confusion, at least.
Thanks.[/quote]
This is the second time I’ve had to switch back to habridge since the official Vera skill was released :-\ - the first time being when the entire system was down for 4-5 days.
Grouping devices in a room with an Echo and saying “Lights On” or “Lights Off” isn’t working on any of the devices that do not respond to the in-app commands. Additionally, scenes no longer work.
I can confirm that the Alexa-enabled groups are a new v3 feature not supported by the current v2 Vera Control skill.
Additionally, for the new “lights on” feature to work in v3 the devices need to be discovered in Alexa as a LIGHT display category as opposed to a SWITCH (or other types).
As a feature request for a new Vera Control v3 skill, I would like it if the user could select the display category for each device from the skill initialization page (the page where you can include each device or rename them before discovery). Basing the Alexa display category only on the Vera device category or subcategory might cause problems with other clients and how devices are organized with the current category/subcategory scheme.
Are you sure on that? While the alexa-enabled groups are a new v3 feature, I got mine working such that I can ask the lounge echo to ‘turn off the lights’ and it obliges by just switching off the Lounge Group. Likewise, from the Bedroom Echo, I can control the Bedroom group the same way. Previously I had to address it as the group name (I.E. “turn off Lounge Lights” or “turn on Bedroom Lights”).
That functionality (for me at least) is working fine and this is something that has gone a long way improving the WAF.