Blog post about Ezlo VOI™

Hi @LibraSun

Delete is not working because of the beta version. We are working on it. That will be released soon. I will inform you.

Cheers ilkan


@ilkan, could someone please post a video of a Linux-firmware Vera Edge actually using VOI? I kinda feel like I’m being punked here, staring at blank screens in the .369 app where “Amazon Alexa” should be.

I’ll also take any and all suggestions to try – thought that was the purpose of our “Vera Dashboard” Google Group, but evidently it’s not being used for communication?? – since I got the Edge and flashed it just for this purpose!


  • Libra


On a positive note. With the .360 beta Google Home started working.

Cheers Rene


Hi @LibraSun, we’ve done a fresh setup - just upgraded a Vera Edge controller to the Ezlo Linux firmware and we’re able to use Ezlo VOI™ commands, here is a short video:
Vera Edge running Ezlo Linux firmware - Ezlo VOI™

I talked with our team and answers are provided now in the group, lately it was not on the radar. Thank you for bringing it up.


1 Like

Thanks (I watched it), but… seems that, no matter how many times I repeat the App > VOI > [+] > “Amazon Alexa” > “Allow VoiEzloProfile” > “Linked!” > [Done] process, I get absolutely no “Alexa” device as your video depicts.

So, is that just me? Just .369? Other users as well?

CORRECTION: Somehow, I’m back on .360 of the app?!? Will keep waiting for .369 to roll around again.

NOTE: I even see “Libra’s Ezlo VOI” listed among registered devices in the Alexa App > Settings > Device Settings list … except it shows “Device offline. Some setting may not be available.”

NOTE, TOO: I even removed/unregistered the “VOI” entry in that Alexa devices list, then logged out of the Vera spp, and started everything from scratch. No dice. Like I said, waiting for .369 to install itself. C’mon, Google!

Stumped. - Libra

Hi @LibraSun,

For me the beta also shows .360. It was available since March 13. I have not seen a .369 version. I expect they are spending a bit more time testing the next Beta as the .360 should never have been made availble as Beta.Too many Vera functions broken.

Cheers Rene

Yeah it was definitely not ready for external testing, that said I don’t mind as my Edge was bought just for experimentation.

Well, my big problem is that the app is mostly broke for Vera’s even the current production version of the app. There was too much focus on the new forgetting to regression test the existing (what 99% uses).

Maybe I was dreaming? Perhaps my fancy footsteps of deleting/reinstalling the beta app to force-push .369 over the weekend just nabbed me .360 all along?

Times here in New Orleans are stressful, so that’s entirely possible/probable.

I just know I won’t be doing much testing with .360 or any other version until someone else says the coast is clear for simple things like listing Devices and Scene editing (i.e. it’s no fun to beta test alpha ware!).


From build 7.40.360 we made two new releases on the beta that gathered the fixes made by us based on customer care tickets and community raised issues. The latest is 7.40.371.
Due to the current circumstances with COVID-19, Google warns us that they will have a delay in reviewing the apps to a week or even longer.

This delay is also confirm in the Play console’s Help documentation.

We are sorry about any inconvenience this may have caused. We are doing the best we can.
Thank you for your feedback and reviews.


Who ever imagined software would be affected by an actual virus??

1 Like

Hehe, I must say I’m glad I work for a software company as our entire org has been able to WFH without issues.


Answer: Because otherwise the Spot is the only light source in a bedroom we prefer porch black while sleeping.

1 Like

Short answer: Nope.

Long answer: I tried every variation of command asking the master bedroom echo spot to turn off its screen, with no success.

Oh, well. That’s an Alexa problem, not yours.

At seemingly random times, I get an error message popping up saying “Locations were not found”.

NOTE: “phone to silent” is an IFTTT recipe I routinely use in this fashion through Alexa.

UPDATE: Success! By trying this same command from a different Alexa device (specifically, the last one in the VOI list), it worked!! See screenshot below:

You are right. Alexa doesn’t support that.

Assume that, you have alexa physical devices A and B. When you send a command to use your alexa device B’s capabilities from your device A it might not work because of alexa.

For example when you send command to your device A “tell me the weather of new york” it works. But when you send command to your device A “tell me the weather of new york from my device B”. It does not work. In alexa many of the alexa device related commands works for only in that device.

Thus, please think about VOI as a virtual device that you can reach it from Vera app.


Ah, so my week long experiment was doomed from the outset. I see.

Meanwhile, I’ve been able to successfully play music and such at whichever Alexa I indicate, as here:

In your IFTTT case is also the alexa problem not VOI. As I said voi is the virtual represetation of the alexa. If physical alexa can do something, voi can do. When you see “voi controller is not reachable” like response from vera app there might be a problem on VOI.


Play music is the exceptional case. You can do it between your alexa devices.

Ok, I see. Let us check that case it with Alexa team. As you know, VOI is still in beta. Some of the capabilities are limited.



1 Like