v2.2.3 is out

Official announcements from Z-Wave.Me team. Check this forum to get information about new releases and bug fixes.
Post Reply
User avatar
ronie
Posts: 34
Joined: 29 Jun 2015 09:50

v2.2.3 is out

Post by ronie » 15 Jul 2016 13:18

Dear users,

we are proud to announce that new v2.2.3 is out. Please have a look on the ChangeLog for more info.

In this version we have mostly focused on fixing issues from v2.2.2 like login problems produces by dependency problems and known problems with readKey. Also we did fixes and enhancements affecting the usability of our user interface like
enhancing app error handling, refactoring z-wave device management and info messages if z-way-server isn't available.

We've also updated ExpertUI v1.0.6:

New features
  • - Configuration: Select Device Description No configuration file #103
    - Configuration: button Set All to Default #136
    - Bitrange support and add description in the Configuration #50
    - Descriptions about colors of Routing Table #154
Fixes
  • - Can't configure second parameter #174
    - Thermostat widget sends wrong command #146
    - Associations tab does not work for devices with multiple instances/endpoints #167
    - Expert commands use input field from instance 0, regardless of the actual instance #168
    - In Association tab Association to 118:0 write 118.0 and not just 118. #173
    - Battery Icon Update Problem #179
    - Wrong handling of Expert Commands prototypes #184
    - New device name not showed in Configuration for field #183
    - After Include Redirection Error #178
    - In Configuration don't show self #169
    - In Interview results dialog run interview on the corresponding channel #181
    - Use real scale instead of explicit °C #193
Hope you will enjoy this new step forward.
As for us, same procession, we are starting to work on the next version. ;)

[UPDATE]

The Network > Reorganization / Network > Timing Info functionality in Expert UI has some problems with the new mongoose 6.4
So this functionallity is not available since we've fixed the problem.
Updates via Network > Routing Table are still working.

#######################################################################################################



Because unfortunately some of you guys had some trouble with the latest stable releases:

In our test laboratorities we're testing our software on many different gateways and OS until we're sure it is stable enough so we can release it. Unfortunately we could not fetch all of the different use cases outside ... if we try to do this, it will end up in a mess and stop developement. Also our test process will be improved regularly in particular to avoid the recurrence of known issues.

Your support helps us to find issues, usability mistakes and finally to improve our software. We hope that you will also support us in future.

Thanks for your support.



#######################################################################################################



Some of these hints should help to make your life with z-way easier:

Do Regularly Backups / How to restore them:

Regularly backups especially before fw updates could protect you for loosing data. Z-way gives you different ways to create and restore backups:

Smart Home UI (regular way):
  • - Menu > Management > Backup will create a file with ending .zab that you can download
    - this file contains whole: config.json (controller data, profile data, room data, virtual device data, instance data), z-way, userModules and all other storage files except of notifications
    - Restore with .zab file of your choice via Menu > Management > Restore
Attention:
If your Z-Way Controller (RaZ/UZB) is completely reseted, you're not able to restore with .zab backup. This backup file allows you only to repair/restore failed nodes or their missing interviews.

ExpertUI (for experts):
  • - Network > Controll > Create Backup will create a file with ending .zbk that you can download
    - this file contains whole: z-way stuff only and no Smart Home configuration
    - Restore with .zbk file of your choice via Network > Controll > Restore
Note:
By default the restore of z-way will not overwrite the network topology, what allows you only to repair/restore failed nodes or their missing interviews. If you do a restore with overwriting existing network topology information you have a chance to restore your complete z-way after it got lost (not recommented). But this could also lead into routing problems, so also Network > Reorganization will be necessary. Use Call for NIF under Configuration > DEVICE NODE > Interview to get idle nodes back. Battery driven devices needs to be woken up.

Via ssh:

Every Smart Home UI fw update creates a backup from the last installed z-way-server version under /opt marked as z-way-server_DATE. Next to a downgrade via the common way through Smart Home UI, you can also do this via ssh. First stop the z-way-server

Code: Select all

$ sudo /etc/init.d/z-way-server stop 
rename the current z-way-server folder like

Code: Select all

$ sudo mv /opt/z-way-server /opt/z-way-server_old 
and make the backup folder to the current one

Code: Select all

$ sudo mv /opt/z-way-server_DATE /opt/z-way-server 
after that start your z-way-server

Code: Select all

$ sudo /etc/init.d/z-way-server start. 
Note: This will not affect a completely reseted z-way controller all other stuff should be back again.

Reload Apps (Smart Home UI):

Sometimes apps where marked as broken in BE if e.g. dependencies correct. After you're getting such an error please check the event log (next to time field). There you should get the correct app (class/folder) name. Use this to reload the app via

http://MYRASP:8083/ZAutomation/api/v1/m ... e/APP_NAME

If successful and the app code isn't broken you should be able to use it again.

Consider this as a temporary workaround. We work to make the software handling this problem on its own.

Deactivate readKey service:

The readKey script or service is a new feature that allows us to handle commands send by push buttons that are placed on the new RAZ model what is still in progress.
If you have problems with the service you can disable it via

Code: Select all

$ sudo systemctl disable readKey

To remove it from autostart, remove the script with

Code: Select all

$ sudo rm /etc/init.d/readKey

Post Reply

Who is online

Users browsing this forum: No registered users and 2 guests