zwave JS-UI newby: extremly slow and lots of messages

[renerene]

finally made the jump today and switched from openZwave to Z-wave JS UI, by following https://www.domoticz.com/wiki/Zwave-JS-UI

Problem: new zwave MQTT devices are very slow, takes several seconds

Also:
2) all devices are refreshed each second in MQTT explorer, leading to a LOT of messages. Screenshot shows status after ca 30 minutes
3) allthough "disable MQTT gateway" is acitvated, messages keep blinking/updating in MQTT Explorer
4) nodeID_xx and the renamed version are both shown in MQTT explorer
5) domoticz log is loaded with 'dicovered' messages


Would be great if someone could help. WAF is an issue at the moment

[roblom]

Just to be sure; did you press on save on the bottom right of the page?

[renerene]

Just to be sure; did you press on save on the bottom right of the page?

Ah, i did not. Issue 3) is solved

Issue 4) is also solved after reboot.
New information: switch speed is normal (fast) but domoticz status update takes about 3 seconds

[renerene]

6) DzVents scripts can not switch the new devices.

(and domoticz updates still slow.)

Do i need to use 'store' button under Home Assistant menu?

[mgugu]

No, store has only to be used if you change something in Hass Json Device

[mgugu]

6) DzVents scripts can not switch the new devices.

For some reason, after domoticz is restarted, some devices (not all) are not synchronized (You can check that from domoticz panel). What I do is to activate/desctivate the device from zwave-js-ui panel and then it is OK until the next domoticz restart. Of course retain is set on in zwave panel.

[renerene]

For some reason, after domoticz is restarted, some devices (not all) are not synchronized (You can check that from domoticz panel). What I do is to activate/desctivate the device from zwave-js-ui panel and then it is OK until the next domoticz restart. Of course retain is set on in zwave panel.

Please tell me more. How can (de)activeate devices?
Are my settings ok?

[mgugu]

Go to the device panel, select the non working device, then the non working function. For example for a switch click true/false:

[renerene]

Go to the device panel, select the non working device, then the non working function. For example for a switch click true/false:

controlling the switches this way works fast and reliable.
In Domoticz however, switch reactions are slow and bad responsive

[BartSr]

Since a few days ago I also use ZwaveJs-UI. As I also faced some problems I started a chat with 'the ZwaveJs team'. It appears the ZwaveJs version which comes with docker is very old. Maybe update to newer version might help. I have to investigate how to upgrade. I presume, due to the dockercontainer it's impossible to update from within ZwaveJs-UI.

[waltervl]

Since a few days ago I also use ZwaveJs-UI. As I also faced some problems I started a chat with 'the ZwaveJs team'. It appears the ZwaveJs version which comes with docker is very old. Maybe update to newer version might help. I have to investigate how to upgrade. I presume, due to the dockercontainer it's impossible to update from within ZwaveJs-UI.

Where is your chat with the ZwaveJS team?

[BartSr]

I probably used wrong naming.
have a look at issues:
graphic don't show 'neighbour'lines #3599
Don't know how to reproduce an URL

[akamming]

Since a few days ago I also use ZwaveJs-UI. As I also faced some problems I started a chat with 'the ZwaveJs team'. It appears the ZwaveJs version which comes with docker is very old. Maybe update to newer version might help. I have to investigate how to upgrade. I presume, due to the dockercontainer it's impossible to update from within ZwaveJs-UI.

i don't understand what you are saying. If you use the instructions on the wiki, you get the latest zwave js ui

anyway: if you used these instruction, the following command will update your docker image to the latest:

docker compose pull (pulls latest docker image)
docker compose down (shutsdown and removes current containter)
docker compose up -d (recreates and starts container on latest docker image)
docker system prune -f (removes old docker image)

[BartSr]

Well, for sure I carefully followed the Wiki instructions. But with some help from Linux expert I managed to get latest version.

[waltervl]

This is no Linux knowledge but Docker knowledge.....

[BartSr]

IMHO you need to know the LINUX commands to control the docker containers.
A Linux-expert was required to get a quick result.

[waltervl]

Again, Linux has nothing to do with docker. You need docker commands. Docker is just an application you install (on Linux or windows or whatever)

[BartSr]

Hi Walter,

For me every command to control something from Linux commandline is a LINUX command.
But...
As the commands I used all were like docker blablabla you consider these as docker commands?
In that case I am fully with you.

But my LINUX expert was able to instruct me
For the records how I got the newest ZwaveJS version in docker:

docker-compose stop
docker-compose rm -f
docker-compose pull
docker-compose up -d

But maybe there are more ways to get same result but for me this got me the desired ZwaveJs version.
Actually :
ZwaveJs-UI 9.8.3.3
ZwaveJs 12.4.3

Hopefully we have a bright sky again

[waltervl]

Yes indeed, those are docker commands.
And dependent on your docker installation it could also be (remove the '-')
docker compose stop
docker compose rm -f
docker compose pull
docker compose up -d

If you google for 'update docker compose container' you will find a lot of instructions like https://www.redswitches.com/blog/how-to ... ontainers/