We’ve released a new Ezlo Linux Firmware LIVE release v.2.0.13.1550.8 for Ezlo Plus and Ezlo Secure Ezlo controllers and Vera Edge running Ezlo Linux fw
New Features:
Added support for creating and restoring backups
Added support for sending logs to cloud during logs rotation( added new logs.send_mode setting options )
Added new Scenes Blocks (the support on Web UI will come part of the new releases):
Bug fixing and improvement on the Wifi connectivity
Fixed the issues with Controller not being able to connect to a hidden WiFi network
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 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
Currently, we have some units set to send logs in each rotation as it is the default value and it this is not affecting the creation of backups, meaning backups are not being created every hour but each day instead.
Hello, new EZLO Secure user. Forgive me if I am asking the wrong questions in the wrong place.
Yesterday my hub I went off-line and did not come back for about an hour. During that time I feverishly attempted to reset and bring the Hub back online to no avail. Apparently The hub was automatically updating to this new firmware mentioned in this thread.
Is this normal for hubs to automatically go off line and update without any notifications at all?
Could have saved me a lot of grief had I known this update was taking place.
Following this update I noted some small bugs appear that were not there prior to update. How do I go about reporting those?
Thanks for taking the time to respond to my questions
Yes unfortunately at the current time the Ezlo hubs auto update and you can’t disable it.
We have requested an option to allow us to manually choose when the hub should update or not to the latest firmware version, but as yet it hasn’t been implemented.
To log bug and feature requests create an account on the Jira ticketing system here.
This is still broken, these are the time stamps of the 10 backups listed in the Online API Tool after setting upload logs back to the default setting of “each rotation”.
Sun May 23 2021 13:17:32 GMT+0100
Sun May 23 2021 13:17:00 GMT+0100
Sun May 23 2021 12:17:51 GMT+0100
Sun May 23 2021 12:17:44 GMT+0100
Sun May 23 2021 11:17:00 GMT+0100
Sun May 23 2021 10:18:02 GMT+0100
Sun May 23 2021 10:17:00 GMT+0100
Sun May 23 2021 09:17:48 GMT+0100
Sun May 23 2021 09:17:00 GMT+0100
Sun May 23 2021 08:17:43 GMT+0100
Ok, what I see is that the log rotation setting does seem to work, but the log level, logs color and logs indent have no true effect. The setting si changed, but I see no effect in the log files. However, if I use the v1/method/setEzloLogLevel?logLevel=DEBUG http command the log level does change. Except in the hub.settings.list
So, with the beta it looks like the backups stay at daily even if the log rotation is set yo each rotation.
if you copy that request, and then select custom you can change it to any request the API supports, and not just the ones backed in the apitool web page. You do have to change the ID for each request you send btw.
OK thanks that works. I just changed the last digit on the ID to another one. They should really add this command and the ones for the backups to the Online API Tools menu of available commands to make it easier.