Enroll to our Linux Beta Program now

It will show as Offline in the https://home.getvera.com gateway as there is currently no Web GUI.

You can only connect to it via the Vera mobile app and presumably also via SSH command line if its like the Ezlo Plus.

even in Vera Mobile app it is offline.
it seems I do not have back up in my flash I connected to vera.how can I downgrade to Vera firmware?

@Ioana

Can anyone from Ezlo assistant this user please, who is having issues with the Vera Edge and reverting back to the original Vera firmware after a failed attempt to install the Ezlo firmware.

Thank you.

2 Likes

Hi,

I’ve opened a ticket for you, with the reported issue → ECS-430.

Whenever you bump into an issue, please open a ticket using the steps described here. After you’ll create an account (in case you don’t have one already) you should be able to see the above issue, and select to be notified when there is progress.

Let me know if I can help you with anything else.

Ioana

2 Likes

Hi @Alireza44907,

If you can get to the hub via the API Tool (https://apitool.ezlo.com/) then you can submit this as a custom command. It will restore the Vera firmware (not just Luup)

{
    "id": "123456",
    "method": "hub.firmware.luup.switch",
    "params": {}
}

Cheers Rene

2 Likes

I face the offline issue with my Vera Edge when I upgraded it to Ezlo. Even I tried using Ezlo Atom (2 different units) they were offline too. How can I get information about servers like their IPs and ports to ping them?

HI @Alireza44907,

Note that the new Ezlo FW does not have a web interface and will show as off-line in the home.getvera.com list of controllers (maybe that message can be changed, @Ioana . It can only be accessed via the Android or iPhone apps.

Cheers Rene

For all Ezlo hubs the message in webUI should already be there, saying that the VeraMobile app must be used with download links to App Store or Google Play. I’ll double check to see if there is a bug.
The only untreated case should be for VeraEdge using Ezlo Linux fw, as this is just in Beta now.

Hi,
I know that but even using vera mobile it shows unit offline. I have not tested the unit with a new account or an account without vera units linked to it. Does it matter?

It should not affect in any way if you use the same account. So, in your case, the unit never appeared online in the VeraMobile app?

Yes, I think the issue is about my Internet provider, that is why I look for IPs and ports

Hi @Alireza44907,

The local communication to the controllers is at port 17000 , but i do not know all the ports that are used to connect to the Ezlo servers. What I can see is https (433) and 8001 as outgoing, but those should not be blocked by you ISP or you would have loads of problems.

To find out the local IP addresses of your controllers you would have to look at your router.

Cheers Rene

Hi
Thank you for your information, Using VPN the unit becomes online that is the reason why I doubt IPs of servers are blocked by my ISP provider.

Can I connect to units locally using ports you gave me?

Hi @Alireza44907,

You can connect local. You have to enable anonymous access as described here CW's IDIOT GUIDE - To Ezlo platform HTTP API commands aka Luup Requests - #2 by cw-kid - General Discussions - Ezlo Community

Cheers Rene

Not sure if this has been asked recently. When will the Ezlo Linux firmware be available for the Vera Plus?

Hello, @walshchristopherj

Currently, we don’t have an ETA for when the Linux firmware will be available to Vera Plus and Vera Secure as it’s right now for Vera Edge controllers.
Our plan is to get this available for all Vera users at some point, however, we are focused on the Ezlo Plus and the Ezlo Secure controllers for now.

Thank you for your understanding.

1 Like

Hi! Can I enroll my ezlo plus gateway in this program?

Ezlo Plus firmware is beta :grin: and should auto update on the hub.

1 Like

Thanks for answering me, the firmware version of my ezlo plus is 2.0.14.1570.3 has not been updated to a recent beta version.

Mine is version 2.0.19.1714.2

Try rebooting your hub.