No new devices in Domoticz

[Marmachine]

I am succesfull in moving to Zwave-JS-UI so far...
Until today i've had my Aeotec Z-stick 5G integrated with Domoticz, now i see my nodes in MQTT Explorer, so far so good.
Now i am expecting new devices to popup in Domoticz, but they don't.
I have checked configuration, but i don't see what I might have missed.
Ohh... and yes i have checked "accept new hardware" setting

[robertsLando]

Did you enabled mqtt discovery?

[Marmachine]

Where do i do that? In Domoticz i don't see that option... do i first need an update for that? (i'm on 2023.1)

If you mean the setting in Z-Wave JS UI settings, under Home Assistant, that's on yes. (however, i am on Domoticz)

[akamming]

and did you enter the actual IP adress (so no localhost or 127.0.0.1) as the host adress for the MQTT server?

[Marmachine]

Yes, i will try to add some more info later today.

[FriedlNetDZ]

Please give me some more information about your settings in Z-Wave JS UI and in Domoticz. I had exactly the same error pattern.

[kpine]

Did you re-create the container after changing the yaml to use device /dev/serial/by-id/usb-0658_0200-if00:/dev/zwave?

[Marmachine]

Here's what i have in OpenZwave Control Panel

[kpine]

Why are you using OpenZwave Control Panel? You can't run both software at the same time.

[Marmachine]

Oh, okay... i need to run docker compose up -d again? First docker compose down?

[kpine]

Seems you got it already, but yes, run docker compose up -d anytime you change the compose file.

[Marmachine]

Well... okay, devices are back, most remain undefined but i see their messages in MQTT Explorer
Now how would i get them added as new devices into Domoticz?

[kpine]

okay, devices are back, most remain undefined

I'd suggest posting your entire docker compose file. It looks like you've mis-configured the store volume as well.

Although, they look like battery devices, so perhaps not. In that case, you will need to manually wake them up to perform interviews for the first time.

[Marmachine]

I have three sitting right at my desk here... actually one (NodeID 003) is powered by USB (its an Aeotec Multisensor), two others (are some chineese brand) and battery powered. They blink and send a message on motion through MQTT, so their basic functionality seems okay. I was expecting the powered Aeotec to announce itself, but generally i'll look into waking up all of them.

So i guess the old configuration (like i showed from OpenZwave Control Panel) isn't somehow re-used then i guess?

Here's my docker compose file:

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_SECRET=mySecretSession
      - TZ=Europe/Amsterdam
    devices:
      - '/dev/serial/by-id/usb-0658_0200-if00:/dev/zwave'
    volumes:
      - ./store:/usr/src/app/store
    ports:
      - "8091:8091" # port for web interface
      - "3000:3000" # port for Z-Wave JS websocket server

[kpine]

Compose file looks good. You don't need port 3000 though if you are only using MQTT, that is for the Home Assistant Z-Wave integration.

You must have included node 3 on battery power? Because it is acting like a battery device. You can't include on battery power then add USB power later, you won't get mains-powered functionality.

The battery devices might not function properly until they are interviewed.

[Marmachine]

Okay, great! All there now:

So now how to get these as new devices in Domoticz? ("accept new hardware" is ON)

[kpine]

So now how to get these as new devices in Domoticz? ("accept new hardware" is ON)

Domoticz has it's own documentation, did you check there? https://www.domoticz.com/wiki/Zwave-JS-UI#Installing_ZWaveJS-UI

Probably better to ask for additional help in the Domoticz support forums if you still have issues with integrating it.

[FriedlNetDZ]

Is it working now or do you have problems with domoticz?

[Marmachine]

The previous was very helpfull to understand and get my nodes in MQTT.
I haven't found out how to get my devices in Domoticz... no new devices have been added, old devices have disapeared.
Already had hardware configured in Domoticz: MQTT Client Gateway > MQTT Auto Discovery Client Gateway with LAN interface
So something doesn't seem to be working right ...?

[akamming]

best way to troubleshoot is the following order:
A) try to get the devices visible in ZWAVE JS UI --> most common cause why not visible: Something wrong with configured serial port for ZWAVE gateway
B) download MQTT explorer (https://mqtt-explorer.com/) en connect to your mqtt server and check if you can see the discovery topic. If you cannot connect: Troubleshoot your mqtt server until you can connect to your mqtt server. If you can connect, but do no see the devices: Check you mqtt settings zwave js ui until you see them in MQTT explorer
C) Check if devices are visibile in domoticz. If you cannot see them:

• check if you domoticz client connects to mqtt server (if it does not, check your mqtt settin
• if and if does: Check if autodiscovery is enabled in both domoticz and zwave js ui and if the discovery topic is correctly entered in domoticz setup (should be the same as the discovery topic in zwave js ui)

good luck!

[Marmachine]

Yeah, all is check, but no devices.
Through Node-red i can send MQTT messages to toggle a (virtual) device on and off in Domoticz.
Node-red is triggered on motion messages from nodes that publish through ZWAVE JS UI to MQTT
So i see the Nodes in MQTT (also confirmed through MQTT Explorer) and Domoticz is connected to the broker since i can toggle a switch through MQTT...
I have found a wiki page, https://www.domoticz.com/wiki/MQTT#Add_hardware_.22MQTT_Auto_Discovery_Client_Gateway.22 but it didn't bring any news until my eye catched this detail... MQTT Autodiscovery Setup From 2023.1 beta

So i guess, since i'm not on beta, this is never going to work with my stable version: 2023.1 and so one needs to update!