Updating zwave-js-ui doesn't get the new version

[xijio]

Describe the issue
home assistant says thats too old
"The version of Z-Wave JS Server you are currently running is too old for this version of Home Assistant. Please update the Z-Wave JS Server to the latest version to fix this issue."

When I run
root@zwave-js-ui:~# bash -c "$(wget -qLO - https://github.com/tteck/Proxmox/raw/main/ct/zwave-js-ui.sh)"
It gives output that indicates it updated

 _____                                  _______    __  ______
/__  /_      ______ __   _____         / / ___/   / / / /  _/
  / /| | /| / / __ `/ | / / _ \   __  / /\__ \   / / / // /  
 / /_| |/ |/ / /_/ /| |/ /  __/  / /_/ /___/ /  / /_/ // /   
/____/__/|__/\__,_/ |___/\___/   \____//____/   \____/___/   
                                                             
 ✓ Stopped Z-wave JS UI
 ✓ Updated Z-wave JS UI
 ✓ Started Z-wave JS UI
 ✓ Cleaned
 ✓ Updated Successfully!

But home Z-Wave JS UI is on:
I am running

zwave-js-ui: 8.0.0
zwave-js: 10.2.0
home id: 3826058893
home hex: 0xe40d068d

The github page says the latest version is 8.11.0 https://github.com/zwave-js/zwave-js-ui

Screenshots
If applicable, add screenshots to help explain your problem.

Bug reports will be closed after 12 hours of NO activity.

[tteck]

Currently I'm not using Zwave JS UI, looking over the code, it seems to be downloading the new version. what's the contents of /opt/zwave-js-ui?

[xijio]

root@zwave-js-ui:~# ls -alR /opt/zwave-js-ui/
/opt/zwave-js-ui/:
total 185775
drwxr-xr-x 3 root root         5 Mar 23 07:00 .
drwxr-xr-x 3 root root         3 Sep 21  2022 ..
drwxr-xr-x 9 root root        20 Mar 23 19:36 store
-rwxr-xr-x 1 root root 206021291 Sep 21  2022 zwave-js-ui
-rwxr-xr-x 1 root root 197612326 Mar 23 08:03 zwave-js-ui-linux

/opt/zwave-js-ui/store:
total 410
drwxr-xr-x 9 root root      20 Mar 23 19:36 .
drwxr-xr-x 3 root root       5 Mar 23 07:00 ..
-rw-r--r-- 1 root root     992 Sep 22  2022 cert.pem
drwxr-xr-x 2 root root       2 Sep 21  2022 config
-rw-r--r-- 1 root root   41189 Sep 21  2022 db9213a2.jsonl
-rw-r--r-- 1 root root 1984449 Sep 21  2022 db9213a2.metadata.jsonl
-rw-r--r-- 1 root root   75697 Sep 21  2022 db9213a2.values.jsonl
-rw-r--r-- 1 root root   51307 Feb  2 21:48 e40d068d.jsonl
drwxr-xr-x 2 root root       2 Mar 23 19:37 e40d068d.jsonl.lock
-rw-r--r-- 1 root root 2252371 Mar 23 19:36 e40d068d.metadata.jsonl
drwxr-xr-x 2 root root       2 Mar 23 19:37 e40d068d.metadata.jsonl.lock
-rw-r--r-- 1 root root  113537 Mar 23 19:36 e40d068d.values.jsonl
drwxr-xr-x 2 root root       2 Mar 23 19:37 e40d068d.values.jsonl.lock
-rw-r--r-- 1 root root    1674 Sep 22  2022 key.pem
drwxr-xr-x 2 root root      16 Mar 23 17:31 logs
-rw-r--r-- 1 root root    1104 Mar 23 08:00 nodes.json
drwxr-xr-x 2 root root       3 Mar 23 08:03 sessions
-rw-r--r-- 1 root root    1177 Sep 22  2022 settings.json
drwxr-xr-x 2 root root       2 Sep 21  2022 snippets
-rw-r--r-- 1 root root     186 Sep 21  2022 users.json

/opt/zwave-js-ui/store/config:
total 9
drwxr-xr-x 2 root root  2 Sep 21  2022 .
drwxr-xr-x 9 root root 20 Mar 23 19:36 ..

/opt/zwave-js-ui/store/e40d068d.jsonl.lock:
total 9
drwxr-xr-x 2 root root  2 Mar 23 19:37 .
drwxr-xr-x 9 root root 20 Mar 23 19:36 ..

/opt/zwave-js-ui/store/e40d068d.metadata.jsonl.lock:
total 9
drwxr-xr-x 2 root root  2 Mar 23 19:37 .
drwxr-xr-x 9 root root 20 Mar 23 19:36 ..

/opt/zwave-js-ui/store/e40d068d.values.jsonl.lock:
total 9
drwxr-xr-x 2 root root  2 Mar 23 19:37 .
drwxr-xr-x 9 root root 20 Mar 23 19:36 ..

/opt/zwave-js-ui/store/logs:
total 948
drwxr-xr-x 2 root root     16 Mar 23 17:31 .
drwxr-xr-x 9 root root     20 Mar 23 19:36 ..
-rw-r--r-- 1 root root  62468 Nov 11 00:00 zwavejs_2022-11-10.log.gz
-rw-r--r-- 1 root root  40533 Jan 26 00:00 zwavejs_2023-01-25.log.gz
-rw-r--r-- 1 root root  76254 Feb 15 00:00 zwavejs_2023-02-14.log.gz
-rw-r--r-- 1 root root 128021 Feb 16 00:00 zwavejs_2023-02-15.log.gz
-rw-r--r-- 1 root root  72134 Mar 17 00:00 zwavejs_2023-03-16.log.gz
-rw-r--r-- 1 root root  60282 Mar 18 00:00 zwavejs_2023-03-17.log.gz
-rw-r--r-- 1 root root  82417 Mar 19 00:00 zwavejs_2023-03-18.log.gz
-rw-r--r-- 1 root root  35365 Mar 20 00:00 zwavejs_2023-03-19.log.gz
-rw-r--r-- 1 root root  68137 Mar 21 00:00 zwavejs_2023-03-20.log.gz
-rw-r--r-- 1 root root 109162 Mar 22 00:00 zwavejs_2023-03-21.log.gz
-rw-r--r-- 1 root root  44640 Mar 23 00:00 zwavejs_2023-03-22.log.gz
-rw-r--r-- 1 root root 822584 Mar 23 19:36 zwavejs_2023-03-23.log
lrwxrwxrwx 1 root root     22 Mar 23 17:31 zwavejs_current.log -> zwavejs_2023-03-23.log
-rw-r--r-- 1 root root   1918 Mar 23 00:00 zwavejs_logrotate.json

/opt/zwave-js-ui/store/sessions:
total 14
drwxr-xr-x 2 root root   3 Mar 23 08:03 .
drwxr-xr-x 9 root root  20 Mar 23 19:36 ..
-rw-r--r-- 1 root root 378 Mar 23 08:03 rL9f_9ppcjBo5MSLLAdOKAo32tO5oWEJ.json

/opt/zwave-js-ui/store/snippets:
total 9
drwxr-xr-x 2 root root  2 Sep 21  2022 .
drwxr-xr-x 9 root root 20 Mar 23 19:36 ..

[tteck]

I think I see the issue, working on it

[xijio]

FWIW I also had an issue with the home assistant update, should have mentioned that. The home assistant lxc wouldn't start he home assistant UX, I ran "sh UPDATE" from that lxc and told it to install the stable branch, that got it going again. Don't know if this is a red herring or if it's helpful but wanted to share in case it's useful information

[tteck]

Nope, it's working correctly. It shows that you have the new binary -rwxr-xr-x 1 root root 197612326 Mar 23 08:03 zwave-js-ui-linux (Mar 23)

[tteck]

Did you clear browser cache? Is Home Assistant still complaining?

[xijio]

I cleared cache and I'm still getting this in home assistant:

Retrying setup: Invalid server version: Z-Wave JS Server version (1.22.1) is incompatible. Update the Z-Wave JS Server to a version that supports at least api schema 26

[xijio]

It's weird because it the Z-Wave JS UI about tooltip shows it's running this version:

zwave-js-ui: 8.0.0
zwave-js: 10.2.0
home id: 3826058893
home hex: 0xe40d068d

8.0.0, according to the github release (https://github.com/zwave-js/zwave-js-ui/releases/tag/v8.0.0) is about 6 months old.

Also from the LXC commandline:

root@zwave-js-ui:/opt/zwave-js-ui# ./zwave-js-ui --version
2023-03-23 20:22:21.833 INFO APP: Version: 8.0.0
2023-03-23 20:22:21.834 INFO APP: Application path:/opt/zwave-js-ui
 
  ______  __          __                      _  _____     _    _ _____ 
 |___  /           / /                     | |/ ____|   | |  | |_   _|
    / /____   /  / /_ ___   _____         | | (___     | |  | | | |  
   / /______ /  / / _'   / / _     _   | |___     | |  | | | |  
  / /__        /  / (_| | V /  __/   | |__| |____) |   | |__| |_| |_ 
 /_____|      /  / __,_| _/ ___|    ____/|_____/     ____/|_____|
                                                            

It definitely seems like it's somehow pulling an older binary.

edit: oh it looks like there are two binaries, the LXC starts zwave-js-ui, but there is another, more up-to-date binary called zwave-js-ui-linux.

root@zwave-js-ui:/opt/zwave-js-ui# ps -aux|grep -i zwave
root         133  0.0 26.2 877200 137800 ?       Ssl  20:18   0:08 /opt/zwave-js-ui/zwave-js-ui
root         396  0.0  0.1   3244   708 pts/1    S+   20:25   0:00 grep -i zwave
root@zwave-js-ui:/opt/zwave-js-ui# file zwave-js-ui
zwave-js-ui: ELF 64-bit LSB executable, x86-64, version 1 (GNU/Linux), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=13036c1784f2698165c295b9f9f0b94e2cd8a0a4, for GNU/Linux 2.6.32, stripped
root@zwave-js-ui:/opt/zwave-js-ui# file zwave-js-ui-linux 
zwave-js-ui-linux: ELF 64-bit LSB executable, x86-64, version 1 (GNU/Linux), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=06d669b4b84f03ea5198d36584f920d542ca0ab9, for GNU/Linux 2.6.32, stripped

root@zwave-js-ui:/opt/zwave-js-ui# ./zwave-js-ui-linux --version
2023-03-23 20:24:08.581 INFO APP: Version: 8.11.0
2023-03-23 20:24:08.582 INFO APP: Application path:/opt/zwave-js-ui
  ______  __          __                      _  _____     _    _ _____ 
 |___  /  \ \        / /                     | |/ ____|   | |  | |_   _|
    / /____\ \  /\  / /_ ___   _____         | | (___     | |  | | | |  
   / /______\ \/  \/ / _' \ \ / / _ \    _   | |\___ \    | |  | | | |  
  / /__      \  /\  / (_| |\ V /  __/   | |__| |____) |   | |__| |_| |_ 
 /_____|      \/  \/ \__,_| \_/ \___|    \____/|_____/     \____/|_____|

[xijio]

I did:

root@zwave-js-ui:/opt/zwave-js-ui# mv zwave-js-ui zwave-js-ui.old
root@zwave-js-ui:/opt/zwave-js-ui# ln -s zwave-js-ui-linux zwave-js-ui
root@zwave-js-ui/opt/zwave-js-ui reboot

and now zwave-js-ui is reporting the newer version and home assistant is working.

zwave-js-ui: 8.11.0
zwave-js: 10.12.0
home id: 3826058893
home hex: 0xe40d068d

Let me know if this will break something with future update or if there is a better long term fix

[tteck]

I am unsure about what steps you'd take in the future. The \cp -R zwave-js-ui-linux /opt/zwave-js-ui command should overwrite the existing binary file with the same name in the /opt/zwave-js-ui directory. At least it has for me in the past.

[xijio]

I am unsure about what steps you'd take in the future. The \cp -R zwave-js-ui-linux /opt/zwave-js-ui command should overwrite the existing binary file with the same name in the /opt/zwave-js-ui directory. At least it has for me in the past.

I see that in the script, are there logs someplace where errors get output? I'm not sure why my old zwave-linux-js binary stuck around. I can manually copy zwave-js-ui-linux to zwave-js-ui instead of using a symlink but if the script works as intended it will just blow up my symlink with a duplicate anyway, so I doubt my fix will have an impact, I'm just concerned other people might run into this issue that the new version isn't getting copied for some reason

[tteck]

Just now saw your edits, what does your service file look like

service_path="/etc/systemd/system/zwave-js-ui.service"
echo "[Unit]
Description=zwave-js-ui
Wants=network-online.target
After=network-online.target
[Service]
User=root
WorkingDirectory=/opt/zwave-js-ui
ExecStart=/opt/zwave-js-ui/zwave-js-ui-linux
[Install]
WantedBy=multi-user.target" >$service_path

This is the zwave-js-ui.service that the script creates, did you use the script from this repo for installation?