ioBroker MQTT used with Zwave JS UI

[nesheimt]

Describe the bug
I want to connect and control the Zwave JS UI (stand-alone) using the MQTT Broker. The Zwave JS UI requires that a separeate get/set topic is used to write new values the the z-wave devices.

The MQTT-broker have such functinality(different topics for set/get), but I'm not able to write anything, seems like the Zwave JS UI do not accept the messages.

If I however manually create a /set topic for the topic comming from the Zwave JS UI (eg targetValue) the the targetValue.set is able to change the zwave device.

In MQTT-Explorer the messages comming from the ioBroker MQTT (apparently) looks the same, bur behaved different on the Zwave JS UI client.

Expected behavior
I would expect being able to use the ioBroker with the option "different topics for set/get" enabled to control the Zwave JS UI.

Screenshots & Logfiles
If applicable, add screenshots and logfiles to help explain your problem.

Versions:

• Adapter version: 6.1.2
• JS-Controller version: 6.0.11
• Node version: 20.18.0
• Operating system: Windows 11

Additional context

It works if I create an ioBroker MQTT broker (without different set/get topics) and create an MQTT client (with different topics to enable set/get). However, it would be convenient to use only one broker (I already have one set up).

The logfiles are:
SEPARATE.SETGET.DISABLED: Here I created the /set topic manually and controlled the z-wave device
SEPARATE SETGET ENABLED: Here I tried to control the z-wave device with the option "different topic for set/get enabled"

Debug mqtt SEPARATE SETGET DISABLED.txt
Debug mqtt SEPARATE SETGET ENABLED.txt

[nesheimt]

I'd like this to work, but it does not:
MQTT-broker(different topic for set/get enabled) <--> Zwave-JS-UI

However, this works:
MQTT-client(different topic for set/get enabled) <--> MQTT-broker(different topic for set/get disabled) <--> Zwave-JS-UI
but then I need two extra MQTT-instances, and an unecessarty long value chain (=more points of possible failures).

I don't see why the "direct connection" to Zwave JS UI does not work, so I'm thinking some kind of bug?

[nesheimt]

Hi @Apollon77
This post have been here for some time without any replies so I try to ping you since you are the first name on the developer list. Is there a bug here or is it jus the way it is?

[Apollon77]

I honestly do not use mqtt adapter deeply enough to have an answer directly and would need to check logs...

[nesheimt]

I honestly do not use mqtt adapter deeply enough to have an answer directly and would need to check logs...

I would be great to the to the bottom of this. I think that "the best z-wave integration" between ioBroker and a stand-alone Zwave JS UI using MQTT. The reason for this is that there are contineous improvements and this is always up to speed in Zwave JS UI. The zwave2 adapter(which probably would have been the best option) seems not to be prioritized due to more important tings.

A MQTT connection with the least number of "points of failures" is therefore important.