Clearing cookies seems to do the trick. Thanks waltervl!

Thx waltervl. Will give it a try. Keep you posted.

When logged in to Domoticz, I always get kicked out after a few minutes. I do experience this for a long time. Sometimes causes me to redo (scripting) work if I forget to press save every other minute or so. Of course we can live with it, but it is pretty annoying. I’ve read in a post of Waaren that ...

See https://docs.docker.com/config/contain ... matically/

Basically I checked the (current) Restart Policy for my running zwave-js-ui container docker inspect zwave-js-ui | grep -i restart -A 5 It was “unless-stopped”. I changed it to “always”: docker update zwave-js-ui --restart always Then rebooted my RPI to test. All came up now. Docker-compose.yml defin ...

Solution can be found here in case someone needs it: https://github.com/zwave-js/zwave-js-ui/issues/3646

I’m also not a docker expert but I basically followed all the instructions here https://www.domoticz.com/wiki/Zwave-JS-UI and of course started the zwavejsui-ui container manually with docker compose -d. The whole MQTT-, zwavejsui-ui-, Domoticz-package runs perfectly fine, but the thing is: when I n ...

Thanks for responding waltervl. Here the contents for zwavejs-ui: pi@raspberrypi:/opt/zwavejs-ui $ cat docker-compose.yml version: "3.7" services: zwave-js-ui: container_name: zwave-js-ui image: zwavejs/zwave-js-ui:latest restart: unless-stopped tty: true stop_signal: SIGINT environment: - SESSION ...

Question a bit in line with the previous one: I do have everything technically working with MQTT and ZWaveJS-UI containers. Happy with it solar. However after following the instructions, I do have a docker-compose.yaml file in both /opt/mosquitto and /opt/zwavejs-ui. When restarting my RPI (power up ...

Yes thanks, will sure do!

See https://github.com/zwave-js/zwave-js-ui/issues/3631 for the solution. Thanks to waltervl, mgugu and the github zwavejs-ui specialists.

Thanks waltervl and mgugu. Already did a clean install as my attempt upgrade Raspbian to Bookworm ruined my Pi-OS. Results after clean install
Were exactly alike. Will aks the Zwave-JS-UI specialists in their GitHub repository.

I ran some test with your suggestions: first I changed to '/dev/serial/by-id/usb-0658_0200-if00:/dev/ttyACM0' in docker-compose.yaml and restarted the zwavejs-ui container. Connected to the UI and changed Zwave Serial port settings to zwave serial port.png and SAVED :D . This resulted in Driver ...

Might my zStick Gen5 running firmware 1.0 need a firmware update ? (think 1.2 is the latest if I’m correct). Thanks for your responses sofar. Will consult the GitHub guys as well in the meantime.

I’m also having troubles to get the Aeon zwave gen5 going (or at least cannot get my ZWaveJS-UI to a stable run. It starts, I do see devices coming into the GUI, but after about a minute the full zwavejs-ui container restarts. And over and over again. I am on Buster. See https://www.domoticz.com/f ...

I’m pretty much stuck. Anyone any suggestions for a direction to look into? Hope someone can help me out. Otherwise I need to revert back to OZW… . Thanks in advance for your thoughts.

By the way: a "docker compose up" shows: root@raspberrypi:/opt/zwavejs-ui# docker compose up [+] Running 1/1 ✔ Container zwave-js-ui Recreated 0.4s Attaching to zwave-js-ui zwave-js-ui | 2024-02-27 21:04:24.357 INFO APP: Version: 9.9.0.09b107a zwave-js-ui | 2024-02-27 21:04:24.390 INFO APP: ...

Unfortunately still a looping container. Here a list of my Pi USB devices: pi@raspberrypi:~ $ ls /dev/serial/by-id -l total 0 lrwxrwxrwx 1 root root 13 Feb 23 22:36 usb-0658_0200-if00 -> ../../ttyACM0 lrwxrwxrwx 1 root root 13 Feb 23 22:36 usb-RFXCOM_RFXtrx433_A12WY8N-if00-port0 -> ../../ttyUSB0 So ...

Thanks Varazir and others. Am not able to answer the questions yet as I decided to upgrade to Bookworm in the meantime, but the upgrade ran into an error (libc6) and wacked my full raspbian (seems to be a known error. At least not to me. So I had to recover from an SD-card image. Luckily only one ...

Thanks. Got this: zwave-js-ui | # zwave-js-ui | # Fatal error in , line 0 zwave-js-ui | # unreachable code zwave-js-ui | # zwave-js-ui | # zwave-js-ui | # zwave-js-ui | #FailureMessage Object: 0x74007764 zwave-js-ui exited with code 0 Running Buster currently. Do you think I need to upgrade to ...