Linux Firmware v2.0.74.3006.4 [production-191] for Ezlo Plus, Ezlo Secure

Company Talks Release Notes
, , , ,
1

Linux Firmware v2.0.74.3006.4 [production-191]

New

  • Stabilization of Sensor Groups has been implemented in Bypass v.02.
  • ForwardNotifications feature added and notificationBlock made optional in Notifications Meshbot v03.1.
  • Access to cloud storage token and cloud API URL v02 is now available.
  • Implemented search methods in Lua Core v02.
  • LPEN v2 optimizations and data access improvements have been implemented.
  • Sensor Groups v2 has been implemented for enhanced experience.

Fixes & Improvements

  • ForwardNotifications parser in Notifications Meshbot v03.1 now allows the notificationBlock to be optional.
  • Implemented the get_device_settings_data search method in Lua Core v02.
  • Implemented the search method get_items_data in Lua Core v02.
  • Implemented common filters in the search method get_devices_data for Lua Core v02.
  • Added support for listing notification settings from TCDS in LPEN v2.
  • UI and Cloud now informed about Sensor Groups v2 implementation.
  • Added support for IAS WD cluster with new sound options and settings.
  • Savvi Siren integration now recognizes the siren as a security device, enhancing functionality and acting as a default siren for Ezlo Plus hubs without needing a meshbot.
  • Added ID tagging to all commands in the ZWave addon for improved command execution tracking.
  • Implemented transaction flow for Z-Wave thermostats.
  • CMS signals are now sent when SOS buttons are pressed on the 2GIG keypad.
  • Quick arming mode for the keypad has been added as a new device setting.
  • Added abort window delay for direct CMS signals using the protect.contactId object in Security Events.
  • Security Events now allow control of the protectNotification flag for Sensor Groups.
  • Implemented protectConfig usage in Lua events for Sensor Groups v2.
  • Optimized memory usage for fetching scenes list, improving performance even with a large number of scenes.
  • Fixed the negative entry delay issue in House Modes during alarm status updates.
  • Renamed policies and child device groups to “Names” for improved UI clarity.
  • Missing files are now logged when using config_reader.
  • Print info.json and generator_version during tcds meshbot deployment in LPEN v.03.
  • Static templates deployment adjusted to prevent meshbots creation with empty local_rules.
  • LPEN v.03 now uses local_rules element from tcds for static templates deployment.
  • LPEN v1 now fetches cloud TCDS data by path for Data Segments access.
  • ACSM v02: Fixed live data issues in Meshbot templates, addressing integer overflow and minor bugs with field names and types.
  • Added functionality to set oem_id for created local template settings in ACSM v.02: tcds-converter.
  • MSE protocol configuration can now be changed via MQTT message.
  • AAC (Mpeg4-Audio) support is now configurable from the configuration file.
  • AAC codec support has been added for enhanced compatibility with older cameras.
  • LPEN v1 now ignores external devices and items for tcds templates.
  • Ezlo Protect subscription status is now reflected in the Plugin Protect’s SOS Buttons.
  • Documentation of SOS buttons methods and events in the API is now available.
  • Logging now supports partitioned logs for hub.log.send, update, and reboot operations, enhancing organization by adding date suffixes to log files.
  • Added logging for received SIGTERM and SIGINT signals in webrtc v2 for improved service shutdown visibility.
  • Implemented asynchronous logging for hub.log.send to prevent blocking of the ha-uid service.
  • Added periodic printing of heap and VM memory usage in the ha-cameras daemon after significant steps in the flow.
  • Updated the HTTP method for sending notifications in Meshbot v05.
  • Implemented exponential backoff algorithm for reconnecting to NMA server under specific conditions.
  • Added MQTT WebRTC v2 reporting functionality to the addon service metrics.
  • Added request duration and average request duration metrics for the Http server in Reporting v3.
  • WebRtc v2 now logs and responds to unknown requests in mqttwebrtc, improving error handling.
  • Added OpenTelemetry generator for trace and span values in firmware.
  • Removed security broadcast fields for devices from the Null Group in Sensor Groups v2.
  • Local meshbot template settings updated to rename rules to local_rules, id, and actions in ACSM v.05.
  • Recovering from a frozen ha-metrics service is now successful.
  • Added snapshot statistics to the hub.service.info.get/info, including request counts, execution duration, and error totals per stream.
  • Fixed an issue where the Centralite Motion Sensor 3328-G was duplicating when paired.
  • Savvi KeyFob now functions fully as a 4 button remote with meshbot capabilities.
  • Kwikset HomeConnect 620 ZWave Smart Lock pin codes weekly restrictions now function correctly.
  • Fixed bug causing deployment status to be incorrectly stored as an error in LPEN v.03.
  • Fixed undefined behavior during SET command executions for ZWave devices.
  • Fixed improper handling of waiting time during device firmware update process.
  • Pin codes for Yale YRD216 & 246 locks are now stored correctly, resolving issues of incorrect or disappearing codes.
  • Z-Wave pairing issues with S2 devices, including delays and failures, have been resolved.
  • The YRD246 lock’s connectivity issues with the Z-Wave network have been resolved.
  • Fixed an issue where scenes were not properly handling setpoints for thermostats GC-TBZ48 and TBZ500.
  • Broadcast now includes a unique alias upon sensor restoration.
  • Fixed a syntax error in NMA calls resulting in a ‘404 Not Found’ response.
  • Resolved an issue where the CMS received duplicate signals when the DW sensor was triggered.
  • Fixed an extra space in the name of the “14 Instant interior – interior doors” sensor group.
  • Bypass alias is now only present in a single item_updated broadcast for a device, eliminating duplicate signals.
  • Intrusion broadcast no longer displays aliases during a NO INTRUSION event.
  • Fixed issue where variable values were being set to null after a controller restart in scenes expressions.
  • Fixed the wrong parameter name “meshbots_ds3_id” in notification meshbot to “meshbots_s3_id”.
  • Fixed an issue where hub.notification.settings.list returned empty ARN, and user_id and permission_role were set to “-1”.
  • Fixed an issue where local meshbots were periodically being re-created without external calls.
  • Fixed an issue where the hub.scenes.list command received no response.
  • Portable auxiliary now includes aliases in broadcasts for improved notifications.
  • Portable panic broadcasts now include aliases for enhanced functionality.
  • Fixed panic now has aliases in broadcasts for the sensor group.
  • The alias for the Instant Perimeter in Sensor Group [13] has been corrected to BURGLARY PERIMETER.
  • Default group no longer has “sensor_group” role and is now assigned “house_modes” role.
  • Sensors are now armed and disarmed immediately after setting a group.
  • Sensor group [1] Portable Panic has been successfully added to the policies list.
  • Smoke sensor added to Fire sensor group can now no longer be bypassed.
  • Deleted devices are now automatically removed from the protect buttons database table.
  • Fixed incorrect signal payload structure in the Protect security events broadcast.
  • hub.policies.list now properly returns the policies list instead of an empty response.
  • Download with redirect in CloudStorage now utilizes the key parameter.
  • Fixed an issue causing a token fetch error when restoring devices after uninstalling the plugin or deleting its devices.
  • Services can now write to ubus without requiring a restart of the ha-watcher.

Thank you for your continued support, and please let us know if you encounter any issues or have feedback!

Release notes link:

1 Like
2

How do we get this update as the autoupdate still don’t work.

3

Hello @Tim88,

We have checked your Ezlo Plus, and it has been running this firmware version for the past 1 hour and 17 minutes.

4

I guess you also noticed that I had to reboot it to force it to update, it did not update automatically.

5

The firmware update worked for me this time. I restarted yesterday, immediately after reading the message. After the restart, the old firmware was still displayed. Now, 19 hours after the reboot, the new one seems to be installed. Is the update not installed during the reboot, but some time later?

6

Very long list this time, by the way. Nice to see that something is happening (even if most of the things don’t directly affect me or I have no idea what they’re talking about :thinking:).

I picked out one point out of interest:

What does “Implemented transaction flow for Z-Wave thermostats.” mean?

1 Like
7

Hello,

The new update UI is ready for grooming by the engineering team. However, the changes required to implement this new feature/UI will impact the current update process for controllers in general.

1 Like
8

My Ezlo Secure is still on v2.0.59.2759.2. Please update me to the latest production version and investigate and fix why the auto update hasn’t been working for several versions.

9

My EZLO Plus hub hasn’t been updated since July 9th of last year. It looks like the Update setting of Auto still doesn’t work - and what are the additional settings of 1 and 2?
In any event I’d like my hub updated ASAP please.

10

Hello @tinman and @chuckf2,

Your controllers have been updated to v. 2.0.74.3006.4. However, the auto-update will not be executed at the moment because our engineers are working on implementing a new UI for updates, which has affected the current auto-update process.

Thank you for your patience and understanding.

11

Thank you.

While the auto-update process is being re-worked can you detail or point me to a post that details the manual update process so I don’t have to keep bugging you?

12

As far as I know, a manual update is not possible at the moment. The only thing that helps is to monitor https://updates.ezlo.com/ and if the controller is not updated to the new firmware, report this here.

13

Thanks for the link

14

I see version 2.0.76 is available. Since automatic and manual update procedures have not been published I’m requesting you to install the update but please backup up the controller first. Thank you.

Can I get on a list where you just update my controller whenever a new update comes out?

1 Like
15

Hello @chuckf2

We have updated the controller with the serial ending in 8105 to firmware version 193.

While our engineers continue working on the new firmware update UI, we’d like to propose a dedicated space in the forum where users can request firmware updates. This would help ensure that updates are only applied with user consent and provide a simple, organized way to manage requests.

The idea is straightforward:
:white_check_mark: Users can post a short message like “Firmware update” in the thread.
:white_check_mark: Once the update is applied, a like from our team will confirm that it’s done.
:white_check_mark: We can also announce new updates in the same thread, keeping participants informed so they can decide whether they want to request the update or not.

Let us know your thoughts! Would this approach work for you?

16

Sounds like a good idea.

1 Like
17

Hello everyone,

We have introduced a dedicated thread for requesting manual firmware updates and staying informed about new releases.

You can now request a firmware update and check for announcements here:
:link: Firmware Update Request & Announcements

This will help ensure updates are applied only with your consent and keep everything organized.

Feel free to check it out and let us know your thoughts!