Updates for EZLogic - 1.37.1 (Ezlo Hubs only)

Company Talks Official Announcements
, ,
1

Updates for EZLogic - 1.37.1 (Ezlo Hubs only)

Link: https://ezlogic.mios.com/
Previous: Updates for EZLogic - 1.36.1 (Ezlo Hubs only)

Cloud MeshBot. Actions. NuCAL node
In addition to Local MeshBot in the previous release, we changed UI representation for Cloud Variables in Cloud MeshBot.

In case if you want to extract specific element from the array (1), you should type the index in the input (2) and then drag and drop the property. By default it will have the name as “items [index]” (3).

image
image1083×769 95.8 KB

Cloud MeshBot. Trigger. Cloud Variables
We changed Cloud Variables node in Trigger in Cloud MeshBot.
To select a variable before, you had to select a service, your account and then a variable.
Now, you will see all your Cloud variables under the same field.

image
image801×544 49 KB

Complete trigger will look like:

image
image1185×223 11.9 KB

Note: Changes for Local MeshBot are in progress.

Local MeshBot. Action. Controller node

We are glad to announce Controller node in Actions in Local MeshBot.
It has Reboot and Reset controller capabilities.

image
image1505×316 22.3 KB

Reset controller has two values.

image
image1189×310 21.7 KB

Soft reset - will restart a hub.
Factory reset - will restore a hub to its original state by erasing all of the information stored on it.

Fixes and improvements:

  • Fixed right side comparand value type for “string” capabilities in Local MeshBot.
3 Likes
2

What’s the different between “Reboot controller” and “Reset controller - Soft reset”? Isn’t "reboot the same as restart?

3

Hi, @Odysee

I got more details:

1- reboot - reboots the hub.
It just stops the firmware via the reboot operations, and starts the firmware after the host system reboot.
It all keeps running in previous conditions, configs, database records.

2- soft-reset - doesn’t reboot the hub.
updatecmd --soft_reset:

  • calls stop.sh;
  • touch .zwave_reset_required;
  • migration_tool --reset_data;
  • rotate logs with label “soft-reset”;
  • calls start.sh

So, it stops the firmware, tells something to zwave to do on next start, (makes some other steps), clears RAM from logs, starts the firmware back;

makes some other steps:

  • drops wifi settings;
  • drops database version table;
  • drops battery defaults;
  • drops zigbee flasher table.
1 Like