Domoticz

roblom wrote: Saturday 27 August 2022 15:18
[*] I also have Fibaro smoke detectors these are recognized and added by MQTT discovery but there are only two devices added for each detector.
- Air Temperature
- battery_islow
But in OZW I had several more, like heat switch, housing switch, fire alarm, etc. Especially the last one is quite mandatory for a smoke detector. Also the configuration settings are not fully loaded. Can I solve this and if yes how?
[/list]

Sarcas wrote:

roblom wrote: Saturday 27 August 2022 15:18
[*] I also have Fibaro smoke detectors these are recognized and added by MQTT discovery but there are only two devices added for each detector.
- Air Temperature
- battery_islow
But in OZW I had several more, like heat switch, housing switch, fire alarm, etc. Especially the last one is quite mandatory for a smoke detector. Also the configuration settings are not fully loaded. Can I solve this and if yes how?
[/list]

I seem to remember it took a long time (hours/days?) before all devices were complete.

enboer wrote: Tuesday 04 October 2022 23:14 I understand that I have to switch from OZW to the MQTT setup, sooner or later...

dobber wrote: Sunday 25 September 2022 19:59 Is the battery level visible in zwavejs2mqtt? I have one zwave fibaro door sensor and two zwave+ fibaro door sensors. On the "+" I get battery status, but not on the old version. If the battery level is not present in zwave2mqtt it is not a domoticz issue.

red59 wrote: Friday 07 October 2022 7:50

dobber wrote: Sunday 25 September 2022 19:59 Is the battery level visible in zwavejs2mqtt? I have one zwave fibaro door sensor and two zwave+ fibaro door sensors. On the "+" I get battery status, but not on the old version. If the battery level is not present in zwave2mqtt it is not a domoticz issue.

Hello,

Sorry for late reply. Yes battery level is visible in zwavejs2mqtt but never updated...2 weeks ago i have replaced a battery on a fibaro door sensor ans today battery level is still red 0%, even after full reinterview of the node.
I know it is not a domoticz issue but if someone has solved this problem that would be great to share.

JuanUil wrote: Wednesday 12 October 2022 19:55 Hi all,

since 2015 i am using Domoticz now.
For a long time everything worked well.
I have a lot of Z-wave devices.
Last months I see that especially on switching groups it is not working anymore
Domoticz says switch is off but lamp is still on a.s.o.
The WAF has dropped to zero.
So my plan is:
make a new install on a reserve pi4
switch to zwavejs2mqtt
and hope to be happy again.
I have read the complete topic now but since I am a complete noob on linux and all programming I was looking for a wiki to do the above.
Can somebody point into the right direction?

Thnx in advance
Jan

mgugu wrote: Thursday 13 October 2022 17:57 Check https://docs.docker.com/engine/install/ ... stinstall/ docker group

pi@Pi4-Nieuw:~ $ docker run --rm -it -p 8091:8091 -p 3000:3000 --device=/dev/ttyUSB-ZwaveJan/dev/zwave --mount source=zwave-js-ui,target=/usr/src/app/store zwavejs/zwave-js-ui:latest
docker: Error response from daemon: error gathering device information while adding custom device "/dev/ttyUSB-ZwaveJan/dev/zwave": not a directory.

harrykausl wrote: Friday 14 October 2022 7:54 I‘m still on OZW with version 14532. I have problems with timers on my heating thermostats, they seem to sleep and I have to do temperature changes several times. I think, the problem was not in the last stable, because since that something changed in updating database immediatley with new values. So I think its time to switch to zwave2mqtt.
OK so the question. Can I switch to zwave2mqtt without using docker (install everything directly on the pi)?

mgugu wrote: Friday 14 October 2022 0:27 This is another problem now.
Looks like your zwave controler "/dev/ttyUSB-ZwaveJan/dev/zwave" is not correctly referenced