Domoticz

OMG spend half the day to get Zwave-JS-UI running. Had an enormous amount of errors.
Finally got it running, tested 1 switch and working. So started updating all the names, took about 5 hours to complete.
Suddenly lots of errors dropped, switch not found, nothing was working anymore. Restarted the docker and it worked again, for several minutes and stopped again.
Returned back to Openzwave, can't leave it in an erroneous state for the evening/night.

how do you test?
disable domoticz
enable zwave-js-ui and see how stable it is from there
or did you do the import in domoticz and disabled zwave there

i thought i would load everything into zwave-js-ui and then change the zwave path to something none existent so i could run domoticz with openzwave and zwave-js-ui side by side but when you change the path the devices disappear

I have spent slot of time configuring all my z-wave devices in domoticz, and now its going to be removed?
Do Home Assistant use z-wave and aeotech usb stick, is it compatible with home Assistant ?
I need to replace domoticz with something else.

tjabas wrote: ↑Wednesday 21 December 2022 18:17 I have spent slot of time configuring all my z-wave devices in domoticz, and now its going to be removed?
Do Home Assistant use z-wave and aeotech usb stick, is it compatible with home Assistant ?
I need to replace domoticz with something else.

Why replace Domoticz ? It is still working and with a new update i "could" be the case Open Z-wave will be removed.
You can still use Zwave devices with ZWave-JS-UI in Domoticz
Or don't upgrade

But i need to run the new js-ui on a windows computer?

On the pc you are running Domoticz
But only when OZW will be depreciated. So you still have time

tjabas wrote: ↑Wednesday 21 December 2022 18:17 I have spent slot of time configuring all my z-wave devices in domoticz, and now its going to be removed?
Do Home Assistant use z-wave and aeotech usb stick, is it compatible with home Assistant ?
I need to replace domoticz with something else.

OpenZwave is software that communicates with your Zwave-Stick and Domoticz (and other domotica systems). But that software project stopped so we need other software to communicate with our Zwave Sticks. There is currently only one alternative: Zwave-JS. This is also used by other domotica systems.
So Zwave as a hardware protocol is not deleted only the communication software is changed from Openzwave to ZWave-JS-UI. No need to move away from Domoticz!
But as the software is changed you have to do something in Domoticz and on your Domoticz server. That is what this forum thread is about......

tjabas wrote: ↑Wednesday 21 December 2022 18:36 But i need to run the new js-ui on a windows computer?

Read the wiki https://www.domoticz.com/wiki/Zwave-JS-UI

Thanks for your answers, so i need to buy a new z-wave 700 stick, and re-pair all z-wave devices again?

No. Just install Zwave-JS-UI and configure it.
See the wiki link

madpatrick wrote: ↑Wednesday 21 December 2022 18:59 No. Just install Zwave-JS-UI and configure it.
See the wiki link

So no need to re-pair all devices?

tjabas wrote: ↑Wednesday 21 December 2022 19:03

madpatrick wrote: ↑Wednesday 21 December 2022 18:59 No. Just install Zwave-JS-UI and configure it.
See the wiki link

So no need to re-pair all devices?

No, please read the wiki section Migrating from OpenZwave

Another day, another time to continue...
Unfortunately the same problem as yesterday.
This is what I did:
install zwave-js-ui in docker
configured zwave-js-ui to use mqtt prefix domoticz (as configured in domoticz MQTT autodiscover hardware).
disable the openzwave hardware

All devices are added to the database, removed devices are re-added.
Test of switching is working, see logfile: Busy preparing the update of IDX numbers in pass2php and renaming all created devices.
After some time the switch isn't found anymore: New updates are also no longer received in domoticz. They do appear in MQTT Explorer.

that's weird
you have MQTT on, did you switch off the regular MQTT gateway?

and no localhost but regular ip address of the mqtt server

I only have this as MQTT hardware:
MQTT Auto Discovery Client Gateway with LAN interface 127.0.0.1

Because zwave-js runs in docker I there put 192.168.2.2 as ip address, the real address of my domoticz server. On 127.0.0.1 it can't connect to Mosquitto.

And the switch is gone? Or the renaming triggered something?

I have 2 aeotech gen5 sticks, one as a backup, i recently started experimenting with home Assistant , im thinking of installing z-wave js on that one, just to make some tests, but what will happen if i run both sticks at the same time, both in domoticz and home Assistant, will this work or should i turn of domoticz while i play with Hass? Could this tests fuck up the z-wave installation on domoticz?

Hmmm, needs more investigating on my installation. Has been running all night without problems. I started working in zwave-js-ui, updating location etc and all of the sudden it stopped. Had to restart domoticz and the zwave-js docker to get it back. Will try to pin down when exactly it happens.

Addition: I see 2 problems. One is that the updates no longer arrive thru the MQTT autodiscover hardware and a second one is the switch not found error.

From my experience, contrary to what is suggested in wiki configuration screenshot, retain flag MUST be set to ON.
This allows the broker to keep in memory the config messages which are necessary each time domoticz is restarted.
If you need to remove definitely devices from domoticz (for example in case you remove a zwave node), you have to remove the corresponding config messages, simply by publishing "" at the config message topic (with MQTT explorer for example).

Could you post a screenshot with all settings from zwave-js-ui please?
Lots of confusing settings and I don't know what to set.