Beta - Ezlo Linux v. 2.0.9.1382.14 hot fix for Ezlo Plus, Ezlo Secure, Vera Edge controllers

Company Talks Official Announcements
#1

We’ve released a hot fix for the Ezlo Linux v.2.0.9.1382.14 for Ezlo Plus, Ezlo Secure and Vera Edge controllers:

Hot fix:

  • Fixed the issue with scenes that have scene controllers as triggers stop working after the firmware upgrade. Please note that, in order to fix the issue, the users that already upgraded to 2.0.9.1382.13 will need to recreate the scenes after upgrading to the new firmware version.

Known issues:

  • Issue with the Led behaviour in the devices exclusion process where the LED on the controller flashes as if the controller is still in exclusion mode even after clicking the “Exit” button to exit from DPW.

  • Issue with sensors that can have the status changed to Armed after the upgrade in case there are zwave plugin changes for those specific devices from one FW version to another.

  • Issue on devices that support Tamper where the broadcasts and notifications generated are opposite to the actual tamper state

  • Issue on Z-Wave devices with “electric_meter_amper” that is updated only when the hub is restarted. Ampere meter not changing value instantly once pairing a device supporting it (for example pairing a switch and adding some load to it - e.g. connect a bulb)

  • Issue with incorrect sunrise/sunset time for scene in case the timezone is changed after enrollment. The sunrise/sunset scenes are calculated based on location and for the moment we do not have UI support to change it after enrollment (API is in progress of being integrated in UI)

  • Issue on Vera Edge where after the first update from Vera FW to the new Linux FW the “Internet” LED is OFF

  • Issues with some Door Locks, as Danalock V3, that are not added with S2 encryption

  • Vera Edge Wifi connectifity issues:

    • Issues the Vera Edge controller not being able sometimes to connect to a Wifi network
    • Issus with disabling wifi interfaces not working on Vera Edge
    • Issues with hub.network.get method reporting AP interface as up, even if it is disabled
1 Like
#2

All my devices vanished after this update!

Scenes and rooms are still there but no devices.
Is there a way to revert or restore a backup?

Edit: @Ioana ECS-435

#3

Hi @Ioana
I did well to wait before creating many scenes to my VeraPlus, I would have to start all over again.
Can you script to rewrite the scenes from a previous version so that we don’t lose the job please?

#4

Same here. No devices left…

#5

You mean Ezlo Plus or Vera Plus?

#6

On EzloPlus

Édit
the goal being to recover the existing scenes and to rewrite them. And it can become a utility for the next time too

#7

Will sit this one out, I believe.

#8

Well, updates aren’t optional yet so I say @Ioana needs to pull this update before more users get affected.

1 Like
#9

Lets hope no power failures.

#10

Just checked my Ezlo Plus it’s still on version 2.0.9.1382.13. All my scenes and devices still look to be present.

However I hadn’t created any scenes that had scene controllers as triggers.

#11

Yep, I’m toast too.

#12

Same here :frowning:

#13

Our engineering team had a process issue…one of the “build servers” was building without going thru the QA process…Its now been fixed…
that is why we only see this issue on certain “builds”…

#14

Ok, good you found the cause. Is it possible for affected users to recover without re-pairing devices?

#15

I think they are working on that now. My advice, do not touch anything for now and wait for the .15 (or .16) release.

And @melih, it should not be possible that a build gets released while bypassing QA.

Cheers Rene

1 Like
#16

I know…

human error does occur…must learn and improve processes everytime there is a human error.

#17

I just updated my EzloPlus right now to this .14 version and it has now worked ok. No devices lost.

Cheers Rene

2 Likes
#18

Guys, packages of 2.0.9.1382.14 firmware were fixed and updated several hours ago.
If somebody updated to it from previous version - they wouldn’t have this problem.
Now we are working on the new build which will restore removed devices.

1 Like
#19

Update build is already available. It will be 1382.15.
We are testing it now and will push it asap.

3 Likes
#20

I couldn’t bring up the device wizard just now to re-add the devices which were removed :frowning: