Beta - Ezlo Linux firmware v.2.0.6.1271.3

We’ve released a new Beta Ezlo Linux firmware v.2.0.6.1271.3 with the following:
New Features:

  • Implemented hub.item.dictionary.clear method. The support for the method in the Zwave plugin will come together with the next release.
  • Implement Lua API for working with House Modes in Lua
  • Integrated Temperature Scale Settings. The default scale is Fahrenheit now. Also please note that the UI support for this feature will come at a later time with new mobile apps release.

Improvements/Changes:

  • Improved RGB LED behaviour for H2 hubs
  • Improvements on working with the built-in Siren on Ezlo Secure
  • Improvements on working with VistaCam 702.
  • Added unique id field to each broadcasts from the controller

Fixes:

  • VistaCam 702 Camera fixes:

    • Fixed the issue with endless snapshotting making camera addon memory leak
    • Fixed the issue about being impossible to add multiple clients to hub streaming
    • Fixed the issue with no snapshot file from camera addon
    • Fixed the issues with the local live stream not stopping after deleting camera
    • Fixed the issues where sometimes add_camera_stream was failing after 10 seconds with error map::at
    • Fixed two-way audio channel not being closed
    • Removed low camera stream when deleting a device
    • Fixed the issues about the settings_file_signature setting must be stored per camera
    • Fixed the issues with controller not requesting token after stream removing
    • Fixed the issues where the local stream was getting 3 minute delay or freeze after long permanent streaming
    • Fixed the issues about not being able to add a second camera
  • Fixed the issue with device triggered scenes running when they shouldn’t - sporadic (Issues caused by the 2GiG Panic button)

  • Fixed the issue where the ZCOMBO CO/Smoke + first alert sensors had “unreachable” status after firmware update

  • Fixed the issues where sometimes hub.network.changed was sent with huge delay after try_connect (~5 minutes)

  • Fixed the issues with error “Bus request timeout” when when hub.network.wifi.scan.start invoked

  • Fixed the issues with the SSID characters that weren’t added correctly if ssid contained a space

  • Fixed the issue where controller was getting disconnected every few minutes

  • Fixed the issue on the 2GiG Panic Button where sometimes only 1 broadcast was sent

  • Fixed the issue where there were broadcasts about the tamper states changing when it was not actually triggered

  • Fixed the Issue with 2GiG devices stop working after controller reboot

  • Fixed the issue with incorrect thermostat setpoint values immediately after pairing

  • Fixed the issue with rediscover was failing for S0 devices

  • Fixed the issue where hub.network.modem.pin_code.set API was not working

  • Fixed the issue where if battery was unplugged and controller rebooted battery status was not sent in hub.info.get

  • Fixed the issues where after the upgrade there were multiple duplicates of already included devices

  • Fixed the issues about being unable to turn off the built-in Siren on Ezlo Secure siren from mobile apps

Known issues:

  • 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 the low-resolution snapshots not working on VistaCam 702.
  • Issue with not being able to set the sirens to off from Preset Modes on relay connection
  • Issues with incorrect built in siren default state for Home/Night modes (the siren default state is Play for HOME/NIGHT modes but it should be OFF by default)
  • Issues with some Door Locks, as Danalock V3, that are not added with S2 encryption
  • Issue with cases when devices can be removed from the controller after the Firmware update upgrade
  • Issue with 3 videos are created instead of 1 when recording
  • Issues with Spontaneous Wi-Fi disconnects and Controller not reconnecting after a disconnect
  • Issues with the motion sensor on VistaCam702 being armed after the firmware update
  • Issues with Smart Start devices being add multiple times in some cases and breaking inclusion of other devices like cameras
  • Issues with Network Setting not being updated on some cases.
  • Issues with the camera Plugin scripts that can cause problems while adding camera
5 Likes

great work guys, lots of fixes!
Keep building!

2 Likes

Problem saving location. Not sure if was working previously, but unable to save after entering my postcode, and confirming the address details.

my location has disappeared and can not add/edit location, also timed scenes seem to fire twice.

You can use the apitool to check your location using custom and the following:

{
    "id": "_ID_",
    "jsonrpc": "2.0",
    "method": "hub.coordinates.get",
    "params": { }
}

If you want to set the location, use the following:

{
    "id": "_ID_",
    "jsonrpc": "2.0",
    "method": "hub.coordinates.set",
    "params": {
          "latitude" :  xx.xxxxx,
          "longitude" : yy.yyyyy 
     }
}

Hi
it’s good to have an API but it would be better a real web interface for a simple user …

2 Likes

Agreed, but a work-around in the interim is the next best thing :wink:

1 Like

hi
is it possible to add a section in the application which allows to play with the API directly instead of going through the web?

Timed scenes are not working again.

My sunrise and sunset based scenes did not fire on 1 January but they worked today. I don’t know if is the same issue but mine seems related to the New Year rollover.

The day before they fired twice with in 10 seconds, then on 1st they never fired. This evening they worked as normal.

1 Like