Alexa.getvera.com certificate expired

Anyone have any updates or fixes? I have to reenable the Vera skill (in the Alexa app) every 24 hours. “Dave” from eZLO support had me try a few things, then told me:

…we’ll need to wait for a response from the team in charge. There is no ETA at the moment.

Would it be possible for the Ezlo devs to post the source code for the Alexa skill on github. Maybe someone can then refactor the code to work on a local server.

It’s clear that this skill is no longer being maintained by Ezlo, so why not release the source code and let us users have a chance at regaining some functionality to this much needed function.

I’ve also had the Alexa skill get disconnected every day or two for the last few weeks. It’s driving me nuts. Alexa is how I control every thing, but most of my devices are connected to a vera edge.

Same thing here. Seems to be worse after switching to Alexa Plus
Can someone from support verify?

Hello everyone,

Our Cloud and Development teams are aware of the issue and are actively working to resolve it as soon as possible. At this moment, we don’t have an estimated time of arrival (ETA) for the fix, but we’ll keep you updated as soon as new information becomes available.

Thank you for your patience and understanding.

it’s been happening every day for the past few days
at least I’ve become and expert at re-enabling it

1 Like

This is a problem again. Can’t enable to Vera Alexa skill, mostly get an error saying it can’t be enabled at this time. 1 out of 10 times I can get it enabled, but as soon as I try to use the skill it instantly disabled.

1 Like

Same problem here and the connection is lost within 12 hours. Since Vera hasn’t come up with a fix, maybe the better question is what Z-wave controller should we be migrating to that doesn’t have such problems. This is very frustrating!

same
is the vera / alexa connection EOL ?

Again. Would it be possible for the Ezlo devs to post the source code for the Alexa skill on github. Maybe someone can then refactor the code to work on a local server.

It’s clear that this skill is no longer being maintained by Ezlo, so why not release the source code and let us users have a chance at regaining some functionality to this much needed function.

Especially if there is no appetite to maintain it because of Ezlo development.

Hello everyone,

Our team is working to resolve the issue as quickly as possible; however, we do not have an ETA yet. The skill/connection is not at EOL and was actually updated a couple of months ago, but this time the problem is different and our team is actively investigating it.

Thank you for your patience and understanding.

1 Like

Any details on what the problem is and why the continuing disruptions in functionality with the skill?

Hello @Tim88

Our engineering team is still actively working on the Alexa integration issue, but we do not have any new updates or an ETA to share at the moment. We understand how inconvenient this is and really appreciate your patience; as soon as we have concrete progress to report, we will post an update here on the forum.

Ok, Alexa skill is not EOL. Just like Vera support?

Vera was abandoned years ago when Ezlo took over.
Just look at the FAQ from 5 years ago, it is still online.

I have had Vera from the beginning, Vera 1, 2, 3, and plus. The product works decent and never have had an issue upgrading until Ezlo. Never went to Ezlo because of the lack of migration and the feeling Vera was kicked to the side and abandoned. I do not trust Ezlo to support their products. Still running 7.32b5 awaiting the official release for 5 years now. Not to mention the continuing maintenance releases as promised.

Sadly I think I will have to finally jump ship and go to another hub. If I have to start over with Ezlo, might as well do it with another product that actually has support.

Alexa support has been a rollercoaster ride since the beginning and absolutely unusable for the last month. At best it kind of worked with constant messages from Alexa that a device was not responding even though it controlled the device.

From the FAQ:

How long will the Vera platform continue to receive support? Will you continue to release firmware upgrades?*

The next firmware upgrade (7.32) is already planned, and we will be maintaining support for the platform. After 7.32 we’ll be making maintenance upgrades on an as-needed basis to ensure full functionality

Hello @DLR,

We totally understand your frustration, and we truly appreciate that you’ve been with Vera from the very beginning. You are right that the shift from Vera to Ezlo created challenges for many users, especially given how different both platforms are.

Our goal has been to build a more modern and scalable system while maintaining essential support for Vera controllers. Part of this process included developing a migration tool to help users move devices and configurations from Vera to the new Ezlo platform. However, due to the complexity and differences in the underlying architecture, the migration tool still has some limitations and may not cover all device types or use cases.

Even so, our team continues to provide maintenance updates and solutions whenever possible — including addressing the recent Alexa skill issues, which were impacted by Amazon’s backend and app changes. We’re actively working to restore stable functionality as soon as possible.

We truly value your loyalty and feedback.

1 Like

I’m sure we all appreciate the continued support on a legacy system but if it’s being supported and maintained how/why were Amazon’s backend changes not addressed proactively by Vera/Ezlo.
Did Amazon not communicate the upcoming changes to Vera?
I have many skills on Alexa that seem to have made it through Alexa’s backend changes. Was Vera doing something that was not technically supported by Amazon and Amazon closed the loop causing the skill to stop functioning.
It would be nice to get some technical details on what the issue is.

1 Like

If only you guys would have done what you said you would do. Release 7.32 firmware and continue to add new devices to vera. I would have migrated to the MIOS platform by now even if I had to rewrite scenes and add devices back in.
The first bad experience I had with Vera support was when UI7 was released, the Wayne Dalton WDHA-12R Home Link Bridge was broken, support was never able to fix this and stopped responding to requests for status.
Next was not releasing 7.32 firmware and supporting new devices as stated would be the case thus Vera was abandoned.
Now Alexa is utterly broken. Some days it may link for a few min and allow control of 1 device before unlinking again most of the time it says it linked but never works. This has been going on for a month or so. We are working on it just reminds me of the WDHA-12R problems I had in the past. Promises of a solution with none ever coming.
So the blame is Amazons backend changes. They gave you guys no notification of an upcoming change that could break the Alexa interface? Or they did and no one did anything until it broke? And now no one knows how to fix it? Or you guys can’t fix it and wont admit it.
It does not say much for a company that does not keep its promises and keeps its customers in the dark.

1 Like

Should let AI take a crack at it.

There are so many things that are being ‘worked on’ I’m not confident that this will actually be resolved.