Domoticz

no this one doesn't work like that I took the device to the stick

BartSr wrote: ↑Sunday 10 March 2024 23:03 prefix to be changed both in zwavejs as well as domoticz hardwarepage

You need to set the prefix under 'dicovery prefix' in the 'homeassistant' settings on Zwave js ui

bvdf0251 wrote: ↑Saturday 16 March 2024 22:47

BartSr wrote: ↑Sunday 10 March 2024 23:03 prefix to be changed both in zwavejs as well as domoticz hardwarepage

You need to set the prefix under 'dicovery prefix' in the 'homeassistant' settings on Zwave js ui

To what? I've set everything to zwavejs

Discovery prefix (default homeassistant) in Zwave-JS-UI cannot be the same as the normal prefix (default zwave). So they cannot be all Zwavejs.... So check your settings in Zwave-JS-UI that you not made them the same.

The discovery prefix of Zwave-JS-UI (default homeassistant) should be filled in Domoticz MQTT auto discover configuration.

I've set it to 'domoticz' can be anything you like.

Make sure to set domoticz to allow new devices and hit save in Zwave js ui

Also Domoticz is not a very smart choice as it is the same as the default Domoticz topic when using the Domoticz MQTT hardware gateway. Better leave it all just default....

@waltervl
I should not advise to keep all prefix to be homeassistant.
In case you are using AD for different sources such as zwave, zigbee, otgw etc. it makes it difficult to see relevant data in mqtt explorer.

Yes, so for users not so knowledgable and only using Zwave-JS-UI default settings is the best to avoid situations like this.
If you add Zigbee2MQTT you can choose to change the Discovery prefix settings in Zigbee2MQTT or Zwave-js-ui. But is is not needed. And only change the Discovery prefix as both platforms already use different prefixes for their own topics by default (zigbee2mqtt and zwave).

@waltervl
for the records. prefix zwavejs works like a charm whereas just zwave don't.

BartSr wrote: ↑Monday 18 March 2024 13:36 @waltervl
for the records. prefix zwavejs works like a charm whereas just zwave don't.

Are you talking on the zwave-js-ui MQTT prefix or the zwave-js-ui Discovery prefix?
There should be no difference between zwave or zwavejs for MQTT prefix unless you use prefix zwave also for something else in your MQTT environment.

when I was in process of getting the zwavejs-ui the mqtt prefix zwave (aof course same in domoticz) did not work.
After changing into zwavejs it did.

BartSr wrote: ↑Monday 18 March 2024 18:04 when I was in process of getting the zwavejs-ui the mqtt prefix zwave (aof course same in domoticz) did not work.
After changing into zwavejs it did.

Again you are mixing up things. In Domoticz you should enter the Zwave-JS-UI Discovery prefix (default: homeassistant).

well of course you shouldnot .
once in zwavejs-ui you set zwavejs as prefix in domoticz it has to be same

Guys, please take this offline as this doesn't contribute to the current issue which is with ZWAVEJS2MQTT & the ZWAVEME usb stick, which currently doesn't allow to join the devices again to it!
You seem to be agreeing without knowing it... so PM is a great tool for that!

@Keef
Do you have more info about type of zwave stick apart from zwaveme??

Something like this?

That seems about right, are you able to see the devices in Zwave js Anyway? And control them from there?

I don't get that from what's currently posted.

I can only see my zwave stick and I can't add anything

Did you look for support on this issue on the ZwaveJS2Mqtt github site?
What have you done in an effort to try and debug this?
Did you look at the Logfiles in ZwaveJS2Mqtt for errors?

Yeah, first it needs to work on Zwave-JS, otherwise it will never work on Domoticz.