- No there is no dependency on mosquitto version, this is just a message broker
- You can add a second MQTT gateway. Or even a third or a fourth per usage

Moderator: leecollings
Tried another time today and found something interesting about this.waltervl wrote: ↑Tuesday 03 January 2023 16:06This is issue seems to be related to this https://github.com/domoticz/domoticz/issues/5179Egregius wrote: ↑Tuesday 03 January 2023 14:53 I have one small issue with zwave-js-ui instead of openzwave.
A lot of my dimmers don't respect the soft dimming time set to the minimum and use the factory default 3 sec. Because of that a lot of lights react slow.
Just tested by restoring an old snapshot of my domoticz server and the lights all switch on instantly. With zwavejs that takes 3 seconds.
Is what JackD suggested everything in one container or one “image” not possible? I think that this suggestion make life for some off us more easier.JackD wrote: ↑Monday 07 November 2022 19:30 After almost a year of not updating Domoticz, and the fear of the loss of Open Z-wave support in future releases, I updated Domoticz yesterday to beta14599. And can report that in beta14599 the open z-wave is still functional, but in the log there is a note that tells it is depreciated.
Perhaps make a super Domoticz docker container which has it all, Domoticz, ZWave-JS-UI, Mosquitto and everything else you need, including a very detailed and up to date step by step installation manual. Then you again have the "one stop shop" and would make it a lot easier for us not IT specialists. Just a suggestion, don't know it this is technically possible
Sorry for the bit of nagging, of course I appreciate all you who spent there time in building and maintaining Domoticz.
Benneton wrote: ↑Monday 13 March 2023 20:37 I am at the same stage as you are, more or less ready to take the plunge in the deep end...
My guess is that current devices will have to be migrated to the new ID's found by Zwave-JS-UI.
Done via the replace option on devices. At least that is what I had in mind to do.
Yes, that much is clear, the question is, will I be able to identify the new devices.Benneton wrote: ↑Monday 13 March 2023 20:37 I am at the same stage as you are, more or less ready to take the plunge in the deep end...
My guess is that current devices will have to be migrated to the new ID's found by Zwave-JS-UI.
Done via the replace option on devices. At least that is what I had in mind to do.
Code: Select all
version: '3.3'
services:
domoticz:
image: domoticz/domoticz:stable
container_name: domoticz
restart: unless-stopped
# Pass devices to container
devices:
- "/dev/serial/by-id/usb-0658_0200-if00-port0:/dev/ttyACM0"
ports:
- "8080:8080"
volumes:
- ./config:/opt/domoticz/userdata
environment:
- TZ=Europe/Amsterdam
#- LOG_PATH=/opt/domoticz/userdata/domoticz.log
Change your docker compose.yml to dev/serial/by-id/usb-0658_0200-if00:/dev/ttyACM0.Dave47 wrote: ↑Friday 17 March 2023 7:46 Hi. We have a problem from the beginning.
First we install docker compose
docker composer up -d the output is:Code: Select all
version: '3.3' services: domoticz: image: domoticz/domoticz:stable container_name: domoticz restart: unless-stopped # Pass devices to container devices: - "/dev/serial/by-id/usb-0658_0200-if00-port0:/dev/ttyACM0" ports: - "8080:8080" volumes: - ./config:/opt/domoticz/userdata environment: - TZ=Europe/Amsterdam #- LOG_PATH=/opt/domoticz/userdata/domoticz.log
pi@raspberrypi:/opt/domoticz $ sudo docker compose up -d
yaml: line 8: did not find expected key
pi@raspberrypi:/opt/domoticz $
We have pair all devices in secure mode. Is that maybe the problem.
How can we fix this?
Possible to write a key rule in version 3.3 and how can we do that?
What will be the right path for device if:
pi@raspberrypi:/opt/domoticz $ ls -al /dev/serial/by-id
total 0
drwxr-xr-x 2 root root 60 Mar 15 18:30 .
drwxr-xr-x 4 root root 80 Mar 15 18:30 ..
lrwxrwxrwx 1 root root 13 Mar 15 18:30 usb-0658_0200-if00 -> ../../ttyACM0
Users browsing this forum: No registered users and 1 guest