Yes I was one of the victims but as you mentioned several times before, we where warned that this should be happening.
Thanxz Piet
Moderator: leecollings
Yes I was one of the victims but as you mentioned several times before, we where warned that this should be happening.
i run buster and a usb hub where the aeotech gen5 z-wave stick is mounted, in JS UI i now get all nodes but there are no names or no hardware names at all, and after about 20 seconds they all dissapear and after about 20 sec again they all appear, could it be the usb hub that is switching between the usb devices i have attached to the hub?
That's not correct: Anything that is seen as a serial-usb interface may cause numbering change of /dev/ttyACMx or /dev/ttyUSBx devices at boot. Even during an uptime, if the device disconnects (unreliable device/cable, some energy saving done switching off USB power not disabled, user unplug/replug to associate a new device with these battery sticks...) it's number will increase at reconnect.
You can still use default devices names (could change if you plug something more and reboot) or use persistent usb devices,so in short: if you cant use /dev/serial/by-id you are screwed and cant use the zwave anymore??
Other solutions will move to zwave-js at some point too. homeassistant already did. they didn't deprecate openZwave but not sure how long they will support it.if zwave is so hard to use now i am afraid this will reduce the members using domoticz a lot!that is a pitty.
Spot on. If zwavejs-ui ois working for users o f Domoticz and HASS is standard using it, this should work.
Problem solved. It was the flash with Win32DiskImager which had put the mess so I was not able to write on the SD Card.Michel13 wrote: ↑Thursday 04 January 2024 11:33 Hello,
I am trying to install ZWave-JS-UI on my RPI 3B following the wiki.
The problem starts with the installation of Docker-compose.
This process takes a huge time to complete (almost 1/2h !)
.
.
.
It looks like the installation is OK, but at the next step I have the following message :I did that twice with same result.Code: Select all
pi@raspberrypi:~ $ docker compose up -d -bash: docker : commande introuvable
Is there something wrong ? Any idea to solve it ?
Code: Select all
restart: always
Various reasons... If you are going to use docker anyway, it makes much more sense to use docker for other 'services' as well.
Updating a docker (if necessary... ) can be done by the executing the following command in the dockers folder (which you can place in a file in your /sbin folder so you can use it whereever needed)akamming wrote: ↑Sunday 07 January 2024 13:49 I understand, bit it is more difficult and also updating your systeem is more difficult. A simple sudo apt update && sudo apt upgrade -y won’t do the trick anymore… you have to upgrade each individual container as well
Anyway: not saying it is a bad idea, but since this thread is called the “easiest way to migrate” I Thought we can keep it simpler
Code: Select all
docker compose pull && docker compose up --force-recreate --build -d && docker image prune -f
Users browsing this forum: No registered users and 0 guests