Breaking Change ZWave JS UI (> 2024-11-29)

[MickLesk]

On 2024-11-29 a breaking change was introduced in ZWave JS UI. (#585)
ZWave JS UI is now operated via additional Envoirement values.

After these steps have been performed, it will be possible to simply execute the “update” statement again.

Please note the following steps before updating:

1. Do an Backup of your installation:

cp -r /opt/zwave-js-ui /opt/zwave-js-ui_bak

2. Remove old folder & create new folder

rm -rf /opt/zwave-js-ui
mkdir -p /opt/zwave-js-ui
mkdir -p /opt/zwave_store

3. Move your old storage files to this path

cp -r /opt/zwave-js-ui_bak/store/*  /opt/zwave_store

4. Enter Main Folder:

cd /opt/zwave-js-ui

5. Update Package:

RELEASE=$(curl -s https://api.github.com/repos/zwave-js/zwave-js-ui/releases/latest | grep "tag_name" | awk '{print substr($2, 2, length($2)-3) }')
wget -q https://github.com/zwave-js/zwave-js-ui/releases/download/${RELEASE}/zwave-js-ui-${RELEASE}-linux.zip
unzip -q zwave-js-ui-${RELEASE}-linux.zip

6. Create .env File:

cat <<EOF >/opt/.env
ZWAVEJS_EXTERNAL_CONFIG=/opt/zwave_store/.config-db
STORE_DIR=/opt/zwave_store
EOF

7. Update Service

nano /etc/systemd/system/zwave-js-ui.service

Check [Service] and add or change missing:

User=root
WorkingDirectory=/opt/zwave-js-ui
ExecStart=/opt/zwave-js-ui/zwave-js-ui-linux
EnvironmentFile=/opt/.env

[xanderphillips]

Worked perfectly for me. After second time of losing my store contents I searched and found this fix. Thank you! Would be awesome if the fix could be back-engineered into the updated version to prevent the loss of store folder for those who have not updated yet.

[GeorgeCastanza]

Thanks for this @MickLesk.

[tremor021]

Always backup your LXCs before issuing a update. You can never know if they changed something in the way app gets updated